Majestic Dash 8 Q400 - MCPPro+EFIS+2 GF166's V2.1

Slayer

Now with the release of GIT 2.2.4.1 software we have the ability to export GF166 profiles so I've included support for those.

I've updated a few things I wasn't happy with and included 2 profiles to use with GF166 radios. You must purchase the retail version to use the radios import functions, everything else remains the same and should be able to be used on the previous version of the software.

As with my other versions you need to clear out your bespoke events first as more functions were added. Please have a look at the readme before jumping in.

There is a small issue with toggling the radios between the left and right sides that should get corrected in a future GIT update.

Slayer

The radio issue mentioned above appears to be  corrected in today's GIT release.

If anyone runs into issues please don't hesitate to ask.

Slayer

Had to re-export the configs again -  All the changes didn't go through.  Please use version 2.3.0.0 of the software and the new Goflight drivers.

As usual blow out all the bespoke events, reimport  and then reimport the MCP, EFIS and radios

Slayer

Newest version

Slayer

...

admin_pps

Hey Steve,

The new version of GIT supports the Majestic Q400 External XMl Interface directly now (version 2.4.1.0 +) so you can think about simplifying your config as there is no need for the Start Bespoke Event anymore and all the other complications. See this for more info: http://www.pollypotsoftware.org.uk/support/user-guide/user-guide-git/19-operating/97-configuring-goflight-devices-additional-information-majestic-dash-q400.html

Best wishes

Steve

Slayer

That's great! I'll revise the profile once I return from Flightsimcon. Thanks for all your hard work.

Slayer

I've had a chance to read over everything. 

So basically to use the fake lvars will require a total remake using this method since we are not supposed to use the fake LVARS and  the old method together.

I'm assuming you can't use the two together because you could potentially have a code for a wrong variable if they both fired close together and you had low FPS . 

Steve removed the need to use the read/write/ codes etc and incorporated everything off the spreadsheet with the reads and write being done on the fake lvars behind the scenes to make it easier to manipulate.

The problem I had originally was that very few of the simconnect events/lvars work at all and there is a lot missing from the majestic documents as well so I had to poke and prod their mouse events to get what I wanted in the end. ( the pitch wheel is a perfect example, I had to emulate what I saw happening in the detective which required 2 things to make it work.)

 I'm not sure it's worth the time investment to do a total rewrite as I'll still have to work around the limits of what majestic made available. It took weeks of picking away at it 1 item at a time until I had it working satisfactory. Many of the items were not obvious as to which  item in the spreadsheet would manipulate what you wanted, I never documented what the CRC 's were and to be honest some things took me hours to figure out. It's spaghetti code lol.

I do see this method very useful if I were to be building a full simpit  and wanted to map every function but someone else will have to pick up the torch on this

 This may all  change yet again when they release the training version... It's supposed to be networkable across multiple PC's