Orbiter Video Thread

[Tex]

Orbiter Baseland Demo - YouTube

This is awesome. Thanks for your work on this. I shared your video on my Twitter - I'm sure others will be interested in seeing these capabilities.

 

[Tex]

Orbiter 2016 - Live Stream #2 goes live Sunday, Aug 20th @ 3pm EST / 19:00 UTC!

http://youtube.com/user/texfilms/live

 

[Tex]

Thanks for coming by the live stream guys! Sorry the chat seemed to LAG, so I missed some of your comments. It was fun today!

 

[IronRain]

Ahw missed it
More planned?

 

[marcogavazzeni]

Zoomed universe :ninja:

Windows Movie Maker
Space Engine
Orbiter 2016
ASVI base
Deltaglider

 

[Wolf]

Nice :thumbup:
It looks you used another sim for the first part of the video, am I wrong here?

 

[marcogavazzeni]

Nice :thumbup:
It looks you used another sim for the first part of the video, am I wrong here?

http://spaceengine.org/

 

[Wolf]

Wow, huge improvements since the last time I checked it. Great video

 

[marcogavazzeni]

Neptune launch

 

[boogabooga]

What's with the floating box?

 

[Pioneer]

What's with the floating box?

It's a monolith

 

[PhantomCruiser]

Should be 1x4x9? :shrug:

 

[Tex]

 

[jedidia]

Should be 1x4x9? :shrug:

Why stop at 3 dimensions?

 

[PhantomCruiser]

Those are the dimensions that are readily apparent

 

[indy91]

A short video with NASSP and the AGC emulator showing the Apollo 14 procedure that was used to prevent an abort caused by their faulty abort button. It also shows what happens when you don't use the procedure and follow the nominal timeline for Powered Descent Initiation. Spoiler: the computer will start the abort maneuver at the instance of ignition.

For Apollo 15 and later the computer had a simple crew procedure for ignoring both of the abort buttons. This is just one of the fun things you can do with the flown AGC software!

 

[GLS]

Project Apollo NASSP 8.0 Alpha - Masking the Abort Discrete on Apollo 14 - YouTube

A short video with NASSP and the AGC emulator showing the Apollo 14 procedure that was used to prevent an abort caused by their faulty abort button. It also shows what happens when you don't use the procedure and follow the nominal timeline for Powered Descent Initiation. Spoiler: the computer will start the abort maneuver at the instance of ignition.

For Apollo 15 and later the computer had a simple crew procedure for ignoring both of the abort buttons. This is just one of the fun things you can do with the flown AGC software!

I'm not claiming I know the AGC, but I think you might have a problem. I remember reading that they changed to P71 for ignition... but you still have P63. I went and found this page which details this issue, and according to this part...

Fortunately, another path in the Abort Monitor Routine to close this window of vulnerability was found -- MODEREG: the Mode Register memory location that held the number of the program or "major mode" that was currently running. That register was accessed mainly for the PROG display on the DSKY, but was also checked by the Abort Monitor Routine in case P70 or P71 was already running. If an abort was the current major mode, there was no need to start a new one.

...the DSKY should be displaying P71.

 

[indy91]

I'm not claiming I know the AGC, but I think you might have a problem. I remember reading that they changed to P71 for ignition... but you still have P63. I went and found this page which details this issue, and according to this part...

...the DSKY should be displaying P71.

Good question. I had to do a bit of research before I found the answer.

First, changing the value of the mode register (MODREG, address 1010) in the erasable memory doesn't actually change the program that is running, so even if MODREG is 71, the AGC still runs all the routines for Program 63.

The reason for the DSKY still showing 63 is that the mode register doesn't get written to the DSKY every so often. When you change the program in the AGC with Verb 37 (e.g. V37E 63E) the routine first checks if the program number is valid (AGC doesn't actually have 99 different programs), then it writes the program number from the user input to MODREG and then once, just once, updates the program number that gets written to the DSKY. In the DSKY there are latching relays for every display, so if the computer never writes a new program number to the output channel for the DSKY again, which it doesn't in normal operation, then the "63" on the DSKY won't change.

There are a few ways to update the DSKY from the mode register again though. There is a verb to artificially cause a restart (Verb 69). If I use that then the DSKY gets an updated program number and it now says 71.

 

[Topper]

;-)

 

[martins]

Creative use of the hover engines, I like it! Do you do active terrain avoidance when coming over the foothills, or was it just lucky that nobody scraped their behinds on the hilltops? :lol: