Problem Orbiter Sound 3.5 and Windows 7

dan

New member
Joined
Jul 24, 2009
Messages
4
Reaction score
0
Points
0
I recently installed Windows 7 Release Candidate clean install (wiped my hard drive of all installed programs). I used to have Windows XP and Orbiter 2006 P1 with Orbiter Sound 3.5 working perfectly. Now that i have installed the new OS I have been having problems with Orbiter Sound 3.5. When it is loaded on Orbiter, the LaunchPad works fine but when i start Orbiter up, it successfully goes to the loading screen, although when finished, the screen goes black and a window pops up that says "orbiter.exe has stopped working." I looked at the Orbiter log and the Sound log:

**** Orbiter.log
Build Sep 29 2006 [v.060929]
Found 1 joystick(s)
Module AtlantisConfig.dll [API v.060425]
Module DGConfig.dll [API v.060425]
Module OrbiterSound.dll [API v.060425]
Module TrackIR.dll [API v.060425]
TrackIR module not found.
Module ScnEditor.dll [API v.060425]
Module Rcontrol.dll [API v.050206]
Module Meshdebug.dll [API v.060425]
Module InterMFD421.dll [API v.050206]
Module Framerate.dll [API v.050206]
Module FlightData.dll [API v.050206]
Module ExtMFD.dll [API v.060425]
Module CustomMFD.dll [API v.060425]

**** Creating simulation session
DirectDraw interface OK
Direct3D interface OK
Zbuffer: 32 bit
Render device: Fullscreen 1600 x 1200
Device has hardware T&L capability
Joystick throttle: Z-AXIS
Joystick throttle control detected
Module Sun.dll [API v.050206]
VSOP87(E) Sun: Precision 1e-006, Terms 554/6634
Module Mercury.dll [API v.050206]
VSOP87(B) Mercury: Precision 1e-005, Terms 167/7123
Module Venus.dll [API v.050206]
VSOP87(B) Venus: Precision 1e-005, Terms 79/1710
Module Earth.dll [API v.050206]
VSOP87(B) Earth: Precision 1e-008, Terms 2564/2564
Module Moon.dll [API v.041022]
ELP82: Precision 1e-005, Terms 116/829
Module Mars.dll [API v.060425]
VSOP87(B) Mars: Precision 1e-005, Terms 405/6400
Module Galsat.dll [API v.041022]
Module Jupiter.dll [API v.050206]
VSOP87(B) Jupiter: Precision 1e-006, Terms 1624/3625
Module Io.dll [API v.041022]
Module Europa.dll [API v.041022]
Module Ganymede.dll [API v.041022]
Module Callisto.dll [API v.041022]
Module Satsat.dll [API v.050206]
Module Saturn.dll [API v.060425]
VSOP87(B) Saturn: Precision 1e-006, Terms 2904/6365
Module Mimas.dll [API v.050206]
SATSAT Mimas: Terms 113
Module Enceladus.dll [API v.050206]
SATSAT Enceladus: Terms 33
Module Tethys.dll [API v.050206]
SATSAT Tethys: Terms 101
Module Dione.dll [API v.050206]
SATSAT Dione: Terms 59
Module Rhea.dll [API v.050206]
SATSAT Rhea: Terms 68
Module Titan.dll [API v.050206]
SATSAT Titan: Terms 100
Module Hyperion.dll [API v.050206]
SATSAT Hyperion: Terms 595
Module Iapetus.dll [API v.050206]
SATSAT Iapetus: Terms 605
Module Uranus.dll [API v.050206]
VSOP87(B) Uranus: Precision 1e-006, Terms 1827/5269
Module Neptune.dll [API v.050206]
VSOP87(B) Neptune: Precision 1e-006, Terms 391/2024
Finished initialising world
Module DeltaGlider.dll [API v.060425]
Module ShuttleA.dll [API v.060425]
Module ShuttlePB.dll [API v.041022]
Finished initialising status
Finished initialising camera
Finished initialising panels

Orbiter Sound Log Started
*****************************

--------------------------------------
ERR01= Vessel->ConnectToOrbiterSoundDLL3: Unable to connect to OrbiterSound 3.5 - not installed or activated

--------------------------------------
ERR01= Vessel->ConnectToOrbiterSoundDLL3: Unable to connect to OrbiterSound 3.5 - not installed or activated

--------------------------------------
ERR01= Vessel->ConnectToOrbiterSoundDLL3: Unable to connect to OrbiterSound 3.5 - not installed or activated

