OHM PrometheusLV For Orbiter10

[OrbitHangar]

Author: zatnikitelman


This is the Prometheus Launch Vehicle updated to Orbiter10.
This is a realistic near-tech launcher family now for Orbiter10 using common-core technology similar to a DeltaIV, AtlasV, or Angara. You can launch 15, 60, 90, or 110 tonnes to low Earth orbit.

Install by extracting into your main Orbiter directory.
Documentation is in ORBITER_ROOT\Doc\PrometheusLV

***IMPORTANT*** A bug has been discovered that causes a crash when the countdown with the launchpad reaches T-2 seconds. As a workaround, insert DEBUG in Prometheus's scenario file definition until I can release a patch.


DOWNLOAD

 

[mojoey]

wow...nice start to a tuesday! keep up the good work!

 

[Pipcard]

(this is on a clean version of Orbiter 2010)

In the scenario "Prometheus", I press F2 to go into the rocket to find that it has no fuel. I press U to start the autothrottle (not autopilot); there is a countdown. At -2 seconds, Orbiter crashes.

 

[Zatnikitelman]

I was unable to replicate by re-downloading Orbiter100830 and downloading Prometheus from Orbithangar.
Have you edited the Prometheus scenario in any way? Are you using Orbiter, or Orbiter_NG? If NG, then what graphics client? Can you also post your Orbiter.log file? Are you using OrbiterSound?

 

[Pipcard]

I was unable to replicate by re-downloading Orbiter100830 and downloading Prometheus from Orbithangar.
Have you edited the Prometheus scenario in any way? Are you using Orbiter, or Orbiter_NG? If NG, then what graphics client? Can you also post your Orbiter.log file? Are you using OrbiterSound?

I have not edited the scenario at all. I am using the default Orbiter (without any graphics clients). There is no OrbiterSound, but I also tried it with OrbiterSound installed, and it crashes too.

Here's the Orbiter.log, because you were curious:

Module DGConfigurator.dll .... [Build 100830, API 100830]
Module ScnEditor.dll ......... [Build 100830, API 100830]

**** Creating simulation session
DirectDraw interface OK
Direct3D interface OK
Graphics: Viewport: Window 1274 x 688 x 32
Graphics: Hardware T&L capability: No
Graphics: Z-buffer depth: 32 bit
Graphics: Stencil buffer depth: 8 bit
Graphics: Active lights supported: -1
Loading 15382 records from star database
Module Sun.dll ............... [Build 100830, API 100830]
VSOP87(E) Sun: Precision 1e-006, Terms 554/6634
Module Earth.dll ............. [Build 100830, API 100830]
Module EarthAtmJ71G.dll ...... [Build 100830, API 100830]
VSOP87(B) Earth: Precision 1e-008, Terms 2564/2564
Module Moon.dll .............. [Build 100830, API 100830]
ELP82: Precision 1e-005, Terms 116/829
Finished initialising world
Module Prometheus.dll ........ [Build 111121, API 100830]
Module Prompad.dll ........... [Build 111121, API 100830]
Finished initialising status
Finished initialising camera
Finished initialising panels
Finished setting up render state

There seems to be no problems when loading the scenario, but when that countdown reaches -2, it crashes. Does the Hardware T&L have anything to do with this?

---------- Post added at 07:09 PM ---------- Previous post was at 06:55 PM ----------

When I said clean, I meant that there were no other add-ons installed. I did make a few changes to the Orbiter.cfg, Sol.cfg, and Orbiter Launchpad settings.

I downloaded 100830 (as clean as you can get) again and Prometheus. The tanks were full this time, but the same thing happened as the engines ignited (-2 seconds). Crash.

 

[Zatnikitelman]

Just to eliminate everything, try running with a default Orbiter.cfg, Sol.cfg, and Launchpad Settings. Then if you don't have the problem, make your changes one by one until the problem appears.

 

