The Quick Answer
| Common Issue | High rendering lag in OBS despite smooth in-game FPS |
| Primary Fix | Disable Twitch Enhanced Broadcasting |
| Key Setting | Cap in-game framerate to 60 FPS |
| Encoder | NVENC H.264 at 6000 kbps (Expected best choice) |
The Single-PC Streaming Struggle
Streaming visually demanding, atmospheric titles on a single-PC setup often comes with a steep performance cost. Several content creators and players exploring the subterranean horrors of The Mound: Omen of Cthulhu are encountering a frustrating discrepancy: the game feels perfectly smooth on their own monitor, but the broadcast output in OBS Studio or on Twitch is plagued by heavy freezing, constant buffering, and severe rendering lag.
Based on recent community reports, this isn't an isolated hardware failure or a random bug. The issue stems directly from how aggressively the game consumes GPU resources, leaving OBS starving for the rendering overhead it needs to compose the stream. While we wait for official optimization patches—as the game is still in its pre-release and active development phase—the community has already identified several reliable workarounds. If your stream statistics are showing dropped frames and rendering delays upwards of 26 milliseconds, you need to adjust both your in-game configuration and your broadcasting software settings to restore stability.
Understanding Rendering Lag vs. Encoding Lag
Before changing any sliders, it helps to know exactly what is failing in your setup. OBS Studio relies on your graphics card for two distinct tasks: rendering the scene (compositing your game, webcam, alerts, and overlays into a single canvas) and encoding that finalized video to send to Twitch or YouTube.
When streaming The Mound, players are primarily reporting high rendering lag rather than encoding lag. One community member noted that their OBS statistics showed up to 18% of frames missed entirely due to rendering delays, dropping the stream output to around 24 FPS while the game itself maintained a smooth frame rate locally.
This happens because the game's dynamic lighting, volumetric fog, and detailed expected system requirements push your GPU utilization to 99%. When the GPU is maxed out, OBS simply cannot render the stream canvas in time for the next frame. The solution is forcing the game to leave a small slice of GPU performance available for background applications.
Crucial Fix: Disable Twitch Enhanced Broadcasting
One of the most significant breakthroughs for stabilizing the stream comes from disabling a relatively new feature: Twitch Enhanced Broadcasting.
Twitch Enhanced Broadcasting attempts to create multiple resolution encodes (like 1080p, 720p, and 480p) simultaneously on your local machine using your GPU's encoder. The goal is to provide multiple quality options for your viewers without relying on Twitch's servers to transcode the video. While this is a great feature for lighter titles, it places an enormous, multiplied strain on your hardware.
Community testing indicates that turning off Enhanced Broadcasting is the single most impactful fix right now for this specific title. After disabling it, some streamers reported their rendering time plummeting from a sluggish 19.2 ms down to a highly stable 4.8 ms, with rendering lag dropping from 13.2% to under 0.8%.
To disable this feature: - Open OBS Settings and navigate to the Stream tab. - Uncheck the box labeled "Enable Enhanced Broadcasting." - Switch back to a standard single-output stream configuration. - Acknowledge that viewers will now rely on standard Twitch transcoding (if available to your channel status).
Optimize Your OBS Studio Configuration
Beyond Twitch-specific features, you need to configure OBS to aggressively defend its own resource allocation. Windows will naturally prioritize the foreground application (the game), so you have to manually tell the operating system that OBS is just as important.
Run OBS as Administrator
Always right-click OBS Studio and select "Run as Administrator." This is not a placebo; this simple step allows OBS to allocate GPU resources more effectively at the driver level, preventing the game from entirely suffocating the broadcast software during heavy scenes.
Set Process Priority
Inside OBS Settings, go to the Advanced tab. Look for the "Process Priority" dropdown and change it from Normal to "Above Normal" or "High." This ensures that when the CPU and GPU are deciding which task gets processing time first, OBS is near the top of the list. This heavily reduces frame drops during intense combat scenarios or when numerous hostile creatures suddenly appear on screen and spike the engine's resource demands.
Use Game Capture Instead of Display Capture
Avoid using Display Capture whenever possible. Capturing your entire desktop introduces unnecessary overhead, forces the Windows Desktop Window Manager to work harder, and can cause severe visual stuttering. Add a "Game Capture" source in OBS, set it to "Capture specific window," and select the game's executable. This hooks directly into the graphics pipeline and is far more efficient for modern titles.
Fine-Tuning Encoder Settings
For a standard, stable broadcast without Enhanced Broadcasting, the community recommends the following baseline settings to minimize GPU load: - Encoder: NVENC H.264 (if you are on an NVIDIA card, as it uses a dedicated hardware chip separate from the 3D rendering cores). - Resolution: 1080p output (scaled down using Lanczos filtering if playing at a native 1440p). - Frame Rate: 60 FPS. - Bitrate: 6000 kbps (CBR) – ensure you aren't confusing network dropped frames with rendering lag. If your internet connection cannot stably handle 6000 kbps, drop down to 4500 kbps at a 720p output. - Preset: P5 (Slow / Good Quality) – Avoid P6 or P7. The highest presets introduce multipass encoding that wastes critical GPU resources for negligible visual gains. - Look-ahead and Psycho Visual Tuning: Disable both of these checkboxes in the NVENC settings. While they can improve visual quality in high-motion games, they utilize the CUDA cores on your GPU—the exact same cores the game desperately needs to render its lighting and geometry.
Tweaking In-Game Graphics for Stream Stability
Even with OBS perfectly tuned, you still need to create headroom on your graphics card. If you let the engine render as many frames as it possibly can, it will always reach maximum utilization.
The Golden Rule: Cap Your Frame Rate
The single most effective way to eliminate rendering lag in OBS is to cap the in-game frame rate. If your monitor is 144Hz and the game is running at 120 FPS, it is using every ounce of processing power available. Capping the game to 60 FPS (or 90 FPS, depending on your hardware headroom) artificially limits GPU usage to around 70-80%. That remaining 20% margin is exactly what OBS needs to composite and render the stream canvas smoothly without stuttering.
Never play with an uncapped frame rate when streaming from a single PC, especially not in unreleased or early-build games that haven't received their final optimization passes.
Lowering Volumetrics and DLSS
The Mound: Omen of Cthulhu leans heavily on dark, atmospheric lighting. The subterranean environments are filled with dynamic light sources, reflections on wet cave walls, and complex shadows. While it looks incredible, it is mathematically demanding. - DLSS / FSR: Ensure DLSS or FSR is enabled. If you were playing on the "Quality" preset, consider dropping it to "Balanced" or "Performance." One streamer noted that lowering DLSS from High to Low/Medium settings immediately stabilized their Twitch output and eliminated rendering lag. - Shadows and Fog: These are the usual suspects for tanking performance. Dropping volumetric fog and shadow resolution by one tier will barely impact the visual experience for your viewers—who are watching a compressed video feed anyway—but will claw back significant rendering headroom. - Window Mode: Ensure you are playing in exclusive Fullscreen mode, or test Borderless Windowed if Fullscreen causes alt-tab capture issues. Some users report slightly better hook performance in standard Fullscreen.
Addressing Audio Desync Issues
A common side effect of severe rendering lag that many streamers overlook until they review their VODs is audio desync. When OBS drops video frames because the GPU is overloaded, the audio track (which requires almost zero GPU power and relies entirely on the CPU) continues to record and broadcast in real-time. Over a long streaming session, this mismatch causes your microphone reactions and the in-game sound effects to drift further and further away from the visual action.
If you are fighting monsters and your viewers hear your screams three seconds before the creature even appears on the stream, rendering lag is the culprit. Fixing the GPU overload using the methods above—specifically capping the frame rate and lowering DLSS—will naturally resolve the audio drift. However, if you want an extra layer of protection, ensure that your audio sample rates in Windows Sound Control Panel and OBS Audio Settings match perfectly (usually both set to 48 kHz). This prevents the CPU from having to resample audio on the fly, saving a tiny bit of processing overhead and maintaining perfect sync.
Co-op Streaming Considerations
If you are putting together a squad for a co-op multiplayer session, remember that hosting the lobby might add slight CPU overhead. While network traffic doesn't directly impact GPU rendering lag, any heavy CPU usage can occasionally cause frame pacing issues and system interrupts. If your PC is already struggling to handle the OBS encode and the game simultaneously, let one of your friends host the session. The client-side load is typically much lighter than acting as the authoritative host for enemy AI and player positions.
Looking Ahead
Because The Mound: Omen of Cthulhu is still undergoing active development and community testing, these performance quirks are entirely expected. Developers often optimize resource management, refine volumetric lighting costs, and add better capture hooks as a game approaches its final build.
For now, content creators will need to make minor visual compromises to ensure their audience can actually watch the broadcast. By disabling Enhanced Broadcasting, running OBS as Administrator, strictly capping the in-game frame rate, and tweaking your upscaling settings, you can completely eliminate the severe freezing and delay issues currently frustrating the community. Do not let technical hurdles stop you from sharing the cosmic horrors lurking below.
Sources
- Community performance reports regarding OBS streaming and rendering lag.
FAQ
Why is my stream lagging even though The Mound runs smoothly on my screen?
This happens due to rendering lag. The game is utilizing nearly 100% of your GPU, leaving OBS with insufficient resources to composite and render the stream frames. Capping your in-game frame rate is the most effective solution.
Should I use Game Capture or Display Capture in OBS?
Always use Game Capture for The Mound: Omen of Cthulhu. Display Capture is less efficient and can introduce unnecessary input delay and rendering overhead.
Does hosting a multiplayer lobby affect my stream?
It can. Hosting a session increases CPU overhead. If your system is already struggling with encoding, it is expected that letting a friend host will improve your overall stream stability.