Search results

Magellan would be a great example of that as the solar arrays were deployed prior to the IUS SRM-1 burn and the same would have been true if the original plan to launch it on a Centaur G on STS-81I would have held.

Not just upper stages but other payloads as well, like the HST Space Support Equipment (SSE), which is the various carriers as well as the Flight Support System (FSS). All of that was controlled through Standard Switch Panels.

Speaking of SPARTAN; I've had this one laying around forever, should I finish it?

X-52? Then see this thread: https://www.orbiter-forum.com/threads/logitech-x52.42182/

OPS 801 PRO.

OPS8 has all of the pre-entry checkout stuff. Just execute the FCS CHECKOUT steps in the generic Orbit Ops FDF (page 7-13), just skip the SECONDARY ACTUATOR CHECK (APU) on 7-17 and go directly to step 6, APU SHUTDOWN and then head back to OPS2 to regain the DAP.

No. The MECO altitude is always less than your OMS-2 altitude as OMS-2 is meant to circularize the orbit, to lift the perigee out of the atmosphere and prevent an early entry. Remember, initial ascent trajectory is sub-orbital to ensure that the massive ET doesn't fall in populated areas. Hence...

MECO altitude is altitude where MECO occurs, MECO Target Altitude is the target altitude of OMS-2.

Discovery in roll after lift-off from LC-39B for STS-31.

Maybe you could add a comment to this issue on Github: https://github.com/orbitersim/orbiter/issues/381

GLS: While you're doing ground stuff, could you deactivate GVA venting at T-4 minutes instead of being coincident with GVA hood retraction as that's when venting from the ET LOX vents stopped as LOX Drainback was initiated.

Level 16 by default, Earth is level 19 with the high resolution package.

Yes, everything is calculated relative to the sun so once you get far enough away from it, the precision of the engine just collapses as it is in the end just a double precision floating point integer number. Eventually the numbers get so big that things like docking becomes impossible due to...

Can someone please take another go at this issue: https://github.com/orbitersim/orbiter/issues/382 I have hit a bit of roadblock thanks to no information whatsoever when trying to troubleshoot a CTD issue involving a base cfg file. This is is the verbose log file output: *** Orbiter.log...

Another sun issue. The solar disc is not hidden by base meshes as shown in the attached screenshot. The rays are hidden as expected but the disc is still visible when it should be hidden.

Is there a upper limit to the number of metalness textures that a single vessel can use? I've attached a screenshot showing the problem. Despite the radiator panels and Ku band antenna having properly made metal and roughness textures, they're not rendered. Other textures that also have metal...

Yes, remove all the files it created, and extract them into a temporary folder and then run the Setup.exe file in that folder.

No. ISS remains in its normal LVLH attitude until capture is sensed. Just follow the Rendezvous checklist and you will be fine.

Try installing this: https://www.microsoft.com/en-us/download/details.aspx?id=8109

In that case, it's already possible. This is from the Lua implementation of the default Atlantis: function define_animations() local midx = 1 -- mesh index for all external animations local vidx = 2 -- mesh index for all VC animations -- ***** 1. Cargo door and radiator animations...