Most of the commonly reported issues and questions are answered in the Frequently Asked Questions (FAQ) option under the Support menu of this website.
*** PLEASE NOTE ***
Your forum account is not the same as the account used in the shop. They are completely separate accounts.
1st December: A new version of the GoFlight Interface Tool for MSFS is now available.
12th November: A new version of the GoFlight Interface Tool for X-Plane is now available.
6th June: A new version of Virtual Flight Sim Hardware is now available (huge update)
21st November: A new version of the GoFlight Interface Tool for FSX/FSXSE/P3D is now available.

GIT X-Plane not finding/parsing all datarefs

SlayerSlayer
in GoFlight Interface Tool - Technical Support
Hey Steve, 

I've been trying to create a profile for the Flight Factor 757 off and on since the X-plane version of GIT came out and have given up a few times. The issue I'm running into is the dev never bothered to include a list of datarefs. The problem is detective can't see most of the private datarefs even with the "Monitor DRE Private datarefs" box checked 

If I use DatarefTool I can see these datarefs and manipulate their values and it works. GIT should be able to sniff these out too but it can't. I suspect there is something getting missed where GIT is searching for the datarefs or isn't parsing them all. The ones that are giving me fits in detective start with a "1-sim/AP/" etc

I also tried manually putting a few datarefs into the datarefs.txt file, then they show in detective but if I try to use the dataref nothing happens .

Steve McNitt

Comments

  • admin_ppsadmin_pps

    Hi Steve,

    I know for certain that the program checks for a number at the beginning of the extracted Data Ref and removes it because some aircraft do not have a space or tab etc in between a value and a dataref.

    If all the datarefs with a number have a hyphen after the number, I can build in an exception to the rule and allow them through?

    Best wishes

    Steve

  • SlayerSlayer
    edited September 2016
    That would be great, here is an exact copy of a few that don't show to help build the exception:

    1-sim/AP/fd2Switcher
    1-sim/AP/fd1Switcher
    1-sim/ndpanel/1/adiBRTrotary
    757Avionics/CDU2/rte


    The strange thing though is that a few of the 1-sim and 757Avionics datarefs do show through, example:

    1-sim/ap/at/at_target_epr 
    757Avionics/autoland/op

    Thats why I'm not sure if it's a parsing problem or if it isn't finding all the datarefs in the aircraft files

    The author of DRT has a rather long thread about a similar issue on the .org and they were having parsing issues due to the naming conventions used in the files.


    Also interestingly it affected the JAR A330 as well, I remember a post on here by another user that none of the datarefs shows up for that either and it uses these wacky naming conventions like the 757, so this may help you fix that problem too,

    in case of the A330 some of the datarefs start with a number and some of the .obj files used caps in the extension of the filename (.OBJ) so their parser couldn't find the datarefs.


    Steve McNitt
  • admin_ppsadmin_pps

    This issue should now be resolved in 1.7.0.0

    Best wishes

    Steve

  • SlayerSlayer
    Working great I can see many more datarefs and now the commands for the FF 757 :) I will have an EFIS and MCP profile out soon
    Steve McNitt
  • trevgtrevg
    I will have an EFIS and MCP profile out soon

    Hi Steve have you managed to get time for the profile yet ??
    If you have I wouldn't mind a copy, fed up trying this afternoon.

  • SlayerSlayer
    Got a few more mcp lights to figure out and i should have it done
    Steve McNitt
Sign In or Register to comment.

© Vanilla Keystone Theme 2025