Attached Link: http://www.horseless-headsmen.co.uk/CorrectRef/CorrectReference1.1.zip

Thanks!! Will certainly try it out. :) Irene

Wonderful idea! May be even more necessary for P5 than in P4, because P5 sometimes hangs up dead when it can't find an OBJ or something.

Howard, Sounds great. I don't want to know the down and dirty details, but how does it do it? By comparing the path with folder content? That is, does it check each path to confirm it? Just curious. mac

Does thsi work with P5? I have several "runtime" folders... would I run it once for each of them?

Tell me, please, that this proggy will allow me to copy over my P4 Runtime folder in its entirety to P5's Runtime folder (yes, I know how to do it so P5's unique Runtime content is not overwritten by the incoming P4 files), then run you program and correct all the transferred content to reference the correct texture, geometry, etc. files in the new P5 file structure environment. Yes? Please?

.

Cowabunga! Thengkew, Thengkew, Thengkew

.

Hooray for Howard! :) Thank you again for putting all the work into this. It's much needed. Phoenix

Howard, Is it only my imagination, or does this thing change the extension from .bum to .jpg where appropriate? Bless your little heart! But it appears to me you have no public wishlist. What's that about? ;) Phoenix

Thanks.

I'm withy nu-be....getting it for when I'm smart enough to use it..:)...thanks Beav

Can't wait to try it. Thanks.

Looks good so far, but you should let me skip the search for texture folders. i have a LOT of places it can look - and I >know< where I want it to go :)

My 1.6Gb libraries folder took just over 2hrs to scan, 6500 files later I only had 480 textures to find, this little gem saved me weeks of slow searching, Thanks again Howard ;) Rob

that should say took 2hrs to scan & correct.

Ok... I am doing mine inc hunks as I already have my content seperated into seperate runtimes based on where I got them (Daz, Renderosity, RuntimeDNA, PoserStyle etc) ... the Renderosity folder took about 20 minutes... 1171 files checked, 2537 references fixed, 4 unfound files (I found em by hand). Thank you :)

Hogwarden, This is a really good idea. Thank you. - TJ

how about a Mac version Please ????????????????

Can't connect, always "connection refused..." Any other have problems ? Laurent

Has anyone tried copying their P4 Runtime folder into its respective P5 counterparts, then running CorrectReference? Does it correctly remove old references to the "MetacreationsPoser4" path so files will realize they are now in the P5 Runtime environment?

Hiya... And in reverse order... Yeah... It will do that! It'll replace the references with ones which point to the right folder. Oh, ablc... I think my site has a small bandwidth! Please try again later or get someone who already has CR to e-mail it to you!?! No MAC version I'm afraid! Should have written the blighter in Java! Point taken Soulhunter... but utilities like this have to be fool-proof! (ducks!!) I'll see what I can do for the next version... but I will need to get to work on PBooost for P5 soon!! Phoenixamon... you know I don't think it does... I'm not in front of my machine at the moment... It does search for files with different extensions... a lot of the Poser 4 content calls for PICT images where there are actually tiffs... CR corrects these. But I think an unfound BUM will come up in the Unfound Files list rather than replace with a same-named jpg. I will need to ask the user to state "prefer P4 or ProPack types" for the program to decide what to do here... oh... and I don't have a wishlist! I'm too busy writing the programs to use Poser!!!!! Bah! Terry Mitchel... Yes!!!!! Maclean... yes it scans through each file looking for file pointers. It then searches for the required image file in the selected textures folder and corrects the reference accordingly, then saves the file. Pendarian and Puntomaus... men of few word, huh? Howard:)

You're wrong, Howard. :) It does change .bum to .jpg if the BUM is not present and the JPEG of the same name is. I was shocked and amazed. Of course in one instance it couldn't find horn.jpg, so replaced it with thorn.jpg, which was incorrect. But it's wonderful. :) Phoenix

Oh!!! I must have put that in in a moment of meditative zombie coding! "couldn't find horn.jpg, so replaced it with thorn.jpg, which was incorrect." yes, I can see how this can happen... thorne.jpg does contain "horn" so CR will match it. I could make this more stringent, but this would slow down the app. But this does have its benefits... the file now doesn't contain any incorrect pointers, so will load up in Poser3/4/5 no problems, and not upset PBooost switching... and it'll become quiet apparent that the texture is wrong when you load the object! A fairy's head texture on a viking helm? LOL. But, on the whole, it looks like this is a success!!!!! H:)

