I paged through the forums (probably not well enough, which is usually the case, even with the search feature xD!!), but I can't find an instance of this issue.
I installed an add-on... I wish I could remember which one, I just know it recall it being a vessel... but something happened so fast that I couldn't really see what was going on. Almost as soon as the add-on was extracted, Orbiter popped up as though I had opened it (which I didn't, at least not manually), and then shut down again. When I opened it again (I normally use D3D9 and orbiter_ng.exe, but have tried with both that and the standard executable), more than half my modules and scenarios are missing, even though they're technically still installed; I checked. It's as if Orbiter had somehow reset. Even the log file is virtually clean. When this first happened, ever time I closed either Orbiter.exe or orbiter_ng, it would throw an error. Here's the log file:
It actually looks like there's something that's getting flagged for being out-of-version or something. I hadn't had that issue previously. Maybe I just need to go back and install everything again? -_-;; FAIL, because that takes forever, but I'm willing to do it. Also (and perhaps this should actually go in a D3D9Client thread, even though I don't think that caused the issue), when I select the D3D9 client in orbiter_ng.exe, when I launch Orbiter, it treats it as though it's not installed, even though it's checked off.
I installed an add-on... I wish I could remember which one, I just know it recall it being a vessel... but something happened so fast that I couldn't really see what was going on. Almost as soon as the add-on was extracted, Orbiter popped up as though I had opened it (which I didn't, at least not manually), and then shut down again. When I opened it again (I normally use D3D9 and orbiter_ng.exe, but have tried with both that and the standard executable), more than half my modules and scenarios are missing, even though they're technically still installed; I checked. It's as if Orbiter had somehow reset. Even the log file is virtually clean. When this first happened, ever time I closed either Orbiter.exe or orbiter_ng, it would throw an error. Here's the log file:
**** Orbiter.log
Build Nov 5 2011 [v.111105]
Timer precision: 3.39808e-007 sec
Found 0 joystick(s)
Module AtlantisConfig.dll .... [Build 111105, API 111105]
Module AtmConfig.dll ......... [Build 111105, API 111105]
Module DGConfigurator.dll .... [Build 111105, API 111105]
Module RWarpMFD.dll .......... [Build ******, API 060425]
---------------------------------------------------------------
>>> WARNING: Obsolete API function used: oapiRegisterMFDMode
At least one active module is accessing an obsolete interface function.
Addons which rely on obsolete functions may not be compatible with
future versions of Orbiter.
---------------------------------------------------------------
Module CustomMFD.dll ......... [Build 111105, API 111105]
Module OrbiterSound.dll ...... [Build 121120, API 100830]
Module JumpDriveMFD.dll ...... [Build ******, API 060425]
Module D3D9Client.dll ........ [Build 130712, API 100830]
Orbiter Version 111105
D3D9Client Build [Jul 12 2013]
Exception Code=0xC0000005, Address=0x04A39597
EAX=0x00000000 EBX=0x00000000 ECX=0x04A909AB EDX=0x00A2DB34 ESI=0x04CDBF70 EDI=0x76E25689 EBP=0x00A2F7A8 ESP=0x00A2F778 EIP=0x04A39597
C:\Users\na\Desktop\Orbiter2010\Modules\Plugin\D3D9Client.dll EntryPoint=0x04A91DBB, Base=0x04A30000, Size=1449984
Exception in clbkDestroyRenderWindow()
============================ ERROR: ===========================
Failed loading module Modules\Plugin\D3D9Client.dll (code 998)
[Orbiter::LoadModule | .\Orbiter.cpp | 612]
===============================================================
It actually looks like there's something that's getting flagged for being out-of-version or something. I hadn't had that issue previously. Maybe I just need to go back and install everything again? -_-;; FAIL, because that takes forever, but I'm willing to do it. Also (and perhaps this should actually go in a D3D9Client thread, even though I don't think that caused the issue), when I select the D3D9 client in orbiter_ng.exe, when I launch Orbiter, it treats it as though it's not installed, even though it's checked off.