OHM Space Plane Eridanus 1.11

DelRioPilot

New member
Joined
Aug 3, 2009
Messages
87
Reaction score
0
Points
0
I have a problem with this spacecraft's staging, despite having the required Vrinka add-ons.

Basically, the SRB's and other components (like the nose launch tower), will just "blink" away when jettisoned.

This problem does not appear to happen to other spacecrafts I have.

This is a great add-on, but if anyone can help me with this problem I'd greatly appreciate it!
 

diogom

Well-known member
Joined
Aug 2, 2010
Messages
1,374
Reaction score
416
Points
98
I have a problem with this spacecraft's staging, despite having the required Vrinka add-ons.

Basically, the SRB's and other components (like the nose launch tower), will just "blink" away when jettisoned.

This problem does not appear to happen to other spacecrafts I have.

This is a great add-on, but if anyone can help me with this problem I'd greatly appreciate it!

You mean they disappear?
Try [ame="http://www.orbithangar.com/searchid.php?ID=4661"]Stage.dll for Orbiter 2010[/ame]
 
Last edited:

Interceptor

Well-known member
Joined
Mar 28, 2008
Messages
2,718
Reaction score
76
Points
63
Location
Michigan,Florida
Hi,fausto I was just wondering if you are going to update this addon,anymore,not to bug you,but I would really like you to fix the Ummu bug,since I use this great addon alot.Thanks
 

fausto

FOI SuperMod
Joined
Jul 13, 2008
Messages
797
Reaction score
2
Points
0
Location
Monza (Milan)
We're talking about a possible D3D9 compatible package update, but nothing about UMMU at the moment, i'm sorry..:shrug:
 
Joined
Oct 5, 2009
Messages
70
Reaction score
0
Points
6
We are working to change the position of the docking protection cone:


Now the cone opens downwards, avoiding to block the jets of the RCS engines. But not expect the release of this upgrade until the new year (maybe even until march).
 
Last edited:

kerlix

Donator
Donator
Joined
Mar 28, 2010
Messages
294
Reaction score
47
Points
43
Sorry for posting in such an old thread. But I had a few questions.


First, I know that the package comes with a few payloads for the cargo bay. But I'm working on constructing my own space station and I noticed that most of the ISS modules are just too big to fit into the cargo bay. At least I think. Most of the time I can see them sticking out through the cargo doors. It could just be bad placement on my part.


Do we know the dimensions of the bay? Also, are there any FOI cargo modules that were released post-Eridanus that I can use that will fit? I found a few references here and there, but it appears that they were never finished/released.

If not, that's okay. I can find other ways to get modules to orbit using the Quasar. But I like the RMS and the ability to dock and then position new modules to my station during construction.


Thanks for any pointers.
 

orbitingpluto

Orbiteer
Joined
May 1, 2010
Messages
618
Reaction score
0
Points
16
Sorry for posting in such an old thread. But I had a few questions.


First, I know that the package comes with a few payloads for the cargo bay. But I'm working on constructing my own space station and I noticed that most of the ISS modules are just too big to fit into the cargo bay. At least I think. Most of the time I can see them sticking out through the cargo doors. It could just be bad placement on my part.


Do we know the dimensions of the bay? Also, are there any FOI cargo modules that were released post-Eridanus that I can use that will fit? I found a few references here and there, but it appears that they were never finished/released.

If not, that's okay. I can find other ways to get modules to orbit using the Quasar. But I like the RMS and the ability to dock and then position new modules to my station during construction.


Thanks for any pointers.


You're probably not using the offsets enough. To reacquaint myself with how Eridanus does payloads, I ran a few test scenarios with the Habitat Core from [ame="http://www.orbithangar.com/searchid.php?ID=2857"]Space Station Modules addon[/ame] loaded aboard Eridanus via the config file. For the first test, I deliberately left the offsets at zero for all axes and left the rotation and direction values at the defaults. After eight to ten minutes of browsing the web in another window, I saw something similar to what you described.

attachment.php


It's a bit too high, and after opening the bay doors(didn't grab a screenshot for that, sorry) it also was too close to Eridanus's external airlock as well. But, it's just a matter of getting the offsets right, and lucky for me, my first guess was close to what was needed, so I only had to sit through two more launches.

Leaving the X offset alone, putting the Y to -2, and the z to -1.5, shifted the Habitat Core down 2 meters and aftwards 1 and half meters and it fits, mostly.

attachment.php


