Thought Id better post it here, even if I feed the spread (range 0-1) into a min I still get MAX FLOAT, if I put a MAX node and it gets caught, so its big a negative, I’m now clamping it with a map node, but obviously its not the value I want! It doesnt show up in tty either
After adding a map node to clamp, I get
00:04:52 * : [event.call: error occured in TMex9EffectNode](event.call: error occured in TMex9EffectNode): Zugriffsverletzung bei Adresse 00612EEE in Modul ‘vvvv.exe’. Lesen von Adresse 00000000
Everytime I change the values of the spread.
I’ve just noticed That I didnt actually connect the map to the rest of the patch, it seems to have stopped the MAX Float and added the above error in its place?
It was still happening with the map…
It seems to be within Damper, I’ve replaced with linear and it seems to work, I’ll report back after more testing…
Still getting that error message above though
Same thing for me, i regularly see maxfloat on dampers. It’s on a patch where there’s a lot of dampers and min nodes, all connected on the outputs of a fft4. When my render produces artifacts bugs, I have to search which damper is bugging… Usually, I fix the problem by deleting the node and re-creating it, but it rebug some minutes after. The bug appeared after the 6th or 7th damper i created. Is it an overload of fft damped data?
Help Cat !!!
12 and filtered for me too.
IS that effect error generic .fx file problem again?
I’ve seperated all my techniques into seperate fx files now, to get around the enum bug, can you guys still not recreate this?
Maybe I should email you this patch?
MaxFloat on Damper output. Appeared also when i used the Oscillator node instead of Damper. It is the only Damper (Osc) node in this patch. When I connect a new Damper it’s fine, no prob. MaxFloat appears only after restarting/loading the patch.
I use beta21.
Somebody can help/explain here?
Thanks a lot!