Cruachan

Does this not suggest that the common factor is more likely to be found in the GPU driver software and not the individual Application, dll, etc. Can’t help but feel that the responsibility for finding the all-encompassing solution rests with NVIDIA (does this error occur with AMD GPUs?). NVIDIA must be aware that this happening and when it is likely to happen. I am no programming expert but, by now, I would have expected their drivers to be far more tolerant of faults such as this show-stopper. Mike.

Hi Marcus, I am wondering whether we are approaching the point where we can say with some confidence that specific drivers are at the root of this problem? Following your error-free experience with 460.79 I now have them installed. So far so good but, as yet, have not had time for extended testing. It may just be that Nvidia, in common with other Developers, are still finessing the marriage of their complex GPU drivers with the nooks and crannies of the DirectX 12 coding environment. Regards, Mike

Hi @SolRayz As I said, I’ve yet to be convinced that running out of VRAM is behind this irksome error. More likely something else is responsible. The fact that some drivers seem more vulnerable than others suggests, to me at least, that their operation under DirectX 12 is the key. Someone, prove me wrong! Mike

Hi Marcus, Not quite at that point yet...lol! Thanks for your very helpful response! I’m aware of most, if not all, of your listed suggestions as I’ve read your posts on this topic elsewhere on this forum. 1/2. I do see negative VRAM spikes from time to time and this usually signals a brief coarse stuttering event. LP0 usually runs flat out so wondering whether these negative spikes are the result of brief oversaturation of scenery data being delivered from the other LPs which has to be queued before it can be handled by LP0 and then transferred on to the GPU for rendering - assuming, that is, I’m understanding what’s going on correctly. I lock at 120fps and peg my frame rate at 31 via NCP. No VSync or TB. I run GSync + VRR checked in sim. Most of the time performance is very smooth (with or without EA) and with very little in the way of micro-stuttering. I always fly with ORBX Global, etc. and, yes, as @Nuno Pinto has stated, the visuals are indeed stunning! 3/4. Trueglass.dll is disabled. Not sure whether I have the reallight.dll file - I will check. 5. Bathymetry is OFF 6. Vegetation shadows are OFF as adversely affects performance. So, that leaves the graphics Driver. I’ll test with 460.79. Fingers crossed! Regards, Mike

Hi, Impressive and interesting as all this may be, It fails to explain why during testing @OzWhitey did not encounter the DXGI ERROR DEVICE HUNG fatal error. Or, is this annoying issue now specific to the more recent V5.1 (HF1)? I have an 11GB card and can encounter this somewhat random and unpredictable error with less than half VRAM usage (as shown in P3D). Perhaps these experiences are suggesting that something else is responsible - Driver, DX12 optimisations? VRAM saturation may not be the prime cause, if it ever was, and it seems likely that LM/Nvidia should be looking elsewhere. Until this is sorted out, IMHO, while performance is good, it cannot be said that P3D V5.1 (HF1) is currently 100% stable. Mike

Hi Simbol, To clarify, and in case there was any confusion, this was after the removal of those Prepar3D v4 registry hacks followed by running the original AILRPro installation. In fact, the removal of those hacks allowed the running AILPro to progress further during the initial loading of P3Dv5.1 (HF1): This AILPro splash window disappeared after a few seconds and, without any interventions on my part, loading continued until that 2nd error, as detailed in my previous post, appeared. So, in conclusion, while it seems very likely that the removal of those hacks had some effect, I cannot state definitively that their removal was solely responsible for the eventual successful outcome as a fresh install of AILPro followed by a system reboot appears to have been necessary to remedy matters. Or, perhaps I am overthinking this..lol! I suppose I could reinstate those hacks to test but, at this point, my feeling is to avoid rocking the boat! Best regards, Mike

