Ok, try opening ME, Ctrl-N, to create a new STS-101, save it, and then export a T-31s scenario of that, and check what happens please.
Aha! It works when I do it that way, without changing anything else.
Ok, try opening ME, Ctrl-N, to create a new STS-101, save it, and then export a T-31s scenario of that, and check what happens please.
Hmm, I was expecting that not to work due to some "comma vs dot" issue... better this way.Aha! It works when I do it that way, without changing anything else.
Hmm, I was expecting that not to work due to some "comma vs dot" issue... better this way.
I was looking at the LCC code, and I might have found the issue. Could you go back to your 41G mission, and change the launch time by 1 second please?
The current launch time logic might be sensitive to rounding and the first frame of the sim could be T-30.99s or so, and the would mean the "LPS Go For Auto Sequence Start" command never gets issued. I went back to your log and, sure enough, the related log entry is missing (I missed this the first time looking at the log ).
I meant the launch time itself, in the Launch tab. Don't lose sleep over a 1s difference in launch time, as Orbiter is not using UTC, so there is already a difference of 50s or so in the 1980s.I tried removing one second in the scenario export page, but that still gives a T-31second start point in the sim, so I manually removed 1 second from the 41G scenario's MJD and that made it start at T-32 seconds in the sim...and the problem did not occur.
I meant the launch time itself, in the Launch tab. Don't lose sleep over a 1s difference in launch time, as Orbiter is not using UTC, so there is already a difference of 50s or so in the 1980s.
BTW: could you post the (troublesome) launch time you input into ME, so I can then confirm this issue gets fixed?
For now (v1.8) I'll change the LCC so there is less chance, or hopefully none, of falling into this hole again. Eventually (v2.0) I'll change the start time to T-40s or so (somewhere where no commands are issued) to avoid this entirely.
Only something? That is why I'm reworking all of that.there's something wrong with the RCS currently
Turning it slowly is what I am trying to do, but due to the deadzone it is pvery difficult to establish and maintain <2°/s rate as you end up overshooting it and up with a 3°/s or more rate. It is good to read that this will be taken care of. On the same subject, I have found that a 2.0 value for RHCRate in SSV_OV.cfg is a pretty good value for a proper RHC response rate simulation through the keyboard.Only something? That is why I'm reworking all of that.
This problem seems to be more related to the OrbitDAP (which should also see some improvements as it will have to adapt to the new RCS). Maybe the RHC deadbands are wrong, and the "no fire area" is larger than it should be, or maybe that is OK and it is just the way it works, as the vehicle was usually turned by the DAP and slowly.
Hi there!Hi, GLS, Why does the Crawler Transporter could not stop at the point of the docking height (3 feet), and could not attaching to the MLP ?
I could but it would take a LONG time, so the effort/reward ratio isn't that good. I remember there are a few pistons "on the inside" that are not animated, and should be easy to do, but I haven't got to them yet.Another quest is if you can make the track animation of the Crawler Transporter ?
Try the "MLP roll-off" scenario, go up the pad slowly and check the LDS as you move left and right, to get the gray bar centered. The 2 modes you need are the G CIRC, which turns the CT left of right, and the CRAB mode which basically shifts the CT to the side, without turning it, so keeping the orientation to a target.I think that GLS's Crawler Transporter mod is much better than allof the others, I expect to see the CT jacking the space shuttle to move , but it is too difficult to do that .
The STS-93 IUS Deploy Checklist should be available somewhere on the internet... but lots of switches don't work yet, so maybe I should make a simple checklist.Does anyone have the IUS deployment checklist, I looked everywhere and in the manual the section is blank.
If I remember correctly, Cab 3 is the one towards the pads, and Cab 1 is towards the VAB. There is a switch in the LDS display that controls which position it shows, so you don't have to change cabs. With that you can see where each end is in relation to the target. For fine lateral control, putting the Mode push button in +-2º, is very useful as it cuts the steering commands by a third.Hi ,GLS , I have tried to use scneditor to get the gray bar centered ,but I don't know where is the correct point of the foward or behind
It should be that 2.91 position. Currently the jacking is controlled by switching between pre-defined target positions, which be all the needed positions.and another problem is that I couldn't control the jacking to stop ,it always auto stop at 2.91 feet ,so I couldn't know if this is the correct point of the docking height?