Question / Help Not the resolution I want

Martenj

New Member
When I record my gameplay, often Overwatch, the games doens't lag, and the outcome is acceptable. But there is one thing that's been bugging me and that is that the resolution just isn't the way how I see it whilst playing. It's kind of blurry. I'd love for one of you to look at my latest log file. Btw, my resolution in game is 1920x1080, and my monitor can only play 1920x1080, so it's nothing there

Here's my latest log file: https://obsproject.com/logs/2IAkgZsqaXcMyxC9

I don't need to have it fixed right now, but in the loading screens and the character selection screens, in Overwatch, the recording (the outcome) lags a lot. Would appreciate it if someone took at look at that too.
 

R1CH

Forum Admin
Developer
Use either game or display capture, not both. Game capture will generally perform the best. Also go back to simple mode and use one of the recording presets, as CBR is not good for recording.

DKwFejd.png
 

Martenj

New Member
Thanks alot. This helpet me with the quality, but now for some reason the final recording has gone back to lagging a lot as it did before. I asked this question before and I've done everything again, that I was told, but it keeps lagging. Do you have any solutions of why that is, and how I can fix it?

Log file: https://obsproject.com/logs/45Ml7X8jIxCuzT3u
 

Narcogen

Active Member
You still have both a game capture and a display capture in your scene. You shouldn't, this can negatively impact performance. Keep them in separate scenes or scene collections.

With your settings, you are overloading your GPU:

22:47:15.149: Output 'adv_file_output': Number of lagged frames due to rendering lag/stalls: 9186 (23.4%)
22:47:15.149: ==== Recording Stop ================================================
22:47:15.194: Video stopped, number of skipped frames due to encoding lag: 35185/39316 (89.5%)


https://obsproject.com/wiki/GPU-overload-issues

22:36:53.331: base resolution: 1920x1080
22:36:53.331: output resolution: 1920x1080
22:36:53.331: downscale filter: Lanczos
22:36:53.331: fps: 144/1


You are recording at 144fps, which is going to be seriously challenging on a single PC rig. The 1060 is a decent card but not exactly a powerhouse.

22:36:53.331: YUV mode: 709/Full

Full color is not going to look right on most displays.

22:58:24.890: [NVENC encoder: 'recording_h264'] settings:
22:58:24.890: rate_control: CBR
22:58:24.890: bitrate: 40000


As R1CH mentioned above, you shouldn't be using CBR rate control for recording. For recording with NVENC you should be using a quality setting.
 

Martenj

New Member
I have removed the display capture, I have put my recording down to 60fps, and I've gone back to simple, and am currently using "Indistinguishable Quality". But for some reason this doesn't show in my log files. And yes, I have clicked on "Apply" after I've changed the settings. I've also changed the color mode to "Partial".
As you mentioned me recording in 144fps, I've tried to record in 60fps, but then the outcome is only like 30fps.
So to summerize: The fps is good at recording at 144fps, the quality is still off, and my log files are crazy.

Here's my latest log file, if you can find anything: https://obsproject.com/logs/zjdWuYKfI7VxR2D4
 

Narcogen

Active Member
22:47:15.149: Output 'adv_file_output': Number of lagged frames due to rendering lag/stalls: 9186 (23.4%)
22:47:15.149: ==== Recording Stop ================================================
22:47:15.194: Video stopped, number of skipped frames due to encoding lag: 35185/39316 (89.5%)


I have a difficult time reconciling the assertion that "FPS is good, but quality is off" from the above session which indicates a massive number of lagged/skipped frames.

23:04:49.542: Video stopped, number of skipped frames due to encoding lag: 45696/48758 (93.7%)
23:13:06.979: Max audio buffering reached!
23:13:06.984: adding 896 milliseconds of audio buffering, total audio buffering is now 960 milliseconds (source: Desktop Audio 2)


Other entries in the log (such as the above) seem to indicate significant system overload, which is usually the cause of problems regarding increasing audio buffering.
 

Martenj

New Member
Well, now when I've watched more of the clip, I've noticed that there are some lags in the recording, but not so many that 90% of the frames are gone. But what do you want me to do? I've got no idea.
 
Top