Forum: Poser - OFFICIAL


Subject: Reason number 4

Tyger_purr opened this issue on Oct 31, 2006 · 71 posts


kuroyume0161 posted Tue, 31 October 2006 at 5:36 PM

Quote - Now the question is whether just the renderer and associated modules are multithreaded, or the entire app. Although being up to multithreading at reason 4, one wonders if we might actually see some of the more esoteric requests like weightmapping in some form, or dynamic micropoly LOD around joints, or actual soft body dynamics to a limited degree; multithreading would make the calculations for sbd reasonable.... Customizable UI is also probably one of the reasons... ...and wouldn't it be a hoot if they'd implemented .daz file support? Or possibly .psd export support, Vue Infinite.... Is it time for 5 yet...?

Most apps are multithreaded.  Not many apps are multi-processing.  Cinema 4D only utilizes the processors for rendering.  This goes for most 3D apps that do multiprocessing - it is restricted to the rendering engine.  Problem with it in other areas is that there really isn't a need for that level of support and user-interaction.

C makes it easy to shoot yourself in the foot. C++ makes it harder, but when you do, you blow your whole leg off.

 -- Bjarne Stroustrup

Contact Me | Kuroyume's DevelopmentZone