Project

General

Profile

Bug #668

Custom engine sounds in mods don't play on mac (with workaround)

Added by Snjo almost 11 years ago. Updated almost 8 years ago.

Status:
Closed
Severity:
Low
Assignee:
-
Category:
Plugins/Add-Ons
Target version:
-
Start date:
05/20/2013
% Done:

100%

Version:
Platform:
OSX
Expansion:
Language:
English (US)
Mod Related:
No
Votes:
Arrow u r green
Arrow d r red

Description

Platform: Mac
Issue: sounds defined on parts that are in the ksp/sounds folder don't play on mac. Must be in the parts own folder.
To reproduce: Define an effect sound as described below, or try the firespitter mods propeller engines.
Probable cause: Sounds are pulled from the wrong folder on mac
Versions: At least 0.18 to 0.19.1


In my firespitter mod I have custom engine sounds defined for propeller engines. I have gotten several reports from Mac users about the sounds not working.
I didn't know if it was an issue with the sound files themselves, or a scripting error in the official code. Turns out it was the latter, as one of the users found a workaround.

The sounds are defined:

// --- Sound FX definition ---

sound_fsmustangstart.wav = engage
sound_fsmustang.wav = power
sound_explosion_low = flameout

the engage and power sounds are placed in the ksp/sounds folder. but unlike the flameout sound, which is an official sound, and probably handled differently, they do not play.

The workaround is to place the sounds inside a sounds folder in the part folder for each part. Seems there is an issue with how you handle file paths in the cfg parser or sound loading code.

If you want to test this bug on your own, the firespitter mod is on spaceport. Try any of the engines.
I don't have a mac myself, but I can confirm it works fine on linux and windows.

History

#1 Updated by RexKramer almost 9 years ago

  • Status changed from New to Need More Info

Unfortunately, this is not the ideal place to report issues with mods, better results will likely be obtained with the mod creator.

With that said, this one dates back to 0.19. Is the issue still present, or at least requiring the workaround described above?

Marking need more info. If this issue is no longer present, please mark resolved.

#2 Updated by Snjo almost 9 years ago

The whole system was changed after that, removing this bug in favor of sounds not working on any platfrom, but workarounds are known. You can close the issue

#3 Updated by RexKramer almost 9 years ago

  • Status changed from Need More Info to Resolved
  • % Done changed from 0 to 100

#4 Updated by TriggerAu almost 8 years ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF