That's because he wants to sell you newer stuff, the modules have not changed over the years  other than they are now gray instead of black.

 

WHAT??? You're kidding me, right??? (He says in mock horror, tongue in cheek.) That, of course, did enter my mind. And I thought about it, since he was kind enough to say he'd be glad to sell me a new one at 15 percent off. It just wasn't worth it. The old stuff, except for the LEDs, works fine, and the knobs turn all the proper pointers and displays in the cockpit. And after all these years of simming, I'm just about done with any major equipment purchases. Besides, DYI-ing it is more fun.

 

 

So how far do we get with Goflight's own software?

 

Not very far to be honest,

It supports Default aircraft and has built in support for LevelD, iFly 737 and Project Magenta.

The Goflight software from Pollypot is far more comprehensive and can handle anything that it can find the LVars for.

For panels coded in C/C+ then the FSuipc mouse Macros is an easier way to go.

 

So basically if the addon uses any default functions and many do use parts of the Default AP code the Goflight stuff will work for those functions, If there are custom coded functions in the AP code then you will need to use something else either FSuipc or the Pollypot Goflight tool.

 

 

I couldn't get any of them to work...tried and tried and tried. Did you have the CX 2.0?

 

Greg,

I had the CX 2.0 and the mouse macros work fine in this addon.

Here is the .MCRO that I was using. Every other function not in this mcro  worked fine

with the goflight stuff set to default, I disabled my Goflight MCP in the Goflight software and used my older (small) Goflight Adv Autopilot panel with the functions covered in the Mcro set to not used in the Goflight software, everything else set to default.

[Macros]
Module="ESDG_CitationX.GAU"
1=HDG UP
1.1=RXa4390*X55cc,19
1.2=RXa43b0*X55cc
2=HDG DOWN=RXa43d0*X55cc,19
3=ALT UP=RX763e0*X55cc,19
4=ALT DOWN=RX76400*X55cc,19
5=FLC BUTTON=RX165ca0*X55cc
6=VSPEED BUTTON=RX165ac0*X55cc
7=ALT Hold BUTTON =RX165cf0*X55cc
8=HDG Hold BUTTON=RX165d40*X55cc
9=NAV LNav BUTTON=RX165c50*X55cc
10=NAV VNav BUTTON=RX165c00*X55cc
11=APPR BUTTON=RX165b60*X55cc
12=BC BUTTON=RX165a70*X55cc
13=BANK BUTTON =RX165b10*X55cc
14=NOSE DN=RX1658a0*X55cc
15=NOSE UP=RX165850*X55cc
16=AP MASTER=RX1659f0*X55cc
17=YAW DAMP=RX1659a0*X55cc
18=efis 1 up=RXeb260*X55cc
19=efis 1 down=RXeb2b0*X55cc
20=efis 2 up=RXeb0f0*X55cc
21=efis 2 down=RXeb140*X55cc
22=efis nav button=RXeb1b0*X55cc
23=efis fmc button=RXeb190*X55cc
24=efis pre button=RXeb1d0*X55cc
25=ias mach co butt=RX165bb0*X55cc
26=range plus=RX16b1c0*X55cc
27=range minus=RX16b200*X55cc
28=Heading up=RXa43b0*X55cc
29=aileron left wd=RX749a0*X55cc
30=aileron right wd=RX748e0*X55cc
31=efis selector +=RXeb260*X55cc
32=efis selector -=RXeb2b0*X55cc
33=fms button=RXeb190*X55cc
34=rudder trim left=RX4f5d0*X55cc
35=rudder trim righ=RX4f560*X55cc

Huh...go figure.  I tried for hours to get even one macro to work...tried many switches.  Couldn't get FSUIPC to show the name dialog at all with that airplane.  Logging was on and I could see that FSUIPC was aware I was clicking...just no dialog.  I gave up.  The frozen MFD was the last straw.  A shame because, even with the rough VC, I really, really wanted to like that plane and would have stayed working on it a long time to get it to work.

 

Gregg

The old stuff, except for the LEDs,

 

Odd, I have the old stuff also (Circa 2005 ish) and the LEDs work fine?

 

I've done the mouse macro process also using FSUIPC ... althought I applaud Pete's work here most newer aircraft just don't work with mouse macros.  Also, FSUIPC will only work with events and can't work with Lvars (local variables).

 

I know GIT (GoFlight Interface Tool) is difficult to use and still can't sometimes get all Aircraft features to work, but it's the only tool that has got me "close" on newer aircraft ... however the CS 777 is turning out to be difficult for some elements.

 

