Carenado PC-12

The update should also fix the problems with the Avodyne EX500. However, the Java code associated with the Coherent GT Engine does not appear to have been touched. This shows the review of the files changed with V1.2 in Explorer. I have therefore deactivated the relevant avionics in the panel.cfg. Since then I have had no more frame rate drops on two reference flights with more than 1 hour flight time.

2 Likes

Hi! Interesting. I would like to try this too. Would you be able to say what lines you removed/commented?

1 Like

Did you check the taskmanager for any other process having a high power usage?
I have DivX installed and their updater runs random at very high and doesn’t stop. I’ve also experienced a windows bug, which activates due to a memory leak bug with the default Photos app which seems to be activated sometimes resulting in a high cpu usage of the process Shell Infrastructure Host. I got rid of these stutters and performance drops by searching through the taskmanager.

Second the request to know which avionics to edit out of the panel.cfg

Put a semicolon in front of the appropriate line. Before doing this, please save the panel.cfg in the directory:

[Vcockpit16]
size_mm=640,480
pixel_size=640,480
texture=$AVIDYNE_Screen
;zorder=15

;htmlgauge00=NavSystems/Carenado/EX500/EX500.html, 0,0,640,480

If you are owner of the TDS GTNXi or PMS GTN750 you should not need the Avidyne :wink:

2 Likes

well, after the update i thought i’ll give it a try… loading into the plane, starting the engine → OLD STEARMAN sound back :rofl:

no thanks, i’ll just stay away from this thing… :yawning_face:

3 Likes

Very strange, the sound problems never occurred again after the last update and with the new update everything works very well again…
Five flights without any problem!
Are you flying with the ingame LIVE traffic?
Since I only fly with the “FSLTL-Traffic” no sound problem occurred anyway.

1 Like

I fly all players, as live players do not display friends for some reason.
i fly live weather too.
If there is a specific live trafic setting i might use it as i always try to stay realistic.

The stearman sound came directly while spooling up. In the older versions the sound did change random in flight, not at the very first spool up :smirk:

Well, what you use as live traffic now I still don’t know - never mind…
Try to switch off live traffic in the game and only use live traffic from “FSLTL-Traffic”:
then you really have the real traffic via “Flightradar24” in the game and it is much better - exact description can be found at “FlyByWire” - very easy to install and handle :wink:
Online players can still stay switched on, because these are 2 pairs of shoes… :beers:

1 Like

Why not just turn the power of the Avidyne off?
If it’s turned off, logically you shouldn’t need to hack the cfg files.

Are you saying it’s still running even if turned off?
I can’t believe their code would allow that, as it’s pretty basic to bypass processing in a power off state.
Depsite the bugs and slow updates, they do know what they’re doing even it takes them some time to get the planes to a good state.

I’ve been pretty vocal in this thread about Carenado and this plane in particular. I bought it day one and was very disappointed with the state it was in, and frankly quite angry about having spent money on it.

This was followed by further anger and frustration with Carenado for not showing a lot of interest or urgency in fixing things.

However, after the latest update I will admit, it’s finally in a decent state (FINALLY!) and I’ve had some enjoyable flights in it.

The whole episode has definitely made me very weary of buying from them again though, I’ve learned my lesson.

6 Likes

Well for me VR Zoom doesnt seem to work in this new update and the Navigraph beta 8.1 charts wont work as well but just in this plane. Both are fine in other planes in VR. Anyone else having same issue?

Well, with the C182, Mooney and PC-12 updates it looks like Carenado may have started in January with some good New Year resolutions.
They started out pretty well in 2020 and 2021 but 2022 has really been trying service-wise. So let’s hope this is a trend they’ll stick to. :slight_smile:

5 Likes

It seems the code is loaded the very first time you power on the planes av switch, because the so called bus is in power state, so yes - it is running in the background then. But this is my own expirience. Make yours.

I don’t have a problem with it on or off personally, I’m just interested in it as a potential bug.

