My son just got bored with the default scenarios, so I just installed for him the full package of STS 2016 (including all required addons for launches & payloads, in the given order, respecting earth.cfg from SF as a no-go, etc.), but it CTD just before (any) scenario launch (even the first tweets of sound can be heard before CTD). No errors on logs. Same happens if I try to open a non-related scenario, for example the Orbiter Sound 5.0 demo videos scenarios.
I have, subsequently, made a separate Orbiter 2016 installation (on another disk partition) and I installed ONLY the core STS 2016 and the 3 required addons: Sound, D3D9 and Multistage. Launched it via _ng and everything works OK, of course, bar any payload related scenarios.
Same Modules selected at start, same video settings.
Are there any possible explanations/reasons for such behaviour? I know that it might be a trial-and-error enterprise, but some leads would be helpful. Thanks!
I have, subsequently, made a separate Orbiter 2016 installation (on another disk partition) and I installed ONLY the core STS 2016 and the 3 required addons: Sound, D3D9 and Multistage. Launched it via _ng and everything works OK, of course, bar any payload related scenarios.
Same Modules selected at start, same video settings.
Are there any possible explanations/reasons for such behaviour? I know that it might be a trial-and-error enterprise, but some leads would be helpful. Thanks!