Pendarian and Puntomaus... men of few word, huh? LOL... no, just wanted to wait for your response to the question above my post and had to test it. But works great so far. Thank you :-) BTW, I'm no man.

I would leave it as is. Since it reports exactly what it has changed and what the replacement file was, I can easily scan through afterwards and see if I want to manually fix any of the changes. I'm just super happy with it. Like I've mentioned, I never ever install textures in their default locations, so this is going to save me work every time I install something. Now what I REALLY want is a database driven app for the organization of Poser files. If you've ever used DreamWeaver... like the file management system in that. The first time you run it, it has to scan through all your OBJs, Textures, CR2s and so on. It gives a unique ID to every object and databases them along with their location. It indexes the CR2s as well, databasing the geometry and texture references in each, cross-referenced with the index numbers of those external objects. Once it does that the first time, it can straight off give you a list of unreferenced OBJs (safe to delete) and you use it like Windows Explorer. If you move a texture, the CR2 that references it will automatically be updated. If a texture is missing, it can give you a list of possible matches. It stores the "last indexed" date for each file and when you run it again it only needs to index files that are new or modified since the last indexing. It can do uninstalls since it knows what file is linked to what. It can be used to move files into external Runtimes to be stored on CDs for Poser 5. It can make biscuits and sing. :) I will pay handsomely for that app. :) I am actually going to try to code it myself, ut I don't think I'm going to be able to manage it, so I offer up the suggestion to any taker. Phoenix :D Phoenix

Go, Phoenix, Go!!! Oh and Puntomaus... Sorry about the gender confusion!!! Howard:)

ablc you managed to get hold of it yet? seeing as howard said it's ok I can email it to you if you haven't. Rob

John, I bought OO after Howard announced this free utility. It's not the same app. OO allows the user more flexibility. This is just a quick all-in-one-shot utility. It guestimates and sometimes does it wrong. OO lets the user interact far more. Go for the program I was describing above. It's very much like OO, but being database driven, it would be able to accomplish a lot more. I have a very solid vision of the app, but I doubt I have the programming skills to pull it off. If you want to snag the concept, I'm just waiting to pay someone for this thing. Phoenix

