Sat, Jan 25, 2:56 PM CST

Renderosity Forums / Poser - OFFICIAL



Welcome to the Poser - OFFICIAL Forum

Forum Coordinators: RedPhantom

Poser - OFFICIAL F.A.Q (Last Updated: 2025 Jan 24 6:22 pm)



Subject: setting up scene with alot of props


5200north ( ) posted Tue, 19 January 2010 at 7:57 PM · edited Fri, 24 January 2025 at 7:02 PM

file_446789.jpg

if i am setting up a scene and i'm using alot of props should i "consolidate" most of them by exporting them as an .obj and then reimporting the new obj i created to replace the props. i thought i read about doing this to make rendering easier.

for example, if you look at the picture i've posted, would it be a good idea to combine all the items on the floor as one obj instead of separate poser props? i'm new so i hope my question is clear.


BloodRoseDesign ( ) posted Tue, 19 January 2010 at 8:15 PM

Well I'm not too sure about combining the props making your scene less heavy for Poser, but I may be wrong on that (somebody check me please, and not too hard against the boards! 😄)
I do know that if you import an obj and make a prop of it that Poser embeds the obj as code to your pp2 file, that makes the file somewhat heavy. It's better to have the pp2 file (prop file) call for the obj where ever it resides in the Runtime folder structure. But I'm looking at this as a developer and not too sure if the rendering side cares one way or another.

So basically I don't know one way or another but just wanted to try and help. 😉

Missy Woot!


ockham ( ) posted Tue, 19 January 2010 at 8:29 PM · edited Tue, 19 January 2010 at 8:30 PM

With that particular scene, I doubt that it would make a difference. 

"Objectification" can help if you have dozens of figures with morphs;
turning the figures into rigid items would save Poser from calculating
the morphs, and thus free up some memory for other things like
textures.  Even then, I don't think it would speed up the rendering as such.

My python page
My ShareCG freebies


markschum ( ) posted Tue, 19 January 2010 at 9:18 PM

It wont matter if geometry is seperate or embedded as far as scene loads and rendering is concerned. It saves disk space if you want to keep multipke copies of a prop with different textures  in your library.

If for example the props on the floor is a good layout you can export it as a single obj and make a single prop from it for ease of use later.


bagginsbill ( ) posted Tue, 19 January 2010 at 10:40 PM

If you have one of each prop, it won't make any difference. If you have two or more of each prop, you will make the memory use increase, not decrease. See those two VHS tapes? (Well, I think they're VHS tapes.) That is one copy of the geometry in memory. If you export it and re-import it, there will be two copies.

As far as the renderer is concerned, it makes no difference. Even morphs make no difference to the renderer. The final morphed geometry is sent to the renderer, same as what is used to show you a preview.

Note that external binary morphs that you're not using (value = 0) are not loaded into memory.


Renderosity forum reply notifications are wonky. If I read a follow-up in a thread, but I don't myself reply, then notifications no longer happen AT ALL on that thread. So if I seem to be ignoring a question, that's why. (Updated September 23, 2019)


5200north ( ) posted Wed, 20 January 2010 at 1:15 AM

thanks, i think i get it now...


Privacy Notice

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.