We have multiple sound designers working on our project and there is no guarantee that their local directory structure the same. We use the audio source directory for localization purposes. Because this must be an absolute path it causes problems when users with different directory structures add .wav files to the project.
Could this please be addressed? I don’t see any reason why this path couldn’t be absolute or relative.
- Magog asked 11 years ago
I would like to see this change as well. We have multiple sound designers working in our studio too and forcing them to have the same path is not ideal.
This also wouldn’t work well if you were working on a branch of your game as the path would need to be reset each time you branch the content.
- vatoloco answered 11 years ago
I think this was changed from being relative wasn’t it? I seem to remember having to change paths at some point in the last few months, so I guess there was a good reason for it. When that happened it was easier just clearing the "Audio source directory" and putting the path into the sound definitions instead, and in doing so losing the flexibility that provided.
If it has to be absolute (relative would be preferable for me too), it would be nice to support being able to just use the root drive e.g. "\Audio\Stuff" so that the hard drive selection isn’t forced to C: or whatever. I realise this is a Windows thing though, so might be problematic.
- crouton answered 11 years ago
Please login first to submit.