Sound Packs for AMSO

[Matte]

Hi, has anyone ever done sound packs for AMSO?
i saw on the readme that is possible, so maybe someone have done it...
it is not very nice to listen: <<Eleven, Houston, you're go for orbit>> while flying with Conrad...

 

[NukeET]

Hi, has anyone ever done sound packs for AMSO?
i saw on the readme that is possible, so maybe someone have done it...
it is not very nice to listen: <<Eleven, Houston, you're go for orbit>> while flying with Conrad...

This is definitely needed...a different sound pack for each mission.:2thumbsup:

You may notice that the name on the back of the LMP's PLSS, on those missions after Apollo 11, always show "Mitchell".

EDIT: PLSS backpacks for LMP after Apollo 14.

 

[Matte]

You may notice that the name on the back of the LMP's PLSS, on those missions after Apollo 11, always show "Mitchell".

Hemm, negative, sir. in AMSO i can see every back pack with the correct name...

 

[NukeET]

From Apollo 15, click on the image to enlarge:

 

[Matte]

OMG, you're right. didn't notice it before? why does it happen?

 

[NukeET]

OMG, you're right. didn't notice it before? why does it happen?

Don't know why this happens.

I tried editing the textures for Apollo 15 LMP to "Irwin", but it didn't work.:sorry:

fftopic: Went to the same high school as Jim Irwin, and so far the only astronaut I've heard speak in public - yes, i'm old. So, this "bug" is personally annoying.

 

[Matte]

but are u shure it is a bug? i mean, have u looked at the codes? maybe the programmer wanted to do it...but why? :lol:

 

[NukeET]

I'm not sure it is a "bug" - calling it that may be too harsh.

Look in your Orbiter install directory\Textures\AMSO

Notice how there is an entry for plss_xx_y.dds, where xx=11 or 12 or 14 or 15 or 16 or 17, and y=1 or 2. Note that there isn't a y=2 for xx>14.

Placing "plss_15_2.dds" in this path doesn't result in the correct name showing up in any Apollo 15 scenarios.

Renaming "plss_15_2.dds" to "plss_11_2.dds" results in the following screen shot:

IMO, I think it is an oversight in the code. Don't have access to the original code used to generate the dll file.