| 1 | | I created a PR with a possible fix for this here: |
| 2 | | https://github.com/scummvm/scummvm/pull/3424 |
| | 1 | The forum thread provides more context for this issue, and it seems that a fix will not be as easy as I thought. |
| | 2 | |
| | 3 | For context I'm linking here the original discussion for this on sourceforge: |
| | 4 | https://sourceforge.net/p/scummvm/feature-requests/94/ |
| | 5 | |
| | 6 | In addition, when the scumm scripts forcefully enable and disable showing "subtitles", scummvm updates the configuration values too. See: https://github.com/scummvm/scummvm/blob/62dbb28aa383e99ca74509e8aa30f3b84b70f2a5/engines/scumm/script.cpp#L617 |
| | 7 | eg. |
| | 8 | {{{ |
| | 9 | ConfMan.setBool("subtitles", !value); |
| | 10 | }}} |
| | 11 | |
| | 12 | This means that skipping certain cutscenes that do this (forcefully enabling and disabling subtitles) or letting them play in full will potentially result in different values for the ScummVM confman "subtitles" key, probably overriding and overwriting the user's explicit setting. |
| | 13 | |
| | 14 | I guess it's a good thing there's the F9 hotkey as a workaround for this frustration -- even though it won't work for the intro text. |
