Frames missed / skipped when recording Destiny 2

[Airsucker]

Previous Log Files - https://obsproject.com/logs/ANUwwX5NOY7OVbm8
Current Log Files - https://obsproject.com/logs/E146gI3rjW55W1sJ

Hey all, I linked my log files for my recent attempt at using OBS. Honestly since Destiny hit EOL with the last update, it's affected my ability to stream or view streams significantly. I'm hoping I can at least fix my ability to record. I noticed significant frames missed due to rendering lag upwards of 30% and skipped frames due to encoding lag in the same ball park.

RTX 2070
i7 9700
32 gb DDR4

Hardware accelerated gpu scheduling is already off and has been for some time. I've never had issues streaming or recording before a month or so ago.

 

[rockbottom]

Current log lacks a encoding session.

Previous log, Rendering Lag is GPU Overload & there's plenty of it. Your encoding lag is a result of it & the fact that your overloading your CPU too. Load reduction is in order.

13:08:41.892: [ffmpeg muxer: 'simple_file_output'] Writing file 'I:/Videos/2026-07-18 13-08-41.mkv'...
13:09:44.281: [ffmpeg muxer: 'simple_file_output'] Output of file 'I:/Videos/2026-07-18 13-08-41.mkv' stopped
13:09:44.281: Output 'simple_file_output': stopping
13:09:44.281: Output 'simple_file_output': Total frames output: 1918
13:09:44.281: Output 'simple_file_output': Total drawn frames: 1873 (3743 attempted)
13:09:44.281: Output 'simple_file_output': Number of lagged frames due to rendering lag/stalls: 1870 (50.0%)
13:09:44.282: Video stopped, number of skipped frames due to encoding lag: 1813/1936 (93.6%)
13:09:44.282: ==== Recording Stop ================================================
13:11:29.283: adding 106 milliseconds of audio buffering, total audio buffering is now 106 milliseconds (source: Game Audio)

1) Disable Game DVR, it's not needed & you might save some resources for something else.

2) Until there is no Rendering Lag, run all of your monitors @ 60HZ, this will reduce/eliminate the overload on your CPU. You may be able to run your main monitor @ 120HZ when using OBS but don't go higher. 9700 is far from elite, see link.

3) Fix your sample-rate mis-matches. Also disable "Use Device Timing" for Discord audio. You're already using the Device Timing of Game audio.

13:07:44.165: WASAPI: Device 'SteelSeries Sonar - Microphone (SteelSeries Sonar Virtual Audio Device)' [48000 Hz] initialized (source: Mic)
13:07:44.178: WASAPI: Device 'SteelSeries Sonar - Gaming (SteelSeries Sonar Virtual Audio Device)' [96000 Hz] initialized (source: Discord)
13:07:44.179: WASAPI: Device 'SteelSeries Sonar - Gaming (SteelSeries Sonar Virtual Audio Device)' [96000 Hz] initialized (source: Game Audio)

13:07:44.117: [win-wasapi: 'Discord'] update settings:
13:07:44.117: device id: default
13:07:44.117: use device timing: 1
13:12:34.640: [win-wasapi: 'Game Audio'] update settings:
13:12:34.640: device id: default
13:12:34.640: use device timing: 1

4) Use Game Capture if possible, far more performant than Display Capture.

Test

Encoding Performance Troubleshooting | OBS

OBS Knowledge Base. Learn best practices to solve encoding performance issues

obsproject.com

Does Refresh Rate Affect CPU Usage? (60Hz vs 240Hz)

Thinking of upgrading to a 240Hz or 360Hz monitor? Read this first. High refresh rates punish your CPU much more than your GPU.

calculatebottleneck.com