OHM Proton Launch Vehicle v.2.2

[jgrillo2002]

Most of the satellites which are using tugs (DM or Breeze) are heavy to reach the orbit, so Proton brings them to the suborbital trajectory only. So you need to perform another manual burn to circularize the orbit.

Ah ok thanks. one question. do you know the mission trajectory for these satellites like were they in geostationary orbit. and where were they placed at that time? a mission document might be helpful. I checked the manual but it didnt help out

 

[Zeehond]

I have a small issue with the new update: If I want to return to the Orbiter Launchpad with ctrl-q, I get a window with a picture of the shuttle and with the message: "Please wait while Orbiter is closing down the simulation session..." which hangs at about 80% of the progress bar. This happens with a completely clean and fresh install of orbiter 2010 P1 with only the Proton addon added.

EDIT: This was on windows 7 64 bit. On windows XP, it crashed at the same window with the window saying "orbiter.exe has encountered a problem etc."

 

[IronRain]

that's because crtl-q shuts down orbiter. It's a standard key combination in windows which shuts down programs

 

[VF2_Rolf]

Beautiful Proton...been having lots of fun with it. Thanks very much.

 

[ryandtw]

I actually modified the Proton scenarios to allow more baseline Proton-K and Proton-M configurations, including the usage of the Breeze-M upper stage on the Proton-K - it did happen!

 

[Wishbone]

I started the Glonass scenario once more and found that DM-2 has weird RCS configuration, it seems like one of the thrusters is facing the wrong way. This confuses all autopilots.

 

[markweasal]

i dont like it alert

make it so the thing dosent need that something 3.5 program for the meshes

 

[Wishbone]

Well, here's my "I like it" alert... .NET 3.5 is fairly common this time of the year and saves a bit of time with the memory garbage collector. Hope Thorton would hunt down and exterminate the shutdown and RCS bugs, though.

 

[Thorton]

RCS bug in DM has been fixed. What did you imply by shutdown bug?

 

[Wishbone]

Every time I get out of a Proton or TMA or ISS scenario, Orbiter CTDs...

 

[Thorton]

IIRC, it's kml writer error and i won't fix it simply because it appears with only one shutdown option (deallocate memory). Since i don't use this option i don't wanna waste time searching for bug.

 

[N_Molson]

I recently noticed that IMFD 5.5 and ProtonLV 2.2 seems to conflict. Not a big problem tough, since there are plenty of navigation MFDs around...

 

[Thorton]

How exactly do they conflict?

 

[tblaxland]

IIRC, it's kml writer error and i won't fix it simply because it appears with only one shutdown option (deallocate memory). Since i don't use this option i don't wanna waste time searching for bug.

If the error is with an external utility (kml writer?) and it is not possible or difficult to remove the bug, would it be possible to add an option to disable its use by your addon (personally, I rarely view trajectories in Google Earth anyway). The "deallocate memory" option is very widely used because it is the default for O2010 P1.

 

[Wishbone]

There are a couple of heisenbugs that crop up somewhat at random: ISS scenarios (TMA-20, to be precise) starting only after the second time, with the first one experiencing a CTD, Soyuzes and Protons CTD-ing in midair at launch or during the first orbit. However I tend to agree with Thorton that "deallocation" as the default option doesn't work (please note that there's a hidden conflict of interests for me, since my behind has been recently bitten by the CTD at exit bug after adding the LPSolve dll). Sometimes add-on writers use static variables and AFAIK they do not get a notification that the simulation is being closed. Relying on OS memory management seems to be the least of evils, same rationale actually as going for GC memory management in the .NET framework, or Lord forbid, Java.

 

[N_Molson]

How exactly do they conflict?

I get a CTD when the loading of the scenario is finished.

Also, in the ISSR (last version), there is often a CTD lets say 60-90 seconds after the separation between the third stage and the Soyuz/Progress. Seems related to the discarded stages getting destroyed. To counter this, I use StateSaver and "clean" the last saved scenario. The third stage doesn't seem to cause any trouble.

 

[boby_nadeau]

