Idea Farscape Module on an ET?

[richfororbit]

Hello,

Would anyone be interested on making it possible to have a Farscape module attached to an ET, with SRB's along with it. Essentially replace the shuttle for the Farscape Module?

It may not appeal to many, but I had thought about a while back.

[ame="http://www.orbithangar.com/searchid.php?ID=232"]Farscape 1[/ame]

Thanks for reading.

 

[Delta glider]

How will it get into orbit?
The farscape doesn't have any SSMEs.
All concepts like yours had SSMEs on the main vehicle.

 

[orbitingpluto]

The Shuttle is an integral part of it's stack-removing it requires putting a vehicle which duplicates the Shuttle's capabilities where the Shuttle went(realistically, the Farscape-1 will never be that vehicle), or putting Shuttle-side hardware like the SSMEs and computers on the ET, at which that point you have some sort of SDLV, of which there are a bunch on the Hangar to pick from.

It might be easy enough to give the Farscape-1 thrust like 3 SSMEs- it uses a early form of Vinka's spacecraft after all, but finding someone interested in working for an half-hour to an hour for a silly idea that isn't even their own would be a tough search to undertake. Learning how to use multistage would be far easier than finding a willing individual, but then you have still have a relatively small Farscape-1 hanging off that huge ET.

Don't want to learn to code? As I said, there are various SDLVs on the Hanger, as well as an SLS on the forum in this thread. If you come to the conclusion that it's wasteful to launch the little Farscape-1 on LV that can easily do 50 metric tons(the Farscape-1 is around 8mt) and that looking like a wee remora on a whale isn't cool, I'd suggest the [ame="http://orbithangar.com/searchid.php?ID=4703"]North American DG Launcher by n_molson[/ame] as a suitably STS-like launcher that isn't STS-huge. As a plus, since the Farscape-1 weighs so little, you can use the 2 SRM version of the DG launcher, so it looks even more like a STS stack.

 

[richfororbit]

I don't know anything about this, just incase some skilled user might want to try this.

I suppose the module would have sit on the tank where the shuttle was, ofcourse the support struts are too far apart.

I didn't think it'd be popular.

 

[orbitingpluto]

Look, this doesn't require a 'skilled' user, whatever the definition of that is. If you want to go the replace the Shuttle with the Farscape-1 route, Multistage comes with a manual explaining what all the lines do, and examples of STS, all in plain text so the only programs you'll need is a .pdf file reader and Notepad. And if you can't figure out the manual on you own, at the very least I'm willing to help you out; I guess other people here on OF will be willing to help explain stuff as well.

Or, you could use one of the alternatives I suggested, like the DG-Launcher:

The only things I did was edit the scenario file- removing the Delta-Glider, copying in the Farscape, and then changing a line in the DG-Launcher's core to attach the Farscape instead of the Delta-Glider I removed. Typing out what I did took longer than doing it.

Not being popular is an excuse for other people to not build on your idea- for you, it's all about whether or not you want it. If you want to, I could to point you directly to the manuals and examples, point out what stuff you should look at especially, and lay out how you go about getting started. With something like attaching the Farscape to a SDLV or something, I can guarantee it'll be easy, less than 20 minutes, but something closer to your original idea will take something near an hour(perhaps less), depending on whether it's multistage or Velcro.

C'mon, you got a mentor, a half-baked idea, and a weekend ahead of you: what could possibly go wrong?

 

[richfororbit]

I guess you sussed out I don't do much on the weekends.

I had just previously been using the constellation files, landed the Altair pretty badly, more of attempted success, a few tumbles. It is quite nice. Nice to see Mars from the surface of the Moon only looking out the front window Azimuth dead ahead.

It's always repetitive, youtube space related documentaries and episodes of Star trek.

Hmm, I'm going to insert the module files into Orbiter, as I had done reinstall weeks back. I think I still have the old copy which included Phantom's editing of the file, he made it workable such as the wings, and it being able to dock. How ever that isn't a priority.

