Search results

Still not quite following, the non j mission alpha is the main branch with the experimental features listed in the release and the j mission alpha is that plus the SIM bay and J mission consumable edits.

Not sure what you are asking, for the O24 builds there are only 3 options, the base version the alpha and the J mission alpha. You should not be mixing a j mission install with a non j mission install, they need to be their own clean installs, since dragging and dropping doesnt remove files...

Well the save file has the touchdown points from the bad install saved, and you have everything deployed, so you will have to deal with them not being at the correct visual elevations unless you go back to a save before deploying everything

Sounds good, feel free to reach out if you need help or have questions as usual. Also consider joining our discord channel its usually quite active with users and developers! https://discord.gg/9PnBbt38U2

Different texture installs is likely why, the surface height being different in the landing site textures between different installs. And if the rover appeared you had a J mission branch installed, which is not to be used with Apollo 14 or earlier.

All the EASEP ALSEPs are on all the current branches. A J mission branch should be installed on its own unless you are building from source, copying that into an orbiter install then copying a non j mission branch can leave a lot of artifact files. You also should not be using a j mission...

If they differ on the laptop and desktop installs you might have messed up the texture install on the desktop, maybe try a fresh install? Also are you using the landing site textures from the links in the QSG on either install?

When I load your save everything is deployed. Which textures files did you install when you installed O24? It might be an issue with that. They all seem floating for me, so that tells me your surface textures and mine differ for some reason.

do you have a save where its not working? if one item deployed the others certainly should

The items and order deployed by the CDR and LMP are in the guide, they are a specific order by each crewmember on the surface listed in there.

So the CDR and LMP both have a deploy order shown in the document above. Which build are you on?

Current information now found in https://www.orbiter-forum.com/threads/nassp-installation-information.43603/

Keyboard commands now found in https://www.orbiter-forum.com/threads/nassp-installation-information.43603/

Attached to this thread is the current Quick Start Guide for NASSP. It explains NASSP 8/Orbiter 2016 beta installation and NASSP 9/Orbiter 2024 and OpenOrbiter installations. It also contains a bunch of useful tips and tricks and the NASSP keybinds. Last Updated: 1 JUN 2026

Probably best to move this to another thread as its unrelated to compatibility at this point. Ping me in a new thread and we will see what's up.

The nonessential bus powered scientific equipment outlets and on 8 it powered the flight qualification instrumentation as well, so the NONESS buss was powered up for SPS burns to record qualification data.

All of these settings are listed in the quick start guide FYSA

I have the nvidia app but never have run into this

All I can tell you is the keyboard commands in the QSG all work in O24/OO on a US keyboard for certain. Left Alt + R does the crew recovery for me (with the hatch open, of course)

All of those keybinds work on O24. Are you using a US keyboard?