v1.1 Update Details
-
That's a good trick with the symbolic link. I remember setting that up for X-Plane years ago.
This is a truly bizarre issue. Are you sure you don't have a second copy of the v1.0 Turbine Duke somewhere on your computer that is somehow being loaded and superseding the one in this linked community folder?
Could you send me the contents of the panel.cfg files in any of the panel directories, please?
-
here is one of the panel.cfg files:
// Panel Configuration File
[VCockpit01]
size_mm = 320,234
pixel_size = 320,234
texture = $GNS530Screen
htmlgauge00=NavSystems/GPS/WT530/WT530.html, 0, 0, 320,234[VCockpit02]
size_mm = 350,190
pixel_size = 350,190
texture = $GNS430Screen
htmlgauge00=NavSystems/GPS/WT430/WT430.html, 0, 0, 350, 190[VCockpit03]
Background_color = 0,0,0
size_mm = 650,768
visible = 0
pixel_size = 650,768
texture =$GTN750Screen_PMS
htmlgauge00=NavSystems/bksq-aircraft-turbineduke/pms50_gtn750_int/gtn750_int.html, 0,0,650,768[VCockpit04]
Background_color = 0,0,0
size_mm = 650,287
visible = 0
pixel_size = 650,287
texture =$GTN650Screen_PMS
htmlgauge00=NavSystems/bksq-aircraft-turbineduke/pms50_gtn750_int/gtn650_int.html?index=2, 0,0,650,287[VCockpit05]
size_mm = 800,110
pixel_size = 800,110
texture = $Radio1ComScreen
htmlgauge00=Generic/Radios/bksq-aircraft-turbineduke/KX155B/KX155B.html?Index=1, 0, 0, 800, 110[VCockpit06]
size_mm = 800,110
pixel_size = 800,110
texture = $Radio2ComScreen
htmlgauge00=Generic/Radios/bksq-aircraft-turbineduke/KX155B/KX155B.html?Index=2, 0, 0, 800, 110[VCockpit07]
size_mm = 500,70
pixel_size = 500,70
texture = $AdfScreen
htmlgauge00=Generic/Radios/bksq-aircraft-turbineduke/KR87A/KR87A.html,0,0,500,70[VCockpit08]
size_mm =440,100
pixel_size =440,100
texture =$TransponderScreen
htmlgauge00=Generic/Transponders/AS330/AS330.html, 0,0,440, 100[VCockpit09]
size_mm = 256,52
pixel_size = 256,52
texture = $DmeScreenTurbine
htmlgauge00=Generic/Radios/bksq-aircraft-turbineduke/KDI572R/KDI572R.html, 0,0,256,52[VCockpit10]
size_mm = 1024,94
pixel_size = 1024,94
texture = $Kns81Screen
htmlgauge00=Generic/Radios/bksq-aircraft-turbineduke/KNS81/KNS81.html?Index=1, 0, 0, 1024, 94[Vcockpit11]
background_color=0,0,0
size_mm = 650,768
pixel_size = 650,768
texture = $GTN750Screen_TDS
htmlgauge00=WasmInstrument/WasmInstrument.html?wasm_module=Gauge/TDSGTNXiGaugeModule.wasm&wasm_gauge=GTNXI750U1, 0,0,650,768[Vcockpit12]
background_color=0,0,0
size_mm = 650,287
pixel_size = 650,287
texture = $GTN650Screen_TDS
htmlgauge00=WasmInstrument/WasmInstrument.html?wasm_module=Gauge/TDSGTNXiGaugeModule.wasm&wasm_gauge=GTNXI650U1, 0,0,650,287[VCockpit13]
size_mm = 512,374
pixel_size = 512,374
texture = $RadarScreen
htmlgauge00=NavSystems/bksq-aircraft-turbineduke/bksq_wradar1/bksq_wradar1.html, 0, 0, 512, 374[VCockpit14]
size_mm = 512, 175
pixel_size = 512, 175
texture = $EngineMonitorScreenTurbine
htmlgauge00=Generic/Misc/bksq-aircraft-turbineduke/EngineTrendMonitor/EngineTrendMonitor.html?Index=1, 0, 0, 512, 175[VCockpit15]
size_mm = 512, 1024
pixel_size = 512, 1024
texture = $EngineInstrumentReadouts
htmlgauge00=Generic/Misc/bksq-aircraft-turbineduke/EngineInstrumentReadouts/EngineInstrumentReadouts.html, 0, 0, 512, 1024[VCockpit16]
size_mm=0,0
pixel_size=0,0
texture=$NONE
background_color=42,42,40
htmlgauge00= NavSystems/bksq-aircraft-turbineduke/pms50_gtn750_int/AP1.html, 0,0,0,0[VCockpit17]
size_mm=0,0
pixel_size=0,0
texture=$NONE
background_color=42,42,40
htmlgauge00= NavSystems/bksq-aircraft-turbineduke/pms50_gtn750_int/AP2.html, 0,0,0,0[Vcockpit18]
size_mm = 860,388
pixel_size = 860,388
texture = $Kln90Screen
htmlgauge00=NavSystems/bksq-aircraft-turbineduke/KLN90B_int/KLN90B_int.html, 0, 0, 860,388[Vcockpit19]
size_mm = 700, 1024
pixel_size = 700, 1024
texture = $TabletScreen
htmlgauge00=Generic/Misc/bksq-aircraft-turbineduke/BlackSquareTablet/BlackSquareTablet.html, 0, 0, 700, 1024[VCockpit20]
size_mm = 512,374
pixel_size = 512,374
texture = $WeatherSquare4000Screen
htmlgauge00=NavSystems/bksq-aircraft-turbineduke/WeatherSquare4000_int/WeatherSquare4000_int.html, 0, 0, 512, 374[VPainting01]
size_mm = 3072,3072
texture = $RegistrationNumberExt
location = exterior
painting00=Registration/bksq_duke_registration.html?font_color=black&stroke_size=45&stroke_color=transparent&shadow_color=0x6D3913&sv=1&sx=5&sy=41.5&sr=5.5&sk=20&ss=325&tv=0&tx=16&ty=8&tr=0&tk=20&ts=338&wv=0&wx=32&wy=20&wr=9&wk=30&ws=225, 0, 0, 3072, 3072//This Black Square aircraft utilizes a novel dynamic tail number system for better liveries.
//The tail number can be positioned on the winglets, the tail, or on the sides of the aircraft, or any combination at the same time.
//Each position ("s" = side, "t" = tail, and "w" = winglets) has the following associated variables:
//"v" = whether to show the tail number in that position (0=false, 1=true)
//"x" = the nose-tail position of the tail number
//"y" = the top-bottom position of the tail number
//"r" = the rotation of the tail number (will accept decimals)
//"k" = shears the tail number, positive values shear top towards tail
//"s" = the font size of the tail number
//Example "tk=30": t = tail, k = skew. This will shear the tail number on the tail towards the tail of the aircraft by 30 degrees
//For livery creators, the tail number will not automatically resize, so make sure there is room for a full six character number
//Apologies for the short variable names. MSFS seems to cap URL's at around 215 characters.
//Tail Number Positioning:
//Side +X -> Forward, -Y -> Up
//Tail -X -> Forward, -Y -> Up
//Wing -X -> Forward, -Y -> Up
//NOTE: These values can be easily edited live using the Coherent GT Debugger from the MSFS SDK.[VPainting02]
size_mm = 1024,256
texture = $RegistrationNumberInt
location = interior
painting00=Registration/Registration.html?font_color=white, 0, 0, 1024, 256 -
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 -
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?
-
@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", -
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 -
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 2PANEL.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 -
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?
-
@Black-Square Duke IFA_Q0VMU.rar
https://flightsim.to/file/75050/infinity-airways-blacksquare-turbine-dukeI'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.
-
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.
-
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