Thanks for the patience then.

Where do I begin to get this working?

farscape:Spacecraft\Spacecraft
  STATUS Landed Earth
  POS -80.604146 28.608107
  HEADING 330.01
  RCSMODE 0
  PRPLEVEL 0:1 1:1 2:1
  MeshSkin Shuttle_Discovery_Skin
  GEAR 0 0.00
  O2ConsumptionSetting -1
  FuelConsumptionSetting -1
  MainenginePower -1
END

For the third scenario.

 

[orbitingpluto]

By third scenario, did you mean "DG-Launcher (North America) - Cape Canaveral to ISS.scn"? That's a bit overkill for the Farscape, since there's six SRMs in that scenario. I think it's best to use the "DG-Launcher (North America) - 2 GEM60s configuration.scn", so I'll use that for my examples.

Anyway, the DG-launcher is Velcro-based, so what I'm going to say here will also work for other Velcro-based addons. So, let's open up "DG-Launcher (North America) - 2 GEM60s configuration.scn" and see what we have:

BEGIN_DESC
Launch a boosted DeltaGlider-IV from Cape Canaveral LC39A. Your mission is to bring back astronauts from the ISS. 


Make sure the DG-Launcher is selected (F3), wait 30 seconds, then press "O". That should bring you (very) roughly on the ISS orbital plane (Rinc = 2.7°). 


Once in orbit, select the launcher and press "J" for separation.


For this mission, you have only 1 pilot on board, no cargo and your fuel tanks are only 50% full. Are 2 GEM60 SRM enough to achieve orbit ?

END_DESC

BEGIN_ENVIRONMENT
  System Sol
  Date MJD 66351.6280783951
END_ENVIRONMENT

BEGIN_FOCUS
  Ship DG-Launcher
END_FOCUS

BEGIN_CAMERA
  TARGET DG-Launcher
  MODE Extern
  POS 2.74 -0.42 -98.15
  TRACKMODE TargetRelative
  FOV 50.00
END_CAMERA

BEGIN_HUD
  TYPE Surface
END_HUD

BEGIN_MFD Left
  TYPE Surface
  SPDMODE 1
END_MFD

BEGIN_MFD Right
  TYPE Orbit
  PROJ Ship
  FRAME Ecliptic
  REF Earth
END_MFD

BEGIN_SHIPS
ISS:ProjectAlpha_ISS
  STATUS Orbiting Earth
  RPOS -4937514.46 3605440.61 -2841742.28
  RVEL 1720.282 -3032.127 -6858.566
  AROT 113.44 -3.03 -19.04
  VROT 0.04 -0.01 0.11
  AFCMODE 7
  IDS 0:588 100 1:586 100 2:584 100 3:582 100 4:580 100
  NAVFREQ 0 0
  XPDR 466
END
Discovery:DeltaGliderIV
  STATUS Landed Earth
  POS -80.604146 28.608107
  HEADING 330.01
  RCSMODE 0
  PRPLEVEL 0:0.5 1:0.5 2:1
  MeshSkin Shuttle_Discovery_Skin
  GEAR 0 0.00
  O2ConsumptionSetting -1
  FuelConsumptionSetting -1
  MainenginePower -1
  UMMUCREW Capt-Jan_Bergsein-47-60-72
END
SG1:Velcro/DGL_NA_2_ParticleGEN
  STATUS Landed Earth
  POS -80.604146 28.608107
  HEADING 330.01
  RCSMODE 0
  ATTACHED 0:1,DG-Launcher
  PRPLEVEL 0:1 1:1 2:1
  GEAR 0 0.00
END
DG-Launcher:Velcro/DG_Launcher_Core_US
  STATUS Landed Earth
  POS -80.604146 28.608107
  HEADING 225.00
  PRPLEVEL 0:1.000000
  NAVFREQ 0 0
  CONFIGURATION 0
  PRIMEBOOSTER 1
  PADBIAS 0
  CENTERTHRUST 1
  IGNITENEXT 0
  JETT_ON_MECO 1
  TGT_HEADING 45
  PITCHMULTIPLE 1
  DELAYSTART 8
  SERIESBURN 0 Discovery 0 -4.9 9  0.0 1.0 0.0
