Sorry if this is necroposting, but I recently tried to launch the Torricelli module with the Delta IV Heavy. Everything went great until I separated the module from the sustainer(?). The module ended up in deep space. Zero speed. In fact, all MFD's just produced garbage containing alot of #'s and !'s. So it basically went to the edge of the universe and was no longer visible with external view. Any idea on what could be causing this?
OHM Delta IV Launch Vehicles 3.0
- Thread starter OrbitHangar
- Start date
K_Jameson
Active member
- Joined
- Dec 30, 2009
- Messages
- 1,064
- Reaction score
- 3
- Points
- 38
Apart for the problems, the delta IV Heavy seems a little overkill for the Torricelli module, that has a weight well under 10,000 kg.
For the problem: Are you using Orbiter 2010 or the new Orbiter Beta? With the new version, the sc3 compatibility is not assured.
For the problem: Are you using Orbiter 2010 or the new Orbiter Beta? With the new version, the sc3 compatibility is not assured.
boogabooga
Bug Crusher
- Joined
- Apr 16, 2011
- Messages
- 2,999
- Reaction score
- 1
- Points
- 0
This is not sc3, but compatibility is not assured anyway.
Looks like your launch vehicle delivered your payload straight into NAN space.
Looks like your launch vehicle delivered your payload straight into NAN space.
I'm using Orbiter 2010 with D3D9. Everything looks great.
The reason I used the Heavy was that the documentation states that the Delta IV Medium 5,4 has a max payload of 6000. The Delta IV Heavy has a max of 13000.
The Torricelli config is as follows:
Code:
[CONFIG]
MESHNAME=Antares\Torricelli
SIZE=9
[B]EMPTY_MASS=9250[/B]
FUEL_MASS=5
MAIN_THRUST=0
RETRO_THRUST=0
ISP=3207
ATTITUDE_THRUST=40
TRIM=0.05
PMI=(18.01,18.01,3.16)
CW_Z_POS=2
CW_Z_NEG=2
CW_X=2
CW_Y=2
CROSS_SECTION=(5,5,8)
COG=2.5
PITCH_MOMENT_SCALE=0.00005
BANK_MOMENT_SCALE=0.00005
ROT_DRAG=(0.50,0.53,0.54)
VISIBLE=1
FOCUS=1
CAMERA=(0.0,-0.50,-3.5)Could it be a problem that when I use the "custom payload" feature, I'm linking it to Config/Spacecraft/Torricelli, which happens to be a ".ini" file and not a ".cfg" file? Please keep in mind that in-game, I simply type "Spacecraft/Torricelli".
Or would I simply say that the config path is just "Spacecraft/Spacecraft3", which IS a .cfg file.
I did a search of my Orbiter folder and there isn't a "Torricelli.cfg" in there. Just the "Torricelli.ini", which is where I procured the above quoted info.
EDIT: Actually, no scenario with the Torricelli is working. This is a copy of the log file:
Code:
**** Orbiter.log
Build Aug 30 2010 [v.100830]
Timer precision: 3.09285e-007 sec
Found 1 joystick(s)
Module AtlantisConfig.dll .... [Build 100830, API 100830]
Module AtmConfig.dll ......... [Build 100830, API 100830]
Module DGConfigurator.dll .... [Build 100830, API 100830]
Module D3D9Client.dll ........ [Build 140930, API 100830]
Module OrbiterSound.dll ...... [Build 121120, API 100830]
Module Framerate.dll ......... [Build 100830, API 100830]
Module ScnEditor.dll ......... [Build 100830, API 100830]
Module transx.dll ............ [Build 100824, API 100823]
Module Accelerometer.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.
---------------------------------------------------------------
**** Creating simulation session
D3D9Client: [DirectX 9 Initialized]
D3D9Client: Sytem has XNA math support
D3D9Client: [3DDevice Initialized]
D3D9Client: [Compiling Effects for Shader Model 3.0]
D3D9Client: [Loading Stars]
D3D9Client: [Loading Constellations]
D3D9Client: [D3D9Client Initialized]
Module Sun.dll ............... [Build 100830, API 100830]
VSOP87(E) Sun: Precision 1e-006, Terms 554/6634
Module Mercury.dll ........... [Build 100830, API 100830]
VSOP87(B) Mercury: Precision 1e-005, Terms 167/7123
Module Venus.dll ............. [Build 100830, API 100830]
Module VenusAtm2006.dll ...... [Build 100830, API 100830]
VSOP87(B) Venus: Precision 1e-005, Terms 79/1710
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
Module Mars.dll .............. [Build 100830, API 100830]
Module MarsAtm2006.dll ....... [Build 100830, API 100830]
VSOP87(B) Mars: Precision 1e-005, Terms 405/6400
Module Phobos.dll ............ [Build ******, API 060425]
Module Deimos.dll ............ [Build ******, API 060425]
Module Galsat.dll ............ [Build 100217, API 100215]
Module Jupiter.dll ........... [Build 100830, API 100830]
VSOP87(B) Jupiter: Precision 1e-006, Terms 1624/3625
Module Io.dll ................ [Build 100217, API 100215]
Module Europa.dll ............ [Build 100217, API 100215]
Module Ganymede.dll .......... [Build 100217, API 100215]
Module Callisto.dll .......... [Build 100217, API 100215]
Module Satsat.dll ............ [Build 100215, API 100212]
Module Saturn.dll ............ [Build 100830, API 100830]
VSOP87(B) Saturn: Precision 1e-006, Terms 2904/6365
Module Mimas.dll ............. [Build 100215, API 100212]
SATSAT Mimas: Terms 113
Module Enceladus.dll ......... [Build 100215, API 100212]
SATSAT Enceladus: Terms 33
Module Tethys.dll ............ [Build 100215, API 100212]
SATSAT Tethys: Terms 101
Module Dione.dll ............. [Build 100215, API 100212]
SATSAT Dione: Terms 59
Module Rhea.dll .............. [Build 100215, API 100212]
SATSAT Rhea: Terms 68
Module Titan.dll ............. [Build 100215, API 100212]
SATSAT Titan: Terms 100
Module Iapetus.dll ........... [Build 100215, API 100212]
SATSAT Iapetus: Terms 605
Module Uranus.dll ............ [Build 100830, API 100830]
VSOP87(B) Uranus: Precision 1e-006, Terms 1827/5269
Module Miranda.dll ........... [Build ******, API 060425]
Module Ariel.dll ............. [Build ******, API 060425]
Module Umbriel.dll ........... [Build ******, API 060425]
Module Titania.dll ........... [Build ******, API 060425]
Module Oberon.dll ............ [Build ******, API 060425]
Module Neptune.dll ........... [Build 100830, API 100830]
VSOP87(B) Neptune: Precision 1e-006, Terms 391/2024
Finished initialising world
>>> ERROR: No vessel class configuration file found for:
---------------------------------------------------------------
>>> ERROR: Multistage\Multistage2
>>> [Vessel::OpenConfigFile | .\Vessel.cpp | 252]
---------------------------------------------------------------
>>> TERMINATING <<<It appears there's an issue with Multistage2. I've placed a copy of it into my Modules folder. Does it need to go somewhere else? Or a 2nd copy also placed somewhere?
Help is greatly appreciated.
Last edited:
K_Jameson
Active member
- Joined
- Dec 30, 2009
- Messages
- 1,064
- Reaction score
- 3
- Points
- 38
that numbers are relative to GTO. To LEO the Heavy has over 23,000 kg of payload. Torricelli weight is about 9,200 kg, if i recall correctly. Are you launching in GTO or LEO?
LEO for now. I've scaled down and have been launching with the Medium 5,4. Now if I could only figure out how to launch into a suitable orbit for TLI......
Then I may go up to the heavy to take advantage of the extra delta-v for TLI.
For right now though, I'm (currently, as in right now) trying to figure out how to use LunarTransferMFD to compute a suitable launch time/inclination....
EDIT:
Sorry for going crazy in this thread, but I have a question and I can't seem to figure it out.
I've been able to use this addon to place the Torricelli into a suitable LEO for TLI. The documentation states that the tested inclinations are between 40 and 60. Anything outside of that and the AP tries for a polar orbit (more or less).
Is is possible to launch this addon into a LEO suitable for TLI with minimal relative inclination? If so, how do I go about figuring this out?
I apologize in advance. Figuring stuff like this out has always been a troublesome issue with me. Hyper-futuristic addons like the XR-2 using "magic fuel" is easy, but using something realistic seems to be beyond me.
Then I may go up to the heavy to take advantage of the extra delta-v for TLI.
For right now though, I'm (currently, as in right now) trying to figure out how to use LunarTransferMFD to compute a suitable launch time/inclination....
EDIT:
Sorry for going crazy in this thread, but I have a question and I can't seem to figure it out.
I've been able to use this addon to place the Torricelli into a suitable LEO for TLI. The documentation states that the tested inclinations are between 40 and 60. Anything outside of that and the AP tries for a polar orbit (more or less).
Is is possible to launch this addon into a LEO suitable for TLI with minimal relative inclination? If so, how do I go about figuring this out?
I apologize in advance. Figuring stuff like this out has always been a troublesome issue with me. Hyper-futuristic addons like the XR-2 using "magic fuel" is easy, but using something realistic seems to be beyond me.
Last edited:
To further the necromancy, I guess the 5/2 CTD never got fixed, and the performance still seems way too high, I can use the 4M2 to get a 6500 kg satellite to GTO and 8.45 degrees inclination from Canaveral with enough fuel left to deorbit the upper stage. The 5.4 can zero the inclination.
I don't think the real thing can do that.
I dunno about the 5.2, since I can't use it, and the heavy would just be a waste of fuel, though the real thing would be required to do that.. according to the specs.
---------- Post added at 01:43 AM ---------- Previous post was at 01:34 AM ----------
There is a way in IMFD to time the launch with an eastward azimuth (inclination = latitude), so that you can intercept the moon at the node between planes with a current or slightly off plane TLI, much like the apollo missions did. Been a while since I did that but google can help find the directions for how to do it.
I don't think the real thing can do that.
I dunno about the 5.2, since I can't use it, and the heavy would just be a waste of fuel, though the real thing would be required to do that.. according to the specs.
---------- Post added at 01:43 AM ---------- Previous post was at 01:34 AM ----------
There is a way in IMFD to time the launch with an eastward azimuth (inclination = latitude), so that you can intercept the moon at the node between planes with a current or slightly off plane TLI, much like the apollo missions did. Been a while since I did that but google can help find the directions for how to do it.
Last edited:
boogabooga
Bug Crusher
- Joined
- Apr 16, 2011
- Messages
- 2,999
- Reaction score
- 1
- Points
- 0
Yes, I've noticed the massive overperformance as well. The 5.4 is darn near SSTO with a light payload. I suspect it has something to do with the solid rocket boosters. I watched the first stage ascent with burn-time MFD open. ISP and wet/dry mass seem about right for the core. Also, the heavy performs closer to real world spec.
The author made a stunningly detailed and beautiful add-on, but from other comments he made regarding the autopilot, I get the impression that he did not understand all the math behind rocket science.
The author made a stunningly detailed and beautiful add-on, but from other comments he made regarding the autopilot, I get the impression that he did not understand all the math behind rocket science.
https://en.wikipedia.org/wiki/Azimuth
This was the where I got the basic formula for the autopilot. My code would make adjustments for altitude and recalculate but it just wasn't working as well as it should have. To fix this, when it came close to the desired altitude it would thrust a little left or right to keep the proper inclination.
This was the where I got the basic formula for the autopilot. My code would make adjustments for altitude and recalculate but it just wasn't working as well as it should have. To fix this, when it came close to the desired altitude it would thrust a little left or right to keep the proper inclination.
boogabooga
Bug Crusher
- Joined
- Apr 16, 2011
- Messages
- 2,999
- Reaction score
- 1
- Points
- 0
virii2k, welcome back! Long time no see. 
ZacharyS41
Donator
- Joined
- Sep 9, 2013
- Messages
- 130
- Reaction score
- 11
- Points
- 33
- Location
- Roanoke
- Website
- www.zachsellinger.com
Whenever I start up any of the Delta IV Launch Vehicles addon scenarios, I get a CTD because it's missing spot.dds, which is not included in the ZIP archive. Where do I find the texture?
---------- Post added at 06:09 AM ---------- Previous post was at 06:08 AM ----------
---------- Post added at 06:09 AM ---------- Previous post was at 06:08 AM ----------
Code:
**** Orbiter.log
Build Aug 30 2010 [v.100830]
Timer precision: 5.69957e-007 sec
Found 0 joystick(s)
Devices enumerated: 6
Devices accepted: 5
==> RGB Emulation
==> Direct3D HAL
==> Direct3D T&L HAL
==> Direct3D HAL (AMD Radeon(TM) R3 Graphics)
==> Direct3D T&L HAL (AMD Radeon(TM) R3 Graphics)
Module AtlantisConfig.dll .... [Build 100830, API 100830]
Module AtmConfig.dll ......... [Build 100830, API 100830]
Module DGConfigurator.dll .... [Build 100830, API 100830]
Module Meshdebug.dll ......... [Build 100830, API 100830]
Module TrackIR.dll ........... [Build 100830, API 100830]
TrackIR module not found.
Module CustomMFD.dll ......... [Build 100830, API 100830]
Module LuaMFD.dll ............ [Build 100830, API 100830]
Module transx.dll ............ [Build 100824, API 100823]
Module LuaConsole.dll ........ [Build 100830, API 100830]
Module ScriptMFD.dll ......... [Build 100830, API 100830]
Module OrbiterSound.dll ...... [Build 121120, API 100830]
Module ExtMFD.dll ............ [Build 100830, API 100830]
Module FlightData.dll ........ [Build 100830, API 100830]
Module Framerate.dll ......... [Build 100830, API 100830]
Module Rcontrol.dll .......... [Build 100830, API 100830]
Module ScnEditor.dll ......... [Build 100830, API 100830]
Module ReleaseMFD-Mouse.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 ReleaseMFD-ShiftD.dll . [Build ******, API 060425]
Module vel_hud.dll ........... [Build ******, API 060425]
Module LaunchMFD.dll ......... [Build 150104, API 100830]
**** Creating simulation session
DirectDraw interface OK
Direct3D interface OK
Graphics: Viewport: Window 1444 x 786 x 32
Graphics: Hardware T&L capability: Yes
Graphics: Z-buffer depth: 32 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 Mercury.dll ........... [Build 100830, API 100830]
VSOP87(B) Mercury: Precision 1e-005, Terms 167/7123
Module Venus.dll ............. [Build 100830, API 100830]
Module VenusAtm2006.dll ...... [Build 100830, API 100830]
VSOP87(B) Venus: Precision 1e-005, Terms 79/1710
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
Module Mars.dll .............. [Build 100830, API 100830]
Module MarsAtm2006.dll ....... [Build 100830, API 100830]
VSOP87(B) Mars: Precision 1e-005, Terms 405/6400
Module Phobos.dll ............ [Build ******, API 060425]
Module Deimos.dll ............ [Build ******, API 060425]
Module Galsat.dll ............ [Build 100217, API 100215]
Module Jupiter.dll ........... [Build 100830, API 100830]
VSOP87(B) Jupiter: Precision 1e-006, Terms 1624/3625
Module Io.dll ................ [Build 100217, API 100215]
Module Europa.dll ............ [Build 100217, API 100215]
Module Ganymede.dll .......... [Build 100217, API 100215]
Module Callisto.dll .......... [Build 100217, API 100215]
Module Satsat.dll ............ [Build 100215, API 100212]
Module Saturn.dll ............ [Build 100830, API 100830]
VSOP87(B) Saturn: Precision 1e-006, Terms 2904/6365
Module Mimas.dll ............. [Build 100215, API 100212]
SATSAT Mimas: Terms 113
Module Enceladus.dll ......... [Build 100215, API 100212]
SATSAT Enceladus: Terms 33
Module Tethys.dll ............ [Build 100215, API 100212]
SATSAT Tethys: Terms 101
Module Dione.dll ............. [Build 100215, API 100212]
SATSAT Dione: Terms 59
Module Rhea.dll .............. [Build 100215, API 100212]
SATSAT Rhea: Terms 68
Module Titan.dll ............. [Build 100215, API 100212]
SATSAT Titan: Terms 100
Module Iapetus.dll ........... [Build 100215, API 100212]
SATSAT Iapetus: Terms 605
Module Uranus.dll ............ [Build 100830, API 100830]
VSOP87(B) Uranus: Precision 1e-006, Terms 1827/5269
Module Miranda.dll ........... [Build ******, API 060425]
Module Ariel.dll ............. [Build ******, API 060425]
Module Umbriel.dll ........... [Build ******, API 060425]
Module Titania.dll ........... [Build ******, API 060425]
Module Oberon.dll ............ [Build ******, API 060425]
Module Neptune.dll ........... [Build 100830, API 100830]
VSOP87(B) Neptune: Precision 1e-006, Terms 391/2024
Finished initialising world
---------------------------------------------------------------
>>> 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.
---------------------------------------------------------------
Module Lpad2.dll ............. [Build 111209, API 100830]
---------------------------------------------------------------
>>> ERROR: Missing texture: delta4/spot.dds
>>> [TextureManager::AcquireTexture | .\Texture.cpp | 750]
---------------------------------------------------------------
Finished initialising status
Finished initialising camera
Finished initialising panels
Last edited by a moderator:
garyw
O-F Administrator
- Joined
- May 14, 2008
- Messages
- 10,485
- Reaction score
- 209
- Points
- 138
- Location
- Kent
- Website
- blog.gdwnet.com
a missing texture won't cause a CTD, something else is causing it but it's not clear what it is from the logs.
ZacharyS41
Donator
- Joined
- Sep 9, 2013
- Messages
- 130
- Reaction score
- 11
- Points
- 33
- Location
- Roanoke
- Website
- www.zachsellinger.com
It was Velcro EELVs. I tried to combine Velcro's version of the rocket with your version of the launch pad and it seemed like both didn't mix well.
Similar threads
- Locked
- Sticky
