XML files you need for CS 777 to be used with GoFlight modules and GIT.

Took me a while (about 3 days) to get all these sorted out for the CS 777 and working with all my GoFlight gear.  Here is a single ZIP file containing:

BespokeEvents.xml

BespokeVariables.xml  (primarily for controlling LED states)

CS_B777-200ER_GE.xml 

CS_B777-200ER_GE_GFEFIS.xml  (can import direct into GIT if you just want EFIS functionality)

CS_B777-200ER_GE_GFMCPPRO.xml  (can import direct into GIT if you just want MCP-Pro autopilot functionality)

https://drive.google.com/file/d/0Bw0Q-fAfEZwyRnFYYXRWZzNpZkE/view?usp=sharing

I didn't do every single button, knob, switch, dial in the CS 777 ... as many as I could to fill up my collection of GF gear.  For example I use 1 pushbutton with LED to toggle the 6 bleed air buttons (Eng, APU, ISLN) and 1 push button with LED for the PACK and TRIM AIR and some items like "Hydraulics" I skipped completely.

However the MFD and mode selection for the MFDs are all there so I can check the state of any system and/or checklist.  Individual dimmers for each MFD is mapped to dials and much more.  But I tried to make sure I covered everything I would need in normal flight (no emergency) ... also enough there for APU and Engine start during push back (gives one the opportunity to watch the engines fire up in an external view).

I'm finally mouse free during flight which was my primary goal.

Steve's wonderful GIT is located here: http://www.pollypot-software.org.uk/goflight-interface-tool.html -- if you find the tool useful I highly recommend you donate to his efforts for continued support/development.  He offers FSX and P3D versions.

Now, onto the MJC Q400 and then the Airbus.

Cheers, Rob.

P.S.  I'm sure I'll edit these files over time as I discover better ways to accomplish tasks.