Frame time issue with the Viggen

[droopy114]

Well, finally found the culprit of my horrible stuttering with TrackIr in the Viggen. If the option "resolution of cockpit display" is set at any other setting than "every frames" (no matter the resolution, 256, 512 or 1024), frame time is crazy, despite a perfect 60FPS (you can check frame time by pressing right ctrl+pause twice), if every frames is enable, frame time is perfect (approx' 16.66ms for 60FPS) and TIR perfectly smooth. A screenshot can't capture the moment, but i can post a video later showing the issue. The problem is there's a serious performance drop (like 15/20FPS) if every frames is selected, and a module like the BlackShark, wich use MFCD's, don't have this problem. Another friend of mine have the same problem, so i assume it's not on my end. Could you have a look?

[droopy114]

Surprisingly, no one report this bug, or maybe my first post is unclear, so a video will better demonstrate the problem:

 

 

First part, 512 (standard, not every frame) top left corner, have a look at the frame time: totaly crazy, and cause major TrackIr stuttering/juddering, don't know how you call this, FPS counter is showing 60FPS.

 

Second part, 512 every frame, perfect frame time, TrackIr perfecly smooth.

 

Also if you untick the vsync option, don't cap the FPS, you will notice a big performance impact: 99/100FPS with the option set to every frame, 125/130 with standard non-every frame!

Edited January 23, 2018 by droopy114

[PhilTheBeat]

Thank you Droopy

[FS Voodoo]

Same issue for me :/

 

Envoyé de mon NEM-L51 en utilisant Tapatalk

[droopy114]

Just to say, bug still here in the latest 2.5 version, but not exactly as it was before. Frame time is erratic this time, sometime correct, or totally crazy, depend where you are looking, and it still cost about 15FPS hit. I will post a video later.

[toilet2000]

+1, I've got the same issue on 2.5. I was wondering why my performance in VR was weird, but only with the Viggen. I'll try using "every frame" and see if it helps with FPS consistency.

[RagnarDa]

Hey could you test it with an airstart in the air and also try "every frame" FIRST and then try without "every frame" ?

[toilet2000]

I'll test it as soon as I get home! I'll post back the results.

[RagnarDa]

Also, if you do test it could you upload the dcs.log? Many thanks!

[droopy114]

Will try this too, thanks for looking into it.

[droopy114]

Hey could you test it with an airstart in the air and also try "every frame" FIRST and then try without "every frame" ?

 

here are my results:

 

-launch DCS

-resolution of cockpit display was already set at 512 every frame

-launch the default "airborne intercept" mission

>steady 60FPS, perfect frame time, at about 16.66ms, as expected

 

-leave mission

-choose 512 only, without leaving DCS

-launch "airborne intercept"

>steady 60FPS, perfect frame time, at about 16.66ms, as not expected :huh:

 

-leave DCS

-launch again DCS

-resolution of cockpit display:512 only

-launch "airborne intercept"

>erratic frame time but steady 60FPS, as expected :D

 

Here is a video, default mission "cold start":

 

 

Maybe not easy to see, but this is particuliary noticeable when you look up or down in the cockpit, not in front of you :wassat:

 

Log attached. Thank you!

Logs.rar

Edited February 9, 2018 by droopy114

[Dhorse]

Great! Will try this and see if that's my reason as well. DCS (as of all games) really needs to add that "description pop-up informative text" for all the different settings and what it actually mean/ result in, especially in a game like this with that many settings. That might help people not being forced to search forums for hours, but to Enjoy this beautiful game instead... Perhaps develop a built in "plugin" that informs the player if things seems odd in performance and hopefully also informs what can inflict that... From a video settings point of view... :(

[River]

Is this issue solved or do we still have to pick the "every frame" options ? Thx