Search results

No, ISS live downlinks have existed for quite a while: Standard Definition, with Space/Ground audio: High Definition, sans Space/Ground audio:

I ripped the orbiter ac sound from this video of the immediate post-landing activities and subsequent tow to OPF-1 after STS-132:

New Glenn doesn't have an RTLS profile st this time, only a downrange barge landing, the entry burn is where they lost the stage on the first launch.

Actually, having the xenon lights for the rollout was the exception not the rule.

Also, the spacing between the different carriers are incorrect. The SAC for example is located too much aft and too close to the ORUC and the FSS is located too far aft.

Noticed that STS-61 is flying extra mass in the form of the Multi Use Lightweight Equipment (MULE) carrier. The MULE was first used as HST Space Support Equipment (SSE) on STS-109/SM3B in March 2002. STS-61 only flew the Solar Array Carrier (SAC), the Orbital Replacement Unit Carrier (ORUC) and...

Pad vessel animations are controlled by a dialog window accessed by selecting the appropriate pad vessel (either LC39x or SLC-6) and pressing Ctrl-Spacebar.

Limit is 8, but by default it's set to 4. You can change this by clicking on the Advanced button on the Video tab.

All launches up to and but not including STS-6 used SWTs. STS-7 was the last SWT to be used. Although, STS-6 was the first ET with the LOX Anti-geyser Line removed and substituted with Direct Helium Injection and the GH2 pressurization line moved to where the LOX Anti-geyser Line used be, next...

https://en.wikipedia.org/wiki/Moir%C3%A9_pattern

It is exactly what is says there: Alt-Tab is not support in True Full Screen mode. Not a bug or a problem.

The idea now that Orbiter 2024 has been pushed out is to retire the DX7 version completely, so no more Orbiter.exe with a built in graphics engine. Right now it looks like D3D9Client is here to stay, so on Windows machines, it will become the de facto standard engine. To run D3D9Client, you need...

You need to run Orbiter_NG.exe in order to use D3D9Client. Orbiter.exe only supports the built in DX7 engine.

During ascent, the term TMECO was used but that was not a countdown timer but rather an indicator of when guidance predicted MECO would be at. It being stable for the first few seconds of second stage ascent indicated that the guidance had converged on a solution and was good to the crew and...

So going forward, what is the plan for D3D9Client? Keep it and continue improving things since we should not be bound to the old DX7 client anymore or go with something newer like DX12?

NASA uses the term TGO for Time to Go, at least during the burns.

In this case, I would propose putting the various methods through a simple, yet effective test: Create a bunch of VMs that do not have anything beyond what the O/S itself provides and then see how fast you can get the proper binaries outputted. By doing this test, you will eventually parry...

Did you resave the mission file after changing it?

There's no need to "reuse meshes" as SSV implements the DFI wiring natively by checking the "DFI Wiring Tray" checkbox on the ORBITER tab of the SSV Mission Editor. At the same time, make sure that the EDO Kit" checkbox on the CONSUMABLES tab is unchecked.

The DFI (not "DEFI") pallet always had IECM pallet, even on STS-1 as the original plan was fly it on that mission. But due to development and certification delays with both the RMS and the IECM, both were left off for STS-1 and the DFI pallet flew solo.