Do you by chance use custom image packs with large size images?
Viewing post in 0.11.0a Cannot save game
I made no modification to the game at all. I resurrected the 0.10.3b version of the game to make sure nothing was wrong on my system, and that was just as snappy as ever with getting in a game after character creation, saving, and loading a file, so I ended the experiment.
As an additional point, I looked at godot.2025-5-13_16.59.58.log. That file is 128MB in size and contains 1444049 lines of text, which I believe was from me gaming for a while in 0.11.0. Almost all of the log is the following three lines:
stack sid4115958980 not found
SCRIPT ERROR: Invalid call. Nonexistent function 'remove_effect' in base 'Nil'.
at: remove_effect (res://src/character/ch_dyn_stats.gd:266) - Invalid call. Nonexistent function 'remove_effect' in base 'Nil'.
although some were this:
stack sid2441563634 not found
SCRIPT ERROR: Invalid call. Nonexistent function 'remove_effect' in base 'Nil'.
at: remove_effect (res://src/character/ch_dyn_stats.gd:266) - Invalid call. Nonexistent function 'remove_effect' in base 'Nil'.
And earlier in the file a lot of this:
SCRIPT ERROR: Invalid get index 'sid4115958980' (on base: 'Dictionary').
at: clone_stack (res://src/core/effects_pool.gd:84) - Invalid get index 'sid4115958980' (on base: 'Dictionary').
SCRIPT ERROR: Invalid get index 'sid3522193546' (on base: 'Dictionary').
at: clone_stack (res://src/core/effects_pool.gd:84) - Invalid get index 'sid3522193546' (on base: 'Dictionary').
SCRIPT ERROR: Invalid get index 'sid4241686955' (on base: 'Dictionary').
at: clone_stack (res://src/core/effects_pool.gd:84) - Invalid get index 'sid4241686955' (on base: 'Dictionary').
I do have custom images, but I have resized them to be under 500K and most are between 70K-250K; however, after the first repeat game crash destroying my save file I turned off character sprites and no further game play made use of the custom images. Should I try a play through with the bodies & portraits folders empty?
Custom images are fully removed (bodies & portraits). No joy. Still having to limit myself to a few (1-3) actions before saving into a brand new file and the program most of the time still quits out leaving a bad save file (zero bytes) without an accompanying DAT file. The actions do not seem to matter whether it is selling some items, traveling to a dungeon, entering dialogue options with NPCs, doing Dates/Sex activities, or using the craft system. Sometimes repeating actions that failed to save before are successfully saved but I cannot reliably replicate what works and what does not. 2-5 minutes to load or save plus playtime is rough for casual bug-finding. Looking at the crash report, I don't see anything that jumps out at me like what Jotok saw from the failure at Thread 0 (what the crash report indicates as the failing process).
It is running on a 2011 MacBookPro11 3, Quad-Core Intel Core i7 2.3 GHz, 16 GB RAM, macOS 11.7.10 Big Sur
Strive4Power 0.11.1 with no mods and no custom images. Paper dolls are turned off and background animations are turned off.
When I was running 0.10.3 I had no problems. From the Dev's indications, there are no problems running and saving the game with the Dev's setup. Jotok mentioned something about monitoring the system parameters while playing the game and how the observed operation taxed system resources up to 100%. Is this a stack overrun from the new code that is too much for my computer to handle?
EDIT: Jotok just pointed out a version sequential issue, and upon reviewing the source of my information and... just looking at the title screen, I am forced to admit that I do not have the latest upgrade of S4P and that I have been acting under the mistaken belief that I did and erroneously stated that I did. I have Strive4Power 0.11.0 installed.
I apologize for the additional work and stress this has caused.
Updated to 0.11.0b and the save function seems to be working through testing various actions (travel, dungeon exploration, completing quests, multiple sex/date options, NPC dialogue selections, leveling up, and equipping). The major problem is solved (at least, for me). Still have a case of The Slows, but that is much better than a terminal case of The Can't Saves.