Multi threading hypervoxels, yes or no?

[Ge4-ce]

Ok people..

Jimzip brought up a subject in another thread wich I though was worth investigating more...

He said " don't use multi threading on hypervoxels because it will slow down a lot"

Now, my question,.. maybe it has something to do with the settings?

does it slow down with ALL type of hypervoxels? or just with for example: Volumetrics?

because you can choose sprite, surface or volumetrics..

And maybe there are another bunch of settings that make renderings slow when using multitreading on Dual machines..

any ideas?

[Jimzip]

Heh heh. So someone was listening eh?

I haven't tried it on different types, I just know on volumes it's a no no.
I thought it would speed up the process, but like someone else here put: the processors play traffic-cop.

Sprites should be fine, I see no reason for non-volume calculations to be any different from surfaces. The same (obviously) with the 'surface' setting, although, I'm ready to be told otherwise. I'll do a test and get back to you.

Jimzip :D

[drclare]

I have a dual 800MHz G4 and have noticed that volumetric hypervoxels are slow, but didn't know if it was multithreading doing it. With surface hypervoxels they seemed to be just as fast as regular surfaces.

[Glendalough]

Seems to be 2 questions I can really answer today.
My Humble Experiance seems to show that volumetric hypervoxels (have only used Sprites) render best with one thread. With multi-threading they start at about 30% faster, but in an animation, by frame 30 or 60, they are slower and eventually Lightwave crashes................