There looks to be enough space fore and aft between the rear bulkhead and external airlock for the Core to fit comfortably. Based on the values for the fore and aft docking ports in the Core's config file, plus a little addition, I think the Core spans about 9 and half meters, or around 30 feet. Width-wise though..

attachment.php


attachment.php


..it's actually fine, excluding the protruding docking ports, which extend into the bay at the bottom and protrude through the boom/arm, depending on what side of Eridanus you're looking at. From one port to the other is 4.38 meters, or a few inches over 14 feet. Anyway, making it so the port don't protrude into anything would need some attention to the rot and dir values(rotating the side docking ports to face up and down instead of port and starboard), and probably moving the Y offset up a few tenths of a meter, but that's just a bit of guess work and patience, since I'm reasonably sure that there's enough room.

Also, now that I think of it, I could've saved a scenario after the first launch got into orbit, altered the values in that scenario file, then loaded it up in Orbiter to check the new values, and then after however many changes and loadings, put the fixed values into the Eridanus payload config file, and by doing that, only have to sit through a launch twice.

Well, hope this helps you get a grip on putting payloads into Eridanus.
 

Attachments

  • 15.08.25 08-54-11 Eridanus.jpg
    15.08.25 08-54-11 Eridanus.jpg
    66.2 KB · Views: 157
  • 15.08.25 09-33-40 Eridanus.jpg
    15.08.25 09-33-40 Eridanus.jpg
    102.9 KB · Views: 159
  • 15.08.25 10-04-17 Eridanus.jpg
    15.08.25 10-04-17 Eridanus.jpg
    122.2 KB · Views: 157
  • 15.08.25 10-04-23 Eridanus.jpg
    15.08.25 10-04-23 Eridanus.jpg
    113.1 KB · Views: 158

kerlix

Donator
Donator
Joined
Mar 28, 2010
Messages
294
Reaction score
47
Points
43
You're probably not using the offsets enough.

Thank you. You're probably right. I'm at work and won't be able to mess around with this myself for another 6 hours or so. Is there any way you could post a sample config file showing how you set the offsets? I'm sure it's simple and once I look at it, I'll have an "Ah-HA!" moment and remember I'm not nearly as slow as I appear to be.

I'm just new (to say the least) to altering config files for attachment offsets and rotations. Having an example to see/work off of would help tremendously. Off topic, but I spent a good 2 hours last night trying to put Destiny into Discovery from SF4.8. I could stretch it, make it 300x's the correct size, shrink it down like it had a rubber band around it. Finally figured it out. Took it up to orbit, couldn't grapple it. Released it from the PLDB and it just.........floated........down through the floor of the shuttle and disappeared. Anyways, if I can get things like this into the Eridanus, I'd be a happy camper. I'll attempt the SF4.8 attaching/grappling/rendezvous/docking/re-entering a set of challenges for a new day. Preferably one with a deliciously strong beverage. I mean, have you ever seen all the attachment-related things that have to be put it? And the manual only dealt with attaching the ODSS...... I was smoking like a chimney. But, anyways. Holy work stress-related rant, Batman! Sorry about that.

Back to the topic at hand....

And after looking at the pictures, I'd be fine with the docking ports "hitting" the sides. However, I'd like to try rotating it just to see if the ports would protrude through payload bay doors. If so, I'd just keep it "as is" since, externally (I don't think), there would be anything "off-putting". Not that it REALLY matters. But still. I'd like it to look correct/pretty haha.


Either way, I really appreciate you taking the time to look into this.

---------- Post added at 11:28 AM ---------- Previous post was at 11:23 AM ----------

I'm also going to pick up that addon package. Never knew about that.
 
Last edited:

K_Jameson

Active member
Joined
Dec 30, 2009
Messages
1,064
Reaction score
3
Points
38
Eridanus cargo bay is much smaller than Shuttle.
It retains almost the same width and depth, but is roughly one third shorter. The maximum (certified) payload is around 14,000 kg instead 24,000 (see the manual). So yes, some ISS modules are probably too big for Eridanus.
The concept behind Eridanus was that a ludicrously big cargo bay is obsolete and is more effective to lift big payloads with unmanned heavy cargo launchers.
 
Last edited:

Pipcard

mikusingularity
Addon Developer
Donator
Joined
Nov 7, 2009
Messages
3,709
Reaction score
39
Points
88
Location
Negishima Space Center
The Shuttle's payload bay was that big because it was designed to carry large KH-9 HEXAGON spy satellites.
 