Hi Simbol, Up and running! However, I had to perform a fresh reinstall followed by a warm reboot before the following error cleared: ************** Exception Text ************** System.NullReferenceException: Object reference not set to an instance of an object. at FSRebornAILightsConfig.AIModelsLightsConfig.Load(Boolean LoadStats) at FSRebornAILightsConfig.Configuration.gEXdOBEGtZ(Object , EventArgs ) at System.EventHandler.Invoke(Object sender, EventArgs e) at System.Windows.Forms.Form.OnLoad(EventArgs e) at System.Windows.Forms.Form.OnCreateControl() at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible) at System.Windows.Forms.Control.CreateControl() at System.Windows.Forms.Control.WmShowWindow(Message& m) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.Form.WmShowWindow(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) ************** Loaded Assemblies ************** mscorlib Assembly Version: 4.0.0.0 Win32 Version: 4.8.4250.0 built by: NET48REL1LAST_C CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll ---------------------------------------- AI Lights Reborn Professional Assembly Version: 1.25.0.0 Win32 Version: 1.25.0.0 CodeBase: file:///C:/Program%20Files/AI%20Lights%20Reborn%20Professional%20Edition/AI%20Lights%20Reborn%20Professional.exe ---------------------------------------- Microsoft.VisualBasic Assembly Version: 10.0.0.0 Win32 Version: 14.8.4084.0 built by: NET48REL1 CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualBasic/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll ---------------------------------------- System Assembly Version: 4.0.0.0 Win32 Version: 4.8.4200.0 built by: NET48REL1LAST_C CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll ---------------------------------------- System.Core Assembly Version: 4.0.0.0 Win32 Version: 4.8.4220.0 built by: NET48REL1LAST_C CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll ---------------------------------------- System.Windows.Forms Assembly Version: 4.0.0.0 Win32 Version: 4.8.4250.0 built by: NET48REL1LAST_C CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll ---------------------------------------- System.Drawing Assembly Version: 4.0.0.0 Win32 Version: 4.8.4084.0 built by: NET48REL1 CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll ---------------------------------------- System.Configuration Assembly Version: 4.0.0.0 Win32 Version: 4.8.4190.0 built by: NET48REL1LAST_B CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll ---------------------------------------- System.Xml Assembly Version: 4.0.0.0 Win32 Version: 4.8.4084.0 built by: NET48REL1 CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll ---------------------------------------- System.Runtime.Remoting Assembly Version: 4.0.0.0 Win32 Version: 4.8.4084.0 built by: NET48REL1 CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Remoting/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll ---------------------------------------- FSRebornUIControls Assembly Version: 1.25.0.0 Win32 Version: 1.25.0.0 CodeBase: file:///C:/Program%20Files/AI%20Lights%20Reborn%20Professional%20Edition/FSRebornUIControls.DLL ---------------------------------------- Syncfusion.SfDataGrid.WinForms Assembly Version: 18.1460.0.52 Win32 Version: 18.1460.0.52 CodeBase: file:///C:/Program%20Files/AI%20Lights%20Reborn%20Professional%20Edition/Syncfusion.SfDataGrid.WinForms.DLL ---------------------------------------- Syncfusion.Shared.Base Assembly Version: 18.1460.0.52 Win32 Version: 18.1460.0.52 CodeBase: file:///C:/Program%20Files/AI%20Lights%20Reborn%20Professional%20Edition/Syncfusion.Shared.Base.DLL ---------------------------------------- Syncfusion.Data.WinForms Assembly Version: 18.1460.0.52 Win32 Version: 18.1460.0.52 CodeBase: file:///C:/Program%20Files/AI%20Lights%20Reborn%20Professional%20Edition/Syncfusion.Data.WinForms.DLL ---------------------------------------- Syncfusion.Core.WinForms Assembly Version: 18.1460.0.52 Win32 Version: 18.1460.0.52 CodeBase: file:///C:/Program%20Files/AI%20Lights%20Reborn%20Professional%20Edition/Syncfusion.Core.WinForms.DLL ---------------------------------------- Syncfusion.GridCommon.WinForms Assembly Version: 18.1460.0.52 Win32 Version: 18.1460.0.52 CodeBase: file:///C:/Program%20Files/AI%20Lights%20Reborn%20Professional%20Edition/Syncfusion.GridCommon.WinForms.DLL ---------------------------------------- Syncfusion.SfInput.WinForms Assembly Version: 18.1460.0.52 Win32 Version: 18.1460.0.52 CodeBase: file:///C:/Program%20Files/AI%20Lights%20Reborn%20Professional%20Edition/Syncfusion.SfInput.WinForms.DLL ---------------------------------------- Syncfusion.SfListView.WinForms Assembly Version: 18.1460.0.52 Win32 Version: 18.1460.0.52 CodeBase: file:///C:/Program%20Files/AI%20Lights%20Reborn%20Professional%20Edition/Syncfusion.SfListView.WinForms.DLL ---------------------------------------- Syncfusion.DataSource.WinForms Assembly Version: 18.1460.0.52 Win32 Version: 18.1460.0.52 CodeBase: file:///C:/Program%20Files/AI%20Lights%20Reborn%20Professional%20Edition/Syncfusion.DataSource.WinForms.DLL ---------------------------------------- LockheedMartin.Prepar3D.SimConnect Assembly Version: 4.4.0.0 Win32 Version: CodeBase: file:///C:/Program%20Files/AI%20Lights%20Reborn%20Professional%20Edition/LockheedMartin.Prepar3D.SimConnect.DLL ---------------------------------------- System.Data.SQLite Assembly Version: 1.0.106.0 Win32 Version: 1.0.106.0 CodeBase: file:///C:/Program%20Files/AI%20Lights%20Reborn%20Professional%20Edition/System.Data.SQLite.DLL ---------------------------------------- System.Data Assembly Version: 4.0.0.0 Win32 Version: 4.8.4261.0 built by: NET48REL1LAST_B CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_64/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll ---------------------------------------- System.Transactions Assembly Version: 4.0.0.0 Win32 Version: 4.8.4084.0 built by: NET48REL1 CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_64/System.Transactions/v4.0_4.0.0.0__b77a5c561934e089/System.Transactions.dll ---------------------------------------- System.EnterpriseServices Assembly Version: 4.0.0.0 Win32 Version: 4.8.4084.0 built by: NET48REL1 CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_64/System.EnterpriseServices/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.EnterpriseServices.dll ---------------------------------------- MadMilkman.Ini Assembly Version: 1.0.6.0 Win32 Version: 1.0.6.0 CodeBase: file:///C:/Program%20Files/AI%20Lights%20Reborn%20Professional%20Edition/MadMilkman.Ini.DLL ---------------------------------------- ======================================== By the way, I noted something else after the reinstallation completed: That last line is mostly obscured. I am guessing it says "NOTE: YOU MUST RESCAN ----- AI Models to complete this update" My monitor screen resolution is 2560x1440 Otherwise all seems well. I've saved the initial configuration using default settings meantime. Thanks for your help with this, Simbol. Much appreciated! Best regards, Mike ☺️

