Belmont's Curse Launch Fixes: PC Startup, Title Screen & Steam Deck

Match the symptom before changing settings

Konami's October 14 notice identifies three separate problems. Match the platform and trigger before applying a workaround. A startup failure, an existing save blocked at the title screen and a partially cropped interface need different responses.

These are publisher workarounds, checked on October 18, 2026. PlayBloo has not reproduced the issues, and the notice does not confirm that a patch has resolved them.

PC will not launch with V-Sync off and Unlimited FPS

For Steam and Xbox on PC, Konami identifies a startup failure when V-Sync is off and the frame-rate limit is Unlimited. Its workaround is:

• Temporarily set the monitor's Windows refresh rate below 60 Hz.
• Launch the game and open Settings from the title screen.
• In Video Settings, enable V-Sync, then close the game.
• Restore the monitor's original refresh rate and launch again.

Cannot continue from the title screen after saving

On PS5, Xbox Series X|S, Steam and Xbox on PC, certain system languages, mainly Arabic, can block progress past the title screen after saving and returning there. Konami advises changing the system language to a supported option such as English to continue with the existing save.

Steam Deck interface is partly off-screen

Konami confirms that some Steam Deck UI elements can appear partly off-screen. The notice says a fix is under investigation and provides no Deck-specific workaround. It does not establish a resolution or scaling preset that fixes the problem.

For a different PC problem, check the baseline

These are Steam's published Windows requirements, not a measured performance target. Meeting them does not prove that a particular crash shares the V-Sync trigger. Check the current installation and update state, then note what happens before the failure: before any window opens, during the title screen, or after loading a save.

If the workaround does not resolve it

Prepare a short report with the platform or PC store, game version, exact point of failure, display settings and system language. Record which steps changed the behavior. That makes a support request easier to investigate and avoids treating unrelated symptoms as the same bug.