Depth Of Field bug in cutscenes

[sh3f4n96]

Hi,

today I've made some performance tests to get better fps for SH3 and decided to disable DOF using the DisableDOF parameter inside the .ini file. I just set it to 1 then started making some tests and everything seemed to be correct (no more DOF effect and fps boost, much better).

After this I just started a new game, skipped immediately the very first nightmare scene and checked out the second scene (the one in which Heather appears for the first time and walks among the rabbit costumes). No problems found, the DOF effect was properly disabled... really nice. Here is a screenshot :

Then by chance I closed the game, opened the main menu, started again a new game but without skipping the first nightmare scene... Unfortunately I came accross a bug, the second scene had DOF enabled! Here is a screenshot :

So I decided to check again the .ini file to make sure, but DOF was disabled as I requested...

Then I tried to make more tests, even used a different video card, but DOF was still enabled in that scene...

Finally I found out how DOF gets enabled, even though the .ini file has the DisableDOF parameter set to 1...

• if you skip the first cutscene BEFORE the horse appears, DOF will be correctly disabled.
• if you skip the first cutscene AFTER the horse appears or if you don't skip it, DOF will always get re-enabled! That's so weird.... and the worst thing is that DOF will stay enabled during gameplay and in every following cutscene unless you reboot the game!

In my opinion, the horse frames are supposed to use DOF by code and, when the horse appears, DOF gets forced again. But this is just an assumption...

@07151129 have you ever noticed this issue previously? I tried to figure out if this glitch also happens with WidescreenFix but it seems that there's no option in it to completely disable DOF. In any case, you should be able to replicate it just by following the instructions above.

If this can help, here are my .ini file settings : INI Settings.txt

The biggest problem in my opinion : probably that cutscene is not the only one to force DOF back, so there could be more scenes with this problem. I don't know much about how difficult it can be to find a way to manage this exceptions, but it doesn't seem to be simple...

Please let me know if everything is clear and if you are able to replicate this bug. Thank you so much.