END
SRB-L1:Velcro/DG_Launcher_GEM60
  STATUS Landed Earth
  POS -80.604146 28.608107
  NAVFREQ 0 0
  CONFIGURATION 0
  PRIMEBOOSTER 0
  CENTERTHRUST 1
  TGT_HEADING 45
  DELAYSTART 2
  PARALLELBURN 1 DG-Launcher -3.44 -0.45 -11.5 0.0000 0.0000 -1.0000 -1.0000 0.0000 0.0000
END
SRB-R1:Velcro/DG_Launcher_GEM60
  STATUS Landed Earth
  POS -80.604146 28.608107
  NAVFREQ 0 0
  CONFIGURATION 0
  PRIMEBOOSTER 0
  CENTERTHRUST 1
  TGT_HEADING 45
  DELAYSTART 2
  PARALLELBURN 1 DG-Launcher 3.44 -0.45 -11.5 0.0000 0.0000 -1.0000 1.0000 0.0000 0.0000
END
Systems:Velcro/DG_Launcher_Systems_US
  STATUS Landed Earth
  POS -80.604146 28.608107
  NAVFREQ 0 0
  CONFIGURATION 0
  PRIMEBOOSTER 0
  CENTERTHRUST 1
  JETT_ON_EMPTY 0
  JETT_ON_MECO 0
  TGT_HEADING 45
  DELAYSTART 1
  BOOSTERBURN 0 DG-Launcher 0.25 0.0 0.00 -6.2  0.0000 0.0000 -1.0000  -1.0000 0.0000 0.0000
END
END_SHIPS

BEGIN_ExtMFD
END

What we are really interested in is the stuff in between the BEGIN_SHIPS and END_SHIPS lines; here's them again, plus some annotations explaining what vessel we are going to mess with, and what lines(if any) we're going to edit:

BEGIN_SHIPS
ISS:ProjectAlpha_ISS [COLOR=Red]It's the ISS, and we'll leave it be[/COLOR] 
  STATUS Orbiting Earth
  RPOS -4937514.46 3605440.61 -2841742.28
  RVEL 1720.282 -3032.127 -6858.566
  AROT 113.44 -3.03 -19.04
  VROT 0.04 -0.01 0.11
  AFCMODE 7
  IDS 0:588 100 1:586 100 2:584 100 3:582 100 4:580 100
  NAVFREQ 0 0
  XPDR 466
END
Discovery:DeltaGliderIV [COLOR=Red]A DGIV named Discovery(names go before the two dots symbol(:)), which is going to swapped out for the Farscape[/COLOR]
  STATUS Landed Earth
  POS -80.604146 28.608107
  HEADING 330.01
  RCSMODE 0
  PRPLEVEL 0:0.5 1:0.5 2:1
  MeshSkin Shuttle_Discovery_Skin
  GEAR 0 0.00
  O2ConsumptionSetting -1
  FuelConsumptionSetting -1
  MainenginePower -1
  UMMUCREW Capt-Jan_Bergsein-47-60-72
END
SG1:Velcro/DGL_NA_2_ParticleGEN [COLOR=Red]This is part of the DG-Launcher, though it doesn't have anything to do with attaching the Farscape as a payload, so we will leave it alone[/COLOR]
  STATUS Landed Earth
  POS -80.604146 28.608107
  HEADING 330.01
  RCSMODE 0
  ATTACHED 0:1,DG-Launcher
  PRPLEVEL 0:1 1:1 2:1
  GEAR 0 0.00
