Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
ORBITER-FORUM will be temporarily closed at 2026-07-23 18:00 UTC while we complete some OF maintenance tasks. The amount of downtime is expected to take up to one hour, but probably less.
Which scenario are you loading? Which NASSP version?
Also the latest commit didn't change Apollo 11 LM checklists so I am a little confused.
EDIT: Looks like it was a previous commit changes causing the crash, I will see if I can resolve it
That makes absolutely no sense, you should have all the deployables regardless of the install. Again on your save you had everything deployed.
@Tiny_Bob I am going to ping you on this one
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.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.