[Pipcard]

Just to eliminate everything, try running with a default Orbiter.cfg, Sol.cfg, and Launchpad Settings. Then if you don't have the problem, make your changes one by one until the problem appears.

That's what I did "(as clean as you can get)".

It still crashed.

 

[Zatnikitelman]

Well, I'm not sure what to do at this point. It runs fine on my systems when I do the exact same thing with a perfectly clean install. The only thing I can think of is something weird to do with Visual Studio 2008 and its redistributables. As a final step, could you try and download them from Microsoft and try again? After this, all I can do is see if someone else has the same problem and work with them too.
Here's the link to the VS2008 Redist: https://www.microsoft.com/download/en/details.aspx?id=29

 

[Pipcard]

Tried that. Still crashed.

 

[orb]

Does the Hardware T&L have anything to do with this?

If you have enabled local light sources, then yes.

 

[Pipcard]

If you have enabled local light sources, then yes.

You can have local light sources without Hardware T&L if you put "MaxLights=8" in Orbiter.cfg (visual parameters).

With local light sources disabled, Orbiter still crashes when the engines start up during the autothrottle countdown.

 

[orb]

With local light sources disabled, Orbiter still crashes when the engines start up during the autothrottle countdown.

You didn't say anything about your settings or post Orbiter.cfg, so the only thing from the log which could cause problems was local light sources, there's nothing more. :shrug:

 

[Pipcard]

You didn't say anything about your settings or post Orbiter.cfg, so the only thing from the log which could cause problems was local light sources, there's nothing more. :shrug:

I tried it with an Orbiter that had no settings modified, but it still crashed at the point in the countdown.

 

[orb]

I tried it with an Orbiter that had no settings modified, but it still crashed at the point in the countdown.

Is there some more detailed exception log from orbiter.exe in the Windows Event Viewer?

 

[Pipcard]

Here's what the event viewer says:

Faulting application orbiter.exe, version 0.0.0.0, faulting module 
d3dim700.dll, version 5.3.2600.5512, fault address 0x0000fb77.

 

[orb]

Here's what the event viewer says:

Faulting application orbiter.exe, version 0.0.0.0, faulting module 
d3dim700.dll, version 5.3.2600.5512, fault address 0x0000fb77.

I can reproduce the access violation exception at the same address of d3dim700.dll in WinXP SP3 MCE when I start simulation unpaused with the Prometheus in scenario set to have LAUNCHPAD. When simulation is started paused with LAUNCHPAD in scenario, or when there is no LAUNCHPAD line and unpaused, the simulation launches fine. I didn't check if it crashes at countdown, but I'll do it later when I'll switch back to Windows again.

EDIT: The access violation exception at the same address in d3d7im700.dll occurs at MET:-1.9 seconds.

 

[Zatnikitelman]

Hrm, I still have been unable to reproduce the CTD bug under identical conditions. However, I have noticed that my particle streams from the launcher appear as grey blocks instead of puffy particles. Any ideas on this one Orb? I'm totally stumped here. But regardless, thanks for taking a look at my addon, at least it seems the problem has been narrowed down a bit, couldn't have done that without your help!

 

[orb]

Hrm, I still have been unable to reproduce the CTD bug under identical conditions. However, I have noticed that my particle streams from the launcher appear as grey blocks instead of puffy particles.

Could be because the exception only occurs in Windows XP, and you use Windows 7 x86_64. :shrug:

 

[Pipcard]

If the launchpad is removed, when I press U, the countdown starts at 0 and starts going up. (it never launches)

If I start the simulation paused, then I unpause it, it still crashes at -2 seconds in the countdown.

Could be because the exception only occurs in Windows XP, and you use Windows 7 x86_64. :shrug:

That must be the problem. Somehow this add-on is incompatible with XP.

 

[Izack]

Nope, crashing with exactly the same information as Pipcard under Windows 7 x64 with the same conditions.