Why does this simple patch cause both v and my whole computer to stagger?

its only running my i7 at 10%, and im getting 18fps and my whole computer is lagging. I know v doesnt use my gpu, and for these cheesy graphics it shouldnt be staggering anyways. The only problem i can see is the scale X and Y has a spread of 116 but even resetting the whole node doesnt change it, and why would v cause my whole computer to lag anyways, the last time i had a lagging program affect my system was in the days of windows xp.

test.v4p (21.1 kB)

beware of your spreadcounts!
your Camera is quite heavily spreaded (which doesn’t make sense in your case). remove those spreads and you’re back at full speed.

thanks for the reply, i removed the camera spreads but it still staggers and it causes my whole computer to really bad. It will go 30fps when the geometry is farther fromt he camera but when i comes closer it drops to 12, its really bad, plz help

test.v4p (20.0 kB)

you forgot one.
hint: Distortion

oh, setspread wont let me connect to that one, is there a better way tro control the number of spreads without resetting entire pin/nodes?

hm…don’t quite get that question…could it be that you’re still missing some basics? please take your time and check the tutorials
patching is even more fun when you no longer randomly connect pins but actually know what you’re doing…

Welcome back ;)

The pins have a spread marked in parentheses, but when i open up inspektor it doesnt show this, and i cant manipulate the spreads indepedently. Using a node like setSpread will reset the value of the pin as well as the spread, and it doesnt really help if i just want to change the spread number. The tutorials dont cover this.

hard to understand what you’re talking about. please try to use more words when describing your problem.

you cant say things like: “the pins have a spread marked…” and hope that anyone understands what you mean. pins have names. use those names, when talking about “the” pins.

but it seems you didn’t understand my hint either. so here are some more words:
the Distortion on the Camera is a node-pin. node-connections behave a bit different than all other connections in a sense that they do not leave values in the input-pins when the connection is removed. so removing the node-connection the transformation on Distortion input is set back to the transformation-default (a single Identity-Matrix). ie. the spread is gone as soon as you remove the connection. and you get your fps back.

hope that helps.

“The pins have a spread marked in parentheses, but when i open up inspektor it doesnt show this, and i cant manipulate the spreads indepedently.”

Inspector actually shows if a pin is spreaded but you have to look closely. Between the pins “values” and “descriptive name” theres a little arrow: “>”.
if you have two arrows “>>” instead of one this means its spreaded.
Maybe it would make more sense to show the spreadcount in parantheses there instead of this.

furthermore, when you click one of this arrows, a list on the right side will show up with all the individual slices of a spread and even lett you edit this values manually…

oh i see where the >> shows the entire spread and i can edit the spread number. thanks, but i still got one question, why would v cause my whole computer to stagger? Ive done complex renders in after effects that have consumed all my resources and my computer still never staggered.

vvvv need to be practiced a while before one can say that s\he knows it enough to get from it the best results with the best performances, and also some coding skills are required to really get the best out of it.
contributions are full of very complex examples, realized by experienced users, but these example can run well on most machines.

h99