hi guys

i recently updated my PP2012 with its SR1 - and apart from annoying resetting everything i had as my preference, my file paths when creating mats has gone from

:runtime:textures:Artemis:blah blah

to

c/:runtime/textures/Artemis/blah blah

is there a way to fix this? (apart from using edit pad or note pad - i know how to do that :))

Thanks in advance

Artemis

What you are seeing is a change from "Relative Path" to "Absolute Path" with the update. My question is, what are you using to look at the path?

I have SP1 installed and checked my materials paths with Poser Editor and they all show as Relative.

edit pad ... i've always used edit pad .. and i havent changed my work flow since the SR1.

Interesting. The only textures in my materials folder that are showing up with Absolute paths are the ones I have stored on a different drive. It could be that Poser is creating Relative paths for everything that is in the local runtime with it and Absolute paths for textures that are outside it. I haven't check that yet to be sure.  I'll run some tests.

my textures are in a runtime outside of poser's runtime, its how i create content and not have to worry about the whole C drive thing. but now i do so ...

c/:runtime/textures/Artemis/blah blah

Do you mean that exactly - you have the root of your C drive as the library? I didn't think that was even legal.

You're supposed to have a folder, which then contains a folder called Runtime.

For example:

c:/Baggins/Runtime ...

I suspect Poser is getting confused by your path because it plans to get the parent folder name out of any image path as a prefix, and make the rest relative, but you don't have a parent folder name.

Perhaps it worked differently before, but I bet they had other bugs relating to rooted runtimes. They probably were trying to fix those. I know when I first wrote the new library GUI that it was accused of being unable to handle rooted runtimes, but it was actually Poser that was confused by them, and the library GUI doesn't care about paths at all.

I just made two new materials in Poser Pro 2012 with SP1. I pulled them up in notepad just to be sure.  All of the texture references were "Relative". There was no drive indication.

I do the same thing you do. I have product folders with their own runtimes and the materials in them are all correct, without the drive designation. If you could tell us a little more about how they are arranged in your folders it would help.

My file structure:

:Content Foler Name:Runtime

when i started content creation years ago, the person that taught me the ropes told me to put a runtime directly inside my c dive ...

c:/runtime/ etc etc ....

Poser has its own runtimes as its meant to - i have like 5 runtimes inside of poser as you said BB .... Artemis/Runtime/ etc etc ..

if that makes sense?

I'll leave this to BB. He knows better than I do, but that may be what is causing your problem. I keep everything on my D drive where I have poser. The files are like this:

D:ToxicWolfProduct Name FileRuntime

I then access the "Product Name File" as an external runtime for Poser 7, Poser Pro, etc.

This allows me to test the content in the different versions of poser easily.

its so that it doesnt create absolute paths in the filenames - i can change it all in editpad, its just one extra step i have to take LOL

So what you're saying is you intentionally put things in the root because that was the old way of getting relative paths out of Poser saves.

Now - getting relative paths happens except whent the path begins from the root. If you want to use the built-in support for relative paths, you have to move away from the root.

ok .. and how do i do that?

Rather than having the runtime folder:-

c:/runtime/ etc etc ....

Use:-

c:/My Poser Stuff/runtime/ etc etc ....

yes but for packaging purposes i would have to remove the 

c:/my poser stuff/ from the filename otherwise it will fail testing ..

My experience has been that provided I have "My Poser Stuff" currently loaded as a Poser library, that files saved to it contain correctly formed relative paths.

I appreciate that there may be a problem if you have runtime directly under the root hence my advice to add the "My Poser Stuff" directory and place runtime below that.

I possibly should have mentioned that my texture files are within that runtime, my assumption being that your's were also. If not then they need to be.

Before posting I double checked that this worked. If it works for me my hope was that it will work for you also.

Did you try it?

Suggest creating a "My Poser Stuff" folder and constructing runtime etc folders below that.
Then use the Poser library pallet to add "My Poser Stuff" to it and have that as the current library.
Select the ground plane and apply a texture from within that runtime.
Save the material.

Open the material file in a text editor.
What path format do you see?

Yes my textures are in that runtime (for the product i am creating)..

i'll give it a try as soon as i get back to my computer :)

I went in and checked all of the materials for the content package I am currently working on in Poser Pro 2012. They all have relative paths. They were created from the runtime

D:Product nameruntime

My Poser Pro 2012 is on my D drive. I think Phil is right on this one. It looks like all you need to do is forget about using the C drive. In the old days, that was the way to go. But the Poser programmers realized the problem and "Fixed" it. Using the C drive doesn't work anymore. It only works the "easy" way now. ::::

Yes looks like i am going to have to rethink my flow .... thanks guys.

What do you mean by "rethink", exactly? You seem to be making this way complicated. You don't have to change workflow.

Create a folder. Move that rooted Runtime inside. End of "rethink".

Thats what im going to do. :) ty BB.