Howdy all, those of you who fly the Kodiak in MSFS might already be familiar with a bug that was discovered early after release, within a day or so. The specific bug is that when the “Alternate Attitude Indicator” (top left corner dash/VC) is powered and functioning users will see an 8-10 FPS loss in the simulation. The immediate and excellent work around is to disable the AAI with the circuit breaker (second or third row from bottom, center). Once you do that the AAI will go dark and you will instantly recover those 8-10 frames per second you previously lost. 

My goal of this post is twofold:  1.) To see if anyone knows the status of this bug and when SWS plans to address it and 2.) To get the URL to the SWS support forum if it exists because so far a google search has not been fruitful for me. 

TIA

-B

Edited January 20, 20224 yr by btacon

5 minutes ago, btacon said:

Howdy all, those of you who fly the Kodiak in MSFS might already be familiar with a bug that was discovered early after release, within a day or so. The specific bug is that when the “Alternate Attitude Indicator” (top left corner dash/VC) is powered and functioning users will see an 8-10 FPS loss in the simulation. The immediate and excellent work around is to disable the AAI with the circuit breaker (second or third row from bottom, center). Once you do that the AAI will go dark and you will instantly recover those 8-10 frames per second you previously lost. 

My goal of this post is twofold:  1.) To see if anyone knows the status of this bug and when SWS plans to address it and 2.) To get the URL to the SWS support forum if it exists because so far a google search has not been fruitful for me. 

TIA

-B

There was another fix and that was to reduce the frame rate of the aux display from 10 fps to 5 fps. Very simple to change a number, but I forgot where that file is. Someone  will probably see this question and post it. I never had a FPS problem with the Kodiak, but I am locked to 30 FPS anyway. 

The problem is the backup EFIS. For some reason it's tanking FPS when it's on. The solution: on the very bottom row of circuit breakers, pull the one labeled "3." That'll turn off the backup EFIS and restore your FPS. Hopefully SWS can rectify this issue but I'm fine with just turning it off in the meantime. 

 

EDIT: I realized you already know about this trick. Never mind!

Edited January 20, 20224 yr by liamp51

Just now, liamp51 said:

The problem is the backup EFIS. For some reason it is tanking FPS when it's on. The solution: on the very bottom row of circuit breakers, pull the one labeled "3." That'll turn off the backup EFIS and restore your FPS. Hopefully SWS can rectify this issue but I'm fine with just turning it off in the meantime. 

He already mentioned the circuit breaker but if you read my post there is another fix without having to pull the breaker each time. 

25 minutes ago, btacon said:

The specific bug is that when the “Alternate Attitude Indicator” (top left corner dash/VC) is powered and functioning users will see an 8-10 FPS loss in the simulation.

This is actually not a "bug".. but an inefficiently coded gauge, which SWS has committed to re-coding in a future update.

In the meantime, you can indeed reduce the update frequency of this gauge to your liking which may work for you in the interim.

Edited January 20, 20224 yr by Bert Pieke

18 minutes ago, Bert Pieke said:

This is actually not a "bug".. but an inefficiently coded gauge, which SWS has committed to re-coding in a future update.

In the meantime, you can indeed reduce the update frequency of this gauge to your liking which may work for you in the interim.

Do you remember which file that is, I think it is in one of the panel files for the Kodiak.

Here is the fix. Bert Pieke posted this awhile back. 

 

You can reduce the update frequency for the standby gauge... default is 10.

I run mine at 5 and see no difference.

Look in the panel folder and edit the SWS_ESI500 xml file.

<Gauge Name="SWS_ESI500" Version="0.1">
    <Size X="512" Y="384"/>

    <Update Frequency="5">

Thanks one and all. I’ll definitely try out the cfg edit.  BTW does anyone know a URL to the SWS support forum?

Thanks again,

-B

1 minute ago, btacon said:

Thanks one and all. I’ll definitely try out the cfg edit.  BTW does anyone know a URL to the SWS support forum?

Thanks again,

-B

https://discord.com/invite/Ns7GkWW

4 hours ago, Bobsk8 said:

Here is the fix. Bert Pieke posted this awhile back. 

 

You can reduce the update frequency for the standby gauge... default is 10.

I run mine at 5 and see no difference.

Look in the panel folder and edit the SWS_ESI500 xml file.

<Gauge Name="SWS_ESI500" Version="0.1">
    <Size X="512" Y="384"/>

    <Update Frequency="5">

I tried to change that value, but it made no difference for me, the only thing that helped was to pull the circuit breaker.

Makes no difference to my frame rates but I'm GPU limited.  Must be related to the CPU.

I never notice any performance degradation with that device on... But well, I have an official G-Sync monitor and I have never used an fps counter with MSFS so... that must be it. 😉 My Kodiak flights are butter smooth all day long. It's like sitting in a real aircraft and looking out the window. Very happy with MSFS right now.

Here's an alternate solution I saw elsewhere:

In the panel.cfg file, replace this line:

gauge00=SWS_ESI500!SWS_ESI500, 0,0,512,384

with this:

htmlgauge00=NavSystems/AS1000_BackupDisplay/AttitudeSpeed/AS1000_AttitudeSpeedBackup.html, 0,0,512,384

 

Seems that will replace the ESI with the G1000 standby instrument.   You lose the ESI menu functionality, but you at can at least avoid pulling the breaker and not having any standby.

Edited January 21, 20224 yr by DeepestRed

3 hours ago, DeepestRed said:

Here's an alternate solution I saw elsewhere:

In the panel.cfg file, replace this line:

gauge00=SWS_ESI500!SWS_ESI500, 0,0,512,384

with this:

htmlgauge00=NavSystems/AS1000_BackupDisplay/AttitudeSpeed/AS1000_AttitudeSpeedBackup.html, 0,0,512,384

 

Seems that will replace the ESI with the G1000 standby instrument.   You lose the ESI menu functionality, but you at can at least avoid pulling the breaker and not having any standby.

This works, but be aware there are two panel folders:  panel and panel.noregistration

In my case, I had to change it in both. 😉