[jitter] Bug (?) with jit.gl.slab and @automatic 0
vade
doktorp at mac.com
Wed Jan 9 14:56:03 MST 2008
- Previous message: [jitter] Sharing is Fun [ was re: slab bug]
- Next message: [jitter] Announce: Cyclops 1.3.2 for Mac OSX + Windows
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
You are totally correct - a right to left bug - my god, staring at that forever it just was invisible to me. Ive added a different delay method, now it seems to work. Thanks, ugh, n00b error! :) Im glad I added that (?) to my bug report :D Thanks again, On Jan 9, 2008, at 4:28 PM, Joshua Kit Clayton wrote: > Wrong. Perhaps you are misunderstanding what the bang message does. > It renders the slab with the current input textures, which in your > patch are *both* the same frame. Please look at your trigger logic > and think carefully about what the right input is and when--i.e. it > sets the left texture, then immediately sets the right texture, so > they are only different frames for the duration *between* the two > list outputs of your trigger object. This works with the gate > closed, since it is the first list output from your trigger which > causes the slab to render. However, when you are banging from your > gate, they are now the same frame. Make sense?
- Previous message: [jitter] Sharing is Fun [ was re: slab bug]
- Next message: [jitter] Announce: Cyclops 1.3.2 for Mac OSX + Windows
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
