Question / Help Late frames in The Culling.

Cryonic

Member
Here is the log, uploaded it earlier:
https://gist.github.com/anonymous/24e0e053dd26cae0fb76

CPU is overclocked to 4.5GHz so i have no problems running that resolution/preset at all.
This is the first game that gave me FPS drops on stream without having any problems elsewhere. The game itself loses FPS here and there so it doesnt really make sense to stream it in 60FPS, but thats what i used.
CPU usage never jumped above 70%, RAM - almost 8gb free.
GPU usage was fine, but not maxed out.

I have to use the anticheat-hook for the game, it uses the same anticheat that is built into Rust.

Tried some stuff like Vsync on/off (bad bad tearing forced me to do that, game itself has a strange lock at 62FPS), fullscreen or borderless windowed - nothing changes at all.
 

Osiris

Active Member
The video thread frame timings seem a bit high. What happens with a new scene collection that just contains the game capture? Upload a log from that attempt.
 

dping

Active Member
Yep that fixes it somehow.
Thats the log from a short (3min) recording:
https://gist.github.com/712b088a5df5743358ba

But i need all the sources i have in the main scene and there is no way around it. I also need a solution to the anticheat hook, thats the worst.
What sam686 said but 1280x720 for webcam should be fine.

you might also check your line-in. set it to 48000Hz (in fact check all your audio devices). and I believe you know but I'll mention it anyway. watching your own stream can cause extra video frametime. so either use internet explorer or popout chat.
 

Osiris

Active Member
Yep that fixes it somehow.
Thats the log from a short (3min) recording:
https://gist.github.com/712b088a5df5743358ba

But i need all the sources i have in the main scene and there is no way around it. I also need a solution to the anticheat hook, thats the worst.

You sure that was the right log? It was only capturing one note im or something.
Not sure what solution you want for the anti-cheat hook? It needs to be enabled because of how the game's anticheat works.
 

Cryonic

Member
Well that was the latest log what OBS presented me, so what should be wrong there?
Let me check that again.

Btw: the sound never caused a problem with the 48Khz and my audio interface can support 24bit 192Khz if needed :-)
Webcam resolution is not a problem either, was running fine before. Btw i use that in fullscreen and it is a global source, so it will stay at the highest resoltion possible. This issue is related to the game The Culling, everything else works just fine, even more demanding games like The Division Beta. So what the heck is wrong here.

Running the X99 platform with i7 5820k@4,5GHz i have no problems on the CPU side and can deal with the extra load.


Btw thats the last and right log again, doublechecked, the time and duration are correct:
https://gist.github.com/anonymous/bc562dfaefeacdf02819
 

Osiris

Active Member
Well, if it only happens with that specific game, i'm not sure something can be done on the OBS side. Maybe the game's engine isn't as efficient yet, causing performance problems for OBS' scene compositing, idk. Or mayb something to do with the anticheat it uses, if Rust uses that anti-cheat to, do you also have this issue with that game?
 

Cryonic

Member
Nope, Rust works fine. Besides having actual framedrops below 60 (that makes the 60FPS stream useless cause the source cant keep the min. FPS above that).
I try to figure out what is the source for the problem, but so far i cant tell what i causing the problem.
 

Osiris

Active Member
The GPU seems to be getting stressed a bit, the time it takes for OBS to download the frames of the GPU is higher than it should be, when you are capturing The Culling.
 

Cryonic

Member
The GPU seems to be getting stressed a bit, the time it takes for OBS to download the frames of the GPU is higher than it should be, when you are capturing The Culling.

Well thats a kick in the right direction. Let me monitor that for a bit (Afterburner or NZXT Cam should do the trick).
Solutions could be: overclock it (was running without OC since it is useless and the game drops below 60 no matter what), reduce the settings from maxed out to medium/high mix ingame, play around with the Nvidia crap (just got a new driver, but the issue looks unchanged so far).
I think slapping around 200Mhz on GPU and VRAM would help with that a bit.
 

FerretBomb

Active Member
I've never managed to get Game or Window Capture to work in The Culling. I'm just using borderless windowed mode, and a monitor capture instead (well, GC of DWM due to Win7). Works quite well.
 

