Error During Initialization

[Willfofo 10]

Bought the steam version, works on one of the two computers in the house. Sadly not mine, only my girlfriends.

Game starts, but before even reaching a splash screen i get an 'Error During Initialization' message, and the rest of the screen appears similiar to it is as mentioned here -

http://forums.kleientertainment.com/showthread.php?1228-Don-t-Starve-crash-on-start

bin/LOG file reads:

Starting up

THREAD - started 'GAClient' (3584)

HttpClient::ClientThread::Main()

cGame::InitializeOnMainThread

FMOD Error: Error initializing output device.

SoundSystem::Initialize failed

Shutting down

[Willfofo 10]

I fixed my own bug by unplugging all external audio devices of any form except default speakers and then re-installing audio drivers (FMOD error). Hope this helps someone.

[Corey 374]

Hey thanks for the update! This will indeed help someone else

[JLK 50]

Willfofo, would you be able to tell us which devices you unplugged? We've had some headset issues with the Chrome version in the past. Any additional information that we can pass on to the FMOD guys can't hurt.

[FUNK_DADDY 10]

I had the same message, "Error During Initialization." I realized my speakers weren't plugged in. After reading this thread I plugged in my speakers, hit play, and now the game will load.

[JoeW 37491]

Thanks for reporting in FUNK_DADDY, Glad you got it fixed up!

[Willfofo 10]

I was using the steam version.

Audio devices plugged in:

Sony TV (HDMI) with external audio connected through pre-amp.

Headphones (front jack).

USB audio-interface for both recording and monitoring (USB).

2.1 Speaker system (rear jack).

Unplugged all except my 2.1 Speaker system (rear jack) in, then re-installed audio drivers and plugged the other devices back in

[Willfofo 10]

Seems as though now I can recreate the same error message by changing my default playback device to my USB audio-interface (M-audio fast track, listed as S/PDIF), however setting default playback back to 'speakers' will again fix the issue. At least its not hard to fix on the user end in terms of just re-installing drivers, unplugging and plugging back in devices and not using unusual default playback settings.