Configuring Modules across multiple aircraft?

pegruder

I was wondering, is there an easy way to configure the modules across multiple aircraft?  Its taken about an hour and so far I have them almost setup how I want them, except they only work under the aircraft I had loaded (Beechcraft).  Any other aircraft it looks like I have to build them from scratch.  Am I missing something or is there an easy way to do this?

admin_pps

You can edit the config files and cut and paste for different aircraft (use them with GIT first but don't set anything).

The assumption with GIT is that you are avoiding GFConfig because the aircraft uses custom code and custom/bespoke lvars and events.

If all the aircraft comply with Simconnect standards, you will be better off using GFConfig to create a general config for multiple aircraft. When using lavrs, bespoke events etc, they will only ever work with the particular aircraft involved because the items will be unique.

Best wishes

Steve

admin_pps

PS, liveries for the same aircraft type are handled by the aircraft name in settings. See the user guide for details.

pegruder

I see.  I mainly jumped over to this application because GFConfig doesn't seem to work with FSX:SE.  I don't have any real addon aircraft or aircraft that require special settings, although thats great to know for the future just how powerful a tool this really is.  For me I'd like to get back to the basics although it seems Ill have to load up the CD version in order to do this unless there is some other way.

admin_pps

For FSX SE, you need to manually load the data bridge GFDevFSX.exe when FSX SE has started to get your GF Config settings to work. Goflight know about this issue, but no-one has complained so they won't fix it.

Best wishes

Steve

pegruder

When I try that I get the following error. "The application has failed to start because its side-by-side configuration is incorrect.  Please see the app event log or use the command-line sxstrace.exe tool for more detail."  A little upsetting they dont see to be motivated to fix it.  These modules certainly aren't cheap.  When I load the legacy simconnect, this error goes away, yet I cannot interact with any modules.  They remain blank with the exception of the MCP which just has dashes across the display.

admin_pps

I certainly saw that issue when FSX SE was initially released, however a Steam update fixed the legacy simconnect issue shortly after release which is why Goflight take the position they do.

I certainly did not install any legacy simconnect interfaces to make the Goflight data bridge or GIT to work after the initial SE release update.

Are you running the latest SE version?

Best wishes

Steve

pegruder

Latest SE version.  Just installed it last night.