Richard McDonald Woods Posted July 2, 2016 Share Posted July 2, 2016 Many thanks for the upgrade. Its installation went without a hitch! Should I re-run the Vector Airport Elevation Corrections program after the update? Link to comment Share on other sites More sharing options...
FlavioSSA Posted July 2, 2016 Share Posted July 2, 2016 Good question. May i add another? Why there is a specific option to disable FTX AU? What happened? Link to comment Share on other sites More sharing options...
molleh Posted July 2, 2016 Share Posted July 2, 2016 9 minutes ago, FlavioSSA said: Good question. May i add another? Why there is a specific option to disable FTX AU? What happened? Because Vector conflicts with FTX AU causing various visual anomalies. Thus if you have AU installed, you can check that box and Vector is disabled for that area so that FTX AU works as it should. Link to comment Share on other sites More sharing options...
FlavioSSA Posted July 2, 2016 Share Posted July 2, 2016 Ah, thanks for the answer! Link to comment Share on other sites More sharing options...
Richard McDonald Woods Posted July 2, 2016 Author Share Posted July 2, 2016 So if, after disabling, TFX AU then works as it should, why would anyone wish to have the option of Vector causing 'various anomalies' Link to comment Share on other sites More sharing options...
FlavioSSA Posted July 2, 2016 Share Posted July 2, 2016 Beyond that, why vector is "causing anomalies" with FTX AU in the first place? (Now and not when it was launched) Link to comment Share on other sites More sharing options...
molleh Posted July 2, 2016 Share Posted July 2, 2016 What? Vector was causing issues with FTX AU when it was launched. They just now added the option to fix it. To mcdonar, you have the option because not everyone owns FTX AU... simple. Link to comment Share on other sites More sharing options...
Richard McDonald Woods Posted July 2, 2016 Author Share Posted July 2, 2016 ...and Vector cannot determine whether FTX AU is installed? Enough! Link to comment Share on other sites More sharing options...
molleh Posted July 2, 2016 Share Posted July 2, 2016 It's a checkbox... Is it really that difficult? Link to comment Share on other sites More sharing options...
John Venema Posted July 2, 2016 Share Posted July 2, 2016 FTX Australia is using much older technology and hand-crafted coastlines and rivers, which makes it contrast too much with the newer data used in Vector. This means until we re-visit Australia and make an SP5 using similar data there is going to be a slight mis-match between these products. This is purely a legacy from development which was begun in 2007 versus Vector which was delivered in 2013. Link to comment Share on other sites More sharing options...
FlavioSSA Posted July 2, 2016 Share Posted July 2, 2016 Thanks JV, pretty clear now! Link to comment Share on other sites More sharing options...
teecee Posted July 2, 2016 Share Posted July 2, 2016 I just ran vector 1.4. I am running prepar3d v2.5 and did not see any option to disable Au.. I just did a flight from Wollongong to Port Macquarrie and did not see any anomalies.. Is it possible that I missed something in the install? when would the Au option have appeared during the installation? Teecee. Link to comment Share on other sites More sharing options...
Nick Cooper Posted July 2, 2016 Share Posted July 2, 2016 Hello Teecee, It's an additional option in the Vector Control panel Link to comment Share on other sites More sharing options...
teecee Posted July 2, 2016 Share Posted July 2, 2016 Thanks Nick..Teecee. Link to comment Share on other sites More sharing options...
Ejdv Posted July 2, 2016 Share Posted July 2, 2016 Hello! Thanks all !!! Link to comment Share on other sites More sharing options...
Filippo Nesi Posted July 2, 2016 Share Posted July 2, 2016 For the first time after years and more than 30 Orbx products installed flawless, I am getting this problem while installing the FTX Vector v1.40 patch: Exception not handled in the application. The error message seems to point to an already existing key: Spoiler Le informazioni su come richiamare il debug JIT (Just-In-Time) anziché questa finestra sono riportate in fondo al messaggio. ************** Testo dell'eccezione ************** System.ArgumentException: È già stato aggiunto un elemento con la stessa chiave. in System.ThrowHelper.ThrowArgumentException(ExceptionResource resource) in System.Collections.Generic.Dictionary`2.Insert(TKey key, TValue value, Boolean add) in System.Collections.Generic.Dictionary`2.Add(TKey key, TValue value) in FtxVector.Configurator.Ui.Forms.MainForm.GetAirportFilesToRename() in FtxVector.Configurator.Ui.Forms.MainForm.ApplyBtn_Click(Object sender, EventArgs e) in FtxVector.Configurator.Ui.Forms.MainForm.MainForm_Load(Object sender, EventArgs e) in System.EventHandler.Invoke(Object sender, EventArgs e) in System.Windows.Forms.Form.OnLoad(EventArgs e) in System.Windows.Forms.Form.OnCreateControl() in System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible) in System.Windows.Forms.Control.CreateControl() in System.Windows.Forms.Control.WmShowWindow(Message& m) in System.Windows.Forms.Control.WndProc(Message& m) in System.Windows.Forms.ScrollableControl.WndProc(Message& m) in System.Windows.Forms.ContainerControl.WndProc(Message& m) in System.Windows.Forms.Form.WmShowWindow(Message& m) in System.Windows.Forms.Form.WndProc(Message& m) in System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) in System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) in System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) ************** Assembly caricati ************** mscorlib Versione assembly: 2.0.0.0 Versione Win32: 2.0.50727.5485 (Win7SP1GDR.050727-5400) Base di codice: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll ----------------------------------------FtxVector.Configurator Versione assembly: 1.35.0.0 Versione Win32: 1.35.0.0 Base di codice: file:///C:/Program%20Files%20(x86)/Steam/steamapps/common/FSX/ORBX/FTX_VECTOR/FTX%20GLOBAL%20VECTOR%20Configuration%20Tool.exe ---------------------------------------- Microsoft.VisualBasic Versione assembly: 8.0.0.0 Versione Win32: 8.0.50727.5483 (Win7SP1GDR.050727-5400) Base di codice: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll ---------------------------------------- System Versione assembly: 2.0.0.0 Versione Win32: 2.0.50727.8686 (QFE.050727-8600) Base di codice: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll ---------------------------------------- System.Windows.Forms Versione assembly: 2.0.0.0 Versione Win32: 2.0.50727.5491 (Win7SP1GDR.050727-5400) Base di codice: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll ---------------------------------------- System.Drawing Versione assembly: 2.0.0.0 Versione Win32: 2.0.50727.5495 (Win7SP1GDR.050727-5400) Base di codice: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll ---------------------------------------- System.Runtime.Remoting Versione assembly: 2.0.0.0 Versione Win32: 2.0.50727.5488 (Win7SP1GDR.050727-5400) Base di codice: file:///C:/Windows/assembly/GAC_MSIL/System.Runtime.Remoting/2.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll ---------------------------------------- mscorlib.resources Versione assembly: 2.0.0.0 Versione Win32: 2.0.50727.5485 (Win7SP1GDR.050727-5400) Base di codice: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll ---------------------------------------- System.Xml Versione assembly: 2.0.0.0 Versione Win32: 2.0.50727.5494 (Win7SP1GDR.050727-5400) Base di codice: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll ---------------------------------------- System.Windows.Forms.resources Versione assembly: 2.0.0.0 Versione Win32: 2.0.50727.5420 (Win7SP1.050727-5400) Base di codice: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms.resources/2.0.0.0_it_b77a5c561934e089/System.Windows.Forms.resources.dll ---------------------------------------- ************** Debug JIT ************** Per attivare il debug JIT, è necessario impostare il valore jitDebugging nella sezione system.windows.forms del file di configurazione dell'applicazione o del computer (machine.config). L'applicazione inoltre deve essere compilata con il debug attivato. Ad esempio: <configuration> <system.windows.forms jitDebugging="true" /> </configuration> Quando il debug JIT è attivato, tutte le eccezioni non gestite vengono inviate al debugger JIT registrato nel computer, anziché essere gestite da questa finestra di dialogo. 1. I ran the installer as Administrator, as usual. 2. I have 1.35 installed and properly working. 3. I have Microsoft NET Framework 4.6 installed. 4. Windows 7 64 bit, FSX Steam Link to comment Share on other sites More sharing options...
Doc44kin Posted July 3, 2016 Share Posted July 3, 2016 Crikey this is interesting,it may be the cause of some of my problems!!,must try it....Doc Link to comment Share on other sites More sharing options...
FalconAF Posted July 3, 2016 Share Posted July 3, 2016 Egads! OK, maybe it's clear to everybody else, but from other threads I had read I thought that the AU option in Vector 1.40 was going to be, "If I'm going to fly in AU, I turn Vector off ALTOGETHER. Then when I quit flying in AU and go somewhere else, I turn Vector back on." Is everybody saying it is a one-time thing to do? If you have AU and other ORBX regions, you just check the AU box in Vector and never have to switch back and forth between anything in Vector again? That would be great! Thanks for clarification. Link to comment Share on other sites More sharing options...
Ed Correia Posted July 3, 2016 Share Posted July 3, 2016 1 hour ago, FalconAF said: Is everybody saying it is a one-time thing to do? If you have AU and other ORBX regions, you just check the AU box in Vector and never have to switch back and forth between anything in Vector again? That would be great! Thanks for clarification. You are correct in that assumption. Link to comment Share on other sites More sharing options...
ActiveSky Posted July 3, 2016 Share Posted July 3, 2016 Thanks for the upgradeI find good if there are always new updates for FTX Global Vector.Thank you Link to comment Share on other sites More sharing options...
Filippo Nesi Posted July 3, 2016 Share Posted July 3, 2016 Replying to myself (post #16). I solved by: 1. uninstalling Vector with the procedure described here by John Venema; 2. redownloading all Vector installers from 1.30 to 1.40 3. reinstalling 1.30, 1.35 and 1.40 in sequence having care to run the last library after each installation. Just in case someone else should have the same problem. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.