orbitingpluto

Orbiteer
Joined
May 1, 2010
Messages
618
Reaction score
0
Points
16
The config file to put things in Eridanus for launch is the the file "eridanus_payload.cfg" in the root of your particular Orbiter folder. It's pretty self-explanatory, but here is what the file looks like set up to launch the Habitat Core I used. I haven't made any changes since yesterday morning, so it should look just like the screenshots I posted.

Code:
;set to TRUE if you want a payload in the cargo bay, FALSE otherwise
PAYLOAD_ACTIVE = TRUE
PAYLOAD_2_ACTIVE=FALSE
;vessel name
NAME = HabitatModuleCore
;NAME_2=Cubesat
;vessel class name (configuration file)
CLASSNAME = spacecraft/spacecraft3
;CLASSNAME_2 = spacecraft/spacecraft3
;three axis payload offset in meters  
OFS_X=0
OFS_Y=-2
OFS_Z=-1.5

OFS_X_2=0
OFS_Y_2=0
OFS_Z_2=-5

;three axis payload direction (default is ;0,1,0)

DIR_X=0
DIR_Y=1
DIR_Z=0

DIR_X_2=0
DIR_Y_2=1
DIR_Z_2=0


;three axis payload rotation(default is ;0,0,1)

ROT_X=0
ROT_Y=0
ROT_Z=1

ROT_X_2=0
ROT_Y_2=0
ROT_Z_2=1
;Crew configuration: set to TRUE if you want a member on board, FALSE otherwise
CMD = TRUE
PLT = TRUE
MS1 = TRUE
MS2 = FALSE
MS3 = FALSE
MS4 = FALSE
MS5 = FALSE

Also, note that after launch(and Eridanus is flying free), the same payload information is expressed in Eridanus's section in the vessel part of the scenario file; here is the contents of a scenario file with Eridanus and the Habitat Core in the bay:

Code:
BEGIN_DESC
Contains the latest simulation state.
END_DESC

BEGIN_ENVIRONMENT
  System Sol
  Date MJD 63076.8621657368
END_ENVIRONMENT

BEGIN_FOCUS
  Ship Eridanus
END_FOCUS

BEGIN_CAMERA
  TARGET Eridanus
  MODE Extern
  POS 0.55 27.88 -24.10
  TRACKMODE TargetRelative
  FOV 50.00
END_CAMERA

BEGIN_HUD
  TYPE Surface
END_HUD

BEGIN_MFD Left
  TYPE Orbit
  PROJ Ship
  FRAME Ecliptic
  ALT
  REF Earth
END_MFD

BEGIN_MFD Right
  TYPE Surface
  SPDMODE 1
END_MFD

BEGIN_VC
END_VC

BEGIN_SHIPS
padqb:spacecraft\Spacecraft3
  STATUS Landed Earth
  POS -80.6312600 28.5419000
  HEADING 90.00
  AFCMODE 7
  NAVFREQ 0 0 0 0
  XPDR 0
  RCS 1
  CTRL_SURFACE 1
  CONFIGURATION 1
  CURRENT_PAYLOAD 0
  SEQ 0 2 1.0000
  SEQ 1 -2 1.0000
END
nearpad-j:spacecraft\Spacecraft3
  STATUS Landed Earth
  POS -80.6311600 28.5419300
  HEADING 90.00
  AFCMODE 7
  NAVFREQ 0 0 0 0
  XPDR 0
  RCS 1
  CTRL_SURFACE 1
  CONFIGURATION 1
  CURRENT_PAYLOAD 0
END
Quasar_220-E:Multistage\Multistage2
  STATUS Orbiting Earth
  RPOS -4170948.30 5101962.64 142972.58
  RVEL 5102.001 4341.816 -4016.620
  AROT 131.35 -41.86 56.49
  VROT 0.07 -0.00 0.00
  AFCMODE 7
  PRPLEVEL 0:0.033346
  NAVFREQ 0 0
  CONFIG_FILE Config\quasar\Eridanus\Quasar_220-E.ini
  GUIDANCE_FILE Config\Quasar\Eridanus\guidance_quasar_220-E.txt
  CONFIGURATION 1
  MET 751.108255
  STAGE_STATE 3
  STAGE_IGNITION_TIME 0.000000
  CURRENT_BOOSTER 7
  CURRENT_STAGE 1
  CURRENT_INTERSTAGE 1
  CURRENT_PAYLOAD 2
  FAIRING 0
  GNC_RUN 1
  GNC_PROGRAM 0
  GNC_STEP 23
  GNC_MET 751.158060
  GNC_AUTO_JETTISON 0.000000
