ArsenicDrone
New Member
Re: Diablo 3, Doesn't lag my PC but output is extremely chop
I downloaded OBS tonight and had this problem. Fortunately, after trying to change the resolution, and getting no results, I realized what my problem was: I left Diablo at the default setting of max foreground frame rate of 150fps. This is useless (my monitor doesn't refresh this fast), and eats up a lot of processing power. There's not enough power left to record. Then I changed it to limit Diablo to 30 fps (well, 31 because that slider is twitchy), and it runs beautifully. It's super sharp and pretty smooth, recording at 1080p ("fullscreen windowed"), 3000kbps. I'm recording to a SSD hard drive (shouldn't really matter for a single big file write?), with a computer I built a year and a half ago for ~$350.
Now if I could just get it to record any audio, I'd be set!
Update: I had muted my video player earlier (duh), and when I heard no audio, I switched to mp3 encoding. I figured that should work, but... turns out it doesn't, and when I switched back to the default of AAC, it started working. Problem solved.
I downloaded OBS tonight and had this problem. Fortunately, after trying to change the resolution, and getting no results, I realized what my problem was: I left Diablo at the default setting of max foreground frame rate of 150fps. This is useless (my monitor doesn't refresh this fast), and eats up a lot of processing power. There's not enough power left to record. Then I changed it to limit Diablo to 30 fps (well, 31 because that slider is twitchy), and it runs beautifully. It's super sharp and pretty smooth, recording at 1080p ("fullscreen windowed"), 3000kbps. I'm recording to a SSD hard drive (shouldn't really matter for a single big file write?), with a computer I built a year and a half ago for ~$350.
Now if I could just get it to record any audio, I'd be set!
Update: I had muted my video player earlier (duh), and when I heard no audio, I switched to mp3 encoding. I figured that should work, but... turns out it doesn't, and when I switched back to the default of AAC, it started working. Problem solved.