Viggen Performance

[Emra]

This issue only applies to a very small subset of users currently. Consider that before making any decisions.

 

How does one determine who the "subset of users" is? Can you describe this subset more clearly?

 

The reason I ask is because I`m waiting to make a decision on a module and the Viggen is in the mix.

[toilet2000]

If your answer is related to Nevada - and I'm just only guessing here - the TERRNAV will have its problems finding the corrections, since much of the landscape is more or less flat. If I understood correctly this works with mathematic correlation, which depends on two things that are compared to each other. If both "curves" are flat ... -> :cry: the computer will not make out where this fu.... flat area belongs to ... but this is only guessing around ... OK :pilotfly:

I indeed have nav status 5 on Nevada when flying within range of the radar altimeter very much of the time. And believe me, I am flying really low. Low that my radar altimeter is shit scared ... :p (highest altitude is when landing gear is extended ... it has kinematically touch the ground somehow ... what a bad invention)

 

 

No it's on Caucasus! And on 1.5 it was almost always on "5", not "2". But good idea!

[hughlb]

I am getting crazy amount of stutters and frame drops with the Viggen in 2.5. It's the only aircraft this is happening with, and didn't happen before. My framerate is high, usually around 80-100, but lots of drops and stutters. Hmm, is there a reason that anyone has found?

Edited April 1, 2018 by hughlb

[Holton181]

I am getting crazy amount of stutters and frame drops with the Viggen in 2.5. It's the only aircraft this is happening with, and didn't happen before. My framerate is high, usually around 80-100, but lots of drops and stutters. Hmm, is there a reason that anyone has found?

I don't know if it's related, and I unfortunately don't remember where I read it or who gave the tips, but if you have the game installed on a HDD but got access to a couple of Gb on a SSD it's a good idea to move the map files (now I start to feel really old, apparently I got no memory at all, don't remember the maps location nor their file type) to the SSD and create hardlinks to them in their original place. Due to how the Viggen radar is implemented this tweak will hopefully make things much smoother. It did for me.

[droopy114]

I am getting crazy amount of stutters and frame drops with the Viggen in 2.5. It's the only aircraft this is happening with, and didn't happen before. My framerate is high, usually around 80-100, but lots of drops and stutters. Hmm, is there a reason that anyone has found?

 

See: https://forums.eagle.ru/showthread.php?t=199880

 

Just to say, bug is still here, and cause a lot of performance drop..

[hughlb]

See: https://forums.eagle.ru/showthread.php?t=199880

 

Just to say, bug is still here, and cause a lot of performance drop..

 

That helps to an extent, as my framerate gained considerably - but I'm still seeing huge variations in frame time from 16-40+, which leads to constant stutter. This is unique to the Viggen module, other modules sit at solid 16ms

[droopy114]

That helps to an extent, as my framerate gained considerably - but I'm still seeing huge variations in frame time from 16-40+, which leads to constant stutter. This is unique to the Viggen module, other modules sit at solid 16ms

 

Yep this is a real issue and dev should have a look at what's going wrong with this damn frame time!

[unknown]

Are there any news on this topic? I just had another go in my little test mission(some AI units standing around so that i can bomb them, nothing complicated), first in the Mig-21, after landing i switched to the Mirage-2000C and landed again and switched to the Viggen. I got 40+ fps at the ground with the Mig-21 and Mirage but only low 30 fps with drops to 17-22 fps in the Viggen on the same airfield and less AI units on the map. In the DCS-Log you can see the average frame rate dropping from 50-60 fps (Mig-21/Mirage) to 38-44 fps in the Viggen.

 

Log file attached.

[Cobra847]

We are working on this issue.

[theOden]

We are working on this issue.

:lol:

[Cobra847]

:lol:

 

Hilarious.

Edited April 7, 2018 by Cobra847

[Cobra847]

I believe we've isolated the issue. Testing a fix now.

[funkyfranky]

I believe we've isolated the issue. Testing a fix now.

Thanks :thumbup:

[unknown]

I believe we've isolated the issue. Testing a fix now.

That's some promising news! :thumbup:

 

If you need help testing it...:music_whistling: :smilewink: :joystick: :D

[droopy114]

:thumbup:

[Cobra847]

The fix has been implemented and works great.

We were erroneously rendering some rendertargets that were not required.

 

The Viggen has reduced a 5-6ms frame to frame variance to 0.5-ish. Available in the next patch.

 

Thanks for the patience!

[Holton181]

Excellent!

Thanks

Available in the next patch.

"Viggen patch" or "DCS patch"?

You stated before next "Viggen patch" will come with next "Main DCS patch"...

[Cobra847]

Excellent!

Thanks

 

"Viggen patch" or "DCS patch"?

You stated before next "Viggen patch" will come with next "Main DCS patch"...

 

There are no seperate Viggen patches. We can only ship changes together with DCS.

[Holton181]

There are no seperate Viggen patches. We can only ship changes together with DCS.

Yes, I know. But you have, as I referred to, mentioned you will let the updates and fixes to the Viggen be available only at main/bigger DCS updates, not intermediate/smaller ones.

"Viggen patch"="Main DCS patch" or at next intermediate "DCS patch"?

[Cobra847]

Yes, I know. But you have, as I referred to, mentioned you will let the updates and fixes to the Viggen be available only at main/bigger DCS updates, not intermediate/smaller ones.

"Viggen patch"="Main DCS patch" or at next intermediate "DCS patch"?

 

Intermediate. Sometimes we delay big changes for major patches, but not something like this.

[Holton181]

Intermediate. Sometimes we delay big changes for major patches, but not something like this.

Perfekt, thank you!

[unknown]

The fix has been implemented and works great.

We were erroneously rendering some rendertargets that were not required.

 

The Viggen has reduced a 5-6ms frame to frame variance to 0.5-ish. Available in the next patch.

 

Thanks for the patience!

Thats great news! Thank you very much Heatblur Team!!! :thumbup:

 

That sounds like i can go back to flying at tree level and bomb some targets, not saying sinking ships would be less fun, especially watching the RB15 - should really be called the "cool Terminator" - at work.

 

[Emilio_Ger]

Great news, looking forward! :thumbup:

[Emilio_Ger]

With the latest update the performance in Red Flag campaign is alot better! Great Job HB :thumbup:

[imacken]

With the latest update the performance in Red Flag campaign is alot better! Great Job HB :thumbup:

 

Interesting, I haven’t tried it yet, but it’s not mentioned in the changelog.