SSU V1.25 Release

Status
Not open for further replies.
This is the same joke as the one in the threads "When comes the new orbiter version?".
:rofl:

---------- Post added at 06:21 PM ---------- Previous post was at 06:10 PM ----------

Have you got an rough release date?
I mean not the tuesday joke.;)
 
Last edited:
I'm working on using the RCS thruster controls for RMS translation. Is it realistic to set DiscLines to a negative value?
 
I'm working on using the RCS thruster controls for RMS translation. Is it realistic to set DiscLines to a negative value?

In terms of software yes, the discrete lines are just logical lines - for implementing analog values it is always assuming the difference between a reference voltage and the signal voltage - negative values are indeed possible, but you should be aware, that you can't use the digital functions (IsSet, for example) in such a case.
 
I'm using the lines just to get the RMS RHC/THC imput, so all I need is a value between 1 and -1.
I'm planning to use the thruster input to control the RMS from the RMS Station and RMS camera positions, and use the thruster input for attitude control from all other positions. Does anyone think this could cause problems?
 
Better use -5 to +5, this would then better correspond to the values displayed in the related DPS display.
 
Code has been checked in. RMS translation can now be controlled using the RCS translation controls.

---------- Post added at 07:15 PM ---------- Previous post was at 06:06 PM ----------

Does anyone know the default max rotation rate for the RMS EE rotation? For PL ID 0 (OBSS berth/unberth) it's 0.88 deg/sec, but I couldn't find the value for PL ID ), the default ref. frame.
 
Just tested the new RMS capability and it's very, very nice! Now we just need to do the same for rotational control and we have a winner RMS!
 
could the switch (keypad /) be used like the RCS jets ?
 
Just did a more intensive test of the RMS capability and movement is very, very good and smooth.

Only issue is a VC++ Runtime error message when exiting the scenario.
 
Does the runtime error occur when you run a scenario without the RMS and MPMs?
 
Does the runtime error occur when you run a scenario without the RMS and MPMs?
Source have been identified as CRTMFD. If I have it activated, I get the Runtime error message upon exiting. But if I don't have it activated, no error message upon exiting.
 
Try recompiling the modules, in case the linking got messed up. AFAIK, the CRT MFD code hasn't been changed in a while, so it shouldn't suddenly be causing errors.
 
Try recompiling the modules, in case the linking got messed up. AFAIK, the CRT MFD code hasn't been changed in a while, so it shouldn't suddenly be causing errors.
That did it. Error message is gone.
 
Code for EE rotation has been checked in. I haven't added buttons to the RMS dialog for this, so the only way to control the rotation is using the RCS controls.
 
Could I ask a favor ? Could you remove the startracker info at the bottom left of the screen. I need to see the SC3 attachments, to do the 125 mission stuff.
 
Code for EE rotation has been checked in. I haven't added buttons to the RMS dialog for this, so the only way to control the rotation is using the RCS controls.
How do we use this? For me, the EE rotation controls doesn't seem to be working. Can't get the EE to move using the RCS controls, only with the RMS control dialog.
 
It should work the same way the translation controls do, except you need to be in rotation mode instead of translation.
There seem to be a few problems with the yaw movement, which may be why you're having problems. The pitch motion seems to work, though.
 
It should work the same way the translation controls do, except you need to be in rotation mode instead of translation.
There seem to be a few problems with the yaw movement, which may be why you're having problems. The pitch motion seems to work, though.
Just to confirm: When you command EE pitch down, only the EE is supposed to pitch down right? No other joints?

---------- Post added at 04:58 PM ---------- Previous post was at 04:53 PM ----------

And a bug to report, related to my earlier report about the Runtime error upon exiting.

Seems like I was wrong about pointing out CRTMFD as the source. After some troubleshooting I have found that the Runtime error message seems to be linked to the saving of the A8 panel states.

I remember reading that the new rotary switch implementations were a little bit rough, so could this be the source?

---------- Post added at 05:24 PM ---------- Previous post was at 04:58 PM ----------

Another bug: I don't have any control over the RCS! So manuevering the orbiter is impossible, unless you use the Scenario Editor.
 
Just to confirm: When you command EE pitch down, only the EE is supposed to pitch down right? No other joints?

---------- Post added at 04:58 PM ---------- Previous post was at 04:53 PM ----------

And a bug to report, related to my earlier report about the Runtime error upon exiting.

Seems like I was wrong about pointing out CRTMFD as the source. After some troubleshooting I have found that the Runtime error message seems to be linked to the saving of the A8 panel states.

I remember reading that the new rotary switch implementations were a little bit rough, so could this be the source?

---------- Post added at 05:24 PM ---------- Previous post was at 04:58 PM ----------

Another bug: I don't have any control over the RCS! So manuevering the orbiter is impossible, unless you use the Scenario Editor.
The EE rotations use inverse kinematics; the grapple point will stay at a fixed point, but the direction will change. As a result, multiple joint angles will change.

I'm not sure what would be causing the runtime errors; I'll take a look at this.

The RCS seems to work for me. The RCS can't be controlled from the RMS station, since this position uses the RCS input to control the RMS. The RCS can be controlled from all other cockpit views.

---------- Post added at 12:20 PM ---------- Previous post was at 12:15 PM ----------

DaveS: After you get the runtime errors, can you post whatever has been written to the Current State scenario?
 
Status
Not open for further replies.
Back
Top