OBS renders even when not streaming or recording.
You have a modest computer and GPU and you are overloading it:
16:50:46.681: adding 85 milliseconds of audio buffering, total audio buffering is now 170 milliseconds (source: loop webcam)
16:50:46.681:
16:50:46.767: adding 704 milliseconds of audio buffering, total audio buffering is now 874 milliseconds (source: sfondo)
16:50:46.767:
16:50:47.225: adding 21 milliseconds of audio buffering, total audio buffering is now 896 milliseconds (source: sfondo)
Increasing audio buffering during a stream is usually a sign of general system overload.
16:50:45.442: - scene 'Halo 2':
16:50:45.442: - source: 'Cattura schermo' (monitor_capture)
16:50:45.442: - filter: 'Crop/Pad' (crop_filter)
16:50:45.442: - source: 'Elgato' (dshow_input)
16:50:45.442: - source: 'Apex' (window_capture)
16:50:45.442: - source: 'dead' (window_capture)
16:50:45.442: - source: 'casgo' (game_capture)
16:50:45.442: - source: 'Halo 2 game' (game_capture)
16:50:45.442: - source: 'escape' (game_capture)
16:50:45.442: - source: 'Webcam C920' (dshow_input)
You've got multiple game captures, window captures, and monitor captures in the same scene. This is not recommended and can negatively impact performance. A scene should contain only a single game capture, and never both a game capture and a display (monitor) capture as these interfere with one another.
There is no streaming/recording session in this log, so no information on dropped frames.
