• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

MSFS2020 Override An Aircraft's Panel.cfg

Messages
5
Country
unitedstates
Hello:
I am attempting to install in instrument in an already published aircraft and was told that to do that I must "Override the Aircraft's panel.cfg" but, unfortunately I haven't a clue as to how to accomplish that. I am hoping someone on this forum can enlighten me as to what I have to do.
Thanks for any help you can provide.

Sparky
 
You have to learn how to "create an addon livery," it is a fairly common procedure that has many references and tutorials and then you will need to adapt that procedure to your object. In the same way addon liveries override the models aircraft.cfg, your addon will override the default panel.cfg.
 
I thought surely that clue would open up the answer but, alas, it only led to tutorials about how to go about creating a livery that, while very interesting, did not solve my problem. Perhaps more information would help.
I have the code for an autopilot; the developer said that I needed to "create a community package to override the Asobo" autopilot by creating a panel.cfg file that would somehow replace (by overriding) the original panel.cfg file. He indicated that it was the same procedure that livery creators used to 'override' the original livery. That procedure is what eludes me. And I have searched and searched but so far, come up empty.
I appreciate any additional clues that I can use to solve this mystery.

Sparky
 
An autopilot is far more sophisticated than an instrument, both in reality and sim. Autopilot functionality is going to route through SimConnect and again, you will want to refer to available resources, the SDK has some details and examples for SimConnect. It seems more like you start with SimConnect radio commands, or SimConnect state changes, maybe work up to a remotely operated stick, or rudder, or both, not sure, it's not my forte. But to expect to have a functioning autopilot "instrument" that will work with MSFS through a panel.cfg, seems optimistic.
 
WTT - Working Title Technologies - has written the code for a 3-axis autopilot that is claimed to be better than the one in the Sim. It is controlled by sending it H: commands (button pushes and dial twists) and it replies with L:vars (LEDs and displays). It, in turn, connects with the Sim through the normal SimVars and Event commands. It allows Sim aircraft so equipped to behave like the real thing! To install the code requires overriding any other autopilot; that was the real source of my question.
Thanks for getting back!
 
Do you have access to the panel.cfg? For example, it's not encrypted (because if it is encrypted you're going to have a bad time because you need to know what is in the panel.cfg).

If this is just for you, just for an aircraft that you own then you could just edit the panel.cfg directly without needing to make a project that overrides it.

I ask this because something as "simple" as writing a project to override the panel.cfg isn't really that simple. There's a bunch of files you need to setup correctly which is a real pain in the butt. If you can get away with directly editing the panel.cfg then your life becomes significantly easier.
 
Back
Top