Waterpark Simulator Troubleshooting

Troubleshoot Waterpark Simulator by preserving evidence first, then following the narrowest official path. CayPlay’s pinned Steam support post provides exact Windows locations for save files, the complete game-data folder used for black-screen reports, the crash-log folder, and the support email. Those game-specific instructions are more reliable than a generic list of registry edits, compatibility flags, or third-party cleanup tools.

This hub covers Steam base-game AppID 3293260 on the native Windows public 1.0 branch. Steam Deck and Proton reports do not prove native Linux support, and the audit’s compatibility snapshot predates 1.0. Controller support is listed by Steam, but per-screen prompts and hardware behavior still require current testing.

Protect the save before changing anything

For a lost or corrupted park, use the save recovery guide. CayPlay identifies the folder as:

%userprofile%\AppData\LocalLow\CayPlay\WaterparkSimulator\slots

The folder can contain an .es3 save and up to ten .bac backups. Copy the files to another location before renaming. Never test recovery on the only copy.

CayPlay’s example renames park.es3.bac1 to park.es3. Windows may warn that the extension is changing. The developer also warns that the filename must not contain spaces: park_2.es3 or park2.es3 can be recognized, while park 2.es3 is not.

Try one copied backup at a time, beginning with the candidate you intend to test. If the game still does not recognize the park, restore the untouched originals and contact CayPlay.

Handle a black screen with the official sequence

CayPlay’s pinned post directs players who see a black screen when entering the game to the main-menu video settings. Try the changes one at a time:

1. Lower quality settings.
2. Enable V-sync.
3. Change window mode to borderless fullscreen.

Launch after each single change so you know which one affects the result. Do not change drivers, delete configuration, and add launch options simultaneously; that removes the evidence.

If the official steps do not work, CayPlay asks for the Waterpark Simulator folder at %userprofile%\AppData\LocalLow\CayPlay\WaterparkSimulator and an explanation sent through support email or Discord. Compress a copy if requested, inspect it for personal material, and send it privately rather than posting it in a public discussion.

Preserve crash evidence

For crashes, CayPlay asks for the contents of:

%localappdata%\Temp\CayPlay\WaterparkSimulator\Crashes

Copy the relevant crash folder before relaunching repeatedly. Record what you were doing, whether the park was new or existing, public version 1.0, difficulty, single-player or co-op, host or client, and whether mods were installed.

Send the copied crash content privately to support@cayplay.com or through the developer’s supported Discord route, together with the reproduction. Do not publish crash dumps or personal directory contents on a public page.

The official 1.0 notes mention broad memory and performance improvements, but that does not prove every crash is fixed. Preserve the actual current evidence.

Diagnose a launch or performance problem safely

Confirm that Steam is launching AppID 3293260 and that the public branch is selected. The base game is native Windows and lists Windows 10 64-bit, DirectX 11, and 20 GB available storage in current store requirements.

Use Steam’s supported file-verification feature if installation damage is suspected. Reproduce with third-party mods disabled if possible, because mod compatibility is version-specific and unsupported code can obscure the base-game result.

Change one graphics option at a time and record the outcome. Avoid promising that a driver version, Proton version, or launch flag is universally best; no current 1.0 hardware matrix was established in the audit.

If the issue only occurs on one park, copy the save before testing another backup. If it occurs before any park loads, preserve the game-data or crash folder named by CayPlay.

Separate staff behavior from a technical failure

An idle employee may lack an assignment, path, open workplace, or eligible task. Use the staff guide to verify duty, access, demand, and workload before treating it as a bug.

For a reproducible staff issue, record the staff type, assigned area or workplace, expected task, visible accumulated work, save, difficulty, and current public version. A short clip can show access and behavior better than a general statement that “staff do nothing.”

Do not hire several extra workers or redesign the whole area during the test. One controlled reproduction is more useful to support.

Keep controller and Steam Deck claims bounded

The current Steam metadata lists controller support and the audit records DualShock/DualSense categories from official app details. That confirms a store-level feature, not that every menu prompt or remapping path works on every device.

The audited Steam Deck compatibility snapshot was based on a pre-1.0 build and mentioned manual configuration and small text. It must not be generalized to current 1.0. SteamOS play through Proton also does not make Linux a native platform; Steam currently lists Windows as native and macOS/Linux as not native.

When reporting a controller or Deck issue, include device, connection method, Steam Input state, public game version, screen where input fails, and whether keyboard/mouse still works. Avoid a blanket “supported” or “unsupported” verdict from one device.

Treat mods as an isolated variable

Mods, loaders, and trainers are third-party. A mod version is not a Waterpark Simulator semantic version, and a trainer is not a redemption-code feature. Back up saves before installing or updating unofficial code.

When the game updates, reproduce a problem without mods before reporting it as a base-game defect. Restore mods one at a time only after the unmodified public branch works. Follow the mod author’s current instructions and do not infer that an old loader supports 1.0.

Never download an executable from a page that pretends to be CayPlay support. Official game support routes are the Steam community surface, support email listed by CayPlay, and developer-controlled links.

Know the Demo save boundary

The separate Demo is AppID 3730180. Its Steam page says it was updated July 31, 2026, that old demo saves are incompatible with the new demo, and that new demo saves can open in the full version. Once opened in the full version, they cannot be reopened in the Demo.

That is a one-way product boundary. Copy a Demo save before opening it in the full game, and do not use base-game recovery instructions to promise that an old pre-update Demo file can be converted.

Build a useful support report

Include the exact game and AppID, public version label, Windows version, CPU/GPU/RAM when relevant, save and difficulty, solo or multiplayer role, mods, the shortest reproduction, expected result, actual result, and visible error.

Attach only the specific folder CayPlay requests. Preserve originals, compress copies, and send them privately. Mention what official checks you already tried so support does not need to repeat them.

Search the Steam discussions first as CayPlay recommends, but distinguish a player workaround from a developer instruction. A repeated community fix still needs a version and risk boundary.

Troubleshooting answers

Where are the saves?

%userprofile%\AppData\LocalLow\CayPlay\WaterparkSimulator\slots

Where are crash logs?

%localappdata%\Temp\CayPlay\WaterparkSimulator\Crashes

What should I try for a black screen?

Lower quality, enable V-sync, then try borderless fullscreen, one change at a time, as instructed by CayPlay.

Is Steam Deck support current?

The available compatibility snapshot predates 1.0, so current Deck behavior requires retesting. The game is not listed as native Linux.

Where can I get official help?

Use CayPlay’s pinned Steam support thread and support@cayplay.com. Send requested logs privately.

Sources checked 2026-08-02: CayPlay pinned support, official Steam store, and Demo store page.