v1.1 Update Details

Burnhaven

Could this pms50 add on in community be confusing things?

Directory of C:\Program Files (x86)\Steam\steamapps\common\MicrosoftFlightSimulator\Community\pms50-instrument-gtn750

03/07/2024 02:11 AM <DIR> checklists
08/18/2024 11:46 PM 48,344 checksum.txt
10/25/2023 06:23 AM 1,717 check_integrity.cmd
03/07/2024 02:11 AM <DIR> Config
03/07/2024 02:11 AM <DIR> ContentInfo
08/18/2024 11:46 PM <DIR> Documentation
03/07/2024 02:11 AM <DIR> fpl
03/07/2024 02:11 AM <DIR> html_ui
03/07/2024 02:11 AM <DIR> InGamePanels
08/18/2024 11:46 PM <DIR> Integration
08/18/2024 11:46 PM 66,840 layout.json
08/18/2024 11:46 PM 288 manifest.json
03/07/2024 02:11 AM <DIR> variables
07/10/2023 06:18 AM 21 verify.bat
08/17/2024 07:39 AM 6 version.txt
03/07/2024 02:11 AM <DIR> waypoints

Black Square

Thanks for posting those. The PMS50 folder is just the GTN 750 addon, which should have nothing to do with the message we're seeing here. From the panel.cfg that you posted, there should be absolutely no way for the aircraft to ever load my warning message. At this point, I suggest contacting Just Flight support, since they can look at your screenshots and directories to see what's going on here. If they can't get anywhere, they will bring me in the loop again when we have more information. From what I'm seeing here, I'm still betting that there is another copy of the v1.0 aircraft somewhere that the simulator is loading instead of this one. That seems like the only way to me that it could ever load the old v1.0 warning message.

Unless... you're not using a custom livery installed in the community folder, are you?

Burnhaven

@Black-Square There are a couple of 3rd party liveries in community. Not sure how often I use them but they do reference version 1.0

"dependencies": [
{
"name": "Turbine Duke N80WE",
"package_version": "1.0"
}
],
"content_type": "AIRCRAFT",
"title": "Turbine Duke N80WE",
"manufacturer": "MANUFACTURER",
"creator": "ryanbatc",

Black Square

The liveries could only cause the v1.0 message to load if you were using them while testing this issue. Otherwise, they should have no effect. Since you were able to conduct a global search for text strings before, do you think you could search for the following string in all *.cfg files on your system, or anywhere you think there is even a small chance of there being MSFS related files?

NavSystems/bksq-aircraft-turbineduke/WtGnsSu15Warning/WtGnsSu15Warning.html

Burnhaven

I use Agent Ransack. In the following results, this path is my own and MSFS should be unaware of it "D:\MSFS FROM LAPTOP\Aircraft"
The two entries not stricken through are the same, the first being a link in the community folder and the next the actual location.( a livery)

Search Criteria

File name: *.cfg
Containing text: NavSystems/bksq-aircraft-turbineduke/WtGnsSu15Warning/WtGnsSu15Warning.html
Look in: C:;D:;E:;G:\

Name Location Modified Size Type Hits

~~PANEL.CFG D:\MSFS FROM LAPTOP\Aircraft\Duke - Beechcraft\SaveAircraft_Panel Configs\panel\ 5/22/2024 8:14:24 AM 6 KB CFG File 2~~

PANEL.CFG C:\Program Files (x86)\Steam\steamapps\common\MicrosoftFlightSimulator\Community\Duke IFA\SimObjects\Airplanes\Duke IFA\panel.IFA\ 5/16/2024 4:00:00 PM 6 KB CFG File 2

PANEL.CFG E:\ADD ON LINKER COMMUNITY\Liveries\Duke IFA\SimObjects\Airplanes\Duke IFA\panel.IFA\ 5/16/2024 4:00:00 PM 6 KB CFG File 2

PANEL.CFG D:\MSFS FROM LAPTOP\Aircraft\Duke - Beechcraft\SaveAircraft_Panel Configs\PANELN2830B\ 5/8/2024 3:05:14 AM 6 KB CFG File 2
PANEL.CFG D:\MSFS FROM LAPTOP\Aircraft\Duke - Beechcraft\SaveAircraft_Panel Configs\panel323n\ 5/8/2024 3:05:10 AM 6 KB CFG File 2
PANEL.CFG D:\MSFS FROM LAPTOP\Aircraft\Duke - Beechcraft\SaveAircraft_Panel Configs\PANELN3675D\ 5/8/2024 3:05:04 AM 6 KB CFG File 2
PANEL.CFG D:\MSFS FROM LAPTOP\Aircraft\Duke - Beechcraft\SaveAircraft_Panel Configs\PANELN585K\ 5/8/2024 3:05:02 AM 6 KB CFG File 2
PANEL.CFG D:\MSFS FROM LAPTOP\Aircraft\Duke - Beechcraft\SaveAircraft_Panel Configs\PANELN6060X\ 5/8/2024 3:04:58 AM 6 KB CFG File 2
PANEL.CFG D:\MSFS FROM LAPTOP\Aircraft\Duke - Beechcraft\SaveAircraft_Panel Configs\PANELN610DS\ 5/8/2024 3:04:52 AM 6 KB CFG File 2

Burnhaven

Removing that livery from the PC seems to have the avionics displays working normally now.

Black Square

Very interesting. Thank you for sharing the solution, and I'm glad it's working for you. Could you share a link or the exact name of that livery so I can see exactly what was happening behind the scenes?

Burnhaven

@Black-Square Duke IFA_Q0VMU.rar
https://flightsim.to/file/75050/infinity-airways-blacksquare-turbine-duke

I'm thinking the "autopilot issue" has nothing to do with liveries/avionics messages. I still sometimes get the AP showing the go around light lit "GA" but if I get it into altitude hold first, then I can usually go from there to attitude hold. So it's either I'm not understanding how it works, or it's a bit "fiddly" and I have to remember how to finesse it.

Black Square

Thank you for sharing the exact livery. As for the autopilot, I have very rarely seen what you are describing. The issue is that Asobo provides no way for aircraft developers to detect whether the flight director is in go-around mode. This means that I detect it by process of elimination. In the Dukes, the autopilot should always default to pitch mode, meaning that "GA" will only display if you activate it. However, I saw some circumstances where this could be defeated, particularly by external hardware. I don't know if that matches your situation at all, but the short version is: Due to MSFS's limitations, the autopilot may appear to be in Go-Around mode, when it's actually in no mode at all.

Burnhaven

Got it , thanks. Noticed this thread but I think I know how to use the AP effectively now so haven't finished that post.
https://community.justflight.com/topic/6463/trying-to-get-to-grips-with-the-att-autopilot-mode