OFSS Project Discussions

[Tex]

It seems to have been a bit glossed over, but what exactly is the story with crew on this station? In particular, the absence of any escape vehicle stationed on a permanent basis is worrisome, if there is in fact a permanent crew. In building my station, an XR2 was docked 24/7 ever since assembly progressed to the stage where a permanent crew was needed.

So, is there a permanent crew aboard this station yet? After my mission next week, there will be a permanent escape vehicle docked to the station, but as of yet, there isn't one. It's questionable to have a crew up there without a means of quick return to Earth.

Well, right now that I know of, we don't have a vessel on station capable of holding crew. This will change once the DG4 is on station. The crew will be rotated from the next DG4 flight. So you will be flying up the first DG4 to be left on station. I think to be fair, you should be the one to bring it back down after the next DG4 mission launches. The pilot of that DG4 would then bring it down after the following DG4 mission launches, etc. Once the station gets a little bigger maybe we can consider adding more escape vehicles. Also remember we will have Esastar going to the station in the near future which can hold more people. At that point maybe we can add another DG4 or possibly CTV or something else.

 

[Tex]

Could I sign up for the January 11th, mission 35? I got to do something really cool by hauling up the first of the solar panels, so I'm more than happy to be a delivery boy on a second trip.

Got you scheduled. :thumbup:

 

[Tex]

The following missions are still available:

Mission 22
Mission 26
Mission 31
Mission 34
Mission 35

http://www.orbiter-forum.com/calendar.php?c=2

 

[Shadow Addict]

I'll do Mission 22 now that I have a bit of experience with the shuttle.

 

[radekpl]

I would like Mission 34. Shuttle fleet is perfect to me. I can fly without autopilot.

 

[Tex]

This is quoted from the pilot briefing room thread...

i had this idea while planing my station but i haven't tried it yet.

we could give the PMA (or any other config or spacecraft vessel) ridiculous hight ISP and "cheat" ourselves a gyroscope

Oceanic: I am at a loss with something like this. Would you or someone else be willing to help me find a better solution here. The station is growing in mass rapidly so we'll have to figure something out fairly soon I suspect.

Many thanks for any help you can provide.

 

[Adelanthal]

Wouldn't Zoe work for this? I've run the retrograde autopilot literally from the time of liftoff to landing of the the Shuttle and, if I remember to drop the time skip rate during freezing glitches, still have a mostly full tank. Does anyone else have this experience?

 

[Tex]

I'm having yet another problem with XR5 attachments. The next mission is scheduled for today and I can't get it working at the moment.

Using the XR5 Payload config made for Mustard's solar panels, it only works if the docking port is removed from the config file. If you'll remember we got it attached to the XR5 last time, but PhantomCruiser reported he couldn't get it docked to the station until we added the docking port to the config file. Now for the next mission it appears it will not attach to the XR5 unless the docking port is removed from the config file.

If anyone can help me I would greatly appreciate it. The config file and scenario are included below. Note, this scenario is not yet completed, so please only download it to help me troubleshoot this issue. The finished scenario will be released with the full package as usual.

 

[Woo482]

I think I've fixed the Solar Panels XR5 payload file. do you want me to send them to you ?

 

[PhantomCruiser]

I've got "A" solution, but it may not be "THE" solution...
I added the following to the mbr_its34.cfg file, then copied it to the .cfg directory under the vessels subdirectory. I was able to add the panels to into the XR-5 payload bay via the payload manager [ALT]. I tested it out by flying up to the station, but I did have to use the scenario editor to attach it to the tex.


XRPayloadEnabled = true
Description = ITS3/4
AttachmentPointIndex = 5
VesselsWithExplicitAttachmentSlotsDefined = XR5Vanguard
XR5Vanguard_ExplicitAttachmentSlots = 28

 

[radekpl]

I did not tested yet, but only idea. (I am at work now)
To use this add-on [ame="http://www.orbithangar.com/searchid.php?ID=3262"]Universal Cargo Deck, release 4[/ame]
I know it is new add-on to need for missions, but maybe it will solve the problem.
I will try to test it after work and I will write here is it ok or not.

Radek

 

[Tex]

I've tried UCD twice before and both times I had a center of gravity problem.

 

[radekpl]

hehe I solved your problem
You made mistake.

; === Configuration file for vessel class XR5 P34 payload ===
ClassName = mbr_its34
Module = MBR_ITS/mbr_its34
Size = 34.00
Mass = 15838 ; empty mass [kg]

