- Feb 14, 2023
- Reaction score
- Not on the Sun
Well,I have absolutely no idea why it seems that d3d9 self destructs according to the log
The window does load.The same happens on every scenario.I'm on win10That is strange: the Orbiter log has many entries duplicated.
The D3D9 log shows it dies after spending 4.2s looking at the scenario (seems a lot of time), and apparently without even loading the window (I get the entry "================ clbkCreateRenderWindow ===============" afterwards). Does the same happen with any other scenario? BTW: what is in that "(Current state)" scenario?
Another piece of the puzzle is: what is your Windows version?
Maybe @jarmonik or @kuddel have an idea of what could be failing at that point of the loading...
It gets stuck in loading celetial sphere,and there are three warnings down there,one saying cubic interpolation,one saying missing configs,and the lasst one i forgotCan you see anything interesting in windows event viewer?
You looked in the Windows Event Viewer -> application logs?It gets stuck in loading celetial sphere,and there are three warnings down there,one saying cubic interpolation,one saying missing configs,and the lasst one i forgot
DirectX 9 is the one you need! DirectX 10,11 or higher do not include all the needed drivers!BTW,does directx matter?I have directx 9 but I have heard of directx 11.Does it neeed the absolute newest version to work?
If the redistributable package isn't installed in your computer you will receive an error message "The
program can't start because d3dx9_42.dll is missing from your computer". Or you may see a pop-up
window in Orbiter LaunchPad telling about a missing runtimes. If that happens then download and
extract the content of the package in any empty directory you want and then find a Setup.exe and run
it. You can delete the contents of the directory after the setup is completed. The directory is just a
temporary storage for the installation files.
Here is a link: https://www.microsoft.com/en-us/download/details.aspx?id=8109
okThe logs you've posted are strange...
Could you tell your AntiVrus Software to ignore the C:\Orbiter2016\ path?
The one log where everything "is doubled", seems like another glitch, that might be caused by something completely diferent
Just in case: Have you tried reebooting your system?
DirectX 9 is the one you need! DirectX 10,11 or higher do not include all the needed drivers!
Please install this one [*] - maybe it's just that.
The first time.Hmm, very strange.
Have you ever had Orbiter working before, say on a different computer in the past? Or is this your first time ever installing it?
Did you install from the ZIP or MSI?
It might be worth starting over and re-installing. Maybe despite your best intentions something didn't copy or work right?
It would be very helpful to know what your hardware specs are. There probably isn't a problem with your hardware, but maybe something isn't compatible.
Try running at a very low resolution and see if it will launch (e.g 800x600 or 1024x768).
Try windowed mode.
We all really want to help you get going. I think there is some step that we are all assuming you did correctly, but which you don't know you needed to do.
Could you maybe show some screenshots/video of the install, and your attempt to launch Orbiter. Maybe we'll see something.
Module Sun.dll ............... [Build 160828, API 160828]One small point: The first post in this thread mentions that a crash occurs even in the server version (the blue icon) without a graphics client loaded. So it is unlikely that the problem is related to the graphics subsystem. In fact, using the server version without graphics client may be the best option to continue debugging, since it eliminates any potential graphics problems. If this doesn't work, nothing else will.