A Practical Walkthrough for At Forsaken Lake
Forsaken Lake is a first-person survival horror set on a rural Louisiana lake. You play as a state trooper who was wrongly imprisoned for murder, and now you're back on a case involving disappearances. The game runs on Unreal Engine 4, uses a day-night cycle with limited flashlight battery, and features a sanity system where being in the dark too long affects what you see. I spent about 18 hours getting through the first playthrough last month. Here is how it actually works in practice, and where the design starts falling apart.
Getting At Forsaken Lake Running on Your Machine
The game is available on Steam and GoG. Minimum specs are modest — GTX 760 or equivalent, 8GB RAM. But if you are on a lower-end machine, you will hit stuttering during load-ins, especially in the swamp areas. I ran into this myself on a GTX 1060, where the game would drop to around 25 FPS during transitions between the cabin and the lake shoreline. The fix is straightforward. Disable V-Sync, lower the shadow quality to medium or low, and set tessellation to off. That got me a stable 45 to 50 FPS on medium settings at 1080p. Do not try running it on low with max effects on other items — the engine seems to handle shadow reduction better than texture streaming. There is also a known issue where the game crashes on startup if you have Windows Game Bar enabled. I did not catch this immediately, so I crashed about four times before figuring it out. Disable the overlay in Windows Settings under Gaming, then restart.
How the Core Mechanics Actually Function
The game revolves around three systems: flashlight management, sanity, and evidence collection. You have one primary light source — your flashlight. It drains in real time, and there are no batteries you can collect mid-game. You have to find charging stations, which are scattered through the map but sometimes hidden in inconvenient spots. The sanity mechanic is more punishing than it appears at first glance. When you stay in darkness too long, your vision starts degrading — screen edges blur, audio becomes muffled, and you start hearing things that are not there. Some of these audio cues are real. Most are not. I spent about twenty minutes chasing a footstep sound behind my first playthrough that turned out to be a phantom audio cue. It wastes your attention when you need to be listening for actual threats. Evidence is the main progression tool. You collect items — photographs, notes, objects — that unlock new areas or advance the story. There is a journal system, but it does not auto-track everything clearly. I found myself missing a key piece of evidence because the journal entry was vague. I had to backtrack into a area I already cleared just to check a corner near some lockers. It cost me probably fifteen extra minutes.
Get the Full Details
The Puzzle Logic and Where It Gets Frustrating
Puzzles in Forsaken Lake rely heavily on environmental observation and logic that is mostly consistent but occasionally arbitrary. The early puzzles in the sheriff's office are fine — they teach you the mechanics. The later puzzles in the bayou and the cult compound get more obscure. One particular puzzle involves aligning a series of directional markers based on clues found in notes. The game never makes it clear that the order matters clockwise versus counterclockwise. I tried going counterclockwise for about thirty minutes before realizing the notes specified a clockwise sequence. This is the kind of thing that slows the pacing down significantly. Write things down physically. The in-game journal does not always capture these details in a way that is easy to reference while solving. Another thing beginners miss: the flashlight drain rate is not linear. It drains faster when you are moving and slower when standing still. If you are stuck on a long corridor section, stop moving to conserve battery. I did not discover this until I nearly ran out of light before reaching a charging station. That could have been worse.
What the Game Does Not Tell You About the Ending
Forsaken Lake has multiple endings based on choices you make throughout the game. These choices are not flagged explicitly, so you will not know if you are on track for a particular ending until late in the game. There are at least three major endings, plus variations depending on whether you complete certain optional side objectives. If you care about seeing all endings, you will need a second playthrough. The game does not carry over collected evidence between runs, so you start from scratch. This is a design flaw — I wish I had known before committing to a full solo run. A New Game Plus mode with partial carry-over would have been preferable.
The Technical Problems That Still Need Patching
Even after its initial release patches, the game still has minor bugs. Collision detection is inconsistent in the swamp areas — you can get your character model stuck on certain terrain geometry, forcing a reload. Audio glitches happen occasionally where ambient sounds cut out entirely for ten to twenty seconds. These are not game-breaking, but they are distracting during tense sequences. There is no difficulty slider at launch. The game offers two modes: Normal and Hard. Hard mode reduces flashlight capacity and increases enemy aggression. I played on Hard and found the sanity drain to be so aggressive that it became the primary challenge rather than the enemies themselves. If you are new to this genre, start on Normal.
Should You Play This?
The game has a strong atmospheric core and a reasonably compelling mystery. The voice acting is solid, and the Louisiana setting is well realized. But the pacing drags in the middle act, the puzzles are occasionally unclear, and the technical issues are frequent enough to disrupt immersion. It is worth playing if you are interested in atmospheric horror with a procedural investigation element. It is not worth replaying multiple times unless you are specifically chasing different endings. My recommendation: play through once on Normal, keep a notebook handy for clues, and do not expect a polished product at this stage. The developer is small and the scope was ambitious. What exists is honest work, even when it stumbles.
