Project Apollo - NASSP wow, it's tough!!!

[Messierhunter]

I have to say Tschachim, project apollo is truly an inspirational undertaking. One day, when I can afford it, have the time, and NASSP 7 is completed, I would love to build a simpit dedicated to NASSP's CM.

 

[SlyCoopersButt]

I just got this addon installed yesterday. It's an amazing work! Great job! But a Low-Res version of the Saturn would be nice if it's not too much trouble. I got an average fps of 3-4 per second with the rocket.

 

[FordPrefect]

Great job! But a Low-Res version of the Saturn would be nice if it's not too much trouble. I got an average fps of 3-4 per second with the rocket.

Orbiter Launchpad -> "Extra" tab -> Vessel configuration --> "Project Apollo Configuration" <-double click -> New Window-> "Visuals" tab -> Mesh resolution -> Low resolution -> click OK ...

 

[SlyCoopersButt]

Edit: For some reason the option won't stay where I put it. I still get the same hi-res model and when I go back to the launchpad and look, It's on high again.

 

[movieman]

I didn't use NASSP 6.4.3 since a loooong time, so I'm not sure, but at least according to some docu you can disable the autopilot by keying VERB 46 ENTER in the DSKY.

Yeah, that's in there and works. I've never tried it in the Virtual AGC, though I presume it's not wired up to the IU anyway.

As for which systems work, about a year ago I was quite impressed when I accidentally wired a short-circuit into the electrics and the DSKY lights started flashing on and off as the system overloaded and then briefly recovered as things went offline due to low voltage (then overloaded again as the systems came back online)...

Not sure why low-res isn't working, but you might want to check that it's not specified in the scenario file; in the early days we used to write the high-res/low-res value into there each time we exited Orbiter and it would override other settings.

 

[Tschachim]

joeybigO & Messierhunter: Thanks for your kind words. A CM simpit would be really cool indeed!

Edit: For some reason the option won't stay where I put it. I still get the same hi-res model and when I go back to the launchpad and look, It's on high again.

Sorry for the dumb question, but you close the Project Apollo Configuration window with the OK button (and not Cancel)? Additionally to what Movieman mentioned, you could also open the Config\ProjectApollo\Saturn5.launchpad.cfg file in a text editor and check if the LOWRES setting is 1.

If the problem doesn't go away feel free to post a new topic in our support forum, so we can discuss this problem in detail: http://www.ibiblio.org/mscorbit/mscforum/index.php?board=67.0

Cheers
Tschachim

 

[Urwumpe]

One more technical question: Is it possible to power down the IMU?

 

[Tschachim]

Yes, pull both IMU circuit brakers on panel 5 on the right side (the IMU POWER switch on panel 100 isn't wired yet, but will be very soon:blush. I should mention that only the Virtual AGC is using the IMU actually, the Simple AGC doesn't care. The power consumption and heating doesn't depend on the AGC implementation, of course.

Cheers
Tschachim

 

[Urwumpe]

Well, the problem I experience is, that I get a master alarm, when opening the circuit breakers, I suspect something is missing... but well. I actually only do it after landing for saving battery power, as I am too lazy for learning the checklists before the deorbit burn and so only fly the reentry scenarios. :blush:

 

[Tschachim]

Well, the problem I experience is, that I get a master alarm, when opening the circuit breakers, I suspect something is missing...

If you pull the IMU cb's, you'll get an ISS (Inertial Sub System) alarm because you shut it down, that's the way it should be.

I actually only do it after landing for saving battery power...

In reality this was done even more "drastically": A couple of seconds before splashdown you should power up the Flight/Post Landing bus, which powers the stuff you need after landing only (float bags, beacon light, dye marker, post landing vent etc.) by closing the 3 Flight/Post Landing cb's connected to BAT A/B/C on panel 275. Then untie the batteries from both main buses (MN BUS TIE BAT A/C - OFF and MN BUS TIE BAT B/C - OFF on panel 5), this unpowers both main buses, so almost everything shuts down immediately (AGC, IMU, FDAIs, C&WS, the SCS and ECS stuff etc.).

Cheers
Tschachim

 

[Urwumpe]

In reality this was done even more "drastically": A couple of seconds before splashdown you should power up the Flight/Post Landing bus, which powers the stuff you need after landing only (float bags, beacon light, dye marker, post landing vent etc.) by closing the 3 Flight/Post Landing cb's connected to BAT A/B/C on panel 275. Then untie the batteries from both main buses (MN BUS TIE BAT A/C - OFF and MN BUS TIE BAT B/C - OFF on panel 5), this unpowers both main buses, so almost everything shuts down immediately (AGC, IMU, FDAIs, C&WS, the SCS and ECS stuff etc.).

Argh. I knew that I was doing something wrong.

 

[SlyCoopersButt]

I found my problem. I didn't install it properly. I failed to notice a required zip I needed when I installed it. Works perfectly now!

 

[Native Son]

Leave the pointless arguments over nomenclature to the UN assembly, surely we're above that type of crap..

Well said.

 

[Spicer]

I've actually given up on Apollo NASSP. It's far to difficult to operate...and I feel that I'm a very capable "orbiteer."

I still can't turn the dang autopilot off. I just want to launch it myself. Do I have to use the autopilot?

This sounds un-patriotic of me, but I might just try a mission with the N-1. Wow. I can't belive I just said that.

 

[Kyle]

I like NASSAP, if only it was as Detailed as AMSO, I would prefer it over AMSO.
Maybe they should Merge to make the Greatest Apollo Simulation ever.

 

[Moonwalker]

Well, i wouldn't say that Project Apollo - NASSP is "difficult". It is an advanced level of manned space flight simulation. The goal is to recreate and simulate the Apollo Era systems, its procedures and missions in a historical way related to the workplace of an Apollo Astronaut. It's for sure that it isn't possible to make each "orbiteer" happy since people have different perceptions of space flight simulation. But it is for sure that Project Apollo - NASSP is made for people who are often called "hardcore-simmer". To be highly interested in the Apollo Era, its technology and usage as well as having some spare time is a requirement to become happy with Project Apollo - NASSP.

Talking about AMSO in this context; AMSO is not (yet...) an Apollo systems simulation. AMSO is great in simulating the environment and missions of the Apollo Era. I really like it too. And i agree that merging NASSP and AMSO would be great apparently. But for several reasons this won't happen (licensing, different points of opinions concerning systems simulation and to say nothing of LazyD...).

For now we have two great projects but each with a different usability. I think this actually is a good thing. So almost each Apollo fan might become happy concerning different perceptions of an Apollo simulation. I like to use both although i'm the instrument panel-guru of Project Apollo - NASSP

 

[Kyle]

I wrote down the checklist and was able to launch fine.

 

[mikaelanderlund]

I've actually given up on Apollo NASSP. It's far to difficult to operate...and I feel that I'm a very capable "orbiteer."

I still can't turn the dang autopilot off. I just want to launch it myself. Do I have to use the autopilot?

This sounds un-patriotic of me, but I might just try a mission with the N-1. Wow. I can't belive I just said that.

We choose to run NASSP, not because it is easy, but because it is hard