[REPORTED]FPS sometimes hit hard while in a F/A-18 C

[BIGNEWY]

Thanks we have made the team aware.

 

We will also look into it.

[Deano87]

[BIGNEWY]

Hi there. I was investigating this kind of trouble you run into. I couldn't figure, how there was no real bottlenecking but also lacking performance after landing.

 

Reason for this is possibly a bug in the rendering engine of DCS World itself with the LUA CPU Usage value. Normally, this value hovers around 1-5 % when starting the mission (on ground and air) and just flying around. But after landing, the value for LUA CPU Usage spikes depending on the flying module up to 40% (on the F-18 for example) and it stays this way!

 

I made a video, it shows the F-18 starting on an empty NTTR-Map on the runway with a short round and landing. What you will see is, after landing on the runway, the LUA CPU Usage Value gets to around 40% in the Hornet. The load on the GPU drops significantly and thereby the FPS. There is no bottlenecking at all (not CPU not GPU wise).

 

For this test setting, all shadows are disabled (because they seem to have also a negative impact on the engine calculation and degrading the GPU loadout - especially the case, the more static airplanes are parked around you).

 

I locked the FPS with Rivatuner to 120fps and normally, this is the way, I like to fly around.

 

Watch for yourself:

 

For best viewing results, please use the 1440p quality for this video. (The text is very small in the analysis window).

 

The worst thing is, the LUA CPU Usage stays at this 40% after landing. Even switching to the F-5 and back to an unpowered F-18 doesn't help. To fix this back to normal, you have to leave the mission and load it up again.

 

I think, most people are not aware of this bug, because of gaming around 60fps. As you can see in the end, the FPS are barely around this value so many people wont notice the background high-load at all.

 

This is clearly an issue for people trying to fly in VR and for people who want to fly in much smoother high FPS.

 

Hope, this helps you out and gives a little more insight of what seems to be the problem. This is clearly reproduceable.

 

You can see, there is clearly something off, when watching the frametime line (values in ms - milliseconds). The frametime gives an impression of how fluid the frames are delivered. In the beginning, it is nearly flat with some minor spikes, because the GPU hits the limit and sometimes couldn't deliver 120fps but that is ok, as long as the load of the GPU is around 99%. The ideal way to play games in general, is to bottlenecking the GPU (load should be mostly around 99% so the GPU pushes the maximum available frames) - the CPU should always have some headroom and no usage around 99%. But having low CPU-usage AND low GPU-usage with lowered frames is always a bad sign as you can see in the frametime line after landing. You could see, that the engine is struggling hard in the backround and fighting itself for some reason.

 

 

Thanks for the info, do you happen to have the track replay and options.lua from the video you took?

 

The team would like to replicate with the same circumstance.

 

thanks

[SoloWingX]

Here is a trackfile from me, along with the options.lua in a zipped file...

 

https://drive.google.com/open?id=1DO1tyYInJh5wCSqIz3eLNxy6z9_UP5Ds

 

 

Basically hot start, taxi to runway, a half circle around the airfield, landing, turning around and take off. Excuse my incredibly bad landing :D

 

Not sure how exactly trackfiles work (you get the same head a plane movements, but I guess FPS depends on the viewer's PC), but on my system the FPS is locked at 65 FPS which the game keeps until slowing down below 100 kts after landing. Looking at the base further reduces the FPS to the 40s region, dipping into high 30s. At the beginning, looking at the base has no effect on my FPS, it's rock solid at the "maximal" 65 FPS.

[BIGNEWY]

Here is a trackfile from me, along with the options.lua in a zipped file...

 

https://drive.google.com/open?id=1DO1tyYInJh5wCSqIz3eLNxy6z9_UP5Ds

 

 

Basically hot start, taxi to runway, a half circle around the airfield, landing, turning around and take off. Excuse my incredibly bad landing :D

 

Not sure how exactly trackfiles work (you get the same head a plane movements, but I guess FPS depends on the viewer's PC), but on my system the FPS is locked at 65 FPS which the game keeps until slowing down below 100 kts after landing. Looking at the base further reduces the FPS to the 40s region, dipping into high 30s. At the beginning, looking at the base has no effect on my FPS, it's rock solid at the "maximal" 65 FPS.

 

Thanks, I see the same using your settings and track, the team will check.

 

FYI yep, crew chief says you need to work on your landings ;):)

[SoloWingX]

Thanks, I see the same using your settings and track, the team will check.

 

FYI yep, crew chief says you need to work on your landings ;):)

 

 

I knew I should have made another track with a nice landing :joystick::megalol:

[Deano87]

Excuse my incredibly bad landing :D

 

:lol: I’ll have to take a look now just to see how bad it really is. Hehe :thumbup:

[BIGNEWY]

Hi all

 

thank you for bringing this to our attention, we believe we have found an issue and it has been reported to the team.