My runtime is bloated with old and unused clothing and props. Deleting said items is easy enough, but their OBJ files and textures remain.

Is there an easy way to get rid of these associated files other than wading through hundreds of them and trying to remember which ones are orphans? (It doesn't help that some vendors name them illogically.) Is there a utility that reads the OBJ and JPG links in a figure or prop file and deletes them along with the figure or prop?

(I use a Mac, so Windows-only utilities are welcome for the enlightenment of the PC crowd, but won't help me and my fellow Mac-heads.)

Can't think of any for the Mac.  In fact, I can't think of any for PC even though I know there are a couple.  

You can open the cr2/pp2 in a text editor and check the references in there.  Tedious but it works.  Once you have deleted the complete sets you don't want it should make finding orphans easier.

Or you could always create a new Runtime and install only the stuff you want. 

Quote - Or you could always create a new Runtime and install only the stuff you want.

THIS is easier than cleaning out the old one...lol. Especially if it's many gigs in size.

Laurie

Yeah, Laurie, but the old runtime has hundreds of things I want to keep. And a lot of them have been customized. For me, weeding out the unneeded items is a bit less onerous than starting over with installations.

As for opening all the CR2's and PP2's to read the linked files and deleting them one at a time... yikes. That woiuld work in cases where the vendor unthoughtfully named the files in an unhelpful manner, but is indeed tedious. Hoping for a better solution before resorting to that.

I would think it would be a fairly simple and easy script to read the .obj and .jpg files in the figure and prop files and delete them along with their parents... or move them to an archive runtime. In fact, I'm suggesting it to Netherworks, my favorite script vendor.

Meanwhile, keep the ideas coming! This is an issue that affects almost everyone who has been in this hobby for awhile.

P3d0 has been one of my main utilites for many years. I use Pro so I can't tell you if the free one will also do this but it never hurts to try.

P3DO... a possible answer for Windows users (not Mac), thanks for the tip. Though I wonder why it doesn't allow you to move or delete files in the same window? Seeing the files in one copy of P3DO and switching to another copy to delete them, as you describe, seems to add unnecessary extra steps.

I would absolutely hate to have to do that.  My Runtime is 12 GB after recently slimming it down.  Fortunately, I knew the files to remove without having to search for their relationships.

Per the OP's question: Does P3d0 run on a Mac?  I'd have mentioned it but wasn't sure. 

I didn't ask, I stated, that P3DO is for Windows, not Mac. Unfortunately.

Maybe I'm wrong, but a script showing the associated files of the selected figure/prop seems (at casual glance) very simple to create. Adding the ability to delete or move the files also seems an easy and logical addition to the script. Unfortunately I can't write scripts. I'm hoping a python whiz will see this discussion.

Your reply wasn't there as I typed mine.

Just idle musing here:

-- if these utilities are written in Python or wxPython

AND

-- Python and wxPython are versions of a language that works in both Windows and Linux (which is where I'm doing my wx-learning in... works a treat) then

WHY

-- can't Mac (or Python) create some sort of compatible interpreter (Python is an interpreted language, correct?) to allow scripts to run in that OS?

wxPython does in fact work across both platforms. All praise to vendors (such as Netherworks and Semidieu/ShaderWorks) who are building scripts with wxPython these days. 

We all know that the version of tKinter-based Python used by Poser 9 / 2012 is not compatible with older compiled tKinter-based scripts. It turns out that even if these old scripts are updated, many of them still won't work with 64-bit Macs running Poser 9 / 2012. Even dumbing down Poser Mac to run in 32-bit mode does not help; Poser immediately becomes unusable and its menu commands are removed when trying to use these tKinter scripts in 32-bit mode.

A lot of wonderful scripts will fade away, at least for Mac users, unless someone rewrites them for wxPython. Their original authors do not seem inclined to do so. And since they were free, it's hard to complain about it.

Quote - P3DO... a possible answer for Windows users (not Mac), thanks for the tip. Though I wonder why it doesn't allow you to move or delete files in the same window? Seeing the files in one copy of P3DO and switching to another copy to delete them, as you describe, seems to add unnecessary extra steps.

I sometimes forget things that I have set up for myself personally would look like extra steps to someone else.  You are right it can be done all in one window. 

I've done the text editor bit with library files and it is tedious.  One thing to consider is, and I've had this happen after moving or deleting library files, if you open a Poser file later with those items in it you will be prompted for those items.

To save long waiting times for Poser to find or not find those items, I would go through any files that might be using those items and replace them first before deleting.

There should be a 3rd date value in a unix/linux partition, just like ntfs has the option for but you can disable it in ntfs.

It is called Date Accessed. Huge time saver for something like what you want to do.

Search for . in the Runtime then sort it by date last accessed, choose a cutoff date, then move the newer stuff to a new runtime. Remove the old runtime from the Poser library. That way you will know when you need to move something else that was missed in a date sort.

Quote - wxPython does in fact work across both platforms. All praise to vendors (such as Netherworks and Semidieu/ShaderWorks) who are building scripts with wxPython these days. 

We all know that the version of tKinter-based Python used by Poser 9 / 2012 is not compatible with older compiled tKinter-based scripts. It turns out that even if these old scripts are updated, many of them still won't work with 64-bit Macs running Poser 9 / 2012. Even dumbing down Poser Mac to run in 32-bit mode does not help; Poser immediately becomes unusable and its menu commands are removed when trying to use these tKinter scripts in 32-bit mode.

A lot of wonderful scripts will fade away, at least for Mac users, unless someone rewrites them for wxPython. Their original authors do not seem inclined to do so. And since they were free, it's hard to complain about it.

AH! So TKinter is the culprit.

There is this really slick tool out there to create GUIs for wxPython called wxFormBuilder. There's a version for each of the major OSes. So, all someone would have to do is go into a TKinter-based script, grab and save the functional part of the code, make a similar GUI in wxFormBuilder and then, in external (subclasses) methodss add back all that brilliant functional code, making sure there's no interface stuff in that code.

BTW: makes a strong case for black-box coding (i.e., classes that just do their bit without trying to do any interface stuff), doesn't it? :blink:

This may seem after the fact, the only software that I found convenient for installing and removing content completely, provided that content had not been moved or relocated, is Ahudson's 3D Content Installer.  Installation from zipped content, it generated a text file which tracked all content and pathways.  The beautiful thing about it, take the text file and drop it onto the built-in uninstaller and it would remove all traces of your installation.  Unfortunately, it was never updated after P7, and it is no longer available.  Quite a shame, nice software.

I don't know what I was thinking when I typed "12 GB" above.  My Runtime is currently 85GB.  :)