Cryonic

Member
Game capture with Anticheat works. I need the anticheat to hook it once, then i can disable it, still works.
Dont forget, i run the Win10 Insider with the current build 14279, so thats next level (specially the amount of bugs and "features" aka hidden bugs is pretty huge).

Btw borderless windowed is a bit crazy here, mouse cursor os going wild and the taskbar is on top of the game sometimes. Well, benefits of early access^^
 
Last edited:

FerretBomb

Active Member
Haven't had those pop up under Win7. Unless you meant Win10 being early access, which I fully agree with in general.
Yep, just did a quick test and anticheat GC does indeed work. Unfortunately can't duplicate the frames, or video thread issue. Really, the video thread shouldn't be a problem... it's a bit high, but nowhere near the 16ms theoretical max for 60fps.

I'm actually running the same CPU as well, though I can only hit 4.2 due to cooling issues (or the silicon lottery), and can run 720@60 on Medium without a problem.

Only things I can think of are the semi-rampant W10 performance problems (oe of many reasons I haven't updated), or possibly your video driver? The latest is known to have crash/bluescreen issues, and I haven't updated for a bit... 361.43. Could try rolling back and see if it helps.
 

Cryonic

Member
Win10 itself is really stable and better than anything before. But i use the Insider Preview.
I tested everything here and everything is stable now, even with the latest driver.
The Culling has 2 problems: it maxes out the GPU, no matter what GPU you got. Thats a problem, it is responsible for the late frames. And the game itself is a laggy piece of crap, that is dropping frames all over the ocean while increasing my ping to unplayable 130-150ms+. That can be solved pretty fast, but i dont think that it has any priority.
 

dping

Active Member
Win10 itself is really stable and better than anything before. But i use the Insider Preview.
I tested everything here and everything is stable now, even with the latest driver.
The Culling has 2 problems: it maxes out the GPU, no matter what GPU you got. Thats a problem, it is responsible for the late frames. And the game itself is a laggy piece of crap, that is dropping frames all over the ocean while increasing my ping to unplayable 130-150ms+. That can be solved pretty fast, but i dont think that it has any priority.
if you wish to avoid the accelerated way that OBS MP captures, just enable multiGPU in the game capture. this will make it work more like xsplit in a sense YMMV since I just thought of that.
 

FerretBomb

Active Member
Win10 itself is really stable and better than anything before. But i use the Insider Preview.
Having used both, Win7 sends its regards. 10 is definitely better than 8, but sits a sad second to 7 still. Have to work with 10 from the support end of things, so that might also be coloring my opinion with how it makes it difficult to get anything done as a power user, hiding settings behind multiple layers of hands-off, and locking out certain options (like the option not to install a given update) entirely.
I tested everything here and everything is stable now, even with the latest driver.
The Culling has 2 problems: it maxes out the GPU, no matter what GPU you got. Thats a problem, it is responsible for the late frames. And the game itself is a laggy piece of crap, that is dropping frames all over the ocean while increasing my ping to unplayable 130-150ms+. That can be solved pretty fast, but i dont think that it has any priority.
Odd, as my 980Ti seems to handle it well. Nowhere close to maxing out, even at max settings. I'd suspect an OS or driver issue (again, I'm a few driver revisions back).
Not much that can be done about ping for non-NA players though until the EU/OCE servers are stood up. I see around 25-35ms, but do have a heck of a time in melee against people with high ping... it seems to favor them, allowing stabs through my blocks, and even backstabs from the front (on my screen) with them warping around. For bows and guns it might be more of an issue, I'd expect.
 

Cryonic

Member
I tested that stuff with the current "first" patch.
First: EU server rocks, no more 150+ ping.
Second: the game eats my GPU alive. Thats the first time that i saw over 60°C on my 970 (Windforce GTX 970 OC`d).

Turning on a stream means -5FPS, just watching twitch -3FPS O_O
The basic problem is simple: kick the developers behind until they lower the GPU load.
Btw the GPU load is always at 100%, even in the menu. Client running? Enjoy the heat and the noise level from your GPU and increased electricity bill (its not like we care about that but still^^)..
 
Top