END
DG-Launcher:Velcro/DG_Launcher_Core_US [COLOR=Red]The Core of the DG launcher, where the DGIV is attached to we'll be editing this vessel a bit.[/COLOR]
  STATUS Landed Earth
  POS -80.604146 28.608107
  HEADING 225.00
  PRPLEVEL 0:1.000000
  NAVFREQ 0 0
  CONFIGURATION 0
  PRIMEBOOSTER 1
  PADBIAS 0
  CENTERTHRUST 1
  IGNITENEXT 0
  JETT_ON_MECO 1
  TGT_HEADING 45
  PITCHMULTIPLE 1
  DELAYSTART 8
  SERIESBURN 0 Discovery 0 -4.9 9  0.0 1.0 0.0 [COLOR=Red]Note that this line attaches Discovery(the DGIV) to the Core.[/COLOR]
END
SRB-L1:Velcro/DG_Launcher_GEM60 [COLOR=Red]One of the SRMs- we don't have to do anything to it
[COLOR=Black]  STATUS Landed Earth[/COLOR][/COLOR]
  POS -80.604146 28.608107
  NAVFREQ 0 0
  CONFIGURATION 0
  PRIMEBOOSTER 0
  CENTERTHRUST 1
  TGT_HEADING 45
  DELAYSTART 2
  PARALLELBURN 1 DG-Launcher -3.44 -0.45 -11.5 0.0000 0.0000 -1.0000 -1.0000 0.0000 0.0000
END
SRB-R1:Velcro/DG_Launcher_GEM60 [COLOR=Red]Same deal with as with the other SRM[/COLOR]
  STATUS Landed Earth
  POS -80.604146 28.608107
  NAVFREQ 0 0
  CONFIGURATION 0
  PRIMEBOOSTER 0
  CENTERTHRUST 1
  TGT_HEADING 45
  DELAYSTART 2
  PARALLELBURN 1 DG-Launcher 3.44 -0.45 -11.5 0.0000 0.0000 -1.0000 1.0000 0.0000 0.0000
END
Systems:Velcro/DG_Launcher_Systems_US [COLOR=Red]Another thing we can safely ignore[/COLOR]
  STATUS Landed Earth
  POS -80.604146 28.608107
  NAVFREQ 0 0
  CONFIGURATION 0
  PRIMEBOOSTER 0
  CENTERTHRUST 1
  JETT_ON_EMPTY 0
  JETT_ON_MECO 0
  TGT_HEADING 45
  DELAYSTART 1
  BOOSTERBURN 0 DG-Launcher 0.25 0.0 0.00 -6.2  0.0000 0.0000 -1.0000  -1.0000 0.0000 0.0000
END
END_SHIPS

So, the DGIV attaches to the DG-launcher at it's core, with this line:

 SERIESBURN 0 [COLOR=Red]Discovery[/COLOR] 0 -4.9 9  0.0 1.0 0.0

Now, this line gets explained in detail on page 6 of the Velcro Rocket manual, but the thing I'm going to point out is that the part in red. Right now it tells the Velcro Rockets to attach a vessel named "Discovery" to the DG-Launcher core. So long as there's a vessel with the right name, it'll be attached. So, let's change it to attach to farscape instead:

  SERIESBURN 0 farscape 0 -4.9 9  0.0 1.0 0.0

Keep in mind we ought to paste in the Farscape's vessel information as well, or we'll cause a crash. Now we'll just delete the DGIV to clean up the scenario, and let's take a screen capture or two to celebrate the progress thus far:

Maybe positioning will be lesson two, to see if we can find a spot where this thing doesn't look like it's hanging in mid air. But let's see how lesson one goes.

 

[Loru]

Or you can use HCLV. It has already payload adapter integrated so it's only matter of spawning rocket and Farscape and attaching latter to the rocket via payload manager.

 

[richfororbit]

farscape:Spacecraft\Spacecraft
  STATUS Landed Earth
  POS -80.604146 28.608107
  HEADING 330.01
  RCSMODE 0
  PRPLEVEL 0:0.5 1:0.5 2:1
  MeshSkin Shuttle_Discovery_Skin
  GEAR 0 0.00
  O2ConsumptionSetting -1
  FuelConsumptionSetting -1
  MainenginePower -1
  UMMUCREW Capt-Jan_Bergsein-47-60-72
