I've no first-hand experience as to how Destiny 2 is for hardware resource usage (Optimized or runs like a dog with 3 legs/Console port) Benchmarks seem to put your fps output with default High Settings to roughly 80-120 fps range, for your PC setup.
I noticed you are using Window/Desktop capture, does Game Capture not work with Destiny 2? If it does, it is much better as Game Capture directly hooks into the game, instead of rendering everything you see, including Browsers, other programs and the desktop.
The single largest factor which will help you stabilize your Recording output is capping your fps to 60-63 (V-Sync induces input lag, use a program such as MSI Afterburner of EVGA Precision to cap your fps, 61-63 to try and mitigate any frame tearing if your monitor suffers it) - Note - The suggested fps cap limit is to limit GPU load as much as possible, whilst providing enough fps to allow for consistent smooth recording output. You could try capping your fps output to 75-85, it will help a little and will likely feel a bit more responsive on your monitor than ~60fps.
You could try reducing your in-game graphics settings, this will also assist in reducing GPU load.
As for the below changes, it won't help a lot though will reduce slightly the dropped frames. What it will do is give you a good base to tweak parameters from.
In Video Settings:
- Change your downscale filter to Bilinear.
In Advanced Settings:
Under Video:
- Change your YUV colour space to 709 (1080p and above uses it, 601 is 720p and below)
- Change your YUV colour range to Partial (Full adds extra workload, not really necessary unless you have a lot of banding issues with Contrast/Colour Output/ Just want maximum picture quality at the expense of performance)
-- Note: Partial is 15-235, Full is 0-255 Colour Space range, your GPU driver settings have to be running Full Colour Range for it to be seen by you (Crimson ReLive CP - They always reset it every driver update)
In Output Settings:
Using Output Mode: Advanced
Under the Recording tab:
- Change your Recording Format to .flv, there is no need for .mp4 file format and if your Game/OBS/PC crashes on you you lose your recorded footage, with .flv format you can retain what you recorded. OBS Studio comes with a built in Recording Re-Muxer, so you can convert to .mp4 if really needed for compatibility. You can locate it under File tab (Not in Settings, main window)
- Change your Preset to Recording, then select the blank preset so it automatically saves future changes to the settings below:
Be sure to test with multiple passes each change, so you have a reasonable idea of performance output with each setting:
Encoder Settings to change:
First, change View Mode to Advanced, this will allow for more settings to fine-tune.
For Variable Bitrate Latency Constrained Rate Control Method:
- Change your Target Bitrate to 50,000Mb/s <--- Adjust higher if no encoded/rendered frames dropped, lower if there are.
- Change your Peak Bitrate to 90,000Mb/s
- Change your Minimum QP to 0
- Change your Maximum QP to 42
For Constant QP Rate Control Method: (Change both to the same value)
- Change your I-Frame QP to between 15-23 <--- Adjust lower if no encoded/rendered frames dropped, higher if there are.
- Change your P-Frame QP to between 15-23 <--- Adjust lower if no encoded/rendered frames dropped, higher if there are.
Try OpenCL Transfer enabled, it seemed to help me stabilize the final output after tweaking other settings in BF4 on my i5 2500 non-k skew and r9 290X. Make sure to test each change for a good few minutes, best to revert the change before testing another so you can see the effect from a base.
Upload another logfile like your last (Perfect logfile to upload) and we'll go from there.
