OFSS Pilot Briefing Room

[radekpl]

Do not keep Progress on the station. Progress automatically undock when is full of waste. Progress is Cargo/Waste spacecraft. Cargo up, waste down. And burn in atmosphere of course I think next mission pilot should be undock Progress and burn with it into atmosphere.

 

[george7378]

Problem:

I get this in the Orbiter log file when I try to load my Mission 10 scenario:

**** Orbiter.log
Build Sep 29 2006 [v.060929]
Devices enumerated: 2
Devices accepted: 2
==> RGB Emulation
==> Direct3D HAL
Found 1 joystick(s)
Module AtlantisConfig.dll [API v.060425]
Module DGConfig.dll [API v.060425]
Module AeroBrakeMFD.dll [API v.060425]
Module BaseSyncMFD.dll [API v.060425]
Module ExtMFD.dll [API v.060425]
Module Framerate.dll [API v.050206]
Module OrbiterSound.dll [API v.060425]
Module ScnEditor.dll [API v.060425]
Module ReleaseMFD-ShiftD.dll [API v.060425]
Module ReleaseMFD-Mouse.dll [API v.060425]
Module spacecraft3.dll [API v.060425]
**** Creating simulation session
DirectDraw interface OK
Direct3D interface OK
Zbuffer: 32 bit
Stencil buffer: 8 bit
Render device: Fullscreen 1024 x 768
Device has no hardware T&L capability
Joystick throttle: Z-AXIS
Joystick throttle control detected
Module Sun.dll [API v.050206]
VSOP87(E) Sun: Precision 1e-006, Terms 554/6634
Module Mercury.dll [API v.050206]
VSOP87(B) Mercury: Precision 1e-005, Terms 167/7123
Module Venus.dll [API v.050206]
VSOP87(B) Venus: Precision 1e-005, Terms 79/1710
Module Earth.dll [API v.050206]
VSOP87(B) Earth: Precision 1e-008, Terms 2564/2564
Module Moon.dll [API v.041022]
ELP82: Precision 1e-005, Terms 116/829
Module Mars.dll [API v.060425]
VSOP87(B) Mars: Precision 1e-005, Terms 405/6400
Module Phobos.dll [API v.060425]
Module Deimos.dll [API v.060425]
Module Galsat.dll [API v.041022]
Module Jupiter.dll [API v.050206]
VSOP87(B) Jupiter: Precision 1e-006, Terms 1624/3625
Module Io.dll [API v.041022]
Module Europa.dll [API v.041022]
Module Ganymede.dll [API v.041022]
Module Callisto.dll [API v.041022]
Module Satsat.dll [API v.050206]
Module Saturn.dll [API v.060425]
VSOP87(B) Saturn: Precision 1e-006, Terms 2904/6365
Module Mimas.dll [API v.050206]
SATSAT Mimas: Terms 113
Module Enceladus.dll [API v.050206]
SATSAT Enceladus: Terms 33
Module Tethys.dll [API v.050206]
SATSAT Tethys: Terms 101
Module Dione.dll [API v.050206]
SATSAT Dione: Terms 59
Module Rhea.dll [API v.050206]
SATSAT Rhea: Terms 68
Module Titan.dll [API v.050206]
SATSAT Titan: Terms 100
Module Hyperion.dll [API v.050206]
SATSAT Hyperion: Terms 595
Module Iapetus.dll [API v.050206]
SATSAT Iapetus: Terms 605
Module Uranus.dll [API v.050206]
VSOP87(B) Uranus: Precision 1e-006, Terms 1827/5269
Module Miranda.dll [API v.060425]
Module Ariel.dll [API v.060425]
Module Umbriel.dll [API v.060425]
Module Titania.dll [API v.060425]
Module Oberon.dll [API v.060425]
Module Neptune.dll [API v.050206]
VSOP87(B) Neptune: Precision 1e-006, Terms 391/2024
Module Triton.dll [API v.060425]
Finished initialising world
>>> ERROR: Could not load vessel module:
>>>        [C:\Source\Orbiter\Vessel.cpp / 4982]
>>> ERROR: Mir2
>>>        [C:\Source\Orbiter\Vessel.cpp / 4983]
Module URMS.dll [API v.060425]
>>> ERROR: Missing texture: extremite1.dds
>>>        [C:\Source\Orbiter\Texture.cpp / 781]
Module Spacecraft3.dll [API v.050206]
>>> ERROR: Missing texture: cover.dds
>>>        [C:\Source\Orbiter\Texture.cpp / 781]
Module blc1arms.dll [API v.060425]
Module multistage2.dll [API v.050206]
>>> ERROR: Missing texture: M_soyuz_tma.dds
>>>        [C:\Source\Orbiter\Texture.cpp / 781]
>>> ERROR: Missing texture: M_soyuz_tma.dds
>>>        [C:\Source\Orbiter\Texture.cpp / 781]
>>> ERROR: Missing texture: M_soyuz_tma.dds
>>>        [C:\Source\Orbiter\Texture.cpp / 781]
>>> ERROR: Missing texture: M_soyuz_tma.dds
>>>        [C:\Source\Orbiter\Texture.cpp / 781]

