0
0

I am using a relative path to my audio source directory for a project in Fmod designer 1.6.0.

I have named the directory "Source" and it exists in the same directory as the fmod designer project file. All of the waves that will be used in the project are stored in this Source directory, and I do not intend on moving them in the future.

I have entered "Source" in the fmod project audio source directory field. I like using a relative path here as it makes the project more "portable" than it is with an absolute path. (That is, so long as the project and its source directory exist in the same folder on any system, fmod designer should be able to find the waves used in the project.)

Now, when I add wavetables to sound definitions in this project, I expect to see the filename of the file as the name of the wavetable, without any path prefix, as these files exist immediately in the Source directory that I specified.

However, what I see in the sound definitions are pathed waves, each with prefix of several ../../../ and a path back up to the source folder. Basically it is stepping down from my specified source directory all the way to the root of the drive, then building the path back up to the very same source directory it started at.

Because of this, even though there is technically still a relative path to each wave, it completely breaks project portability because it steps the path down to the drive root and back. It is likely that these wave file paths would also break the possibility of source directory substitution on build.

I would like to see the wave paths fixed to work as expected (It used to work fine, I’m not sure when this changed)

thanks for your support
-jason

  • You must to post comments
0
0

Hi Jason, this is a known issue that we’re hoping to fix in the next week or two.

  • You must to post comments
0
0

This has been fixed for our next release.

  • You must to post comments
Showing 2 results
Your Answer

Please first to submit.