Hi Simbol, Ah, great minds think alike! I was thinking about this while in the shower this morning - ideal place for capturing those elusive moments of revelation..lol V4.5 is installed under Windows 7 so, any V4 registry references are irrelevant under a Windows 10 boot. However.....a few weeks ago I had an issue with the absence of VC switch/flap/gear sounds affecting my RealAir Legacy and Duke installations. Believing this to be the result of bad installs under V5 my fruitless troubleshooting efforts included, yes you’ve guessed, a couple of V4 registry hacks designed to fool the installers that they were in fact installing these aircraft under V4. In the end, I was embarrassed to discover that my Oculus software was changing the sound device default configuration in Windows 10! I left those registry hacks in place in case I wanted to try installing more V4 aircraft into V5 in the future. I will try the effect of removing those V4 hacks from the Windows 10 registry and report back. Best regards, Mike

Hi Simbol, Windows 10 Pro 64bit (2004) / Prepar3D v5.1.12.26829 AI Lights Reborn Professional Edition v 1.25.0 Encountered a problem during loading of the sim following an apparent good installation of AI Lights Reborn Pro today: add-on.xml <?xml version="1.0" encoding="UTF-8"?> <SimBase.Document Type="AddOnXml" version="4,0" id="add-on"> <AddOn.Name>AI Lights Reborn Professional Edition</AddOn.Name> <AddOn.Description>FSReborn AI Traffic Lights Effects Professional edition. Installed version 1.2.0, for support please visit our website at www.FSReborn.com</AddOn.Description> <AddOn.Component> <Category>EXE</Category> <Path>C:\Program Files\AI Lights Reborn Professional Edition\FSRebornConfigChecker.exe</Path> </AddOn.Component> <AddOn.Component> <Category>Effects</Category> <Path>C:\Program Files\AI Lights Reborn Professional Edition\AI Lights Effects V5</Path> </AddOn.Component> <AddOn.Component> <Category>Texture</Category> <Path>C:\Program Files\AI Lights Reborn Professional Edition\AI Lights Effects V5\texture</Path> </AddOn.Component> <AddOn.Component> <Category>SimObjects</Category> <Path>C:\Program Files\AI Lights Reborn Professional Edition\FSRebornObjects V5</Path> </AddOn.Component> <AddOn.Component> <Category>ShadersHLSL</Category> <Path>C:\Program Files\AI Lights Reborn Professional Edition\FSRebornHLSL V5</Path> </AddOn.Component> </SimBase.Document> Exception Text See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box. ************** Exception Text ************** System.IO.DirectoryNotFoundException: Could not find a part of the path 'C:\Users\Cruachan47\AppData\Roaming\Lockheed Martin\Prepar3D v4\Cameras.cfg'. at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost) at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share) at MadMilkman.Ini.IniFile.Load(String filePath) at FSRebornAILightsConfig.AIModelsLightsConfig.InstallAILRPOverviewCamera(String FileLocation) at FSRebornAILightsConfig.Configuration.gEXdOBEGtZ(Object , EventArgs ) at System.EventHandler.Invoke(Object sender, EventArgs e) at System.Windows.Forms.Form.OnLoad(EventArgs e) at System.Windows.Forms.Form.OnCreateControl() at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible) at System.Windows.Forms.Control.CreateControl() at System.Windows.Forms.Control.WmShowWindow(Message& m) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.Form.WmShowWindow(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) ************** Loaded Assemblies ************** mscorlib Assembly Version: 4.0.0.0 Win32 Version: 4.8.4250.0 built by: NET48REL1LAST_C CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll ---------------------------------------- AI Lights Reborn Professional Assembly Version: 1.25.0.0 Win32 Version: 1.25.0.0 CodeBase: file:///C:/Program%20Files/AI%20Lights%20Reborn%20Professional%20Edition/AI%20Lights%20Reborn%20Professional.exe ---------------------------------------- Microsoft.VisualBasic Assembly Version: 10.0.0.0 Win32 Version: 14.8.4084.0 built by: NET48REL1 CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualBasic/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll ---------------------------------------- System Assembly Version: 4.0.0.0 Win32 Version: 4.8.4200.0 built by: NET48REL1LAST_C CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll ---------------------------------------- System.Core Assembly Version: 4.0.0.0 Win32 Version: 4.8.4220.0 built by: NET48REL1LAST_C CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll ---------------------------------------- System.Windows.Forms Assembly Version: 4.0.0.0 Win32 Version: 4.8.4250.0 built by: NET48REL1LAST_C CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll ---------------------------------------- System.Drawing Assembly Version: 4.0.0.0 Win32 Version: 4.8.4084.0 built by: NET48REL1 CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll ---------------------------------------- System.Configuration Assembly Version: 4.0.0.0 Win32 Version: 4.8.4190.0 built by: NET48REL1LAST_B CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll ---------------------------------------- System.Xml Assembly Version: 4.0.0.0 Win32 Version: 4.8.4084.0 built by: NET48REL1 CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll ---------------------------------------- System.Runtime.Remoting Assembly Version: 4.0.0.0 Win32 Version: 4.8.4084.0 built by: NET48REL1 CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Remoting/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll ---------------------------------------- FSRebornUIControls Assembly Version: 1.25.0.0 Win32 Version: 1.25.0.0 CodeBase: file:///C:/Program%20Files/AI%20Lights%20Reborn%20Professional%20Edition/FSRebornUIControls.DLL ---------------------------------------- Syncfusion.SfDataGrid.WinForms Assembly Version: 18.1460.0.52 Win32 Version: 18.1460.0.52 CodeBase: file:///C:/Program%20Files/AI%20Lights%20Reborn%20Professional%20Edition/Syncfusion.SfDataGrid.WinForms.DLL ---------------------------------------- Syncfusion.Shared.Base Assembly Version: 18.1460.0.52 Win32 Version: 18.1460.0.52 CodeBase: file:///C:/Program%20Files/AI%20Lights%20Reborn%20Professional%20Edition/Syncfusion.Shared.Base.DLL ---------------------------------------- Syncfusion.Data.WinForms Assembly Version: 18.1460.0.52 Win32 Version: 18.1460.0.52 CodeBase: file:///C:/Program%20Files/AI%20Lights%20Reborn%20Professional%20Edition/Syncfusion.Data.WinForms.DLL ---------------------------------------- Syncfusion.Core.WinForms Assembly Version: 18.1460.0.52 Win32 Version: 18.1460.0.52 CodeBase: file:///C:/Program%20Files/AI%20Lights%20Reborn%20Professional%20Edition/Syncfusion.Core.WinForms.DLL ---------------------------------------- Syncfusion.GridCommon.WinForms Assembly Version: 18.1460.0.52 Win32 Version: 18.1460.0.52 CodeBase: file:///C:/Program%20Files/AI%20Lights%20Reborn%20Professional%20Edition/Syncfusion.GridCommon.WinForms.DLL ---------------------------------------- Syncfusion.SfInput.WinForms Assembly Version: 18.1460.0.52 Win32 Version: 18.1460.0.52 CodeBase: file:///C:/Program%20Files/AI%20Lights%20Reborn%20Professional%20Edition/Syncfusion.SfInput.WinForms.DLL ---------------------------------------- Syncfusion.SfListView.WinForms Assembly Version: 18.1460.0.52 Win32 Version: 18.1460.0.52 CodeBase: file:///C:/Program%20Files/AI%20Lights%20Reborn%20Professional%20Edition/Syncfusion.SfListView.WinForms.DLL ---------------------------------------- Syncfusion.DataSource.WinForms Assembly Version: 18.1460.0.52 Win32 Version: 18.1460.0.52 CodeBase: file:///C:/Program%20Files/AI%20Lights%20Reborn%20Professional%20Edition/Syncfusion.DataSource.WinForms.DLL ---------------------------------------- LockheedMartin.Prepar3D.SimConnect Assembly Version: 4.4.0.0 Win32 Version: CodeBase: file:///C:/Program%20Files/AI%20Lights%20Reborn%20Professional%20Edition/LockheedMartin.Prepar3D.SimConnect.DLL ---------------------------------------- System.Data.SQLite Assembly Version: 1.0.106.0 Win32 Version: 1.0.106.0 CodeBase: file:///C:/Program%20Files/AI%20Lights%20Reborn%20Professional%20Edition/System.Data.SQLite.DLL ---------------------------------------- System.Data Assembly Version: 4.0.0.0 Win32 Version: 4.8.4261.0 built by: NET48REL1LAST_B CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_64/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll ---------------------------------------- System.Transactions Assembly Version: 4.0.0.0 Win32 Version: 4.8.4084.0 built by: NET48REL1 CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_64/System.Transactions/v4.0_4.0.0.0__b77a5c561934e089/System.Transactions.dll ---------------------------------------- System.EnterpriseServices Assembly Version: 4.0.0.0 Win32 Version: 4.8.4084.0 built by: NET48REL1 CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_64/System.EnterpriseServices/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.EnterpriseServices.dll ---------------------------------------- MadMilkman.Ini Assembly Version: 1.0.6.0 Win32 Version: 1.0.6.0 CodeBase: file:///C:/Program%20Files/AI%20Lights%20Reborn%20Professional%20Edition/MadMilkman.Ini.DLL ---------------------------------------- ************** 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. Appears to be looking for Cameras.cfg installed under Prepar3D v4. I run a dual boot system and Prepar3D v4 is installed under Windows 7. Not sure what I should be doing to resolve this issue so your guidance would be greatly appreciated. Many thanks, Mike