END
SG1:Velcro/DGL_NA_2_ParticleGEN
  STATUS Landed Earth
  POS -80.604146 28.608107
  HEADING 330.01
  RCSMODE 0
  ATTACHED 0:1,DG-Launcher
  PRPLEVEL 0:1 1:1 2:1
  GEAR 0 0.00
END
DG-Launcher:Velcro/DG_Launcher_Core_US
  STATUS Landed Earth
  POS -80.604146 28.608107
  HEADING 225.00
  PRPLEVEL 0:1.000000
  NAVFREQ 0 0
  CONFIGURATION 0
  PRIMEBOOSTER 1
  PADBIAS 0
  CENTERTHRUST 1
  IGNITENEXT 0
  JETT_ON_MECO 1
  TGT_HEADING 45
  PITCHMULTIPLE 1
  DELAYSTART 8
  SERIESBURN 0 farscape  0 -4.9 9  0.0 1.0 0.0
END

This is correct, how ever the scene loads with the Module as shown in my example image.:huh:

 

[orbitingpluto]

Or you can use HCLV. It has already payload adapter integrated so it's only matter of spawning rocket and Farscape and attaching latter to the rocket via payload manager.

Teaching someone to use Payload Manager is kinda like giving a person a fish, when what I'm really after is teaching them to fish on their own. Otherwise, I would fully agree with with you.

farscape:Spacecraft\Spacecraft
  STATUS Landed Earth
  POS -80.604146 28.608107
  HEADING 330.01
  RCSMODE 0
  PRPLEVEL 0:0.5 1:0.5 2:1
  MeshSkin Shuttle_Discovery_Skin
  GEAR 0 0.00
  O2ConsumptionSetting -1
  FuelConsumptionSetting -1
  MainenginePower -1
  UMMUCREW Capt-Jan_Bergsein-47-60-72
END
SG1:Velcro/DGL_NA_2_ParticleGEN
  STATUS Landed Earth
  POS -80.604146 28.608107
  HEADING 330.01
  RCSMODE 0
  ATTACHED 0:1,DG-Launcher
  PRPLEVEL 0:1 1:1 2:1
  GEAR 0 0.00
END
DG-Launcher:Velcro/DG_Launcher_Core_US
  STATUS Landed Earth
  POS -80.604146 28.608107
  HEADING 225.00
  PRPLEVEL 0:1.000000
  NAVFREQ 0 0
  CONFIGURATION 0
  PRIMEBOOSTER 1
  PADBIAS 0
  CENTERTHRUST 1
  IGNITENEXT 0
  JETT_ON_MECO 1
  TGT_HEADING 45
  PITCHMULTIPLE 1
  DELAYSTART 8
  SERIESBURN 0 farscape  0 -4.9 9  0.0 1.0 0.0
END

This is correct, how ever the scene loads with the Module as shown in my example image.:huh:

I forgot to point out that for Velcro Rockets, attachments only come together(at least visual, as far as I know) after Orbiter runs for a second. Just unpause the sim for a bit and everything will look right. Also:

farscape:Spacecraft\Spacecraft
  STATUS Landed Earth
  POS -80.604146 28.608107
  HEADING 330.01
  RCSMODE 0
  PRPLEVEL 0:0.5 1:0.5 2:1
  MeshSkin Shuttle_Discovery_Skin
  GEAR 0 0.00
  O2ConsumptionSetting -1
  FuelConsumptionSetting -1
  MainenginePower -1
  UMMUCREW Capt-Jan_Bergsein-47-60-72
END

You left a fair amount of the DGIV's scenario lines in the farscape's area- I object to it more as a messy thing, but you could also introduce weird errors or even crashes by mixing up scenario code.

Anyway, once everything is more or less like the screenshots I posted, why don't you do a flight to LEO, and I'll start preparing another lesson.

 