I have installed all the addons in the PDF - what can I do?? I need to fly today.

Thanks.

 

[Kveldulf]

Mir2 is part of Energia, so make sure you have that installed. Everything else looks like its Progress. Make sure you have the correct version used in the SCN file.

 

[clickypens]

For my mission, I'm gonna use the scenario posted by George to fly down the HL20. Exams start next week, so I may be a little strapped for time this weekend, but I'll get it done probably tomorrow afternoon.

 

[Tex]

Sounds good, thanks clickypens!

 

[radekpl]

I docked with Progress and I tried accelerate time. It seems that Progress will be full of wastes earliest after new year. After this. Progress will undock automatically. I will fly today new mission and I installed to my Shuttle fleet new PC with fuelMFD I will try to help filled Progress quickly.

 

[PhantomCruiser]

What is the secret to getting the module to latch to tex1? I know I've got to be within .3 meters of the attachment point, and I'm pretty sure I've got right up against it, but I can't attach via the MFD or the hotkey.

I've gotten MUCH closer than the second picture illustrates, but still no joy. I HAD to go to bed, so I'll have to wrap this up Sunday morning.

 

[lennartsmit]

I'm having the same problem as you Phantom. Whatever I do, it isn't docking.
Very frustrating!

 

[Nemoricus]

Same problem. Any ideas as to how to deal with this most vexing issue?

 

[PhantomCruiser]

I'm glad I'm not alone on this, thought it was something I'd done wrong for a while. If a solution pops up I can get it mounted, recover and post the .scn when I get home.

 

[Tex]

Unfortunately I don't have an answer for this other than using the scenario editor to dock it to tex1. Just position it close like you did then use the scenario editor interface to quickly dock it and carry on with the mission.

 

[PhantomCruiser]

I'll give that a try when I get home (about 4 hrs or so). If that doesn't pan out, what does the text look like in the .scn file.
I remember reading in the docs that the module latches to an attachment point rather than a dock. Would it read something like... ATTACHED 1:0,tex1 ?
Would type more, goota go to work.

 

[Tex]

I know for sure you can use the scenario editor to dock P3P4 to tex1.

 

[PhantomCruiser]

--Scratching head-- I've given that a try and the [DOCKING] button is greyed out so I can't select it (when the focus is on the P3P4), I tried it using tex1 as the focus and P3P4 isn't on the list of things to dock with...
If I can't figure it out by tomorrow (Monday) I'll leave the RMS arm holding it place, go ahead and undock to recover the XR-5. I'd be willing to let the tech-reps work on it.
Screenshots of what's gone on so far in just a few minutes.

 

[Nemoricus]

Try jettisoning the payload from the cargo bay before you grapple it with the RMS. That may be the cause of your problem.

---------- Post added at 11:50 AM ---------- Previous post was at 11:32 AM ----------

Nope, that doesn't work, sorry.

I'm going to look into editing the scenario file to do the attachment.

---------- Post added at 11:58 AM ---------- Previous post was at 11:50 AM ----------

I've found the problem. There are no defined docking ports for P34.

The XRpayload_OFSS_P34.cfg file needs the following:

BEGIN_DOCKLIST
0.022 0.425 -7.63    0 0 -1   0 1 0     ;dock to ISS
END_DOCKLIST

Add this anywhere in the configuration file.

 

[PhantomCruiser]

Shiny! Thanks dude, mission will be posted tomorrow morning. Screenshots to follow.

 

[Tex]

Ooops sorry guys! It worked for me, but now I am remembering that was before I had Woo send me that custom config so we could attach it to XR5. My bad! :embarrassed:


I assume you got it working? I will update the config and re-upload the package for the others wanting to fly this mission on their own.


EDIT - Package updated on Orbithangar, thanks for the fix Nemoricus.

 

[PhantomCruiser]

It's all good, before I left for work I had attached the module, extended the panels and enabled sun-tracking. When I get home in the morning I'll recover the XR-5 and you'll have the .scn shortly after.

 

[Tex]

Sounds good, thanks for your efforts to do it right PhantomCruiser.

 

[Nemoricus]

EDIT - Package updated on Orbithangar, thanks for the fix Nemoricus.

Not a problem. This issue was vexing me, too, so I had to figure out a solution somehow.

Anyways, I'm looking forward to my mission and wish everyone else the best of luck on theirs.