Very wise. Really, isn’t it about time MS’s Updates are subjected to far more rigorous quality control before unleashing them on unsuspecting users across the world? To clarify: https://www.windowscentral.com/whats-difference-between-quality-updates-and-feature-updates-windows-10 In the end, the decision rests with the end user. Currently this end user prefers to keep MS at bay as much as is realistically and sensibly possible. That way I can maintain a stable, well-performing setup. I can understand where RA is coming from. His statements are, of course, true. However, it could be argued that his requirements, and those of others who feel the compulsion to keep abreast of technological improvements are somewhat different to the average user such as myself. My system continues to deliver what I need in terms of performance and stability thereby negating any imperative to rock the boat needlessly and prematurely. Regards, Mike

Hi Ian, I wouldn’t worry about it too much. Unless or until something you are running actually needs the latest ‘Feature’ update, why invite further potential hassle? I had the same experience moving from 1903 to 2004. In my case it involved disconnecting all peripheral devices (except keyboard and mouse) prior to the update and each time the computer restarted I avoided failure by returning to the Win10 Desktop via the UEFA BIOS - Saving and Exit each time despite no BIOS changes having been made. However, I have a dual boot arrangement so my difficulties might have related to that in some way. The reality is that there really is little need to accept these so-called ‘Feature’ updates until Microsoft withdraws support for your current version. Even then, providing you can still receive the ‘Quality’ updates, including security fixes, then it seems to me that keeping MS’s meddling off our backs for as long as possible is a desirable objective! There is a way: https://www.windowslatest.com/2020/06/29/windows-10-registry-trick-to-block-feature-updates/ My fingers are tightly crossed! If this works, then I can stay on 2004 until MS withdraws support for this version in December 2021 - 12 months freedom from anxiety worrying when the next ‘Feature’ update will be thrust upon me! Bliss! I know most of you reading this will be surviving these updates without issues, but spare a thought for folk, like me and Ian, who have suffered and consequently share this love/hate relationship with our overlords at Redmond. Regards, Mike