John... Look, I'm sorry if you feel slighted by CorrectReference... But I was unaware that correcting texture references was a function of OO... I read your product description and didn't notice the reference to this near the bottom... I must point out that CR does not correct obj. file pointers at all. It doesn't do anything to organise your files, or even touch on geometries. It doesn't compete with what I consider to be the main function of OO which is to allow you to delete files which aren't used by any of the Poser files in your library. All CR does is correct texture file pointers by batch. It is mainly intended for PBooost users who are having troubles because of incorrect file references. Just so everyone knows, here's your product description for OO. +++++++++++++++++++++++++++++++++++++++++ "Ask yourself- how many times have you downloaded a figure from the Internet, loaded it into Poser, only to get a "FigureRes Geometry: Runtime:Geometries:fairy:blwings.obj not found" error? And, then, of course, when you click the Ok button (to clear the message), Poser looks for this file anyway- taking 3 or 4 minutes (or longer!) to try to find it AND then gives you a message about how Poser is "Low on memory" (and proceeds to delete a figure from your scene!). How were you supposed to know that this figure even used this "obj" file? Wouldn't it have been better if you had known about this ahead-of-time, before you tried to load the figure? Well, now you can- just use the Poser Object Organizer Program to see the "insides" of Poser files! That's right- by clicking on figure files, you can 1) see what obj file and image files are used, and 2) see where those files are actually located on your hard drive, and 3) automatically fix the figure file to "point" to the "obj" file's actual location. What does this mean, to you, the average user? It means no more "missing file" errors- you will know ahead-of-time if you haven't installed all the needed files. Have you ever tried to clean up your Poser files? Have you gone through your figures Library and removed everything you'll never use? What about the supporting obj files- those are probably still on your hard drive, taking up space. How would you know what figures (if any) even use these "obj" files? Well, now you can- just use the Poser Object Organizer Program to scan through your RuntimeLibraries folder and find every figure that uses the obj file... if nothing's found, the obj file is safe to delete! Have you ever looked in your RuntimeGeometries folder to see what's there? If it's anything like mine, you could have TONS of sub-folders... and most of them have odd names. Wouldn't it be nice if you could reorganize the folders and files to YOUR liking? Well, now you can- just use the Poser Object Organizer Program to move the obj file to another folder AND change the figure file's reference. Have you ever wanted a copy of the list of all the files in a folder, but couldn't figure out how? Sure, you could do a screen shot, but you're limited to how many things fit on the screen (and the fact that a screen shot is a graphical image). Now you can finally print the contents as plain text- simply click on a folder, click the Print button, and the list of folders and files will be saved to a text file- ready to be copied and pasted into other documents. You can even print the listing of all sub-folders within the selected folder! When you download a "zip file" package, are you tired of having to place every file in its "recommended" location- usually in folder names like: RuntimeLibrariesFiguresArtistNameCharacterNamefigure.cr2 RuntimeTexturesArtistNameCharacterNameCharacterName.jpg Yes, this is a good method to remember the artist who created the item, but wouldn't it be nice if you could put these files wherever YOU like, and then change the cr2 file to reference the files in the new location? Well, now you can- just extract the files to a folder of your choice and use the Poser Object Organizer Program to adjust the cr2 file to correctly reference the files in their new locations. (Of course, cr2 files must still go in a sub-folder under the "RuntimeLibrariesFigures" folder and images must go in a sub-folder under the "RuntimeTexture" folder. But, which sub-folder should be up to YOU- the user. After all, it's YOUR computer!) What it is: The Poser Object Organizer Program is a Windows application that combines basic Poser-type file-editting features with the familiar "tree-view" of Windows Explorer. (Click here to see a comparison between the Poser Object Organizer Program and similar programs.) Features include: Expand any drive or folder. "Expand" any Poser-type file (cr2, hr2, pp2, etc) to see what files it references. -"Expand" the referenced files to have the program find their actual location on your hard drive. -If the referenced location does not match the actual location, the program will correct this "discrepancy" for you- NO manual code-editting is needed! "Expand" any obj file and you can scan the RuntimeLibaries folder to find figure files that may be referencing it. If no files reference that obj file, it is safe to delete! Print the contents of any drive or folder (and choose to include sub-folders) to a text file. Delete folders & files (you can set your preference to have the program move the files to the Recycle Bin or permanently delete them). If you delete a Poser-type file, the program will delete the rsr file as well. Rename files; if you rename a Poser-type file, the program will rename the rsr file as well. -"Protect" (or not) system files from accidental changes. Change the application's colors (background color, text color, "tree" colors, etc.). Open a file in its default application OR open a folder in Windows Explorer. As you click on each item, certain options will become available- cut, copy, paste, rename, delete, etc." +++++++++++++++++++++++++++++++++++++++ OK, I've got CorrectReference and PBooost... and I got them for free cos I wrote them , And I still will buy OO because it's a danm good utility (when I have the time to do some actual pictures again!) CR is not OO and it never will be. So please... you must see that I have no intention of sabotaging your sales or competing in any way unfairly with your product. Apologies for causing any concern... Howard:)

Gee, no Mac version huh ?? golly all you pc'rs get all the helpful stuff right now. We have to wait even though 95% of the stuff is built on mac. well if some one knows of an app similar to this one (which I could really, really, really use, hint, nudge ) pm me so I can get my life (library) straightend out please M_I_Zombie

is there anyone who could port it over to mac? would you be willing to work with someone to do this howard? No I'm a pc'er too & know next to nothing about Macs, except that the last time I used one I had a great time with Afterdark, ah that 22 inch screen it had was lovely too :) Rob

Attached Link: http://www.hyper-3d.com/content/departments/reviews/archives/poserOO_initial/index.aspx

Hey, CorrectReference would be easy-peasy for someone more familliar with MAC programming... it's a simple little program... but the learning curve is too much for me at the moment! H:)

Phoenixamon :"Now what I REALLY want is a database driven app for the organization of Poser files. If you've ever used DreamWeaver..." Wow, now that would be really fantastic. Each time I work with Dreamweaver and move folders or files I think why can't I do that with Poser. Such a programm would be great.

Attached Link: Revolution

Glad someone likes the idea, Puntomaus. :) It would simplify so many things. Like I said, I'm going to try to write it, but at my level of coding skill it will probably not be ready until Poser 7. I've done some programming, but never for Windows. So I'm really hoping one of these programmers will pick up on it and make it so. Phoenix

