Quick He 111 benchmark

[AristocratPanda]

Hi everyone,

 

I would like to share a couple of screenshots of my quick fps test.

 

Empty sky: ~95fps

Empty terrain: ~68fps

1 He: ~60fps

4 Hes: ~33fps

 

Bottom line: I'm losing ~35fps when there are 4 Hes in my view. I don't understand what my gpu (or cpu) is trying to render so hard that I can not see... I know there have been a lot of discussions on this subject and on DX9 limitations. I'm just hoping for some improvements on this in future.

 

Is there anyone among you getting to have a flawless constant 60fps in a quick mission with 16 bombers in maxed out settings and if so, what specs do you have?

 

Thanks.

 

PS: I'm on a gaming laptop i7 4710hq - 16gb - gtx 860m 4gb

[216th_Lucas_From_Hell]

I get a constant 30 FPS even with 12 bombers (5 Pe-2s and 7 Heinkels) and 4 fighters, because my rig can't render much more than that anyway and that's the limit I set, but that's not very useful, is it?

 

The Heinkel problem is not in terms of graphics but CPU. To elaborate, one AI single-engine fighter has 1 AI + 1 flight model to calculate. One AI Bf-110 has 2 AI (pilot+gunner) + 1 flight model to calculate.

 

1 AI He-111 has 5 AI + 1 flight model to calculate. 4 AI He-111s have 20 AI + 4 flight models to calculate.

 

This is mostly due to the AI complexity of the sim. That being said the developers are aware of this as a problem, and are looking at ways to make this easier on players.

[HagarTheHorrible]

The A.I pilots intellectual capacity never struck me as being overly deep, and as for the A.I gunners, well let's just say Mensa won't need to be running off any extra copies of it's entrance test. I suspect even Babages old computer might have had spare computational capacity after calculating their routines.

[coconut]

 

 

The Heinkel problem is not in terms of graphics but CPU

 

But then why are the slow-downs view-dependent? The AIs don't stop working just because you stop looking at them.

 

I suspected physics were the problem, as if moving objects ran simplified physics when you are not looking at them, and full physics when they enter your view. But the devs have said that simplified physics for AIs were an optimization they were thinking of doing in the future, meaning that's not already the case.

 

This slowdown is a mystery to me, and I have amateur-level experience in 3d, physics and AI programming.

[-TBC-AeroAce]

All I know is my rig with a 5ghz amd 8 core is rubbish with this game compared to an Intel. Ps the rest of my HW is dope

[BSS_Sniper]

 I've never even noticed a single stutter with everything turned up to Ultra. I'm using an 1100T 6 core and Gigabyte R290X 4 gb.

Edited March 6, 2016 by BSS_Sniper

[-TBC-AeroAce]

I've never even noticed a single stutter with everything turned up to Ultra. I'm using an 1100T 6 core and Gigabyte R290X 4 gb.

My cpu is a oc 8350 and I have an 970. The rest is good I get stuttering on normal big time

[SCG_Space_Ghost]

-snip-

 

So, I hesitate to ask, but how does one overclock ones processor.................... Safely :-P

 

PM me.

[Jade_Monkey]

A flight of AI heinkels and a nearby handful of pe2s generated on PWCG brought my game down to a slideshow.

 

The same number of aircraft in a FNBF doesn't have the same effect.

 

Not exactly a scientific test granted, but I don't think it is a graphics issue.

 

In truth I see little performance improvements when I drop all graphics settings down/off.

 

So, I hesitate to ask, but how does one overclock ones processor.................... Safely :-P

Make sure you have a decent CPU cooler before overclocking, or your pc is gonna become a kitchen grill.