Sat, Feb 8, 1:11 PM CST

Renderosity Forums / Poser Technical



Welcome to the Poser Technical Forum

Forum Moderators: Staff

Poser Technical F.A.Q (Last Updated: 2024 Dec 04 2:47 am)

Welcome to the Poser Technical Forum.

Where computer nerds can Pull out their slide rules and not get laughed at. Pocket protectors are not required. ;-)

This is the place you come to ask questions and share new ideas about using the internal file structure of Poser to push the program past it's normal limits.

New users are encouraged to read the FAQ sections here and on the Poser forum before asking questions.



Checkout the Renderosity MarketPlace - Your source for digital art content!



Subject: Imagemap Memory Use


AntoniaTiger ( ) posted Mon, 10 January 2005 at 4:43 PM · edited Sat, 08 February 2025 at 1:03 PM

Obviously, the bigger an imagemap, of whatever sort, the more RAM gets used. But what happens if the same imagemap is used multiple times, such as two figures wearing the same uniform? Does anyone know if Poser stores just the one copy in memory?


an0malaus ( ) posted Tue, 11 January 2005 at 6:46 AM

That appears to be the case AntoniaTiger, provided the file paths to load the imagemap are identical, If you load a second figure of the same type which already has texture imagemaps specified, a second copy of the map is not loaded. You can verify this in P4 or P5 material room by looking at the image map list before and after loading a second figure. The list doesn't change. In P4, you also couldn't load another texture with the same name (in case you were modifying a texture and trying it out) - very frustrating. P4 would just keep using the one loaded and had no way to unload textures other than stopping and restarting Poser.



My ShareCG Stuff

Verbosity: Profusely promulgating Graham's number epics of complete and utter verbiage by the metric monkey barrel.


AntoniaTiger ( ) posted Tue, 11 January 2005 at 7:28 AM

Thanks. P5 still seems to have remnants of that texture-name problem. I've come across problems when two textures have had the same filename, although in different folders, even though textures can be edited and reloaded without apparent problems.


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.