during the work on my last projects i encountered some serious things:
IOBox (Value Advanced):
if set to have multiple rows with different values, undo don’t work correctly
if one changes the value by rightclick+drag and accidently presses other mouse buttons, vvvv will stay in this state forever. the mouse cursor disapears if its somewhere over a vvvv window and no user input will have any effect -> terminate process
Shader:
if there is the same shader multiple times in a patch and different techniques are used, the techniques are set wrong after save+reopen, soemtimes to (nil)
related, changing the shader technique with Ord2Enum is buggy
after getting an error in shader code, the ontop window changes magically. no visible changes on the windows, but keyboard commands are sent to the patch window instead to the shader code editor. so i often delete the whole shader by hitting backspace, or i was not able to write new code…
if one changes the value by rightclick+drag and accidently presses other mouse buttons, vvvv will stay in this state forever. the mouse cursor disapears if its somewhere over a vvvv window and no user input will have any effect -> terminate process
fixed that one
concerning the shader problems, we seem to have 3 serious without reproducible cases:
problems with shader techniques not being loaded correctly
problems selecting techniques with ord2enum
shadereditor fokus problem: shortcuts being sent to the patch even when editor has focus
i’d like to invite everybody who is interested in getting those fixed to try to find a way to demonstrate those bugs. i mean no guessing, but real patches and step-by-step instructions on how to break them. thansk a very lot.
you know christmas is coming up and you ought to behave well if you still believe…
The trouble with the shader techniques and enums, is sometimes they work fine, and some times they dont! I cant find a way to make them happen, but I nearly always have them happen when I really dont need them too!
But I will see if I can create one the breaks to order!
Cat
I have wonderered whether it only happens with shaders in subpatches, similar to the problem I have with random(value) where if the subpath isnt open the node returns the same number, when it is it functions normally, but again not in every patch! But maybe the techniques dont initialise correctly when hidden?
Perhaps the problem is with directx9, as it deals with shaders?
The problem for me has certainly been occuring more on patches where I have more then one instance of the same shader. I’ll certainly try to reproduce the problem reliably.
Joreg, have you encountered the problem at all? Perhaps hardware has a hand in this? It occurs on my 6600gt and my 7900gt cards, and on my athlon xp3200 and my x2 4400 pc’s.
nono. we can’t blame dx9 nor some hardware for this. it is somewhere in updating the enums. it should be reproducible by doing things in a certain sequence…hmm
i think i can reproduce the shader editor window focus problem, just make an error in the shader code, the red line appears and then backspace, c+p, etc. are magically focused to the patch window…
can you really reproduce that, toni? i can’t. i tried several times now, but only making an error in shader code does not cause the focus problem for me.
Ok enum problem, I had a thought, is everyone who experiences it, keeping the fx files in a folder with the patch or in the effects folder?
Im wondering because of the possibly related boygroup fx relative path problem. I’ve just moved my fx to the effects folder, and so far the enums work, but being a spasmodic failure, only time will tell!
Anyone else report?
Also the other problem I’ve had with xfiles not loading when you open the patch and there not connected I’ve solved the same way a preloading textures by connecting and scaling a seperate node to 0, just in case anyone else has that too!
nothing special, as a former vvvv co-developer, i am one of the happy ones who got a vvvv svn acount for the source. sceenshots 3003 and 3004 are from a shader coding night…
