fraction

i got an issue with jit.anim.node which refuses to take the position [0 1 0], or [0 -1 0] on load when it has @tripod 1 set. It would take any other position on the same load, but 1 or -1 on Y if X is set to 0 seems to generate an initialization issue.

i made this example to compare with a jit.gl.text and another one with jit.gl.node attached to it

comment

loadbang

message

jit.gl.camera

jit.anim.drive

jit.anim.node

jit.gl.text3d

jit.gl.node

jit.world

Is that a normal behavior ? is there anything that can be done? i tried a delay on the loadbang, but the necessary delay time to have it working seems unreasonable to me (>500)

Hi Rob,
i got an issue with jit.anim.node which refuses to take the position [0 1 0], or [0 -1 0] on load when it has @tripod 1 set. It would take any other position on the same load, but 1 or -1 on Y if X is set to 0 seems to generate an initialization issue.
i made this example to compare with a jit.gl.text and another one  with jit.gl.node attached to it


Is that a normal behavior ? is there anything that can be done?  i tried a delay on the loadbang, but the necessary delay time to have it working seems unreasonable to me (>500)
thx!


Hi Rob,
i got an issue with jit.anim.node which refuses to take the position [0 1 0], or [0 -1 0] on load when it has @tripod 1 set. It woul

anim-node-refuses-to-take-pos-0-1-0-on-load

I complete : i tried to put @tripod 1 as message after object initialization instead, but it leads to the same result. 

Using a delay in this case for this message, requires also a time of 200 ms, which is a bit better, but still a bit annoying :)

I complete : i tried to put @tripod 1 as message after object initialization instead, but it leads to the same result. 
Using a delay in this case for this message, requires also a time of 200 ms, which is a bit better, but still a bit annoying :)

never mind, i m going to insert a 200ms delay, but i d be curious to know if that's an expected behavior or something that would need to be improved in the object working

yeah there is some complex interaction between lookat, tripod, and the scene hierarchy that takes a couple frames to get right. I would not use delay, but simply count the frames to let a couple pass and after these initial frames pass, send the direction constraining messages.

see if the following trick is helpful in your situation:

in my case i dont think i can use that one, because once can create abstractions with such combination of anim.node and jit.gl.text at different moments, which are not synch to the jit.world at opening.

i was looking for a solution synch to the abstraction loadbang. So if i decide to use that way in conjonction with the frame indication, i ll need to report the frame when occurs the bang, and apply counter. It gets a bit complicated i find

thx rob. good to know that trick, 
in my case i dont think i can use that one, because once can create abstractions with such combination of anim.node and jit.gl.text at different moments, which are not synch to the jit.world at opening. 

 i was  looking for a solution synch to the abstraction loadbang. So if i decide to use that way in conjonction with the frame indication, i ll need to report the frame when occurs the bang, and apply counter. It gets a bit complicated i find

anim.node refuses to take pos 0 1 0 on load