Project

General

Profile

Bug #2100

[Windows] FMOD audio plugin missing from 2.0 installation

Added by Harley51 almost 9 years ago. Updated over 7 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Defect
Target version:
-
Start date:
2015-07-13
% Done:

100%


Description

I have a Sony Vaio. Game starts up fine. When I go forward in Doom up the first stairs. It get part way up and says Doomsday.exe has stopped working.

doomsday.out.txt (12.2 KB) doomsday.out.txt Harley51, 2015-07-13 03:02
doomsday.out.txt (12.4 KB) doomsday.out.txt Harley51, 2015-07-15 19:06

Related issues

Related to Feature #2101: Select audio plugin using Audio Settings dialogClosed2015-07-15

Associated revisions

Revision 5114451a (diff)
Added by skyjake almost 9 years ago

Fixed|CMake|Installer: Missing/excessive installed components

FMOD was not included in the packaged components.

The Assimp static libraries are not supposed to be installed as part
of the SDK.

IssueID #2100

History

#1 Updated by Harley51 almost 9 years ago

Open GL Version is 4.0

#2 Updated by skyjake almost 9 years ago

This looks like an audio issue, the crash seems to have occurred during the starting of a sound effect.

loadAudioDriver: Loading of "fmod" failed
Failed initializing audio driver "FMOD" 
Audio configuration:
  Music: SDLMixer::Music
  SFX:   SDLMixer

I wonder why FMOD has failed to load?

#3 Updated by danij almost 9 years ago

Also, why hasn't the FMOD Ex sound playback driver been switched out and the 'dummy' one used instead, when the former failed to initialize correctly? (With the latter intended to avoid repeatedly checking whether playback is possible).

#4 Updated by skyjake almost 9 years ago

@Harley51: What happens if you try to use "-dsound" or "-openal" command line options when launching?

#5 Updated by skyjake almost 9 years ago

danij wrote:

Also, why hasn't the FMOD Ex sound playback driver been switched out and the 'dummy' one used instead, when the former failed to initialize correctly? (With the latter intended to avoid repeatedly checking whether playback is possible).

Probably the logic for choosing the fallbacks is inadequate. I don't recall the details but I believe there isn't much smartness in it.

I just checked the latest 2.0 Windows build. It appears the FMOD audio plugin is entirely missing from the installation, so that would explain the problem.

I think SDL_Mixer is known to be a bit unstable on Windows, so there's nothing particularly unexpected there.

#6 Updated by skyjake almost 9 years ago

  • Tags set to Audio, Windows, Plugin, Installer
  • Subject changed from Doomsday.exe has stopped working to [Windows] FMOD audio plugin missing, SDL_mixer crashes when playing back a sound effect
  • Category set to Defect
  • Assignee set to skyjake
  • Target version set to 49

#7 Updated by skyjake almost 9 years ago

  • Status changed from New to In Progress

#8 Updated by Harley51 almost 9 years ago

I just updated to build 1656 and now at the main menu screen for Doom you hit Esc and it crashes right away. Entered the commands -dsound: unknown identifier -openal says the same thing.

#9 Updated by danij almost 9 years ago

Harley51 wrote:

I just updated to build 1656 and now at the main menu screen for Doom you hit Esc and it crashes right away. Entered the commands -dsound: unknown identifier -openal says the same thing.

-dsound and -openal are command line options, so they need to be specified before starting Doomsday.

If you are using Snowberry then you can simply choose the associated audio driver at Settings > Sound > Sound driver: (DirectSound or OpenAL, in this case). If you are running Doomsday from the command line, you can specify -dsound or -openal there.

#10 Updated by skyjake almost 9 years ago

danij wrote:

If you are using Snowberry

I don't think Snowberry is being used (it is a 2.0 unstable build).

#11 Updated by skyjake almost 9 years ago

  • Related to Feature #2101: Select audio plugin using Audio Settings dialog added

#12 Updated by Harley51 almost 9 years ago

danij wrote:

Harley51 wrote:

I just updated to 2.0 build 1656 and now at the main menu screen for Doom you hit Esc and it crashes right away. Entered the commands -dsound: unknown identifier -openal says the same thing.

Is there someplace else the commands are suppose to be entered. I entered them in the lower left hand corner of the doomsday screen where it says enter commands and I get this message -dsound: unknown identifier -openal says the same thing.

#13 Updated by skyjake almost 9 years ago

Harley51 wrote:

Is there someplace else the commands are suppose to be entered.

If you are not comfortable with command line options, I recommend you use the 1.15 stable release until 2.0 is more refined and user-friendly so that it doesn't require you to use options.

Here is information about how to use command line options in Windows (from Mozilla web browser's documentation, but applies similarly to Doomsday 2): http://kb.mozillazine.org/Command_line_arguments#How_to_use_command_line_arguments

#14 Updated by Harley51 almost 9 years ago

I ran the commands as suggested with the same crash results.

#15 Updated by Harley51 almost 9 years ago

Any progress on this issue.

#16 Updated by skyjake almost 9 years ago

  • Subject changed from [Windows] FMOD audio plugin missing, SDL_mixer crashes when playing back a sound effect to [Windows] FMOD audio plugin missing from 2.0 installation

#17 Updated by skyjake almost 9 years ago

  • Status changed from In Progress to Resolved
  • % Done changed from 0 to 100

#18 Updated by skyjake almost 9 years ago

  • Status changed from Resolved to Closed

Thanks for the reminder. FMOD should now be installed in the next build, fixing the problem.

#19 Updated by Harley51 almost 9 years ago

Thank you skyjake. That at this point has fixed this problem. This Sony Vaio is touchy on a lot of different software's.

#20 Updated by skyjake over 7 years ago

  • Target version deleted (49)

Also available in: Atom PDF