Search results

Bumping this as I've need of these as well right now.

This is the scenario that it seems to happen most frequently in, STS-125. Attached a complete package, ready to be unpacked and run.

Lately, all of the crashes have been around OMS-2 TIG-2 minutes, usually inside of that, just after enabling left FLT CNTLR PWR on F6 and taking both OMS engines to ARM/PRESS on C3. Not sure if that means anything.

Tried building v1.15 sources in debug mode but the solution failed due to a non-existant orbiterD.lib. Builds perfectly fine in Release mode however.

Remember to make diffuse particle streams affected by shadows so that they aren't visible when they shouldn't be. I've attached a comparison, STS-108 which was a sunset launch (2219:28 UTC December 5 2001). Note how the lower half of the SRB smoke trail is in shadow while the upper half is lit...

Yes. I've tried just about everything here on my end but with very limited information. Maybe D3D9Client is just getting too old for an ever changing OS?

Tried multiple drivers and it remains the same.

No. Can be minutes between any action and the crash.

As I wrote earlier, it is completely random, it can happen at any time, not just OMS-2. Had it happen during first stage ascent, second stage ascent, during +X translation post-ET sep, configuring switches, you name it.

Negative. No change whatsoever.

No. It is completely random other than it requires a prelaunch scenario start. That's it.

Not that I have experienced as of yet. It's this as of yet unexplained sudden exit that only occurs when using a prelaunch scenario. No way to predict when it will happen, just that there's an chance of it happening.

Tried the latest nightly build of Orbiter-x86 and no change. Still crashes.

And that the logs are useless is a known issue which is documented here as an official issue report: github.com/orbitersim/orbiter/issues/382

Now I checked off the entire the list. Nothing have an effect.

The only things on that list I haven't tried is the lights and the launch site.

Logs were posted here: https://www.orbiter-forum.com/threads/space-shuttle-vessel.37856/post-636592 and the post below it.

Nothing special in the logs. This is the post where I first reported it: https://www.orbiter-forum.com/threads/space-shuttle-vessel.37856/post-636422

No joy on v1.11, same CTD during the OMS-2 burn.

And downgrading to even v1.13 yields no change in the CTD behavior.