0
0

Hi. Apologies if this was already asked.

1.) Is there some sort of dependency relationship between version numbers of FMODEx and FMOD Designer?
Do they have to be exactly the same? Can one be higher than the other?
i.e. Would using designer version 4.15 and FMODEx 4.14 cause a problem?

2.) Is there a way, programaticly, to retrieve the version # from a *.fev file? Does it even have one?

Thanks.

  • You must to post comments
0
0

You can use old designer files with newer API versions. It will load old files right back to the first version of fmod designer.

I dont think there is a way to get the version programmatically, but if you use a version higher than the API supports you will get FMOD_ERR_VERSION

  • You must to post comments
0
0

Thanks for the response. Your reply seems to imply that if Designer’s version is higher than FMODEx’s, then the Designer Files might not load. That assumption seems to be backed up by looking at release notes for Designer.
[quote:1iuq7ve2]
* .FEV file format updated! FMOD Designer 4.13.05 requires FMOD version 4.13.05, 4.12.05 or higher.[/quote:1iuq7ve2]
1.) Is that assumption about your reply correct?

2.) Is there a reason why a "stable" version of Designer is not available for download with the same version # as the "stable" version of FMODEx? Without looking closely at the release notes, one might think that "developer" Designer 4.15 doesn’t work with "stable" FMODEx Programmer API 4.14. Those second guesses could be eliminated if there was a version of designer labeled stable 4.14.

3.) Is there a reason why past versions of Designer are not offered for download on the download page similar to the FMODEx Programmer API? It seems like a feature users would appreciate since the "development" version of designer might have bugs & if someone is going to download an older version of FMODEx, they won’t be able to download a compatible version of Designer.

Thanks for your input!

  • You must to post comments
0
0

[quote="NESboi":q1jxthpn]Thanks for the response. Your reply seems to imply that if Designer’s version is higher than FMODEx’s, then the Designer Files might not load. That assumption seems to be backed up by looking at release notes for Designer.
[quote:q1jxthpn]
* .FEV file format updated! FMOD Designer 4.13.05 requires FMOD version 4.13.05, 4.12.05 or higher.[/quote:q1jxthpn]
1.) Is that assumption about your reply correct?
[/quote:q1jxthpn]

Yes, re-read what I said. What you’re looking at talks about the other way around.

[quote:q1jxthpn]
2.) Is there a reason why a "stable" version of Designer is not available for download with the same version # as the "stable" version of FMODEx? Without looking closely at the release notes, one might think that "developer" Designer 4.15 doesn’t work with "stable" FMODEx Programmer API 4.14. Those second guesses could be eliminated if there was a version of designer labeled stable 4.14.
[/quote:q1jxthpn]

That assumption would be wrong. Just use the version of fmod designer that there is. There is no point in making a ‘stable branch’ of designer stagnate for 2 months when new things are being added all the time. It is not as critical to have a tool have a ‘stable branch’ as it is for the API which is going to ship in a final game.

[quote:q1jxthpn]
3.) Is there a reason why past versions of Designer are not offered for download on the download page similar to the FMODEx Programmer API? It seems like a feature users would appreciate since the "development" version of designer might have bugs & if someone is going to download an older version of FMODEx, they won’t be able to download a compatible version of Designer.

Thanks for your input![/quote:q1jxthpn]

If the development version of the api has bugs, use the stable branch.

  • You must to post comments
Showing 3 results
Your Answer

Please first to submit.