|
|
Post by leerylemons on Nov 18, 2021 18:31:48 GMT -5
I recently downloaded some FeralPoodles hairs. She has a file with EA only swatches and a second file for her recolors. These files both contain the mesh. When I installed them, they show as one CAS asset in game, and all the swatches from the EA version and her recolors are showing up. I want them to show up separately, as I like to keep my CC clean and organized. Does anyone know why they are showing up as one and can help me with what I need to modify it so they will show up separately? I updated the display index on each swatch of one of the files, and it didn't do anything for where it appears.
|
|
|
|
Post by Fwecka (Lolabellesims) on Nov 18, 2021 23:24:29 GMT -5
Perhaps the original creator used this method to link all of the swatches. Seems to me that the easiest thing would be to clone a new package file and import the meshes and textures into it so that you have two independent package files. |
|
|
|
Post by leerylemons on Nov 19, 2021 9:59:56 GMT -5
I had issues exporting the mesh. So based on the tutorial you gave me, I just created a new prototype ID and pasted it into every swatch of the existing file, and it worked! Thank you so much for your assistance!
|
|
|
|
Post by feralpoodles on Nov 19, 2021 23:38:30 GMT -5
Omg was just randomly looking through some of the help posts for research, what a coincidence that I found this lol. Yea, the reason they show up as one hair is because I make the separate versions by deleting swatches from the merged version and saving them under different names, so it's technically the same item. Another thing you could do if you wanted to separate the packages for other hairs would be to open the hair in s4s, press ctrl+shift+c, type in studio.exportall, this will export all the textures/lods into a folder where the package is saved. Then you can create a new package, type in studio.importall, this will create an empty folder, move all of the files from the first folder into that empty folder. Then you can enter studio.importall again and it should import all of the files into the swatches/LODs, that would make it go faster!!  |
|
|
|
Post by Fwecka (Lolabellesims) on Nov 20, 2021 2:39:08 GMT -5
That is a great way to do things quickly. Thank you! I'm going to have to try this. In the past, when I've come across a recolor that was dependent on another creator's file, I exported the recolor textures I wanted and then opened the original creator's file (the one the recolor was dependent on) and made new swatches and added the recolor textures I wanted. In other words, I edited the file that the recolor was dependent on. Then I added "Lolabellesims fix" or something to the name of the file so that I knew it's a file that was edited by me. (I'm Lolabellesims. I made this account long before I started sharing my work. That's why the name is different). It's so tedious to do things that way. Your way is much easier.
|
|
|
|
Post by feralpoodles on Nov 20, 2021 3:09:25 GMT -5
I know right, once I learned those commands everything became so much easier, I probably would've given up by now if i had to individually upload 69 textures for each hair I made lol. I've got it set up in photoshop now so I can play an action on the edited texture that recolors it for all my swatches and saves them all in a folder with the s4s importall naming convention, so all I have to do is move the files and auto import them, it's been a lifesaver. I did forget to mention though that the importall function doesn't work on the initial swatches in the package for some reason, but you can get around that by saving the swatches in a color palette, deleting all the swatches in the package, and then applying the color palette, then importing the textures!
|
|
