Post by apeape on Oct 8, 2020 16:08:34 GMT -5
My apologies if what follows should be posted elsewhere. I did try and find a relevant thread I could post to but couldn't find one that seemed appropriate, or that I had permissions to post to. I also hope it's clear that I respect the work put into a software projects like S4S. I maintain several open source projects and know how thankless it can be.
I'm using Sims 4 Studio 1.3.1.6 (Apple Blossom) on macOS 10.15.6.
There are a number of issues that make most of Sims 4 Studio unusable, and I'm wondering if there are workarounds.
1. Path warning on startup.
When starting S4S, a warning is shown saying "Unable to find The Sims 4. Please configure your game path." When clicking on "OK", the Settings dialog appears, and it appears that the path settings are correct. There's nothing I've been able to do that seems to satisfy S4S.
2. Warehouse Export Issues
While in a package file's "Warehouse" view, if I click on a single item in the table view, then click the "Export" button, a "Save As" dialog appears. If I enter a file name, such as example, the exported file name will be example.* (meaning, the actual file name includes the .* as part of the name).
If I instead click on a single item in the table view, then click on "Batch Export", a "Save As" dialog appears with a file name already entered, the file name being a combination of the type, group, instance, with a file extension that describes the item type (eg. CASPreset).
That often works as a suitable workaround, but on larger packages (ie, the game's non-CC packages), that causes S4S to consistently crash.
Using the "Export" button doesn't cause S4S to crash where "Batch Export" would, but requires that you take steps to give the exported file an extension other than .*.
3. Tools - do they work?
Perhaps all of the following issues are related to the first issue related to paths? Just a guess.
Clicking on "Tools > Extract Tuning..." in the menu bar does nothing. No errors, no crashes, no extracting.
Clicking on "Tools > Game File Cruiser" in the menu bar opens the "Game File Cruiser" dialog, but nothing within the dialog seems to work. In the "Type" list, clicking on any checkbox has no effect. "Clear" clears the selections. Typing anything into the search box below the "Type" list does nothing.
Clicking on "Tools > String Table Lookup" opens the "String Table Lookup" dialog, but searching for a string does nothing.
Clicking on "Tools > Color Palette" crashes S4S.
4. Warehouse issues in general
When working with large packages (ie, ClientFullBuild6.package), scrolling the list of items tends to go smoothly for a bit, then suffers from frequent and length freezes.
I've yet to find a pattern that suggests what the issue might be. I thought at first it was related to items with the DST Image type becoming visible, but I don't think it consistently hangs when those enter the view. I think it's quite possible that there is a pattern with items with the RLE 2 Image type. If there's a single item in the visible list that's an RLE 2 image, the lag when scrolling the list is nearly unbearable and unusable.
If there's any else I can share that'd be useful, please let me know.
I'm using Sims 4 Studio 1.3.1.6 (Apple Blossom) on macOS 10.15.6.
There are a number of issues that make most of Sims 4 Studio unusable, and I'm wondering if there are workarounds.
1. Path warning on startup.
When starting S4S, a warning is shown saying "Unable to find The Sims 4. Please configure your game path." When clicking on "OK", the Settings dialog appears, and it appears that the path settings are correct. There's nothing I've been able to do that seems to satisfy S4S.
2. Warehouse Export Issues
While in a package file's "Warehouse" view, if I click on a single item in the table view, then click the "Export" button, a "Save As" dialog appears. If I enter a file name, such as example, the exported file name will be example.* (meaning, the actual file name includes the .* as part of the name).
If I instead click on a single item in the table view, then click on "Batch Export", a "Save As" dialog appears with a file name already entered, the file name being a combination of the type, group, instance, with a file extension that describes the item type (eg. CASPreset).
That often works as a suitable workaround, but on larger packages (ie, the game's non-CC packages), that causes S4S to consistently crash.
Using the "Export" button doesn't cause S4S to crash where "Batch Export" would, but requires that you take steps to give the exported file an extension other than .*.
3. Tools - do they work?
Perhaps all of the following issues are related to the first issue related to paths? Just a guess.
Clicking on "Tools > Extract Tuning..." in the menu bar does nothing. No errors, no crashes, no extracting.
Clicking on "Tools > Game File Cruiser" in the menu bar opens the "Game File Cruiser" dialog, but nothing within the dialog seems to work. In the "Type" list, clicking on any checkbox has no effect. "Clear" clears the selections. Typing anything into the search box below the "Type" list does nothing.
Clicking on "Tools > String Table Lookup" opens the "String Table Lookup" dialog, but searching for a string does nothing.
Clicking on "Tools > Color Palette" crashes S4S.
4. Warehouse issues in general
When working with large packages (ie, ClientFullBuild6.package), scrolling the list of items tends to go smoothly for a bit, then suffers from frequent and length freezes.
I've yet to find a pattern that suggests what the issue might be. I thought at first it was related to items with the DST Image type becoming visible, but I don't think it consistently hangs when those enter the view. I think it's quite possible that there is a pattern with items with the RLE 2 Image type. If there's a single item in the visible list that's an RLE 2 image, the lag when scrolling the list is nearly unbearable and unusable.
If there's any else I can share that'd be useful, please let me know.