-
Notifications
You must be signed in to change notification settings - Fork 28
"Autoplay speed" setting doesn't save #22
Comments
I'm experiencing that too, but the save game seems to preserve the setting for that play, it just doesn't seem to preserve the setting otherwise. |
I'm pretty sure this is purely a script issue. This bit is for anyone who feels like digging into it further; in the compiled script file I found the following bits of interest: %sys_auto_time is init at *title (line 249) regardless of previous value. Other, properly saved variables, are init in *first_init (1281). I don't know enough about the script to be sure if there's a deeper reason for this and it would be nice if someone who knew more could comment. All the same, thanks for the report. Sorry I've let it sit for so long, I suspected it was script-related rather than engine related from the beginning and was hoping to get confirmation. |
It definitely sounds like a script issue. It should be fine with some slight adjustment to the script. |
Is it possible that was intentional or tied to autoplay by default? |
I can't see it being intentional. NScripter is a little odd regarding which variables get saved and which don't, so it's an easy error to occur. We'll definitely take a look at it to make sure it doesn't occur in the final release. |
Actually, after playing with it some more, if you finish a chapter and select a new one in either side 1 or 2, it preserves the setting. The only time I see it reset on its own is when going to the main title screen or loading a save which preserves the setting set for that playthrough. |
The "Autoplay speed" setting in the Configuration menu does not save properly.
To reproduce:
Win7 64-bit.
The text was updated successfully, but these errors were encountered: