Minor issues above my head

Louis

This is for Steve. When the beta interface came out you came into my computer and set it up . I just got a brand new rig built , I bought the interface tool and got the go flight conf. tool last week . I have 9 Go flight modules and when I bought the interface tool last week for some reason every thing that was set for some reason set itself in the interface tool like i had before witch is good cause I don't have to reprogram them . The issue is it has some minor issues and there's no way I can figure it out. Can you come in again with team view to stream line the set up and I'll pay you like last time ? remember your about 7 to 8 hours ahead ----Thanks Louis

admin_pps

Hi Louis,

What are the issues?

Thx
Steve

Louis

I'll try to explain
Brand new computer
Have these drives -- Local Disc (C) -- FSX (E) -- Mass(F)
Mass(F) is the complete back up of my old computer
I bought the Interface tool and downloaded the Go Flight conf.tool last week
The payware Interface tool some how imported all the PMDG settings from the Beta PMDG interface tool to this payware one the settings you assigned way back
In the Go-Flight Confi. i have
DEfaultFSX.gfc
General Aircraft.gfc
When you set me up you added PMDG to it - when i wanted to fly a PMDG i would go in the Go flight Conf. open PMDG and the beta interface pick a 737 and away we we'd go
Now flying general aircraft is fine, but when i open the Interface Pay ware and fly the PMDG they seem to be crossed with the general settings especially the Advanced Auto pilot . Don't know if i explained it right but flying the 737 is not like it was

admin_pps

OK, that is fairly straight forward to fix:

1) Start GFConfig.
1a) If you own an MCP PRO, click on its picture and then click the drop down list box and set it to "Compatible Add-On" (it normally shows FS Default).
1b) If you own an EFIS, click on its picture and then click the drop down list box and set it to "Compatiable Add-On".
1c) If you own an MCP Advanced, click on its picture and ensure that all options are set to FS Default and all actions are set to nothing.
1d) Remove all assignments to all other devices in GFConfig that you wish to control via the GoFlight Interface Tool.
1e) In GFConfig, click File, Save Configuration As, and enter GIT or PMDG and then click Save. You must always load this configuration (if it isn't already loaded) before using the GoFlight Interface Tool.

Best wishes
Steve

Louis

Followed what you said and its coming , few things going on - Brakes on and off you can hear the sound but they don't work. the APU I finally got it to work following the tutorial by Chris from Angle of Attack . This one I don't have a clue - I have both rotaries for the IRS on one RP48 and both rotaries for the start switches on an other RP48 - When I set the engines start switches to Cont on take off in the air I engage the Auto pilot ,at 10,000 feet when I set the start switches to off the whoop whoop sound comes on and the auto pilot goes off and the exactly same thing if I roll the rotary IRS the auto pilot will disengage, have no clue on this one. Also the GF46 is way out and used to work so good when you set it up. It shows Flight and Alt to set it on the over head panel but if I roll the dial to set them, they just show mixed up numbers, the ADF seems to be fine

admin_pps

Try the same flight procedure but don't use the RP48, do it in the Virtual Cockpit and see if the same thing happens in flight.

Check in GFConfig that you have nothing configured for the GF46 in the PMDG config you made from my previous response. I suspect GIT and the GoFlight drivers are both writing to the GF46 and messing things up.

Best wishes
Steve

Louis

Here's what I did after you wrote about the drivers In Go flight Conf I have Default and PMDG when I opened up PMDG I noticed all my 7 modules of radios, buttons, and switches etc were set same as for General Aircraft ,so I set them all to "No selection" and so far so good . Only problem I have now is in the PMDG interface tool my Nav radio GF166 don't work , it will ident the green lights but dark screen --In Device 1 I have the com's and they are fine and I set the Nav the same - input event -on ---NAV_RADIO_SWAP - Input action Nothing- light action Nothing but still can't get the Nav's to work, besides that after 2 weeks of monking around I might get a flight in .

admin_pps

If you find it easier, I think you can setup the GF166's as COM , NAV etc in GFConfig and they will work OK with the PMDG...well last time I checked they did!

Best wishes
Steve

Louis

Tried that and think your right the Nav radio seems to be ok , so far any way .Pretty well every thing is working like it did .My next one for sure shortly will be the PMDG 777 .Still would like to know how in heck did it sneak every setting over from my back up drive from my "ol rig and set every thing in the new payware Interface tool that you set up with the beta is beyond me. So to recap my future purchase with the 777, in the Go Flight conf., right now I have Default - General Aircraft and PMDG- so am I right on saying that when I get the 777 I will make a profile called on '777' and i probably will set the 9 modules pretty close to what I have in the 737NG witch I couldn't do with the bata .

admin_pps

A lot of the GoFlight hardware for PMDG aircraft auto configures so it may necessarily have come from a settings file. If you did copy over any config files, GIT does recognise the old file formats and converts them automatically.

Not necessarily, your new PMDG profile will probably work fine with the 777.

Best wishes
Steve