Mouse free is my goals ... haven't reached that goal yet with any aircraft, but I keep trying.

 

FYI, I have reached out to Steve (GIT dev) and offered any programming assistance for us P3D folks, maybe he'll give me the opportunity to move the product along to be a little more end user friendly.

 

Cheers, Rob.

 

 

So how far do we get with Goflight's own software?

Is it that limited?

 

Depends on the aircraft ... for GA aircraft using standard events you (see Pete's list, it's a long one) you can get pretty far (close to 100%) ... also depends on if you use a GPS unit like the GTN 750.

 

As I understand it the GIT (Goflight Interface Tool) came into existance because GoFlight provided Steve (the dev) free hardware to make it work ... so I guess you can say GoFlight did pay to have the GIT produced.

 

GFConfig is easier to use but less powerful, GIT is harder to use but more powerful in what it can see and do ... GIT also has ability for scripting that can be define for every bespoke created ... i.e. If E1FuelPressure = 50 Goto LowPressure ... etc. etc.

 

You can do A LOT, but unfortunately there are still some events Aircraft developers don't expose (meaning a click in the VC is the only way to make it work).

 

Cheers, Rob.

 

 

Mouse free is my goals ... haven't reached that goal yet with any aircraft, but I keep trying.

 

++ mouseless.  Even non-complex airplanes, generally, have small stuff that evade me.  A2A and the Flight1 Mustang are, probably, the closest I've gotten so far.  Might be able to get the NGX that way but...LOL...I don't have that many switches!! 

 

 

I don't have that many switches!!

 

Buy more switches and buttons ... can never have too many (just make sure you use powered USB hubs)

 

I'm slowly putting together a master list of Lvars and what does and doesn't work with the various 3rd party aircraft.  Will publish it on my web site once I get it at a "reasonably" complete state.

 

It does seem strange how 3rd party aircraft devs don't make their switch/button operations accessible, especially for the more complex aircraft where fiddling around with a mouse at a critical point of flight during bad weather can make for some interesting moments.

 

Cheers, Rob.

Thanks for the GF software feedback,

 

gb.

Quick update, success!!  GIT (Goflight Interface Tool) samples at 6Hz to capture VC inputs ... this is too slow IMHO (at least for the detection side of things).  So what was happening is some events simply just didn't show in GIT ... so I was missing the "entire" picture of what was going on in my CS 777.

 

So, a temp solution that seems to be working in most cases was to rapidly click the VC controls I'm working with until I see these "mysterious" Lvars (local variables) get exposed and (in my case the Lvar "klid") and most importantly the data value the Lvar holds.

 

Anyway, previous VC operations that I thought were inaccessible are now accessible and can be mapped to my GF modules.  I've already donated to Steve's GIT software, but will donate again if he can fix this little issue quickly ... variable Hz sample rate in the detective functions only will probably solve it.

 

Cheers, Rob.

 

 

As I understand it the GIT (Goflight Interface Tool) came into existance because GoFlight provided Steve (the dev) free hardware to make it work ... so I guess you can say GoFlight did pay to have the GIT produced.

 

Rob, this statement is totally untrue and does a disservice to the thousands of hours of R&D carried out by me to develop GIT. I developed GIT because I had over £2000 worth of GoFight equipment and was tired of writing lengthy LUA code to support custom aircraft. Initially the code I developed was for the PMDG NGX (Gofilght PMDG Interface) and I allowed GoFlight to publish it free of charge. There were 2 modules I did not own that I was programming and supporting blind and Goflight kindly offered those modules so that their customer base could be supported for the PMDG NGX. The code was subsequently developed into GIT and GoFlight had no involvement - intellectually or financially.

 

To suggest that somehow GoFlight bankrolled the development of the GoFlight Interface Tool is a blatant lie and suggests to people that their donations to this project are worthless. I will tell you this; that financially my time would have been better spent flipping burgers at McDonolds a 1000 times over than pursuing the GIT project; but I did because its a hobby and passion that interested me.

 

I have no idea why you came to the conclusion you did, but as a moderator of Avsim I would expect much better judgement or at the very least least a conversation with those insinuated in your assumptions.

 

Regards

Steve

Sorry Steve certainly no mis-information intended on my part, my sincere apology and I'm glad you corrected my understanding. I must have mis-understood the information provided to me (by another source)... Again my apology as I should know better, please keep up the great work and hope to see future updates and continued passion.

 

Cheers Rob