Wed, Dec 25, 12:10 AM CST

Renderosity Forums / Poser - OFFICIAL



Welcome to the Poser - OFFICIAL Forum

Forum Coordinators: RedPhantom

Poser - OFFICIAL F.A.Q (Last Updated: 2024 Dec 23 7:38 pm)



Subject: Poser looks for files and Independent Runtimes


Larry-L ( ) posted Fri, 19 January 2007 at 11:44 AM · edited Wed, 25 December 2024 at 12:09 AM

I hope I can frame this properly--here goes.

I, like many, have created Independent Runtimes to organize all my stuff--no big deal.  However, when I create and reopen a saved scene Poser sometimes wants me to look for files that it cannot find.  They could be an obj. or jpg. tex file or whatever needs to be found.  Most times it's just a couple of files or so and no big deal, something I tolerate.  But, other times it may take as much as 10 minutes to find all the files that need to be found before a scene completely loads.

Now, I know that when you save a scene Poser records the paths to the files included in the scene, so I am careful not to move anything in my Runtimes and by and large everything is fine.  But, Poser seems to miss a file or two, or three along the way which causes this tedious exercise.

Does this make any sense and does anyone else experience this?  Better yet, is there a solution?  (no Poser rants please)

I sometimes wonder if this is a bug or if it's something I am not doing right.  Any insight would be appreciated.

Thanks, Larry-L


Victoria_Lee ( ) posted Fri, 19 January 2007 at 12:31 PM

Is this P6 or P7?

Sometimes, when opening a .pz3 made in P6 with P7, P7 won't know the paths and will ask for some stuff.  I worked around this by loading the runtimes I used to create the original scene and then saving it in P7.  After that it didn't ask for the paths again.

Hugz from Phoenix, USA

Victoria

Remember, sometimes the dragon wins. Correction: MOST times.


Larry-L ( ) posted Fri, 19 January 2007 at 12:35 PM

Well, I hadn't thought about that but I have been using P7 since I got it and opening files I've created in P6.  You think that might be it?  I'm going to try it out.

Thanks


Victoria_Lee ( ) posted Fri, 19 January 2007 at 12:40 PM

That's what I've run in to but, again, since I use external runtimes, too, I just load them before loading the scene and then P7 doesn't have any problems finding anything.  Once the scene loads I save it and then offload the runtimes I'm not going to need.  After that, P7 knows where everything is and I don't have to bring in the runtimes I'm not going to need to modify the scene.

Give it a shot.  It's an easy workaround and always works for me.

Hugz from Phoenix, USA

Victoria

Remember, sometimes the dragon wins. Correction: MOST times.


Larry-L ( ) posted Fri, 19 January 2007 at 1:03 PM

Well I've tried it with one scene and it seems to have fixed itself.  I'll try a few more.

Thanks again


Victoria_Lee ( ) posted Fri, 19 January 2007 at 2:44 PM

Any time.  That's what the forums are all about.  :)

Hugz from Phoenix, USA

Victoria

Remember, sometimes the dragon wins. Correction: MOST times.


diolma ( ) posted Sat, 20 January 2007 at 5:00 PM · edited Sat, 20 January 2007 at 5:03 PM

I don't have P7, do have P5 and P6.

Most of my P5 saves load happily in P6, but occasionally I have problems withe "Please locate xyz.jpg" (or similar).

I suspect this mainly happens when what is wanted is not located in the "correct" folder (according to the file that's being loaded) , but in a similar one within the same runtime. For instance, a texture file that isn't in (P5) "RuntimeTexturesxxyyzmyTexture.jpg" (as the file would suggest)but in (P5) "RuntimeLibrariesTexturesxxyyzz...

When running P5, it can't find "RuntimeTexturesxxyyzmyTexture.jpg" so it does a search of it's Runtime and eventually finds the file. You save the scene...

When loading this scene in P6, it too can't find the file, so it does a search of the P6 Runtime and can't find it anywhere, so asks for help.

P6 is clever, but not that clever...

After locating the offending file and getting a successful load (in eg. P6) , you can then re-save the file and it will load properly afterwards. Unfortunately, the references within the PZ3 will now have been changed from relative (starting from "Runtime" references) to absolute ones (starting from the drive letter).Which is fine until the Runtime is moved somewhere else...

The only solid answer that I know of is to correct the references within the offending prop/character. If the texture is in "Runtimelibrariestexture" (or whatever, but the pp2 refers to "RuntimeTextures", then the pp2 should be changed and/or the texture moved to where it should be.

Details, details, details.. It's getting too late for me to concentrate (or type)....

I don't think I'm too far off the mark as to what the underlying problem is, but if anyone knows better I'll be very pleased to find that out:-)

Cheers,
Diolma



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.