Porchpup

No problem. Glad to help.

Here you go..... Back up your Panel.cfg file. Then just replace [Window 05] with this.... [Window05] Background_color=0,0,0 size_mm=1095,1200 position=0 visible=0 ident=405 window_size= .500, 1.000 zorder=85 gauge00=PMDG_737NGX!TopOvhd, 1,-1,1096,75 gauge01=PMDG_737NGX!FlightControls, 0,75,249,348 gauge02=PMDG_737NGX!NavDisp, 0,424,249,255 gauge03=PMDG_737NGX!Fuel, 0,680,249,371 gauge04=PMDG_737NGX!Electric, 250,75,241,976 gauge05=PMDG_737NGX!OvhdCtr, 492,75,115,976 gauge06=PMDG_737NGX!AntiIce, 608,75,237,394 gauge07=PMDG_737NGX!Hydraulics, 608,470,237,145 gauge08=PMDG_737NGX!Doors, 608,616,237,96 gauge09=PMDG_737NGX!CVR, 608,713,237,90 gauge10=PMDG_737NGX!CabinAltPanel, 608,804,237,247 gauge11=PMDG_737NGX!Lights, -3,1052,1097,147 gauge12=PMDG_737NGX!CabinPress, 846,742,250,309 gauge13=PMDG_737NGX!BleedAir, 846,424,250,317 gauge14=PMDG_737NGX!AirCond, 846, 75 ,250,348

Thanks Steve.

Steve is the DATA_FWDOH_GROUND_POWER_AVAILABLE working correctly? I have a toggle switch assigned to turn on the ground power and I'm trying to assign the light above to match the GRD Power Available light. I cant seem to find the right combination. Also it appears in the Light Data as... DATA_FWDOH_GROUND_CONNECTION_AVAILABLE, instead of DATA_FWDOH_GROUND_POWER_AVAILABLE. Is this right?

I'm not sure how the CH works but on my Saitek there is a detent when you pull the throttle back beyond idle. This detent shows up as a button in FSUIPC. Set the reverse thrusters like this...

In FSUIPC make certain that you have your throttle axis assigned using the type of action "Send direct to FSUIPC Calibration". Then go to Joystick Calibration page 3. Throttle 1 and 2 should say "Axis is not processed". If not the just hit Set then Reset and click OK. You should have your A/T manual override set to "In Hold/Arm Mode Only". That will allow you to abort a takeoff by pulling back the throttles and deploying the reverse thrusters.

Absolutely great job Steve. Prime example of the people that make this hobby such a wonderful experience. I can not think you enough for the time you have dedicated to this project. I thought I'd share these with anybody that may want to use them. I made these to keep track of the function settings I used for each switch or button. Always good to have this info backed up, in writing, just in case. I only have these two thus far but have a RP48 on order and will make one for it when it comes in. They are .jpg images so just save and print how ever many you need.

That is because the GoFlight trim wheel acts as a switch and not an Axis.

I thought it was just me but mine does that sometimes on page 62. Locks up and stops responding.

This is something that makes sense. I have no problem posting my full name but maybe things should be different it one is underage.Thanks for the tutorials Matthew. They are well done and have help me since I first discovered them on YouTube.

3D, VC, Ezdok with hot keys or TrackIR if you are working with only 1 monitor.With multi-monitors, the 2D world opens up to a lot of possibles.

Might be a sore subject depending on your opinion of the entire situation. :(

Click Start. Open the Control Panel. If needed click the arrow next to the words "Control Panel" at the very top so that it will display "All Control Panel Items".Click Folder Options. Click the View tab. Then click the line that says "Show hidden files, folders, and drives".Click Apply then OK and you should be good to go.

Too Cool! Isn't this a great hobby.

Are you using EZCA?

My pleasure. Glad I could help.

Got it. Thanks

My Mistake....

Are you guys referring to the "blue arc/tick mark" showing on the display when using FSUIPC for throttle axis assignment?

PM me your email, and I'll send it to you.

Funny thing is, I caught it at just the right moment yesterday and found a letter from the web provider explaining what was going on.I did manage to save it before it was removed but I'm a bit hesitant to post it on a public forum because it does not paint a pretty picture.If what they say is true, it makes perfect sense as to what's going on at GoFlight and some of the new personnel making decisions.I don't think it's a Hack job. Anybody that is a GoFlight fan knows that things have not been normal and something funny is going on.I truly hate to see it because the product is not "Crap" or "Rubbish". It is great equipment and works as advertised at an affordable price.

Huh?Happy New Year To All!!

Bravo! This fixed my hanging when closing out of FSX.Nice work Steve. Everything seems to be working well at this point.

OK....Let's start over here.In the modules folder I have a trimNGX.lua and a trimNGXthread.lua from your original zip file.Then you posted the script, not a file, but a script that I copied and pasted in notepad and saved it as trimNGXtimer.luaDid I do that right?In the FSUIPC.ini file I already had a.....[Auto.NGX]with another lua assigned to 1=Lua bla bla blaSo do I still assign your lua as 0=Lua trimNGXtimer or use another number such as 2?This stuff still confuses me.

Oh My! Is it April Fools Day!