Question / Help FaceRig causes low FPS in OBS stream

Khimari

Khimari

New Member
Hello guys,

I have an issue with app called FaceRig I use for my Twitch broadcast. Whenever I use this app it causes massive FPS slowdowns of OBS encoded stream.

I noticed that whenever I start the FaceRig app, OBS mimics it's window FPS and sets the broadcast to the same count at which the FaceRig app is running, ignoring main game which runs totally OK. I don't understand why and I don't know how to bypass this.

Example:

Mad Max game (Fallout 4, Max Payne 3, Dark Souls II, Elite: Dangerous, CS:GO, all DX9/10/11 games, name it....) is running at 55-60 FPS, while streaming with OBS (whatever encoder, CFR, encoded in full range) - everything runs at high FPS, all fine, smooth, nice and sweet. Than I start FaceRig, which is set to low priority, low quality and the app runs at 15 FPS, because it is a bit demanding (can take 20% of GPU power). Running a demanding game and FaceRig both together at 60 FPS is not quite possible (GTX 670) to be achieved. For FaceRig such FPS is not necessary, usually 10-15 does the job anyway. In the past OBS ignored FaceRig's FPS and just showed the window with lagging character, all fine, stream running at 60 FPS based on the main game, because FaceRig was set to low priority. But in past, two months maybe, it somehow changed and now OBS mimics FaceRig's FPS and causes the encoded stream running at FaceRig's FPS and totally killing the stream by lags.

Result:

Mad Max (55-60 FPS) + OBS (60 FPS - x264/QuickSync/NVENC - doesn't matter) - no FaceRig running => All 60 FPS

Mad Max (55-60 FPS) + OBS (15 FPS - x264/QuickSync/NVENC - doesn't matter) + FaceRig (15 FPS) => Sadness...

Please, can someone tell me why? I am desperate and sad because I love this combo to be used for broadcast and if the FaceRig app lags at 8 -14 FPS - I don't mind, it's ok, but why OBS mimics it's FPS, it ruins everything. Can I do something with this? I tried to run the FaceRig app at different GPU (it's possible even at desktop), not helped.

I use Windows 10. Debug.log is attached.

Please, help :(
 

Attachments

  • debug.log
    334.9 KB · Views: 42
Khimari

Khimari

New Member
Than the system should specify more clearly which log is needed, it is not clear while posting new thread. Which one do you need?
 
C

Cryonic

Member
Facerig is a pretty neat little tool to modify your webcam image in realtime. Sadly it is pretty demanding, with your hardware you have to turn down your settings pretty hard if you want to use it. Or upgrade your hardware to a unreasonable, but powerful enthusiast cpu :-)
 
Khimari

Khimari

New Member
Ya well, nevermind, I did some proper digging and it seems to be all together. Main issue is Windows 10 and it's "once-again-changed" access to D3D API system and handling of emulation of old DX9 stuff. FaceRig has issues to run in DX9 and it seems that running FaceRig in DX11 but with a game running in DX9 causes issues in OBS as well (Counter Strike: Source) if the DX9 game is not running in windowed mode (or windowed borderless). It's pretty ugly but I found at least a small possible bypass for FaceRig. All I need to to is to fire FaceRig off integrated GPU in Haswell CPU. It lags anyway after another game launch, but at least the OBS ignores FaceRig's framerate and stream runs fine, game/stream 60/60.

Best joke is old Max Payne 2. It squeezes the system at it's limits and runs much worse than for example Dark Souls II or Mad Max, it's more demanding. Emulation...

I also found that my main source of issues was a "Monitor capture" source in one of some scenes I had in OBS. Having this thing in list causes overall FPS go off 60 fps to 30 in Win10 if any DX9 or any lower DX app/game is captured (even if monitor capture is not in the actual scene). Good to know. I feel a bit like Indy Jones, discovering secret mysteries behind walls of spider's net... At least Dark Souls II runs fine once again.

I hope that Vulcan will be a success because maybe it will change future games and their situation how they will work when becoming obsolete, because I am quite tired of all this DX sh** . Sadly I am a gamer who loves to play old games. Maybe this is a conspiracy, forcing me to buy stronger and stronger hardware to be able to keep up and play those still older and older games. Seems like nobody likes new games so why not to gain $$$ off those old ones! Those old games are sometimes more demanding than Crysis 3...

I can report no issues with OpenGL games at all no matter what config I use (tested with Rage, Wolfenstein: NO and Evil Within), all is nice and pretty.
 
Last edited:
Khimari

Khimari

New Member
Well, the solution was a nuke bomb - > to buy GTX 1080, now the older i5 CPU is sometimes causing issues with a high CPU demanding game (GTA V, Forza Horizon 6 APEX). It is sadly all about aplication code, when even the strong hardware sometimes struggles because the code is written as it is (my i5 4570 is 4% below optimal border for GTX 1080 but I can still load the GPU at 100% - but I suggest getting something with 4 cores / HT - i7 or such) means FaceRig app and games together are very demanding as Cryonic said and if you mix it with bad game code => problem.

Was a weak hardware, too demanding apps, partly solved. CPU will follow. If you think about why such gpu, believe that after I nuked it I found out that anything else would not work, still weak... stupid apps. Seems like everyone p**** on proper app optimization :(
 
Last edited:
You must log in or register to reply here.
Top