heyas; what is your full poser path? and have you ever had problems with poser complaining it can't find a figure obj that you darn well KNOW is there? have you ever had geometry rsr's corrupted? recently had somebody email me with a mysterious problem of poser not finding an obj, and when i looked at this guy's path i was wondering if it didn't run into some kinda path length limit thing going on. here's the path to the obj: c:program filesmetacreationsposer4runtimegeometrieszygoteanimalseaglebweagle.obj now i just look at that (me, who never uses file names more than 4 letters long) and it just says to me, this is NUTS! now i know poser loves to corrupt my heavy horse rsrs, for no discernable reason. the only thing i can figure is the heavy horse uses a sub-sub directory in the geometries. the path for that is: ..runtimegeometries3dmhh now on my machine, my full path is p:poser.... but i can see if somebody has all this other fluff and nonsense in the beginning, sub-directory paths can start to be getting long, here. too long? we need to investigate! my poser path: p:poser i never had problems with poser not finding my heavy horse objs. certainly not with finding my bweagle.obj. i do recall having corrupted geometry rsrs, though.

c:/3d/Poser4/... Nice and short. Might explain why I have had no problems with finding geometries?

D:/metacreations/poser4 I use the 30GB D drive only for Poser and my data. My other programs and Windows XP are on the C Drive.

my path is F:poser4... use a whole partition only for poser had sometimes problems with obj (poser doesn't find it) then complains that no more memory available and the last imported object or figure disappears out of the scene. sometimes it helps when i delete the rsr file, but not always. sometimes it helps to reinstall the obj file. i found that upper/lowcase can be a problem too ...

I've always used the default path: C:Program FilesMetaCreationsPoser4Runtimeetc.... In all the years I've been pushing Poser around. I've never had an .rsr go bad on me. ScottA

Is this is the original path, what you wrote Bloodsong?
Does the Zygotefolder not be written as ZygoteAnimals ?
This is where my bweagle.obj is saved.
I think the geometriepath is casesensitiv.

My installation of Poser

F:ProgrammeMetacreationsPoser 4....

and no problems with corrupted rsr,s. (knock, knock on wood)

Robert

I wonder if it also has something to do with the number of files in a folder. Poser's File-Open dialogs go crazy when I try to scan a folder with more than about 30 files. That's clearly a bug because other programs like PSP have no problem with File-Open in the same folder. This isn't necessarily related, but seems to be another symptom of poor programming in the file area.

C:Program FilesMetaCreationsPoser 4 Haven't had any problems with misplaced objects or corrupted geometry .rsr's, but I've got Pro Pack, which doesn't use geometry .rsr's anyway. One less thing to go wrong.

d:Poser4 The only other think on that drive is some backup data from my C drive. I get occasional corrupted rsr's, but not very often. However, when rsr's come with downloads they are quite often a problem for me so I never install them and let Poser build a new one for my PC.

I think you can just begin the path at Runtime:...., if the geometry is under Runtime. The other stuff is redundant. I would rather have a lot of similar files in the same geometry folder, than have a blue million different folders in Geometries. I edit the path on most every CR2 I get. I hate scrolling down a long list of folders, many with only one or two files. If you want to avoid Poser corrupting your rsr files, change the attribtes to 'read only'.

Just to be awkward... D:Program filesCurious LabsPoser4 ... the mark of the new(ish)bie.

Nope, nothing wrong with that. Your version of Poser is newer than mine. Poser has gone through 3 companies in its history 1.) Fractal Designs (I had version 1) 2.) Metacreations 3.) Curious Labs Yours is the default installation path for the most recent version of Poser.

hmmm... the bweagle, which is not the same as the bleagle, goes into zygoteanimalseagle. the bleagle just goes in zygoteanimals. but i like to be organized, so i made an eagle directory. jaager: the cr2 can (and does) start in runtime, but somewhere, somehow poser has to tell windows what directory where it is poking around.... isn't there a 256 character limit on directories? or a 10-sub-directory depth limit? i dunno. well, results so far seem to indicate that the problems arent related. thanks guys!

Hey- I wonder if this might not be partly related to Windows filesystem? I know Fat16 is limited in some ways compared to Fat32, so some of these errors might be dependent on which filesystem is installed. Just a thought. Regards- Lemurtek

I use Windows XT and NTFS file system.

I don't know, but I have Poser in its own folder - A Poser - because I want it just under root. I got tired of scrolling in Explorer and made it easy to get to. No one's path would match mine. I just truncate and start with Runtime. Poser is strange, if you put the geometry in the folder with the cr2/pp2, Poser will find it, no matter which path is in the CR2/PP2. This is a handy trick for props with external calls. If you park the geometry and the textures in the folder with the pp2, you can keep the folder on CDR and only put it in the Library when you want to use it.

In my opinion, including software company names in your file structure is daft. Why use "program filescurious labsposer4" when you can just have "program filesposer4"?

Years ago I started changing my installation paths. I had some intricate structure in mind. I got tired of changing the default installation path every time I installed something, or I tried to work with it. It's just plain easier and faster to use the default installation path for most of your software. If you have lots of software, then it becomes more important. One reason I was changing the default installation path was to make room in certain partitions. One thing I found out was that some programs will put files into the partition that has Windows, no matter where you install the program. In the past I had several partitions on one smaller drive. I ran out of room too easily that way. Now one 20GB drive is one partition, and the 30GB is another partition. There is less chance of running out of room.

Having the publisher's name in the path makes sense for companies like Adobe, Macromedia or Corel who have lots of products (there's another one too - Mini-something?) and I suppose the smaller companies like the style, or maybe they hope you'll buy lots of other stuff from them (after all there are ProPack and Avatar Lab from CL).

daft?? a directory named 'program files' is daft, if you ask me. why not just name it 'the entire hard drive'? i never get tired of telling programs where to go. i am a control freak! i will NEVER bow down to having my computer tell ME what to do!!!! (hey! stop dragging me away! leggo! ....!) but seriously, okay, i have p:poser and fat32

DOS used to limit you to something like 100 items in the root directory (C: etc.) so collecting stuff together was a good idea (just a pity no one did it before Win 95). Personally I like having a folder for apps, a folder for docs and a folder for the OS: I just wish Poser could look for its stuff in My DocumentsSomething-or-other as well as Runtime so that I didn't have to keep some of my data in Program files.