|
Post by mylofarmer on Aug 12, 2024 23:12:18 GMT -5
Hello everyone. I've been having an issue since updating Sims4Studio to version 3.2.2.5 last week.
I added CC to a folder containing stuff by a specific CC creator, which contained files that I had fixed the display number and converted the images to DX11 in a previous version of Sims 4 Studio. First I ran the change display number and it fixed for the new CC I added and said it was unable to fix what had been previously batch fixed. That didn't use to happen and all CC would have their display numbers changed according to alphabetical order of the folder's files. So I tried disallowing CC for random. It fixed the new CC, said that some files didn't need fixing and some that didn't actually need to be fixed showed up as "unable to fix".
So just as a test I opened one of the unfixable files, went into warehouse and deleted its batch fix history. Ran change display number again and it worked.
Now if it's a folder with a small quantity of CC I can do this manually, but some of my folders have 300, 400 pieces of CC by a single creator and it would be impossible to edit each file one by one.
Is there anything I can do to keep using batch fixes and not have to edit each file manually?
Sorry if this is the wrong section but I don't really know where to post this.
|
|
|
Post by mauvemorn on Aug 13, 2024 4:14:30 GMT -5
Hi. Could you locate one such file that cannot be fixed because of the batch fix history and share it with us?
|
|
|
Post by mylofarmer on Aug 13, 2024 11:15:23 GMT -5
|
|
|
Post by mylofarmer on Aug 14, 2024 16:01:32 GMT -5
mauvemorn have you had the chance of looking into these files?
|
|
|
Post by S4Player on Aug 15, 2024 3:02:36 GMT -5
Maybe studio has issues with the stuff because the high polygons exceeds by far what TS4 game recommends as a max of 10000.
I just looked at the ripped pants from Darte and this one has big textures and redicously high polygons. For a pair of pants ? THis is crazy. Best not to use such high polygons stuff.
|
|
|
Post by mauvemorn on Aug 15, 2024 3:52:58 GMT -5
Sorry for the wait, lost the thread
Hm, so i just ran Allow for random batch fix on Darte77_Bottom6984.package and it was successful. When i tried to look at the batch fix history right away, i saw an error. When i went back to s4s main menu and opened the package again, the error disappeared and the new batch fix was added.
Could you try this: - create a new folder on the desktop and move one such package in there; - try running a batch fix on this folder instead of mods; - if this wont work, check how much data in gigabytes there is in C:\Users\---\Documents\Sims 4 Studio\Batch Fixes
|
|
|
Post by mylofarmer on Aug 15, 2024 9:11:12 GMT -5
Thank you for getting back. I moved one folder to my desktop and ran two batches there. The first one was to allow CC for random and all files were fixed. Then I ran a second one, to disallow for random. 58 files were fixed and 16 were not. Then I moved the folder back where it belonged, opened my CC and ran change CAS display index sorted by packagename and 70 files were not fixed. But when I selected change CAS display index (not sorted by package name) 20 files were fixed and 53 were not Upon opening one of thse files, I got this in batch history fix: So I see in this last image that neither the CAS display index fixes worked for this file. Last one was Disallow for random. My batch fix backup folder is clean, I tend to delete everything from there once I see I didn't screw something up. EDITSo I was looking at this last screenshot and something stood out to me: the timestamps. First one is MM/DD/YYY, then we have a few DD/MM/YYYY and then the last two ones, from today, are MM/DD/YYYY again. I'm not a native English speaker so I set S4S to my language, which adopts DD/MM as a standart for dates. What might have happened is that when I updated it, I might have wrongfully selected it to English, which may have caused this. Would it be a possibility? Not being able to batch fix because of the date format in timestamps?
|
|
|
Post by mauvemorn on Aug 15, 2024 9:38:19 GMT -5
Does changing the language help?
|
|
|
Post by mylofarmer on Aug 15, 2024 10:04:48 GMT -5
I just tested it and yes, once I set it back to Portuguese I could fix what had become unfixable. So I'm suspicious that the timestamp has something to do with this because the files I fixed with S4S in English ere unfixable in Portuguese. This was an easy fix however because they were not so many files so I could just erase their histories manually
|
|