END
HabitatModuleCore:spacecraft/spacecraft3
  STATUS Orbiting Earth
  RPOS -4170782.26 5101831.42 142934.19
  RVEL 5102.800 4341.140 -4016.782
  AROT 126.53 -36.70 -179.75
  ATTACHED 0:1,Eridanus
  AFCMODE 7
  NAVFREQ 0 0 0 0
  XPDR 0
  RCS 1
  CTRL_SURFACE 1
  CONFIGURATION 1
  CURRENT_PAYLOAD 0
END
EBSS:EBSS
  STATUS Orbiting Earth
  RPOS -4170783.06 5101833.98 142933.50
  RVEL 5102.800 4341.140 -4016.782
  AROT 126.53 -36.70 -179.75
  ATTACHED 0:3,Eridanus
  AFCMODE 7
  NAVFREQ 0 0
END
Eridanus:vessels\eridanus
  STATUS Orbiting Earth
  RPOS -4170781.33 5101833.20 142934.61
  RVEL 5102.800 4341.140 -4016.782
  AROT 126.53 -36.70 -179.75
  AFCMODE 7
  PRPLEVEL 0:1.000000 1:0.995997 2:1.000000
  NAVFREQ 0 0
  CONFIGURATION 3
  COM 0
  PIL 0
  MS1 0
  MS2 0
  MS3 0
  MS4 0
  MS5 0
  ABORT_STATUS 0
  COM_ABOARD 1
  PIL_ABOARD 1
  MS1_ABOARD 1
  MS2_ABOARD 0
  MS3_ABOARD 0
  MS4_ABOARD 0
  MS5_ABOARD 0
  PAYLOAD_STATUS 2
  PAYLOAD_2_STATUS 1
  GEAR 0 0.0000
  DKNOSE 0 0.0000
  TIMER1SCN 201.1640
  PAYLOAD_MASS 13900.0000
  DKHATCH 0 0.0000
  AIRLOCK 0 0.0000
  abort_timer_scn 749.1640
  ARM_STATUS 0.5000 0.0000 0.0000 0.5000 0.5000 0.5000
  SAT_OFS_X 0.000000
  SAT_OFS_Y -2.500000
  SAT_OFS_Z -1.500000
  SAT_DIR_X 0.000000
  SAT_DIR_Y 1.000000
  SAT_DIR_Z 0.000000
  SAT_ROT_X 0.000000
  SAT_ROT_Y 0.000000
  SAT_ROT_Z 1.000000
  SAT_OFS_X_2 0.000000
  SAT_OFS_Y_2 0.000000
  SAT_OFS_Z_2 -5.000000
  SAT_DIR_X_2 0.000000
  SAT_DIR_Y_2 1.000000
  SAT_DIR_Z_2 0.000000
  SAT_ROT_X_2 0.000000
  SAT_ROT_Y_2 0.000000
  SAT_ROT_Z_2 1.000000
  CARGODOOR 1 1.0000
END
END_SHIPS

BEGIN_VistaBoost
END

That all for now, it's a bit late.
 

Pipcard

mikusingularity
Addon Developer
Donator
Joined
Nov 7, 2009
Messages
3,709
Reaction score
39
Points
88
Location
Negishima Space Center
Even the cloud texture in the background looks like Orbiter. :rofl:
That's because it is an Orbiter screenshot, and they just edited the image to add the "AVATAR" and "ISRO" markings.

Specifically, it's a cropped and edited version of one of the images here. And on the same page, T.Neo mentioned the "AVATAR shuttle" so I'm guessing they were looking for pictures of AVATAR and found that page.
 
Last edited:

Urwumpe

Not funny anymore
Addon Developer
Donator
Joined
Feb 6, 2008
Messages
37,635
Reaction score
2,352
Points
203
Location
Wolfsburg
Preferred Pronouns
Sire
That's because it is an Orbiter screenshot, and they just edited the image to add the "AVATAR" and "ISRO" markings.

Yes, exactly. It is a pretty crappy work to claim copyright for it. That is what I meant.
 

boogabooga

Bug Crusher
Joined
Apr 16, 2011
Messages
2,999
Reaction score
1
Points
0
My favorite part is that they watermarked the image that they stole with their website address. :rofl:
 
Top