SP1 issues so far

[alex.767]

- Comm 2 still broken. Already reported here: viewtopic.php?f=105&t=11620&p=95788&hilit=comm+2#p95788
- Sound artifact still present. Already reported here: viewtopic.php?f=105&t=11358&p=94196&hil ... und#p94196
- Performance has taken a nosedive with massive stutters caused by a huge increase in VRAM usage. See this comparison against the NGXu with is similar in terms of being a full PBR VC: https://imgur.com/a/1XGCWrc
- Visuals tab still doesn't seem to do anything. Unless I'm doing it wrong? I select pitot/chocks by default and have cold and dark set. But neither of those items appear on the aircraft on load.

[meese91]

GND COM not implemented?

[xender]

I can confirm the part about performance. I can fly it but right now its by far the one with the heaviest performance toll on my system, and i have everything from pmdg and fslabs.

I find it rather interesting that you talk about vram. I did the same observation too.

[brett.cummings]

I too am getting hit hard by performance coming from 1.0.6

[MurrayD]

I'm getting terrible fps too since updating. Also, the problem of my Virtualfly TQ6 throttles not moving the V.C throttles after calibration is still present.

Regards.

[jarek]

GND COM is only active when battery is OFF (but bat bus switch must be on - the one with white and red stripes)

About COM2 issue - if AUTO COMM knob on radio panel is switched to upper position and 2nd radio is tuned to the ATIS, I can hear it while talking on COM1. Selector (top selector knob is set to 1) Not sure if this is what was expected, but maybe could serve as some some workaround.

[thecoturnix]

Also, the problem of my Virtualfly TQ6 throttles not moving the V.C throttles after calibration is still present.

Regards.

Same here

[matpietsch]

GND COM is only active when battery is OFF (but bat bus switch must be on - the one with white and red stripes)

About COM2 issue - if AUTO COMM knob on radio panel is switched to upper position and 2nd radio is tuned to the ATIS, I can hear it while talking on COM1. Selector (top selector knob is set to 1) Not sure if this is what was expected, but maybe could serve as some some workaround.

You can run I to situations were you want to talk on either com. This is currently not possible from what I see.

[jarek]

You can run I to situations were you want to talk on either com. This is currently not possible from what I see.

On top of the radio panel there is a XMIT selector knob to switch between COM1 and COM2 and PA, you can select on which channel you talk.
If you would like to monitor second frequency, use AUTO COMM. All what is possible here. COM volume knobs are inop.
If I miss something here, then please describe this specific scenario.

[FinnJacobsen]

I just performed a short flight from EKBI to EKSB via a SID, then ODN and ALS VOR's, into EKSB RWY 32 ILS apparoach.

I used VNAV for the entire flight until the automatic Localizer and Glideslope capture.
Everything worked great.

But I also experience bad performance.
Pre SP1 the KA350 was my best performing glass cockpit aircraft, but now it´s on par with the NGXu and is down to 20 fps.
I have tried to uncheck the "Render to transparent texture", but with little impact on fps, and offcourse lost the windshield raineffects.

Has texture sizes or the amount of textures been increased with SP1 ?

[heightsmite]

Another vote for bad performance here, even at simple default airports.

After waiting all this time, the KingAir is unusable on my system; it's much hungrier than the PMDG NGXu (which I can fly smoothly).

[Regis9]

Also, the problem of my Virtualfly TQ6 throttles not moving the V.C throttles after calibration is still present.

Regards.

Same here

In case it helps, I thought I had this issue until I realized I didn’t check off the new box in MVAMS that enables hardware configuration (not the exact words, I’m not in front of my computer right now).

[pilot.adolfsson]

Minor detail, but WAAS is misspelled in the FMS:

[doodlebug]

Are the fps issues related to nightlighting - are any lights on?
Do they persist if you uncheck render transparent surfaces?
Are mipmaps enabled? (please disable)

[SAS443]

Mark points date and time format (both HOUR:MINS and MONTH ) seems to be wrong?

Looks like we have reverse time format MINS:HOURS.

And MONTH seems to be off by "current month"+1. My simulator was set to system time: 11th APRIL 2020, and FMS STATUS also indicated correct date and time. (see last image)

Capture.JPG (72.43 KiB) Viewed 1863 times

Capture2.JPG (40.45 KiB) Viewed 1863 times

Also has FPS issues, but solved by unchecking "render to transparent surfaces" in MVAMS. What does that option even do?

But by and large, a huge step forward! Thanks alot!