Question / Help Game drops frames very hard when Anti aliasing is being on

[Skajdrovski]

My target is to record a Sniper Elite game and when OBS is trying to capture the game with aa, it starting lags so much. I don't know what really is the problem because other games are fine with AA and obs

logs: https://obsproject.com/logs/G2YCFSS5vwDbg57u

 

[Narcogen]

Please post a log with your issue! Here's how...

Make sure the log includes a completed recording or streaming session.

 

[Skajdrovski]

Please post a log with your issue! Here's how...

Make sure the log includes a completed recording or streaming session.

https://obsproject.com/logs/G2YCFSS5vwDbg57u

 

[Narcogen]

No output session in log. Please make sure the log includes a recording or streaming attempt that is complete-- start, observe your issue, stop the session, upload the log. This log is the app starting up and shutting down, no output created.

 

[Skajdrovski]

No output session in log. Please make sure the log includes a recording or streaming attempt that is complete-- start, observe your issue, stop the session, upload the log. This log is the app starting up and shutting down, no output created.

Here's the latest log

 

[Narcogen]

No significant frame drops during that 15 seconds.

14:30:16.162: [NVENC encoder: 'recording_h264'] settings:
14:30:16.162: rate_control: VBR
14:30:16.162: bitrate: 50000

You would very possibly get better results from NVENC with CQP rate control, though.

Other than that, 1080p60 on a single PC rig can be challenging, and it would not be unusual to need to frame cap or turn some features off in order to achieve smooth recording.

 

[Skajdrovski]

No significant frame drops during that 15 seconds.

14:30:16.162: [NVENC encoder: 'recording_h264'] settings:
14:30:16.162: rate_control: VBR
14:30:16.162: bitrate: 50000

You would very possibly get better results from NVENC with CQP rate control, though.

Other than that, 1080p60 on a single PC rig can be challenging, and it would not be unusual to need to frame cap or turn some features off in order to achieve smooth recording.

I got my issue fixed by myself. I saw that the game were using DirectX 8 in obs logs and then I downloaded this magic dll (https://github.com/crosire/d3d8to9/releases) which turning DX 9 instead of 8 and every frame drop is gone (looks like obs isn't very compatible with DX 8). Thanks for the tips with bitrate tho :) Which value do I need to type in ,,CQP level" to get 50 MBPS ?

 

[koala]

Which value do I need to type in ,,CQP level" to get 50 MBPS ?

Quality-based rate control modes like CQP don't work like this. They take whatever they need. Bitrate-based modes like CBR or VBR work this way: they lower the encoding quality until the bitrate of the encoded video is right at the requested bitrate. This means, high motion scenes get more quality removed than low motion scenes, because the amount of video data encoded is higher with high motion scenes than with low motion scenes.
With quality-based modes, you simply tell the encoder to remove a constant amount of quality, regardless of motion. This means, low motion scenes, where barely anything changes, takes up almost no space, while high motion scenes require a large amount of data, because every single frame is very different from the previous one.
The range of all quality parameters is 0..50, which means 0=no detail removed and 50=very much detail removed.
25 is very good compression but compression visible.
22 is double the size of 25 and minimum amount of compression visible
19 is double the size of 22 and no compression visible for most material
16 is double the size of 19 and no perceived difference to the original material
Lower values than 15 don't make sense, as well as higher values than about 30. If you want raw-like quality for postprocessing, use 15-18. The exact value depends on resolution and actual material. A game that was developed for directx 8 has probably not very high detail, so 18-22 should still give you raw-like quality.

 

[Skajdrovski]

Quality-based rate control modes like CQP don't work like this. They take whatever they need. Bitrate-based modes like CBR or VBR work this way: they lower the encoding quality until the bitrate of the encoded video is right at the requested bitrate. This means, high motion scenes get more quality removed than low motion scenes, because the amount of video data encoded is higher with high motion scenes than with low motion scenes.
With quality-based modes, you simply tell the encoder to remove a constant amount of quality, regardless of motion. This means, low motion scenes, where barely anything changes, takes up almost no space, while high motion scenes require a large amount of data, because every single frame is very different from the previous one.
The range of all quality parameters is 0..50, which means 0=no detail removed and 50=very much detail removed.
25 is very good compression but compression visible.
22 is double the size of 25 and minimum amount of compression visible
19 is double the size of 22 and no compression visible for most material
16 is double the size of 19 and no perceived difference to the original material
Lower values than 15 don't make sense, as well as higher values than about 30. If you want raw-like quality for postprocessing, use 15-18. The exact value depends on resolution and actual material. A game that was developed for directx 8 has probably not very high detail, so 18-22 should still give you raw-like quality.

Thank you for clearing this out to me :)