Split View only showing some Events and no Lvars.

robains

Hi Steve,

Couple of issues with 3.5.0 64bit for P3D V4.x:

1. In Detective the Split View only shows a few Events and will NOT show any LVars.
2. Same flashing cmd window appearing as I had with v3.4.10 (per reported in another thread, see video)

I was able to work around #2 by force shutdown of GIT and then make sure I launch GIT AFTER P3D V4 is loaded and in VC.

Cheers, Rob.

admin_pps

The cmd window is for Lua, but it should disappear. I will see if I can re-create the issue.

It sounds like split view is working correctly. Events show in the bottom and Lvars go to the fixed view at the top. You need to sort the fixed view by time to show the Lvars as the view doesn't auto sort.

Best wishes
Steve

robains

Hi Steve,

In my case, if I start GIT x64 before I start P3D V4.1, I'll get the rapidly flashing cmd window that continues popping up as if it's stuck in a loop and there is no timeout specified. If I start GIT x64 after P3D V4.1 is running (in VC, then I only see the cmd window popup once).

On a side note, you might be able to hide the command window using WScript.shell (should be available on all OS versions by default) with filename for execution target and then comma 0 parameter that will set WindowStyle to 0 (hidden).

Thanks for clarification on Split view, sounds like Operator Error (aka Me)

Another note, I can't get GIT x64 to exit/shutdown after I exit P3D V4.1 ... it seems to be holding onto some resource long after P3D has shutdown ... only way to terminate GIT x64 is by force (taskmgr - end task).

FYI, I've got the video recordings done for GIT Part 2 Tutorial ... I had some technical issues with the recordings via my Magewell capture card (audio timestamp data was intermittent which caused Adobe PP to not be able to import the video files but oddly Windows Media player had no problems playing the videos correctly) ... long story short, updated Magewell drivers and "re-captured" my original footage by playing the files back on one PC via Windows Media Player and then capturing the footage again via other PC (Magewell) ... this saved me a ton of time having to redo a lot of work. So now I just have to edit the footage and make it coherent. I'll get to work on Part 3 later in the week or weekend.

Cheers, Rob.

admin_pps

Thanks Rob, I'll look into those issues.

robains

UPDATE on issues:
1. GIT 3.5 will require force shutdown in all cases
2. The GIT "restart" button will consistently trigger the flashing cmd window and then become unresponsive
3. Starting GIT after AS CRJ700 is loaded and in "Ready to Taxi" state, turns off the FO/CO MFDs

Part 2 of tutorial is posted ... working on START ... functionality for WP-6 but having a difficult time due to issue #2 above as use of START requires a "restart" or shutdown. Both not working.

Cheers, Rob.

robains

Another UPDATE:
I can't seem to get the START bespoke to work. I ran a very basic test here:

https://drive.google.com/open?id=13vZXlvsvqXR9nJ3Wlvg6scGzYC2H_pC9

and

https://drive.google.com/open?id=1Ep3lC46fkRX6si3fms4yg65V8RVYua9U

This should have flashed WP-6 button but nothing happened. I went thru all my notes and everything seems to be setup correctly (since restart isn't working I did a forced exit and then fired up GIT again, am I missing something or is this a possible bug?

Cheers, Rob.

admin_pps

These may be issues with the 64Bit version. I'll take a look and come back to you.

admin_pps

"In my case, if I start GIT x64 before I start P3D V4.1, I'll get the rapidly flashing cmd window that continues popping up as if it's stuck" - Can you copy and paste the GIT log when this is happening as I cannot re-create the issue. Do you have another add-on which may initiate a console window from P3D?

"GIT 3.5 will require force shutdown in all cases" - Can you try a clean GIT config by renaming My Documents\GoFlight Interface Tool and see if it still occurs. If not, restore your settings and try a few aircraft to see if its aircraft/config specific.

"The GIT "restart" button will consistently trigger the flashing cmd window and then become unresponsive" - Again try with a clean GIT config as I cannot re-create.

"Starting GIT after AS CRJ700 is loaded and in "Ready to Taxi" state, turns off the FO/CO MFDs" - This could be the syncing switches and selectors stage in GIT. Do you have something assigned in GIT to activate the MFD's. If so is there a light action associated with it so it syncs correctly?

I'll look at Start later on today.

Best wishes
Steve

robains

Thanks Steve,

Back in the office ... I'll try some more diagnostics tonight and report back.

Cheers, Rob.