It doesn’t appear to be as simple as it being on though, otherwise people would be having issues with it on the ground before they even take off. From what I can see, people seem to be saying it kills the FPS after a decent time period of flying, so perhaps it’s a memory leak/eat issue over time, not the fact it’s on per se.

If the conditions can be narrowed down more to replicate it, there’s a much higher chance Carenado can fix it.

Update:

I traced the relevent code and it looks to me like if you turn it off the update processing gets bypassed, so it’s not running in the background if it’s turned off.

There’s a lot more code than this bit, but this is setting the power state on/off and also the HTML element:

powerToogle() {
    if (this.instrumentState == 'off'){
        this.instrumentState = 'on';
    } else {
        this.instrumentState = 'off';
    } 
    diffAndSetAttribute(this.electricity, "state", this.instrumentState);
    if (this.instrumentState == 'on'){
        SimVar.SetSimVarValue("L:EX500_MFD_SPLASH_SCREEN_ST", "number", 1);
    }
}
closeSplashScreen() {
    SimVar.SetSimVarValue("L:EX500_MFD_SPLASH_SCREEN_ST", "number", 0);
    diffAndSetText(this.SplashScreenInfo, "Initializing, prease wait ...");
}

html_ui\Pages\VCockpit\Instruments\NavSystems\Carenado\EX500\EX500.js is built on the A320_Neo_MFD code, and that seems stable, or is it?

It could be an overrun of a variable or something that only kicks in after a time period or certain actions, that snuck in when they adapted it from the A320_Neo code (assuming there’s no issue with that code itself). Need to narrow down the situations when that happens so it’s 100% replicable in order to debug.

Can anyone confirm they still get the FPS issue if the Avidyne is turned off as soon as you jump in the plane, and leave it off?

2 Likes

Yeh, i just ran a second test over Spain, was locked at 60, as soon as i entered my nav data for leco, fps went from 60 to low 40’s almost immediately(and im sure would of kept declining over time). as soon as i switch off avionics (tried one at a time but only both worked), it jumped straight back up to 60.

i suspect whatever caused the avidyne issue, is present in the nav aids also, but ■■■■, i really thought was fixed

Where can I download the pilot´s manual?.

Interesting observation. What makes the bug so difficult to reproduce is the fact that there aren’t any degradations in framerate initially. After about 1 hour flight time the problems start.
The following link deals with the Coherent GT interface, among other things:

If the problem is actually there, you have bad luck in MSFS:

Quote from Section 6 (APIS continued):

“Unfortunately the Coherent debugger doesn’t ship with the sim, but you can still see the effects by editing and building a package.”

Finally, it should be said that today (with Avidyne deactivated in the panel.cfg!) I performed a flight with 4 take-offs and landings and a total flight time of 4 hours in one session without noticing a degradation of the FPS rate.

For me it seems to be confirmed that currently complex gauges in Java-Script with Coherent GT interface are not the best solution in MSFS.

1 Like

That’s way out of date @ * 18 Aug 2020

The Coherant debugger most defintely ships with the sim, it’s part of the SDK.
It’s not bad, has some issues and a little bit of a learning curve.

I can see the value in it, but there are constraints imposed by the Coherant integration.
I can see why they chose it as a solution. Sometimes you have to go with the solution you have, not the one you wish you had, as the saying goes. It is what it is now, and unlikely to change.

SU12 will see them finally release some documentation for the aircraft side of it:

Nocturne answered • Jan 09 2023 at 10:54 PM | B21 commented • Jan 10 2023 at 6:55 PM BEST ANSWERACCEPTED ANSWER

Hello! We hope to have a list of coherent calls in the SU12 update along with updated JS/HTML/CSS documentation. It may not be complete for that release, but we are hoping it will be. It will at least cover the most important of the functions and list the available calls on the C++ side for things like flightplan management… and future updates will expand on the information (assuming it’s not complete for SU12, which, again, we hope it will be).

Ok, then it shouldn’t be a problem for Carenado to narrow down the error relatively quickly :wink: