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.

Errors with DHC6 file

I've installed the interface version 2.0.538.0 and tried to use it for the first time with the DHC6 file.

When trying to rename the aircraft to Aerosoft_DHC6 I get the following error

"Unable to save settings. Index was outside the bounds of the array"

I then tried to import the Aerosoft_DHC6.xml file via detective and I get the following error

"import has failed Value cannot be null. Parameter name:s

Any suggestions please

Paul Gardner
«1

Answers

  • edited November -1

    Hi Paul,

    You'll need the latest version 2.0.665. The errors will be because its expecting keyboard support which only became available in the latest versions.

     

    Best wishes

    Steve

  • edited November -1
    Installed 2.0.655 and get the same errors

    GF 2.23. Win 7 64 bit FSX SP2+ acceleration
  • edited November -1
    nstalled 2.0.655 and get the same errors

    GF 2.23. Win 7 64 bit FSX SP2+ acceleration
  • edited November -1

    Hi Paul,

    Can you attach all your config files to another reply please so I can test things out at my end (BespokeEvents.XML, Settings.XML and user.config).

    Thx

    Steve

  • edited November -1

    Hi Steve

    I only have user.cfg file no bespokeevents.xml or settings.xml


     


        
            
                
               
                
            
       

  • edited November -1

    Hi Paul,

     

    The missing files should be in My Documents\GoFlight Interface Tool

    Thx

    Steve

  • edited November -1
    Steve

    I don't have a folder called GoFlight Interface tool in my documents on my system, nor anywhere else as far as I can see.

    Paul
  • edited November -1

    Hi Paul,

    It looks like GIT has not been completely run as the user.config is at a very basic state and no other files are present.

    Just as a test, get to the virtual cockpit of any aircraft in fsx. Load up GIT, wait for 3 green lights on the status page and then shut GIT down. That should create all the basic files and settings and then try the import again, remembering to follow the instructions whilst in the virtual cockpit of the DHC6 (i.e. the aircraft renaming, loading bespoke events etc.)

    Best wishes

    Steve

  • edited November -1
    Hi Steve

    Thanks for staying with me on this one.

    Loaded up default Baron. Started the interface, 3 green lights and recognised the Baron. Closed and got the message:  "Unable to save settings. Index was outside the of the array". Restarted interface, tried again but got the same message?

    Paul


  • edited November -1

    Hi Paul,

    Are you running with admin rights and UAC turned off?

    Can you provide me with a list of all the Goflight gear your have including quantities of each device so I can replicate your setup.

    Thx

    Steve

  • edited November -1
    Yes admin rights and UAC off

    MCPPRO
    EFIS x2
    LGT
    TQ6 ADV
    T8 x1
    P8 x 3
    GF166 x 5
    MESM
    GF45 x 3

    Paul
  • edited November -1

    Hi Paul,

     

    Still can't replicate your problem. Which goflight drivers are you using and is Windows Update up to date?

    Thx

    Steve

  • edited November -1
    Windows is up to date. I've uninstalled via cp and re-installed new version and checked to run as administrator. UAC is off.

    Same error: "Unable to save setting. Index was outside of the array". I can't seem to get past the settings.


  • edited July 2013

    Hi Paul,

    Do you mean you have tried it with GoFlight Drivers 2.22?

     

    Is the error message a pop-up? If so can you copy and paste the whole error message.

    Thx

    Steve

  • edited November -1
    Hi Steve

    I'm now on 2.22, I removed 2.3via CP reinstalled 2.22 and rebooted. Please see screen shot attached. Yes it is a pop up
  • edited July 2013

    Hi Paul,

    Can you copy and paste the log file once its started up. Also try just quitting instead of clicking Save Settings as it will save automatically.

    Thx
    Steve

     

    PS: Can you try running it with all your joysticks removed (any directx type controller). I'm wondering if the problem lies in this area.

    If still no joy I'll develop a custom version for you that will help us track down where and why its failing on your PC.

  • edited November -1
    Hi Steve

    Solved  it. It was a joystick!!

    I have 3 Joysticks.

    1 x Saitek Pro Flight Yoke direct to PC
    1 x Saitek Rudder Pedals plugged into Monitor USB
    1 x Saitek Cyborg evo, which I use as a steering tiller for jets, direct to PC. This was the culprit. It doesn't like this joystick at all.  Is it possible to come up with a solution so that I can use this joystick?

    Paul
  • edited November -1

    Hi Paul,

    That's great news. Can you provide me the names of all its axes e.g. X, Y slider, dial etc by bringing up the calibration screen and also the actual name of the device as seen in Devices & Printers.

    Thx

    Steve

  • edited November -1
    Hi Steve

    It's called "Saitek Cyborg USB Stick"

    axes I've attached a photo of the calibration screen

    Paul
  • edited November -1

    Hi Paul,

    Having investigated the code with your joystick details I cannot see why it would cause a problem. I think I'll write some debug code and get you to try it so I can get to the bottom of this.

    I'll come back with something shortly.

    Best wishes

    Steve

  • edited November -1

    Hi Paul,

    A debug version is available here: https://www.dropbox.com/s/l1ovy7qa84qvrq9/GIT%20Debug.zip

    It will provide some basic debug information for me to narrow down where I need to focus. I'll then add more debug code to finally track down the issue. Just run the new version with all your joysticks attached and then quit. It will create a debug.txt file in the GoFlight Interface Tool directory that you can then attach in this thread.

    If you have configured anything in GIT that you wish to keep, please take a copy of the directory GoFlight Interface Tool in My Documents. If you have configured anything for the NGX, refer to the back of the GoFlight PMDG Interface manual for details on where the user.config file is and take a copy of that.

    Best wishes

    Steve

  • edited November -1

    Hi Steve file attached.

     

    BTW I have difficulty accessing your site during UK working hurs from here in Japan.

     

    Paul

  • edited November -1

    Hi Paul,

    We had several hours of down time today due to technical difficulties. I've been told everything is sorted out now.

    Best wishes

    Steve

  • edited November -1

    Hi Paul,

    I expected more debug information. Did you quit GIT before posting the debug.txt file?

    Thx

    Steve

  • edited November -1

    Hi Paul,

    Have you had a chance to try this again, making sure you quit GIT before uploading debug.txt?

    Thx

    Steve

  • edited November -1

    Hi Steve

    I've tried to send but I'm having a nightmare getting onto your site and uploading. I attach a retry. I have to start GIT, then plug in the wayward joystick, otherwise I get the "out of array message" and then I close using the x.

  • edited November -1
    sorry wrong file
  • edited November -1

    Hi Paul,

    Yeah I know about the site. The web hosting is playing up at the moment - I'm sick of chasing for a resolution!

    I need you to run it with the joystick plugged in right from the start. Plugging it in afterwards means GIT has no knowledge of it. If no debug.txt file is produced when doing this, then I'm looking in the wrong place for the error. Let me know.

    Thanks

    Steve

  • edited November -1
    Hi Steve

    Then you can use the first debug file as I did exactly as told. Plugged all joysticks in, started GIT, I get an "error out of array save settings" at that point I quit using the X top RHS without saving the settings.


  • edited July 2013

    Hi Paul,

    OK, I'll add some debug code in another area this evening.

    Thx

    Steve

    PS, I noticed that your Saitek rudder pedal axis have not been recognised. Can you provide me a list of the axis names for this device so I can add support for it. Thx

Sign In or Register to comment.