A question for Brian - I was trying to make a 2nd Starship launch pad at KSC LC-39A using your "double Starship launch" scenario, but the pad and Starship ended up at dangerous angles with respect to the ground like the Leaning Tower of Pisa. What did my scenario went wrong I wonder?
Thanks...
EDIT: I myself found the solution! It was again the default date-and-other-format issue at stake, which I met with my old laptop almost 4 years ago:
https://www.orbiter-forum.com/threads/orbiter-2016-with-d3d9-ctd-in-all-scenarios.35786/post-545443
I wonder if this has been fixed in the...
Hi, I have been out of the Orbiter loop for several years due to my old laptop not keeping up with latest developments and that I developed some other interests elsewhere (last I touched the Orbiter folders was like late 2018, an eternity ;)) (+), but now I just finally built my own computer I'm...
Well the story will contain some.....artistic license (I mean the spacecraft will appear as if like persons so....).
However wasn't LIDS/NDS homogeneous?
<off-topic>I am still new to O2016 - what key should I press to hide the camera and time info? In O2010 it was [I] but this is no longer...
A scene which will probably appear in my planned story featuring personification of 2 real spacecraft and their interactions. The idea is to promote both of them ahead of their (first ;)) flights, as well as featuring comparison, contrast and interactions between Old and New in the spaceflight...
Credits now added by yours truly. :thumbup:
Cosmic Penguin on Twitter: "This screenshot is from Dr. Martin Schweiger's Orbiter Space Flight Simulator (https://t.co/4D1h5kkJ9E), something I have played for years. ?The Soyuz add-on used is the Soyuz v1.0 by Nikita Vtyurin & Andrew Thielmann ...
Hi! It's a long time since I have appeared here (though NSF/Twitter members should easily found me still hopping around :hailprobe:), and months since I have took Orbiter for a spin.
Here's a simulation scenario of the accident using igel et al. 's Soyuz v1.0 add-on (so it will only work in...
Here we always uses the decimal point [.] given the British ruling days, but as far as I know no-one on this side of the world actually uses the comma as decimal point. :P
Guess what? It worked! I had to change my region format (date/time etc.) settings to English (from Traditional Chinese as my laptop uses) and Orbiter works instantly.
Given my case, this old one (Simplified Chinese) and then this new case (Korean) all share the same characteristics, it seems...
Checking the events viewer, it seems that every single crash involves Exception code 0xc0000417 and Fault offset 0x000512be.
Googling the exception code seems to indicate interference from other programs, but I have no idea which one. Hopefully Martin can help to see if there's a chance that...
I have done just that to force the GPU to be used in the default orbiter.exe, but that didn't work and Intel Graphics continue to show up there (and CTDs at that same place). Strange because I certainly used that option before.....
One other thing - it happens that my laptop have Visual Studio...
Using the core package without D3D9 also crashes; however my laptop somehow falls back to my Intel HD Graphics chipset when running the default Orbiter.exe, and thus the log is much different:
While my previous attempts during the past 2 days were with clean installations, I have just tried again with the core Orbiter 2016 package from Mirror 1 and D3D9 from the link above. The program continues to CTD.
Here are the logs from this crash:
**** Orbiter.log
000000.000: Build Aug 28...