riclourenco
Donator
Nice! thanks!
Discussion NASSP Orbiter 2024 Compatibility Thread
- Thread starter CaptainSwag101
- Start date
riclourenco
Donator
Hi,
I've already completed my first mission on Orbiter 2024 (I chose Apollo 8). After the splashdown, I noticed that ALT + R key, to place the astronauts in the boat, doesn't work. Will this also happen on the lunar surface with the flag placement and with the EASEP experiments in relation to the "K" key? Going to 11 soon! Are there any alternative keys in O2024?
I've already completed my first mission on Orbiter 2024 (I chose Apollo 8). After the splashdown, I noticed that ALT + R key, to place the astronauts in the boat, doesn't work. Will this also happen on the lunar surface with the flag placement and with the EASEP experiments in relation to the "K" key? Going to 11 soon! Are there any alternative keys in O2024?
rcflyinghokie
LM Junky
All of those keybinds work on O24. Are you using a US keyboard?
riclourenco
Donator
Hi. No, I am using a Portuguese Keyboard. It seems to be linked to another function. Alt + R shows me the FPS in the upper right corner of O24 screen. Alt+R worked fine in O2016B.
Last edited:
rcflyinghokie
LM Junky
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)
riclourenco
Donator
I've already discovered the issue, and it might eventually become a problem for others. It has nothing to do with the keyboard being US, PT, or another. It's related to the NVIDIA APP. This app has some shortcuts, and one of them is ALT Left + R, which turns the FPS display on and off in the upper right corner of the screen. For some reason, this shortcut continues to work while the O24 is running, inhibiting ALT L + R for NASSP. This doesn't happen on the O2016B. I have no idea why. The solution is simple. For those who have the NVIDIA APP and are experiencing this problem, all you have to do is go to the NVIDIA APP settings and remove the ALT L + R shortcut, or assign other keys to the FPS function. You can open the app settings with ALT+Z.
rcflyinghokie
LM Junky
I have the nvidia app but never have run into this
riclourenco
Donator
It's strange, but it happens to me. Anyway, I don't usually use that function in the NVIDIA app, and as long as the problem is solved, it's fine by me. By the way, I wanted to ask a question. It's about the NONESS BUS on the right panel of the CSM. In the checklist, it was always turned on when we were going to do an SPS burn, and turned off when the burn finished. This procedure was removed in Apollo 11 and 12, and the NONESS BUS is now always on since launch. Is there any reason for this? Is it supposed to always be on? The old procedure still exists in Apollo 8.
rcflyinghokie
LM Junky
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.
riclourenco
Donator
Hi, I just landed on Apollo 11 a short while ago, and the only objects I managed to get on the surface were the flag with the "F" key and the drill with the "K" key. I can't deploy any other EASEP experiments, either with Armstrong or Aldrin. Any solution for this?
rcflyinghokie
LM Junky
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.
Similar threads