Hi everyone! Found the answer!! As is often the case, the solution turned out to be embarrassingly simple! I've been tearing my hair out (not wise as already significantly follicly challenged..lol) over this one. Everything I did made no difference whatsoever; with the exception of the continued presence of engine noise, those VC sounds remained stubbornly conspicuous by their absence. Eventually I started comparing the Turbine Duke V2 and Legacy V2 folder properties from the Prepar3D v4.5 installations against their equivalents in Prepar3D v5 and still no joy, everything matched! Sooo frustrating! Then, it was the turn of the Sound folders. Both folders have a collection of wav files so, in a moment of idle curiosity, I decided to play a few in Windows Media Player and........nothing!! At this point a light came on and I headed for..... Windows 10 Sound settings and discovered that the chosen output device was in fact; Headphones (Rift Audio) A quick change to Speakers (Realtek High Definition Audio) and ALL is now well!! So, it would appear that configuring audio correctly (Primary Playback Device) in the sim was insufficient to permit those VC sounds to be heard in the Turbine Duke V2 and Legacy V2. It's also necessary to ensure that the output device in Windows 10 is set to match the sim's setting. Then those wav files will play. I had forgotten that my Oculus software, which always loads at boot, has this irritating habit of changing the Sound output device. I imagine this was why others did not share my experience. Incidentally, I was wrong about being offered a choice of sims (P3D4 and P3D5) during installation of these RealAir aircraft. In point of fact, that option does not present and the installations proceed to completion without incident after altering the path to the v5 Add-ons folder. Don't know where I was given that option. Perhaps it was seen during the Vertx DA62 installation...and that's another problem. Hopefully Sean will revisit this classic in the not too distant future. Regards, Mike

Hi Charlie, Do we have a choice? It’s a sad world when we feel we are being denied the opportunity of conveying our concerns for the welfare of someone who was held in such high regard by our community. I can only hope she becomes acquainted with this thread and feels motivated to respond to us. Kind regards, Mike

h r Hi Charlie, No doubt there is a simple explanation devoid of any fodder for the conspiracy theorists should they, god forbid, appear in this thread. This could be cleared up quite quickly. Perhaps someone from the AVSIM staff could get in touch with Elaine and bring this discussion to her attention? Just a suggestion. Kind regards, Mike

Hi, With respect, you are making an assumption for which we have no real evidence. Regards, Mike