Passed initModule - Ok
attempting focus change...
Focus not ready bypassing focus change - Ok
Attempting RenderViewport initialisation...
Attempting GetStartValue initialisation...
Passed GetStartValue - Ok
Initialising directsound...
InitDS error-> DX Code: E_INVALIDARG
ERROR FAILED TO INITIALISE DIRECTSOUND
Passed ExitModule - Ok


I saw that it failed to initialise DirectSound, so I went to dxdiag and found that another error message pops up and says "Error: problem getting extra sound info."

I do not know what to do from there and if anyone can help me I would appreciate it.

-Dan
 

DaveS

Addon Developer
Addon Developer
Donator
Beta Tester
Joined
Feb 4, 2008
Messages
9,478
Reaction score
732
Points
203
Weired. Use Windows 7 RC1 here and no issues noted. OS 3.5 working nicely, no errors or other bugs noticed.

Must be an error on your machine.
 

n122vu

Addon Developer
Addon Developer
Donator
Joined
Nov 1, 2007
Messages
3,196
Reaction score
52
Points
73
Location
KDCY
dan,

First, I see that this is your first post. Welcome to the forum!

Second, I am wondering, is sound working in general on your machine under Win7 RC1? I would verify that you have the latest drivers from the sound card and/or motherboard manufacturer. Vista drivers tend to work ok in Win7 from what I've experienced.

If drivers are up-to-date, maybe a reinstall of the drivers or DirectX itself would help (failure of dxdiag suggests to me either check sound drivers or DX installation and then go from there).

Anyone else have any suggestions?
 

dan

New member
Joined
Jul 24, 2009
Messages
4
Reaction score
0
Points
0
I had problems with sound overall initially, but i resolved it by using an XP Sigmatel driver in Windows XP compatibility mode.

I will try downloading the Vista Sigmatel driver and installing using Vista compatibility.
 

TSPenguin

The Seeker
Joined
Jan 27, 2008
Messages
4,075
Reaction score
4
Points
63
I had problems with sound overall initially, but i resolved it by using an XP Sigmatel driver in Windows XP compatibility mode.

Did you try running orbiter in XP compatibility mode?
 

Hielor

Defender of Truth
Donator
Beta Tester
Joined
May 30, 2008
Messages
5,580
Reaction score
2
Points
0
You shouldn't need to run drivers in compatibility mode -- it won't be able to do everything it needs to, due to the way compatibility mode works.

Try with the Vista drivers, but try them without compatibility mode first, only using compatibility mode if necessary. Most things written for Vista will work on Win7.
 

bpops

Simpit Builder
Donator
Joined
Jul 31, 2008
Messages
93
Reaction score
0
Points
0
Location
Los Alamos
Website
picasaweb.google.com
I run Orbiter with OS 3.5 on Windows 7 RC1, and no problems here, either.

Have you tried updating your sound card driver from the manufacturer?
 

dan

New member
Joined
Jul 24, 2009
Messages
4
Reaction score
0
Points
0
I tried downloading the vista Sigmatel driver and using Vista compatibility and it says it is not available for my computer model (Sony Vaio VGC-RC110G), so no luck there.

As for updating the sound drivers, is there a driver for Windows 7? I am using a Sigmatel High Definition Audio CODEC
 

Hielor

Defender of Truth
Donator
Beta Tester
Joined
May 30, 2008
Messages
5,580
Reaction score
2
Points
0

bpops

Simpit Builder
Donator
Joined
Jul 31, 2008
Messages
93
Reaction score
0
Points
0
Location
Los Alamos
Website
picasaweb.google.com
As for updating the sound drivers, is there a driver for Windows 7? I am using a Sigmatel High Definition Audio CODEC

Unlikely. Not many companies officially support an unreleased version of Windows. But as someone said up above, Vista drivers should work in most cases (one nice thing about Windows 7).

And I agree with Heilor -- I'd try the 32-bit if you're using 64. I couldn't get Boxee running on my 64bit windows 7 machine, but did on my 32bit win 7 machine -- and they have very similar builds.
 

Hielor

Defender of Truth
Donator
Beta Tester
Joined
May 30, 2008
Messages
5,580
Reaction score
2
Points
0
And I agree with Heilor -- I'd try the 32-bit if you're using 64. I couldn't get Boxee running on my 64bit windows 7 machine, but did on my 32bit win 7 machine -- and they have very similar builds.
This isn't to say that the 64-bit Win7 is inherently bad or unstable--typically, an application failing to run on 64bit is a problem with the application. It can be annoying, though.

I've been using 64-bit Win7 at work since January and at home since April and I haven't had any compatibility issues due to 64-bit (with the exception of attempting to run a 16-bit app, for which I could use XP Mode). I'd recommend using the 64-bit version, an then if you run into problems heading back to 32.
 
Top