[richfororbit]

Removing that doesn't change the fact that the module remains at the bottom under the tank/rocket nozzle.

 

[orbitingpluto]

Notice how the sim time in the upper right corner says zero, and if you look at the engine on the core, you can see the SRMs are standing inside the core. The Farscape in my scenario isn't even near the DG-Launcher, so we can't see it... yet.

I unpaused the sim, let it run a second, then paused to take this screenshot. The Farscape is now where it should be, as well as the SRMs.

 

[richfororbit]

Why is it like that for?

Still no change for my scenario. My scenario is exactly the same?

farscape:Spacecraft\Spacecraft
  STATUS Landed Earth
  POS -80.604146 28.608107
  HEADING 330.01
  RCSMODE 0
  PRPLEVEL 0:0.5 1:0.5 2:1
END
SG1:Velcro/DGL_NA_2_ParticleGEN
  STATUS Landed Earth
  POS -80.604146 28.608107
  HEADING 330.01
  RCSMODE 0
  ATTACHED 0:1,DG-Launcher
  PRPLEVEL 0:1 1:1 2:1
  GEAR 0 0.00
END
DG-Launcher:Velcro/DG_Launcher_Core_US
  STATUS Landed Earth
  POS -80.604146 28.608107
  HEADING 225.00
  PRPLEVEL 0:1.000000
  NAVFREQ 0 0
  CONFIGURATION 0
  PRIMEBOOSTER 1
  PADBIAS 0
  CENTERTHRUST 1
  IGNITENEXT 0
  JETT_ON_MECO 1
  TGT_HEADING 45
  PITCHMULTIPLE 1
  DELAYSTART 8
  SERIESBURN 0 farscape  0 -4.9 9  0.0 1.0 0.0

 

[orbitingpluto]

Why is it like that for?

My guess is that the Velcro Rocket's code only starts moving and attaching vessels after Orbiter starts running- it's not a bad thing though.

Still no change for my scenario. My scenario is exactly the same?

I've looked at your screenshot, and looked at you posted of the scenario, and I don't know what's up. You should post the whole scenario file so I can scrutinize it- try mine below, and see if it's similarly wonky.

BEGIN_DESC
farscape
END_DESC

BEGIN_ENVIRONMENT
  System Sol
  Date MJD 66351.6280783951
END_ENVIRONMENT

BEGIN_FOCUS
  Ship DG-Launcher
END_FOCUS

BEGIN_CAMERA
  TARGET DG-Launcher
  MODE Extern
  POS 2.74 -0.42 -98.15
  TRACKMODE TargetRelative
  FOV 50.00
END_CAMERA

BEGIN_HUD
  TYPE Surface
END_HUD

BEGIN_MFD Left
  TYPE Surface
  SPDMODE 1
END_MFD

BEGIN_MFD Right
  TYPE Orbit
  PROJ Ship
  FRAME Ecliptic
  REF Earth
END_MFD

BEGIN_SHIPS
ISS:ProjectAlpha_ISS
  STATUS Orbiting Earth
  RPOS -4937514.46 3605440.61 -2841742.28
  RVEL 1720.282 -3032.127 -6858.566
  AROT 113.44 -3.03 -19.04
  VROT 0.04 -0.01 0.11
  AFCMODE 7
  IDS 0:588 100 1:586 100 2:584 100 3:582 100 4:580 100
  NAVFREQ 0 0
  XPDR 466
END
farscape:Spacecraft\Spacecraft
  STATUS Landed Earth
  POS -80.6858943 28.5906644
  HEADING 330.01
  PRPLEVEL 0:1.000
  NAVFREQ 94 481
END
SG1:Velcro/DGL_NA_2_ParticleGEN
  STATUS Landed Earth
  POS -80.604146 28.608107
  HEADING 330.01
  RCSMODE 0
  ATTACHED 0:1,DG-Launcher
  PRPLEVEL 0:1 1:1 2:1
  GEAR 0 0.00
