RESOLVED FTX Central on 64 Bit Windows 7 Exception Error FSX

[mitchellsland]

I am having an issue getting FTX Central installed on my Windows 7 64 Bit Machine.

My installation of FSX does not create the registry keys in HKLM\SOFTWARE\Microsoft\microsoft games\flight simulator\10.0

Windows 7 64 Bit creates the registry keys in: HKLM\SOFTWARE\Wow6432Node/Microsoft\microsoft games\flight simulator\10.0

 

I have created the SetupPath registry value in: HKLM\SOFTWARE\Microsoft\microsoft games\flight simulator\10.0 but I still get the exception error.

 

I have also tried the following:

 

uninstall/reinstall FSX

uninstall/reinstall Orbx base

installed OrbxFTXGlobal120

installed FTXORBXLIBS

ran fsx_registry_fix

unchecked read-only checkbox in FSX directory

Edited F:\FSX\ORBX\Scripts\FTXCentral\FTXSettings.xml to point at:HKLM\SOFTWARE\Wow6432Node/Microsoft\microsoft games\flight simulator\10.0

(This stopped the exception but gave an error message that the FSX installation could not be found)

 

Below is the Exception Log, any help would be greatly appreciated!

 

************** Exception Text **************
System.IO.FileNotFoundException: Could not load file or assembly 'System.Core, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' or one of its dependencies. The system cannot find the file specified.
File name: 'System.Core, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'
   at FTXCentral.PublicDefs.TestFTXConfiguratorCFG()
   at FTXCentral.PublicDefs.InitFTXEnv()
   at FTXCentral.FTXC.InitSystem()
   at FTXCentral.FTXC.InitAll()
   at FTXCentral.FTXC.Timer1_Tick(Object sender, EventArgs e)
   at System.Windows.Forms.Timer.OnTick(EventArgs e)
   at System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].



************** Loaded Assemblies **************
mscorlib
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5472 (Win7SP1GDR.050727-5400)

----------------------------------------
FTXCentral
    Assembly Version: 1.0.4.0
    Win32 Version: 1.0.4.0

----------------------------------------
Microsoft.VisualBasic
    Assembly Version: 8.0.0.0
    Win32 Version: 8.0.50727.5420 (Win7SP1.050727-5400)

----------------------------------------
System
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5467 (Win7SP1GDR.050727-5400)

----------------------------------------
System.Windows.Forms
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5468 (Win7SP1GDR.050727-5400)

----------------------------------------
System.Drawing
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5467 (Win7SP1GDR.050727-5400)

----------------------------------------
System.Runtime.Remoting
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)

----------------------------------------
System.Configuration
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5476 (Win7SP1GDR.050727-5400)

----------------------------------------
System.Xml
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5476 (Win7SP1GDR.050727-5400)

----------------------------------------
ge4vbklt
    Assembly Version: 1.0.4.0
    Win32 Version: 2.0.50727.5467 (Win7SP1GDR.050727-5400)

----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

 

[mitchellsland]

I am away on a trip right now and have been reading the forums. It appears that I do not have .net 3.5 installed or enabled. I will try that andnlet you know if this fixes the issue. I do have .net 4.0 installed but I do I think I need 3.5

[Tim Harris]

Hi Mitchell

 

Try the link at the very bottom of our support page for the .NET 4.0 package http://www.fullterrain.com/support.html

 

And to (re)set the FSX registry entry correctly this tool always works perfectly: http://tweakfs.com/download/fsx_reg_utility.zip

[mitchellsland]

Hi Tim -

 

Thanks for taking the time to help me on this.

 

I was able to fix the issue. I downloaded the registry fix and the .NET 4.0. After installing it was still getting the error message above.

 

I was one step away from doing a complete re-install of the OS but I thought I would try to install .NET 3.5.

 

When I tried to reinstall I got an error message from Windows 7 stating:

You must use "Turn Windows features on or off" in the Control Panel to install or configure Microsoft .NET Framework 3.5 SP1

So I went to Control Panel->Turn Windows Features on or off,  and checked Microsoft .NET Framework 3.5.1 and all subsequent checkboxes in that category.

 

I then installed .NET 4.0, the link you sent,  and FTX Central Opened and worked.

 

Not sure how that was unchecked as my windows 7 system is pretty clean, the only thing I use it for is Games, possibly when I updated to .NET 4.5 it unchecked it, who knows.

[Ian Routley]

Good to know.  Thanks for the update.