The Breezer is doing good, both in #msfs2020 and #msfs2024, but even the Devs of the plane weren’t able to eliminate the blacked out “engine monitor” (EIS) from the main PFD (screen).
In panel.cfg, they use htmlgauge00=NavSystems/AS3X_Touch/AS3X_Touch.html?Index=1, 0, 0, 1280, 800
I’d like to exchange the AS3X against the new WT G3X v2 or v1, if only legacy is compatible.
Therefore, I switched (according to documentation - LINK) to the v1 and v2 Working Title G3X by editing the line to:
htmlgauge00=NavSystems/G3X_Touch/G3X_Touch.html?Index=1, 0, 0, 1280, 800
G3X Documentation of the panel.cfg
The screen stays black afterwards and I can’t tell if the link to the WT G3X HTML is not working or if a fliter needs to be adapted.
Any suggestion welcome.
You might want to relocate my topic to “User support” → “Aircraft & Systems”
There is an Avionics Framework channel on the Working Title Discord server where I imagine you would get a lot of support and feedback.
1 Like
Well, I read their discussions but I think, they support mainly their new G3X and the transition from old AS3X to G3X is a topic of 2023. I didn’t feel mature enough to ask about this little side project.
I’m just hoping, that somebody who created G3X mods for other planes reads this. Many struggled with SU15 and I’d like to hear, if there were suitable strategies to mod an old aircraft or if we’re depending to the goodwill of the developer.
There was a user here who made some G3X mods that he put on fs.to. You might be able to contact him there.
I checked here on the Forum and I can’t tell if he’s still active or not. His old forum tag doesn’t seem to come up with a search, so I don’t know…
https://flightsim.to/profile/EnsiFerrum
.