Space Shuttle Ultra development thread

I know we should. Can we ? :)

Not sure, if we can. I would say yes, we can limit the difference between commanded roll rate and current roll rate to something, the shuttle can achieve in reasonable time.
 
Last edited by a moderator:
Hopefully SC can take one last look at the roll program and fix it. :)
 
Hopefully SC can take one last look at the roll program and fix it. :)

Would not only be useful for roll program, such calculations are also useful for other autopilots.
 
At the moment, the roll program has a constant roll rate (set to 12 deg/sec at the moment).

I think the main problem is with the engine gimbal control. The gimbal control sets the deflection (in the X and Y axes) from the normal position based on the difference between command and actual rates. The deflection is proportional to the error. In the original version, the gains were far too high, which caused consistent overcorrection (and the wiggle). Reducing the gains seems to have fixed the SSME overcorrection; I'll fidget a bit more and see if I can stop the SRB problems.
 
Don't you now use PID-T1 controllers like the real one?
 
The PIDControl class is only used for the OMS TVC at the moment; I haven't converted the SSME/SRB gimballing to use it yet.
 
How is this bug coming ?
 
Could LOD capability, say seven levels be possible in a future release ?
 
Could LOD capability, say seven levels be possible in a future release ?

We can do this already in SSU 1.26 if you want to. I have some code here, which might be useful for generic LOD handling (kD-Trees for large amounts of objects).

But I think, seven levels is too much. Three levels would already be great. If we reduce the numbers of polygons by 4 in each step, we would get a 8000 poly mesh down to 125 poly in the final iteration.

Also, my current favorite "arc" for the next release is finishing the Deorbit/Entry/Landing phase, after we have dealt with the launch in the current one.
 
Also, my current favorite "arc" for the next release is finishing the Deorbit/Entry/Landing phase, after we have dealt with the launch in the current one.
I agree.
 
Do you think three would be enough, for backing away from the ISS, without seeing a noticable transition ?
 
Do you think three would be enough, for backing away from the ISS, without seeing a noticable transition ?

Depends on where you want to save polygons and how large the distance for transition is.
 
What is Space shuttle Ultra and where can i have a taste of it ?

Moderator note: Moved this support request out of the 1.25 development thread.
 
Last edited by a moderator:
What is Space shuttle Ultra and where can i have a taste of it ?

Space Shuttle Ultra is a project to create an accurate and detailed simulation of the space shuttle and it's subsystems.

[ame="http://www.orbithangar.com/searchid.php?ID=3169"]Space Shuttle Ultra V1.06[/ame]
 
checked in updated ODSVC panel without affecting animations. I made the toggles and switch guards look better.
 
Found a bug with the RMS saving: if you close a scenario which contains the RMS and open the CurrentState scenario, the RMS will have disappeared.

This occurs because the RMS is only created by the Atlantis class if the line "RMS" appears in the scenario; however, the subsystem saving code saves this line within the RMS section of the scenario, so the RMS is never created. A similar problem will occur with the OBSS MPMs.

---------- Post added at 10:37 PM ---------- Previous post was at 09:44 PM ----------

There's something wrong with the subsystem loading code. All of the subsystem blocks in the scenario are being skipped when the scenario is loaded.

---------- Post added at 11:24 PM ---------- Previous post was at 10:37 PM ----------

The RMS-specific problems should be fixed now. The general subsystem saving code still doesn't work, though.

---------- Post added at 11:32 PM ---------- Previous post was at 11:24 PM ----------

Fixed the problems with the subsystem saving code.
 
Are the fixes in the release ?
 
Release on Orbithangar has not been updated. Since there are quite a few bug reports/problems, I think the best thing to do is get all of these cleared up, then update the file on Orbithangar.
 
Release on Orbithangar has not been updated. Since there are quite a few bug reports/problems, I think the best thing to do is get all of these cleared up, then update the file on Orbithangar.

Yes, but maybe we can at least release a module patch ASAP, for gathering further bugs.
 
I'm getting "Main engine 3 failure" on every attempt to launch. What is wrong? Even I can't launch during missions flown before. Completely don't know where I made mistake. Sources have been compiled 7th August. At T-6.6, there is no ignition, and at T-0 I'm getting this info about failure.
 
Last edited:
Back
Top