Aller au contenu

Can Tray Importer help find where a piece of CC has been used?


Messages recommandés

Posté(e)

I've been trying to clean out old and unupdated CC hairs recently, but I don't want to just delete them and see random bald townies walking around everywhere. Is there any way to use tray importer (or any other tool) to search the tray for a specific cc package? Ideally I would like to know which sims are attached to which pieces of cc (so I can swap their hairs before deleting) but I would also be happy knowing how many times a piece of cc has been used.

 

I searched for tutorials, but all of them are about identifying the package of a broken/unwanted cc rather than which tray items use it, so I was wondering if it was even possible. Thanks!

  • Team
Posté(e)

Hello @Mandibles,
What you want is the reverse of Tray Importer.
This feature was planned but never implemented.

 

What you can do is compile the list of CC for each .trayitem then compare them to the list of package in your Mods folder.

 

Compiling the list of CC for each .trayitem is the part that will require the more work.

 

To get a list of all your package files in your Mods folder:

On Windows

  • Locate your Mods folder
  • Hold the Shift key then right-click on the Mods folder
    • select Open PowerShell from here (if available)
      • in the PowerShell window type cmd then press Enter.
        This will switch the PowerShell to a standard Command Prompts.
    • Or
    • select Open Command Prompts from here (if available)
  • Type dir /s /b *.package>ListOfAllFiles.txt then press Enter.
    This may take some time to complete.
  • Once done, you should find a file named ListOfAllFiles.txt in your Mods folder.
    This files will contain the list of all the package files found in your Mods folder.


On Mac, the process should be similar.

 

Using something like an Excel sheet, you should be able to compare both list and determine which files are not in use.

  • Team
Posté(e)
Il y a 3 heures, Mandibles a dit :

I'm assuming compiling the list of CC for each .trayitem involves opening them individually in Tray Importer and checking the list?

Yep! If you don't have to much trayitem, it should not take too much work. 😉

 

When loading the CC list, click on the group to select all objects in that group (hold Shift if you want to add another group),

then just right-click on the selected objects and select Copy>Copy path. This will copy the path of each selected object.

 

Then again, something like an Excel sheet will help sorting the list by name without too much hassle.

If you keep the duplicates, you will get how much time a file is used. This is not what you are looking for, but should be close enough.

 

 

I will take a look and see how much work it would require to implement something close to what you are looking for.
I'm not promising anything here! 😉

  • Team
Posté(e)

@Mandibles I've played around and here's what came up: 
pkgusages.png

It does a full scan of the displayed trayitems or just the selected ones (which is the same as loading the cc list).

It shows how much time a file is used.

It doesn't yet show which traytems use the packages, but it's coming.

You can filter the result to show only the (un)used ones or all (default).

  • Yes 1

Rejoindre la conversation

Vous pouvez publier maintenant et vous inscrire plus tard. Si vous avez un compte, connectez-vous maintenant pour publier avec votre compte.

Invité
Répondre à ce sujet…

×   Collé en tant que texte enrichi.   Coller en tant que texte brut à la place

  Seulement 75 émoticônes maximum sont autorisées.

×   Votre lien a été automatiquement intégré.   Afficher plutôt comme un lien

×   Votre contenu précédent a été rétabli.   Vider l’éditeur

×   Vous ne pouvez pas directement coller des images. Envoyez-les depuis votre ordinateur ou insérez-les depuis une URL.



×
×
  • Créer...

Information importante

Nous avons placé des cookies sur votre appareil pour aider à améliorer ce site. Vous pouvez choisir d’ajuster vos paramètres de cookie, sinon nous supposerons que vous êtes d’accord pour continuer. Conditions d’utilisation Politique de confidentialité