Forum Coordinators: RedPhantom
Poser - OFFICIAL F.A.Q (Last Updated: 2024 Nov 26 1:43 pm)
1)Three words Multiple Processor Rendering I would love to start using poser for something other than still pics and tiny animations. Open it up to the market a bit more. 2) Smarter conforming. I like to animate and it sucks when your clothes don't follow their parent. 3) A file managment system that isn't run by an amphetamine abusing primate. Nothing like searching through your runtime looking for that PZ3 you saved... somewhere... 4) Texture management. E V S
I've got just two things, don't really know whether they are added or not, since I didn't check. 1) Use the graphics card for goodness sakes! Make the engine use the card... that's why we got them. ^_^ and 2) Proper cel-shading with different techniques for doing so in one easy click. Anime, Disney, Gourard, whatever.
One word: UNDO. Four words: MULTIPLE LEVELS OF UNDO. Video hardware support is a good one, too: OpenGL previews of the scene before rendering would be nice. {2) Better integration with 3ds Max 4x 5x and 6x.} Support for Lightwave would be nice also. {(especially since the only one available doesn't work under win98.)} Dude, it's the middle of 2004. It's time to bite the bullet and give up Windows 98. It's time to install Windows 2000 or XP. Or do you really want to hold on to your OS until it's 18 years old and can move out on it's own? Since you mentioned it, why don't we ask Curious Labs to add better memory management support when running Poser 6 on Windows 95? Or how about a DOS version of Poser 7?
Well, nothing I say is gonna stop people trying, but do any of you really think CL gives a hoot what we want?? Remember the Poser 5 wishlist? It was jam-packed with all the usual stuff - 'new code, multiple undo, memory leak fix, bla bla bla' - I could recite it in my sleep. Well? Did we get ANY of that? Nope! Not one damned thing. So what makes you think CL are ready to listen this time around? Especially since they've already stated publicly that Poser 6 will have NO MAJOR NEW FUNCTIONS. It will concentrate on stability (read 'getting it to work properly') I applaud the efforts of the users to add their input to a new app. But let's get real, folks. Once bitten, twice shy. mac
Oh, and one other thing. Before anyone starts shouting for a 'from the ground up code rewrite', just remember what it is that makes poser so interesting for a lot of us (and so usable for the rest of you). Yup! You guessed it! The fact that we can get into it's guts and hack it. If it wasn't for poser's crap old code, we'd never have gotten MAT files, morph injection and a hundred other things. Just look at the hoo-hah that was raised when people discovered Daz Studio was writen in binary. mac
This site uses cookies to deliver the best experience. Our own cookies make user accounts and other features possible. Third-party cookies are used to display relevant ads and to analyze how Renderosity is used. By using our site, you acknowledge that you have read and understood our Terms of Service, including our Cookie Policy and our Privacy Policy.
Since it appears to be too late to send any feedback into Curious Labs about desired features for Poser 6, I figured I might as well post my own wishlist here. Here goes: 1) Better lighting system, including real omni lights, and possibly a real dome light with HDRI compatibility. (radiosity would be good too) 2) Better integration with 3ds Max 4x 5x and 6x. (that includes exporting, importing, and general creation/position/size of models/morph target objects) I shouldn't have to buy a third party plugin for this (especially since the only one available doesn't work under win98.) 3) "Texture Poses" eliminated. Move the textures to their own subgroup, and get them out of the pose directory. "Pose" should only ever refer to character positioning, not texturemapping. 4) A softobject modifier, so that figure skin reacts to object colisions, and gravity by deforming. 5) Better hair/fur system. At the moment, the hair/fur system only sems to be able to generate hairs at vertex point. The system should allow for better coverage than that. (for example, letting you specify the number of hairs that will be placed between vertex points. This should also have a toggle switch for low/hi (eliminating al but the control hairs) - so that hair tests can be rendered and motion-checked quickly. That's all I can think of for now. Anybody else got any wishes they want to add? -c*