Skip to content

Troubleshooting

This guide is in need of a revision, it is not up to our current standards

The information it provides is still likely good but we can't guarantee it.

TWO-TORIAL is a community-driven project with limited resources.
If you want to help us out, you're more than welcome to contribute!

You must obtain clean, unmodified and complete data to proceed with our guides

Corrupted or incomplete files will cause unpredictable issues we can't cover.
TWO-TORIAL does not provide or distribute game data. Do not ask.

Hardware Specs

Konami PC Type 6 (ADE-704A)

Based on an AMD Embedded R Series SoC.

CPU: Intel Celeron B810

GPU: AMD Radeon E4690

OS: Windows 7 Embedded

My Game Is Running Slow/Lagging

Make sure you at least meet the above hardware requirements, try to eliminate any unnecessary background processes during play as well.

My Game Is Running Crazy Fast!

The most common reason for this is the game is running over its required 60 Hz, the game is hardcoded to run at 60 Hz and this cannot be changed. To solve this, set your monitor's refresh rate to 60 Hz. You can always check on the game's monitor check if the game is fluctuating around 59.94hz, the NTSC standard. If it's not around there and your monitor is indeed set to 60 Hz, consider trying a different panel or forcing vsync on in your GPU's graphics settings.

Occasional Game Stutters During Play

Sometimes you might have occasional stutters during play, while solutions can vary wildly from general performance issues to bad hard drives, try adding SpiceTools -realtime parameter to your .bat file.

Which Offset Is Which?

If you're getting too many fasts, increase your offset (+). If you're getting too many slows, decrease your offset (-).

No Matter What I Do, the Game Crashes and I Have Multiple Monitors!

This problem is somewhat irregular, but sometimes Nostalgia has issues booting with multiple monitors present, particularly when trying to boot the game windowed. Make sure you're running the latest SpiceTools which has attempted to resolve all instances of this issue.