John... Are we OK with the CR situation? Like I said, I don't want to upset, step on toes or impact sales with CR. Please let me know if you perceive there is still a problem. H:)

Howard, This is the most useful utility to come along since The Tailor (not counting PBooost :) ), and I just wanted to send you a big thanks. I ran it on my Poser installation, and it took 12 hours to complete, but it WORKED. And now, PBooost works like a charm, and the load time on my items is noticibly faster. You've just been elevated to 'Utility God' on my list of Poser folks...THANK YOU!!! ChromeTiger

12 HOURS? CHEEZUS!!! That's one big runtime. And mine is one big head after your comments! LOL! Jelisa... Revolution does look really interesting. I'll download it and see how I get on... ... at least I can develop free apps without any charge! $299 is very reasonable for the small business license. Oooh, but I find Delphi sooo satisfying to write! H:)

satisfying, eh? uhuh ... right .... (lol) -darlisa

Blimey I sound like a real saddo. A bespectacled socially inept spod trekkie with a cat called K9. There's one of those in the corner of our office and he scares me. LOL!

I've just tried to download it, and gotten the message "The requested URL '/CorrectRef/CorrectReference1.1.zip' was not found on this server" Have you withdrawn the utility from distribution?

These programs solve problems that don't exist and therefore are totally unnecessary. As long as the texture is in runtime:textures Poser will find it. Period. Doesn't matter what the reference says in the Mat file, the cr2 or the pp2. That's for sure in Poser 4. In Poser 5 I don't know if Poser loads up the new runtime:texture list when you change runtimes. If it doesn't, it may be a bug. If it does (or is fixed) you don't need to 'fix' references there either. KISS

JeffH, Poser 5 does have a problem finding the textures in linked runtimes if the pathname is the full pathname and doesn't exist there. For example, if the cr2 points to C:Program FilesMetacreationsPoser 4... then my Poser 5 will choke on that because that pathname doesn't exist on my machine. If the pathname is D:Poser 4..., then Poser 5 doesn't have a problem finding the texture since that pathname exists. Whether they fix that or not in the P5 patch, I still prefer to have the pathname start with :Runtime:textures:... -darlisa

Spit, actually, it does solve some problems. There is a very good utility called PBooost, that if you run NTFS drives and the textures aren't referenced correctly and completely, it doesn't work as intended. This is a combination of a problem with file handling by Poser and with NTFS. CorrectReference fixes it so it can work. It also does speed Poser 4 up, as it doesn't have to constantly search for the intended texture. I'm assuming you also find it totally unnecessary to defragment your hard drive, or any other preventative maintenance measures. To each their own.

JCleaver...that problem with PBoost only occurs if you have PBoost...it doesn't affect anyone else. Having an 'incorrect' reference does NOT slow Poser down. That's a myth. Because it doesn't pay any attention to the reference unless the texture is not in runtime:textures. The only thing that slows Poser down is if the texture does not exist and you have many many many textures. That's a very rude reference to my harddrive maintenance habits...which have nothing to do with anything. I defrag my drive thank you very much. Instead of knee-jerk trying to discredit me, why don't you TEST this.

sorry Spit but I have to disagree with you, since using PBooost & Correct Reference Poser4 has gotten noticably faster at loading characters & mat files, my copy of poser no longer has to troll through all the folders to find a texture it can go straight to the right folder, it's quite scary how many items just point to the Textures folder & say "it's in there", I would much rather have them point right to the folder & say "this is the exact folder you need".

C1rcle: My Poser 4 never goes trolling through folders. It loads the list of textures when it opens and hunts in memory. It doesn't even care what's in the reference unless the texture isn't in its list in memory so it doesn't matter what the reference contains. It just looks at the texture name. So I really think your speed up of Poser must be due to something else. Try this. Make copies of a MAT file and change the references in it. One to the exact path/filename. One to an erroneous path but correct filename. One to a correct path but erroneous file name. Then test each. This would be under Poser 4. Because according to darlisa, Poser 5 won't find the texture in a different runtime if the path is not a valid one (it can be an incorrect one though) but it does under Poser 4. My results show that as long as the texture is somewhere in runtime:textures Poser finds it without problem or slowdown no matter whether the reference is correct or incorrect.