Moho Forum

I cannot promise nothing but when I have enough time, maybe, I'll take a look...

synthsin75 wrote:Would there be anyway to maybe find the points or bones that are causing these kinds of errors? Or maybe even make the lua console print a selected bone/point's internal ID? If I could do this then I could compare changes to see if they'll still work. (I'm assuming that these scripts reference the internal ID)

synthsin75 wrote:

Code: Select all

...AS\scripts\3Dgrid.lua:146: attempt to index local 'BRy' (a nil value) 

That would be awesome. I'm not sure though if seeing the internal info would tell me which points/bones are the problem. But anything is worth a try.

3Dgrid.lua but which version? I assume you're using version 10?.

...AS\scripts\3Dgrid11.lua:112: attempt to concatenate local 'tname' (a table value) 

The problem is that if I make a lot of user error debuging then the script does useless things all the time and performance goes down that now is too low.

Sorry for forget the "then" thing but I'm so lazy and didn't check out the script. It would be catched once you load it first time at parsing time.

The best thing to avoid problems is give named groups to the points you need to locally rig BEFORE duplicate the layer. Then once you make the side view it would be very easy select the correct points for the automatic 3Drig.

			ptbone.fLength = diag:Mag()/GE_front3Drig3_2.ptscale
rxbone.fLength = diag:Mag()/GE_front3Drig3_2.ptscale

Genete wrote:The best thing to avoid problems is give named groups to the points you need to locally rig BEFORE duplicate the layer. Then once you make the side view it would be very easy select the correct points for the automatic 3Drig.

The lastest trouble is finding the right bones in a complex model. Is there anyway to reduce the size of the generated bones any more than I can already? What is the initial size (10 in the generation pop-up) determined by?

Code: Select all

ptbone.fLength = diag:Mag()/GE_front3Drig3_2.ptscale
rxbone.fLength = diag:Mag()/GE_front3Drig3_2.ptscale

Lines 282 & 291 seem to be the scale in the 3Drig front 3.2 script. Bone length equals point scale? Is that what it says? How does it determine point scale?

Perhaps if I change the 'recurring' value of ptscale?

function GE_front3Drig3_2Dialog:OnValidate()
	local b = true
	if (not self:Validate(self.ptscale, 5, 30)) then  -- those values (5, 30) can be customized
		b = false
	end
	return b
end

GE_front3Drig3_2.ptscale = 10 -- dividing scale for the pt, Rx and Ry bones

ptbone.fLength = diag:Mag()/GE_front3Drig3_2.ptscale

rxbone.fLength = diag:Mag()/GE_front3Drig3_2.ptscale

		mesh:SelectedBounds(min,max)
		diag = max - min
		if (diag:Mag() == 0) then diag.x = 0.5 end

-- ***************************************************

-- Magnitude of the .pt bone in relation to the diagonal
-- of the selected points boundary.
-- a value of ptscale = 10 is sane 1/10 of the diagonal
-- beyond 30 could be insane.

-- ***************************************************

ptscale = 10

synthsin75 wrote:Thank you sooo much, Genete!!!

I actually think I understood all of your explaination. It's really too bad that our script writers don't have time to do a scripting tutorial. A section by section break down of what the script does is very educational.

I won't ask for a scripting tutorial though. I'm more than happy to get these little hints now and then.

I was very surprised to see that I had guessed right about the bone length being related to the size (spread) of the selected points.

[Let me just make sure I've got this. To change the default dividing factor for bone length in both the front and side scripts, all I have to do is change the 'ptscale=' value?

And to change the input range for this, I just change the values before the note 'those values (5,30) can be customized'?

Thanks a lot!!