HORRIBLE pre-launch sounds in NASSP v4.0 ???

[Curl Snout]

Greetings from Planet 10,

I spent what seemed like days getting a (mostly) working install of NASSP v 4.0 (plus AMSO, plus
Vinka's multistage.dll, plus Vinka's generic spacecraft.dll, plus the complete Apollo 16 pack).  I did
all of this BEFORE installing OrbiterSound.  For the most part, NASSP was working fine (with the
exception of a couple of scenarios - the Apollo 13 launch always crashes Orbiter for me).  Then I
installed OrbiterSound 2.1b - I was careful to first remove and then replace the sound folder
already created by the previous installs culminating in my version of NASSP.   Now I've got a
couple of "problems" ("challenges" if you belong to the glass-half-full camp): 1) all scenarios that
begin pre-launch are accompanied by a horrible, stuttering, gravelly sound - hard to describe
adequately.  2) Some scenarios that worked fine before now crash Orbiter.

I dumped the entire install and started over with a sound-free NASSP (easy to do, as I keep a
copy of every Orbiter folder that I create on a separate hard drive).  This time, rather than
unzipping OrbiterSound directly into my NASSP folder, I unzipped it to a Temp folder and then
manually copied the sound files into the proper Orbiter folders.  I still have the problems outlined
above.  Has anyone else had a similar experience?  Can anyone offer advice or a solution?  Thanks
in any case.

BTW: I'm running Orbiter 021202, with patch 3.  And my NASSP v4.0 is from the full package, i.e.,
it's not v3.0 with the 4.0 "update".

CS Out

[John]

1)Try deleting the the Orbiter.cfg  located in the main orbiter directory so that it can make a new
one the next time you launch Orbiter. If that doesn't work, 2)Try reinstalling your drivers for your
sound card. It is possible they were corrupted in the install process. First remove them then
reinstall and see what happens. 3) The other possiblity is that you might have to reinstall Orbiter
base files again. Install into a diffferent directory then the Sound files then the scenario files. If
this works then just copy your old Scenerio, Texture, Module and other unique folders over the
new directory. I really doubt that this would be necessary but it is one way of finding out if the
problem is with the new sound files, which could be corrupted from the download, or a conflict with
a scenario file or module.   Seems extreme but when all else fails??? or  4) Just download the
sound files again and reinstall them to see if that works. If it does then you know the problem was
a corrupted download. It has happened to me with other downloads.

John

[Curl Snout]

Hey John,

Thanks for your suggestions.  The solution turned out to be much simpler: I re-built my NASSP
install a third time, moved the Sound folder to a different (temp) directory, installed OrbiterSound,
and did NOT replace the pre-existing Sound folder (i.e., the one I had before installing
OrbiterSound).  All appears, and sounds, fine now.  I suspect the contents of the 2
different "vessel" folders are incompatible, but am unsure exactly why.  Anyway, all is well.

Thanks also for the heads-up RE the dumping/recreating the Orbiter.cfg trick.  I was unaware of
that, and have taken advantage of it several times already this morning - The Apollo 11 VAB
scenario is very touchy.

Have fun,

Sam

[John]

Hi Sam

Glad to hear you solved the problem. Also keep the Orbiter.cfg file in mind when and if you ever
have problems setting your windows option. I was having trouble changing from full screen to
windows but deleting the config file solved this problem as well.


John