;----------------------------------------------------
; XR Payload custom parameters
;----------------------------------------------------

; must be set to 'true' for this vessel to be dockable in an XR-class payload bay.
XRPayloadEnabled = true

; cosmetic description; 127 chars MAX., but 40 chars or less recommended
Description = ITS 3/4 .cfg payload for XR5
; Dimensions in meters: X (width) Y (height) Z(length).  This also determines how many standard payload slots are occupied.  
Dimensions = 3 3 8

; attachment point index (0-n) that should be used for grappling in the bay; default=0
AttachmentPointIndex = 0

; === Attachment specs ===
; NOTE: a payload object's attachment point should be set for the CENTER of the bay slot into which it is 
; attached.  Each standard slot is exactly 2.4384 wide (X), 2.5908 high (Y), 6.096 long (Z).  Some XR-class
; ships, such as the XR5 Vanguard, have some slots that are wider as well.
; WARNING: attachment *direction* must be (0 1 0) and attachment *rotation* must be (0 0 1)!  The bay 
; collision detection code expects this.

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

BEGIN_ATTACHMENT
P 0.0 1.15 0.0  0 1 0  0 0 1  XRCARGO
END_ATTACHMENT

Docklist must be before Attachmentlist
But wait little, I will try to update Tex1 config and MCT config. Because dock 1 and 2 seem not good with these solar panels.

tex1OFSS.cfg

; === Configuration file for Tex1 ===

Meshname = tex1
Mass = 1.5e3
Size = 6.0

; === Docking ports ===
BEGIN_DOCKLIST
-0.05 0  5.54  0 0 1   0 -1 0
-0.05 0 -5.54  0 0 -1  0 -1 0
0.1 -1.2 3.45  0 -1 0  0 0 1 
0.1 -1.2 -3.35 0 -1 0  0 0 1
END_DOCKLIST

; === Attachment specs ===
BEGIN_ATTACHMENT
P -0.3 0 0  -1 0 0  0 0 1 XS
P 1.25 -0.85 0   1 0 0  0 0 -1 GS
END_ATTACHMENT

mctOFSS.cfg

; === Configuration file for MCT ===

Meshname = mct
Mass = 2e3
Size = 6.0


; === Docking ports ===
BEGIN_DOCKLIST
0.4 -0.08 5.5   0 0 1   0 -1 0
0.4 -0.08 -5.5  0 0 -1   0 -1 0
-0.94 0 0  -1 0 0  0 1 0
END_DOCKLIST

; === Attachment specs ===
BEGIN_ATTACHMENT
P -0.3 0 0  -1 0 0  0 0 1 XS
P 1.7 -0.9 0   1 0 0  0 0 -1 GS
END_ATTACHMENT

 

[Tex]

Thanks radekpl,

I tried both ways and it failed. Good news, thanks to Woo482's help we were able to get it working another way. Mission 20 package will be released shortly.

 

[Woo482]

I'm always happy to help when ever I can

 

[radekpl]

Hmm I tried my way and it works on my PC

But changes in config file for Tex1 and MCT are great and should be implemented for better visual enjoyment.

But is up to you. You are leader

 

[Tex]

Thanks radekpl, I just needed to get this mission out as we're behind a day now. I'll try your changes for tex1 and mct for the next mission.

 

[lennartsmit]

I'll fly this mission tomorow.

 

[Tex]

Ok, the following missions are still available. Is there anyone left who hasn't flown yet and isn't already scheduled to fly an upcoming mission?

Mission 26
Mission 31

 

[Adelanthal]

Okay, was wondering if this is specific to me, or if this is a problem others have seen:
Pulled the OFSS mission package, installed with replacing all files in the package, and then launch OFSS Mission 21. Every time I jump to the HUD display for RMS-1, I get a CTD. Problem recurs even after reboots. I get the following errors in the Orbiter.log:
>>> ERROR: Missing texture: extremite1.dds
>>> [C:\Source\Orbiter\Texture.cpp / 781]
>>> ERROR: Missing texture: cover.dds
>>> [C:\Source\Orbiter\Texture.cpp / 781]
**** WARNING: Mesh not found: .\Meshes\.msh
**** WARNING: Mesh not found: .\Meshes\.msh
**** WARNING: Mesh not found: .\Meshes\.msh
What am I screwing up?