When I try to load a scenario of the "Mir" addon (ex: the core launch, which need to load the proton K, it bug. Here's the log :

**** Orbiter.log
Build Aug 30 2010 [v.100830]
Timer precision: 2.79365e-007 sec
Found 0 joystick(s)
Devices enumerated: 6
Devices accepted: 5
==> RGB Emulation
==> Direct3D HAL
==> Direct3D T&L HAL
==> Direct3D HAL (ATI MOBILITY RADEON 7500)
==> Direct3D T&L HAL (ATI MOBILITY RADEON 7500)
Module AtlantisConfig.dll .... [Build 100830, API 100830]
Module AtmConfig.dll ......... [Build 100830, API 100830]
Module DGConfigurator.dll .... [Build 100830, API 100830]
Module OrbiterSound.dll ...... [Build ******, API 060425]
---------------------------------------------------------------
>>> WARNING: Obsolete API function used: oapiRegisterMFDMode
At least one active module is accessing an obsolete interface function.
Addons which rely on obsolete functions may not be compatible with
future versions of Orbiter.
---------------------------------------------------------------
Module RWarpMFD.dll .......... [Build ******, API 060425]
Module UMMUFA.dll ............ [Build ******, API 060425]
Module ScnEditor.dll ......... [Build 100830, API 100830]
Module InterMFD55.dll ........ [Build 100826, API 100704]
Module CamShake.dll .......... [Build 100811, API 100606]
Module B3OP.dll .............. [Build 101129, API 100830]

**** Creating simulation session
DirectDraw interface OK
Direct3D interface OK
Graphics: Viewport: Window 1018 x 736 x 16
Graphics: Hardware T&L capability: Yes
Graphics: Z-buffer depth: 16 bit
Graphics: Active lights supported: 8
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 Multistage2.dll ....... [Build ******, API 050206]
**** WARNING: Mesh not found: .\Meshes\Proton_LV/Proton_stg__0_1.msh
**** WARNING: Mesh not found: .\Meshes\Proton_LV/Proton_stg__0_1.msh
**** WARNING: Mesh not found: .\Meshes\Proton_LV/Proton_stg_1.msh
**** WARNING: Mesh not found: .\Meshes\Proton_LV/Proton_stg_2_USSR.msh
**** WARNING: Mesh not found: .\Meshes\Proton_LV/Proton_stg_3.msh
**** WARNING: Mesh not found: .\Meshes\Proton_LV/Proton_interstage.msh
**** WARNING: Mesh not found: .\Meshes\Proton_LV/Proton_fairing_1.msh
**** WARNING: Mesh not found: .\Meshes\Proton_LV/Proton_fairing_2.msh
Module Spacecraft3.dll ....... [Build ******, API 060425]
**** WARNING: Mesh file name not provided
---------------------------------------------------------------
>>> WARNING: Obsolete API function used: VESSEL::SetBankMomentScale
At least one active module is accessing an obsolete interface function.
Addons which rely on obsolete functions may not be compatible with
future versions of Orbiter.
---------------------------------------------------------------
**** WARNING: Mesh file name not provided
**** WARNING: Mesh file name not provided
Finished initialising status
Finished initialising camera
Finished initialising panels
Finished setting up render state
**** WARNING: Mesh not found: .\Meshes\.msh
**** WARNING: Mesh not found: .\Meshes\.msh
**** WARNING: Mesh not found: .\Meshes\.msh
**** WARNING: Mesh not found: .\Meshes\.msh
**** WARNING: Mesh not found: .\Meshes\.msh
**** WARNING: Mesh not found: .\Meshes\.msh
**** WARNING: Mesh not found: .\Meshes\.msh
**** WARNING: Mesh not found: .\Meshes\.msh

 

[astrosammy]

IIRC it uses an older version of the launcher (sorry if I'm wrong).

 

[clickypens]

I'm pretty sure the MIR addon used version 1.3 or something like that. IIRC, there's a patch available on Orbithangar to allow the newer Proton

[ame="http://www.orbithangar.com/searchid.php?ID=4555"]Mir v1.3 scenarios patch[/ame]

 

[nasafreak]

disable the autopilot with the M key

hello, I can't disable the autopilot with the M key in ver 2.2. It just doesn't do anything ?