END
DG-Launcher:Velcro/DG_Launcher_Core_US
  STATUS Landed Earth
  POS -80.604146 28.608107
  HEADING 225.00
  PRPLEVEL 0:1.000000
  NAVFREQ 0 0
  CONFIGURATION 0
  PRIMEBOOSTER 1
  PADBIAS 0
  CENTERTHRUST 1
  IGNITENEXT 0
  JETT_ON_MECO 1
  TGT_HEADING 45
  PITCHMULTIPLE 1
  DELAYSTART 8
  SERIESBURN 0 farscape 0 -4.9 9  0.0 1.0 0.0
END
SRB-L1:Velcro/DG_Launcher_GEM60
  STATUS Landed Earth
  POS -80.604146 28.608107
  NAVFREQ 0 0
  CONFIGURATION 0
  PRIMEBOOSTER 0
  CENTERTHRUST 1
  TGT_HEADING 45
  DELAYSTART 2
  PARALLELBURN 1 DG-Launcher -3.44 -0.45 -11.5 0.0000 0.0000 -1.0000 -1.0000 0.0000 0.0000
END
SRB-R1:Velcro/DG_Launcher_GEM60
  STATUS Landed Earth
  POS -80.604146 28.608107
  NAVFREQ 0 0
  CONFIGURATION 0
  PRIMEBOOSTER 0
  CENTERTHRUST 1
  TGT_HEADING 45
  DELAYSTART 2
  PARALLELBURN 1 DG-Launcher 3.44 -0.45 -11.5 0.0000 0.0000 -1.0000 1.0000 0.0000 0.0000
END
Systems:Velcro/DG_Launcher_Systems_US
  STATUS Landed Earth
  POS -80.604146 28.608107
  NAVFREQ 0 0
  CONFIGURATION 0
  PRIMEBOOSTER 0
  CENTERTHRUST 1
  JETT_ON_EMPTY 0
  JETT_ON_MECO 0
  TGT_HEADING 45
  DELAYSTART 1
  BOOSTERBURN 0 DG-Launcher 0.25 0.0 0.00 -6.2  0.0000 0.0000 -1.0000  -1.0000 0.0000 0.0000
END
END_SHIPS

BEGIN_ExtMFD
END

 

[richfororbit]

The one obvious difference was at the top, farscape wasn't listed below Begin and End.

I tried you're code now there is no module there.:hmm:

 

[richfororbit]

Here is an example image, so now the module is long way from the rocket, that is the rocket that blop in the image.

 

[orbitingpluto]

My scenario should work fine, so I'm suspecting there might be something amiss with your installation of Orbiter. Mind posting the contents of your Orbiter.log file, and give me a general outlook on what you've installed?

 

[richfororbit]

I've installed plenty of addons, some of them work and some don't.

The orbiter log would be this?

**** Orbiter.log
Build Aug 30 2010 [v.100830]
Timer precision: 2.79365e-007 sec
Found 0 joystick(s)
Devices enumerated: 3
Devices accepted: 3
==> RGB Emulation
==> Direct3D HAL
==> Direct3D T&L HAL
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 121120, API 100830]
Module ExtMFD.dll ............ [Build 100830, API 100830]
Module Rcontrol.dll .......... [Build 100830, API 100830]
Module ScnEditor.dll ......... [Build 100830, API 100830]
Module LuaMFD.dll ............ [Build 100830, API 100830]
Module transx.dll ............ [Build 100824, API 100823]
Module FlightData.dll ........ [Build 100830, API 100830]
Module CustomMFD.dll ......... [Build 100830, API 100830]
Module LunarTransferMFD.dll .. [Build 100621, API 100603]

 

[orbitingpluto]

That is the Orbiter.log file, though it seems cut off. It should be a lot longer, with an entire area below that part that starts with a line called "**** Creating simulation session" with a whole lot more info.

 

[richfororbit]

There aren't any other text files that'd display anything of the sort. Should I perhaps just open up a new Orbiter, See what happens.