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.

Import failure

I am having problems importing Rob Ainscough into GIT 2.1.19.5.
The Carenado S550_Citation II.xml imports but throws a lot of errors as it loads each bespoke event for example:

"The Event "BE_LIGHTS_INT_DOME_ON has errored:System.ArgumentOutOfRangeException:Specified argument
was out of range of valid values.
at A.XK.I(String , Boolean)
at A.XK.I (String , String , Boolean , Boolean ), Task will not be loaded , Please check the event in Detective.

Eventually I end up with most of the bespokes available in Detective.
On trying to load Carenado S550_Citation II_GFMCPPRO.xml into the MCP PRO tab I get the following error:

"Failed to load Configuration Data for Device GFDEVHWTYPE_GFMCPRO"

All other configs downloaded such as the J41 etc load into GIT just fine, where am I going wrong ?

regards
glyn

Comments

  • Hi Glynn,

    I suspect that the aircraft has been updated and certain lvars no longer exist. Contact Rob directly to determine what version of the aircraft he built the config for.

    Best wishes
    Steve

  • edited April 2016
    I saw this problem on Bob's system when I helped him in teamviewer with my profile. 

    For some reason the import function was failing and half the bespoke events were blank. It was repeatable, I tried deleting all bespokes and reimporting them and half of them would be empty of code. 

    It had something to do with the goflight driver as he was using version 2.05, once I upgraded him to 2.2.6 the problem went away. I'm not sure how of why but it was very repeatable. The second we put this driver in place it worked flawlessly on the import.
    Steve McNitt
Sign In or Register to comment.