Forum Moderators: Staff
Poser Technical F.A.Q (Last Updated: 2024 Nov 13 12:50 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.
Sorry about this but I might have sorted it... Is it as simple as this? I've noticed that some CR2's use the format ":Runtime:Textures:SeaBeast:SeaBeastTex01.jpg" instead of "C:/Program files/Poser4/Runtime/..." etc for the paths to the textures. Is Poser that clever or am I hoping for too much? Howie.
heyas; yes, use :'s and start at runtime. the thing is, since textures can be placed and loaded from anywhere, its likely that some people dont even have them on the same drive as poser. (i didnt.... i might store them there now that i have a bigger drive... but anyway...) when the pointers are set up like that, i've found that poser asks me to locate the texture, if it can't find it. when i point it to the drive/directory where i actually did put the texture, it then finds any/all subsequent textures that go with it. that seems to work for some people, but many claim poser always asks them to locate ALL the instances of every texture. (i suspect in that case it might be because the pointers are the d:directorystuff format, instead of :runtime:etc: -- but i have no proof.)
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.
Hi, everyone... I'm making up some MAT poses for my Sea Beast figure which I intend to package up for distribution. However... I'm not sure how to make the paths in the MAT files work on the "users" machine? At the moment, I have included instructions for the User to edit the files to correct the texture paths to match where they are on their machine but this seems a little unprofessional. Is there any way to do this correctly? I believe that users will have a similar problem when they open the CR2 as this file also points to the textures as they are on my machine so people will end up playing "find the file". Short of writing a small app to run at installation to correct the paths I don't know what to do! Help! Howie.