GPU usage at 70%+

[martydotzone]

Hello, is there a standard way to post these support issues, listing my hardware and whatnot? Sorry if I'm not following protocol.

Log 1:
https://obsproject.com/logs/woTxlIaWNkwFX26c
Log 2:
https://obsproject.com/logs/hkN2iKnqSEmcZbx5

Here's my PC: https://pcpartpicker.com/user/martydotzone/saved/#view=khPqhM

I usually stream retro games so I haven't had a reason to check how much OBS was using my GPU. I was streaming Elden Ring at 1440p and OBS was using about 73% of my GPU.

I use a plug-in called Aitum Multistream to stream to Twitch and YouTube, and I locally record at the same time too. Without the local recording, GPU usage is at about 63%.

I also use Advanced Stream Switcher and Stream Elements.

I've checked the following things I've seen to do:
- OBS is running in admin mode
- Game Mode is enabled in Windows 10.0.19045
- Hardware-accelerated GPU scheduling is enabled
- I don't have a ton of overlays, effects, filters, browser sources etc, I don't think. Didn't even have a webcam on for this stream.
- Game is captured with Window Capturing

I was told this 4060 RTX has a dedicated chip to handle all the video encoding. If it weren't working properly, I'd get a notification of that right? What percentage of GPU should OBS be using?

If someone skilled at reading the log could take a look, that would be much appreciated. Thank you! :)

 

[rockbottom]

Your set-up needs some clean-up. See anything wrong with this Scene? Most of of them are in the same sinking boat. Only (1) Display, Game or Window capture should be used per Scene.

21:13:43.166: - scene 'Game 16:9':
21:13:43.166: - source: 'bacgr 2' (image_source)
21:13:43.166: - source: 'DS2' (game_capture)
21:13:43.166: - source: 'ER' (game_capture)
21:13:43.166: - source: 'Elden Ring' (window_capture)
21:13:43.166: - source: 'IWD' (game_capture)
21:13:43.166: - source: 'BG3' (game_capture)
21:13:43.166: - source: 'BG2' (game_capture)
21:13:43.166: - source: 'BG1' (game_capture)
21:13:43.166: - source: 'Logi Brio Main Facecam' (dshow_input)
21:13:43.166: - filter: 'Chroma Key' (chroma_key_filter_v2)
21:13:43.166: - source: 'Win98Japan - Discovera' (window_capture)
21:13:43.166: - source: 'VG27A' (monitor_capture)
21:13:43.166: - source: 'WebcamBorder' (color_source_v3)
21:13:43.166: - source: 'Logi Webcam' (dshow_input)
21:13:43.166: - source: 'Goal' (browser_source)
21:13:43.166: - source: 'Scarlet 2i2' (wasapi_input_capture)
21:13:43.166: - filter: 'Compressor' (compressor_filter)
21:13:43.166: - filter: 'Limiter' (limiter_filter)
21:13:43.166: - filter: 'Compressor 2' (compressor_filter)
21:13:43.166: - source: 'StreamElements chat' (browser_source)
21:13:43.166: - source: 'StreamElements Alerts' (browser_source)
21:13:43.166: - source: 'Sounds' (browser_source)
21:13:43.166: - source: 'Twitch Alerts' (browser_source)
21:13:43.166: - source: 'Image' (image_source)
21:13:43.166: - source: 'VLC Player' (window_capture)

Also, uncheck hardware acceleration for all of your Media Sources. This will free up addition VRAM.

 

[martydotzone]

Thank you, I thought if a source wasn't visible then OBS wasn't using resources to capture it until you made it visible. Is that not the case?

Just for anyone else trying to solve their own problem in the future, I didn't realize that Look-ahead, Adaptive Quantization, and Multipass would use the main 3D rendering resources on my GPU.