I'll give it a go & let you know :)

I still can't download it. What good is the tool if people can't get it?

Attached Link: http://205.122.23.229/ronknights/

I apologize for sounding rude, that really wasn't my intention. My point was that system speed is optimized when the hard drive is defragmented, the same as Poser having correct file references. I have noticed that Poser has sped up for me since I ran this utility. Maybe it is coincidence, but I think not. Yes, Poser 4 will find the texture, but you can't tell me that it does not have to search for the texture. Perhaps on a smaller hard drive, or a smaller runtime folder it wouldn't be noticeable; but the speed-up I have gained is quite noticeable. I can't attribute this to anything else. I ran the utility, and afterwards I immediately noticed the difference. Running this utility was the only thing I did at that time. As to your test, I don't believe that only changing one MAT file will show much of a difference. If you have many incorrect references in a scene, the slowdown will be more noticeable. And considering that about 70% of my characters, props, etc had incorrect references, it doesn't take long to make Poser slow down. It's sort of like tugging on a string. Attach a piece of paper to the end and you won't notice the difference in required effort. Now attach a ream of paper and you will definately notice it. As to this program being totally unnecessary, I pointed out that there was indeed a case where it is necessary for some people. Perhaps it isn't necessary for most. No big deal.

I've heard others say that Poser 'speeds up' when the references are all corrected. But noone has told me specifically 'how' it speeds up? Does it load faster or what? I really want to know. 'Corrected' references aren't going to speed up moving things around or changing dials. I really don't think Poser is checking all its libraries against all the textures in runtime:textures when it first opens...maybe it does. In that case Poser would load faster. After that I don't know how speed could be affected. I don't see how having incorrect references could possibly slow down your scene. You've already applied the textures and they're sitting in memory. I think Poser may look for them again when you render. But other than that it doesn't make sense to me. :: Of course, Poser could be looking for the textures every time it encounters them...which would be really silly, but would explain speed differences. Okay, sorry, I shouldn't have said 'totally' unnecessary, but all the jumping up and down and cheering in the thread had to do with the correction of references. So the conclusion I think is that no, it is not necessary to correct the references, but it is highly likely that Poser will speed up (somehow) if you do. Is that fair?

If a library file has incorrect image path references it takes longer for Poser to load in the file as it searches for the right image files.

Howard, I ran this program on my Poser 4 runtime the other day and I ran into a small invconvenience. When the program found a file that was read only, it would notify me and then just stop. I would go in, fix the file and then couldn't figure out how to restart the process without starting over. After doing this a bout 10 times, I finally was able to figure out how to remove the read only permission by selecting my runtime folder, choosing properties, and deselecting the read only option. It asked if I wanted only that folder changed or all subfolders and file. I chose all subfolders and files. After that, CR ran with no more stoppages. Cool program and thanks. -darlisa

"If a library file has incorrect image path references it takes longer for Poser to load in the file as it searches for the right image files." So that's the only speed up? It's a very slight one at that, in fact so slight I can't tell the difference.

heyas; well, i finally took the plunge and organized my texture directories. what a mess! thank goodness for correct reference, or i would have been fixing texture pointers for years to come! as it was, it only took about 3 hours. yes, i have a lotta stuff. the coolest part was to tell the missing stuff what alternates to use, or to tell it to switch to no_map. thanks a million! um, or about three million :)

Spit, if it doesn't help you, don't use it. For me, especially when using MAT files, sometimes Poser will freeze up and/or crash when it can't find a texture where it expects. I especially have problems when it's looking for a .bum file and I don't have one converted for it. Even if it doesn't crash, stuff gets screwed up and I have to try again.