thefixer opened this issue on Aug 07, 2007 · 430 posts
Penguinisto posted Fri, 10 August 2007 at 9:04 AM
Quote - Poser 7 runs slower for two reasons:
- multiple undos..
That's actually easy but for the current implementation with Poser's codebase (not Stewer's fault, mind you, but because Poser's codebase is what it is). D|S has always had multiple undo and it's 10x faster. > Quote - 2. Opengl Advanced lighting, proceedural texture, and transparency previews. Poser is now calculating the new light types, your proceedurals textures, and transparency mapping for preview display in opengl. Slows opengl down for sure..
Again, I apologize, but nope. Poser does a large chunk of that internally when in truth it doesn't have to. It can (almost) all be pushed off to the graphics GPU to work on, leaving the engine and UI more wiggle room. Again, this is Poser's internal architecture and the compromises that had to be made... it's also part of why I've been shouting for years @ CL and EF to tear down Poser and rebuild it from scratch. They're still (I suspect) relying on chunks of code that are well over a decade old (and then some). > Quote - You want new features, there has to be SOME cost somwhere in execution speed.
Perhaps, but if those changes are implemented intelligently, that cost can be minimal. /P