X-Plane 2.0.0.0

DavidWilliams5620

Hi Steve,
Was able to start testing your new x-plane version and have had some difficulties. I wanted to start from scratch so I uninstalled the previous version of GIT, deleted the documents folder (after saving the profiles somewhere else), started GIT to make sure I was running 2.0.0.0 and removed all bespoke events/tasks using the big red button in detective.

Next step, import the bespoke variables and events using detective. Worked OK.
Copied the b738 profiles back into /documents/GoFlight Interface Tool directory.
Foe each of the devices, imported their profile into GIT. Worked OK.
Shutdown GIT and X-Plane.

Start X-Plane and once sitting at a gate in 'cold & dark', start GIT.
As usual the MCP-Pro displays flash and then go dark. (The profiles use AV_Enabled).

Start battery. Nothing. The displays on MCP-Pro , LGT II and the GF-166's should come to life. Nothing seemed to help.

Went back to the Baron to do some testing.
Started the Baron then GIT and setup the Default FS for the MCP-Pro, LGT II and both GF-166. Set all devices up as ENABLED.
Shutdown GIT and X-Plane.

Start X-Plane and once sitting at a gate in 'cold & dark', start GIT.
Everything starts up successfully.

Changed each device to AV_Enabled. Shutdown GIT and X_Plane. Added Aircraft Power (FS Default). (I've attached a zip file with the Baron profiles and the log).

Start X-Plane and once sitting at a gate in 'cold & dark', start GIT.
As usual the MCP-Pro displays flash and then go dark.
Started battery and nothing.

Hope my explanations help.

Thanks.
David

admin_pps

I presume AV_ENABLED was working OK for you in the prior release?

DavidWilliams5620

Hi Steve,
Yes it was working a treat.

David

admin_pps

Ok, I suspect the new blanking code must have messed it up. Leave it with me.

Best wishes
Steve

admin_pps

Hi David,

I can't recreate this issue. Can you tell me what you have put in the power options for the 738.

Thx
Steve

DavidWilliams5620

Hi Steve,
I use the FS Default for both the Baron and the B738.

<?xml version="1.0"?>

-







Thanks.

DavidWilliams5620

Steve,
That was dumb, copying and pasting XML.

I use the FS Default Datarefs (sim/cockpit2/electrical/bus_volts[0] and sim/cockpit2/switches/avionics_power_on)

Thanks.
David

admin_pps

OK, tried that and sim/cockpit2/electrical/bus_volts[0] is always zero, so it will never turn on. Trying /laminar/B738/electrical/power_on_buses also failed, but it was showing a value of 1. This uncovered a bug when the aircraft data is loaded - no custom datarefs could be used as they were not being monitored.

So, the fix will be a new version early this week, but using the laminar dataref above.

Not sure how or why it worked before because sim/cockpit2/electrical/bus_volts[0] is always zero.

Best wishes
Steve

DavidWilliams5620

Steve,
Thanks for the investigation. When I first started to look at AV_Enabled I turned DatarefEditor on to have a look at the values and I thought that when I turned the power on for the aircraft the value of sim/cockpit2/electrical/bus_volts[0] changed from 0.

I did a bit more playing, and as you suggested, have used the /laminar/b738/electrical/power_on_buses dataref. What was interesting was that after GIT has loaded (and didn't seem to work), if I went into the Power Aircraft window and reset the power config (and even selecting the same dataref), it would start working.

This may trigger GIT to start monitoring correctly.

Will wait for the update.

Thanks again.
David

admin_pps

Yes that's right, when configured it is set correctly, when loaded it is not set for monitoring - that's what needs fixing.

Best wishes
Steve

admin_pps

New version is up David.

Best wishes
Steve

DavidWilliams5620

Thanks Steve. I'll try it tonight and provide feedback.

David

DavidWilliams5620

Hi Steve,
Brilliant. IAS/Mach and V/S blanking correctly and AV_Enabled functioning correctly.

Thanks so much.

David