Wed, Feb 19, 2:55 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: GetStringRes(1029,53) ?


lesbentley ( ) posted Wed, 02 October 2002 at 3:19 PM · edited Wed, 06 November 2024 at 5:04 AM

The default P4NW texture map reference is in a "GetStringRes" format:

textureMap "GetStringRes(1029,53)"

Can someone translate this into English for me? Is it a path? Relitive? Absolute? Or is it something else?

I have a MAT file that uses this format, although it seems to work, it throws up two file not found errors.


ockham ( ) posted Wed, 02 October 2002 at 4:16 PM

Supposedly the purpose of this trick is to make multi-lingual names possible. The "string resources" for Poser reside in POSER.RSR, and the numbers here give an index to that file. I suppose (but don't know) that a German version would have, say, "Kopf" in the same index where the English version has "Head". In this case, the index most likely refers to "P4 Woman Texture2.TIF", which is listed within the RSR. You should be able to replace "GetStringRes(1029,53) by "P4 Woman Texture2.TIF", or your own TIF matching the same template.

My python page
My ShareCG freebies


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.