search

microsoft / ProjectAcoustics

Microsoft Project Acoustics
https://aka.ms/acoustics
Creative Commons Attribution 4.0 International
141 stars 22 forks source link

Can't local build anymore with v3 & Unity #101

Closed laurelhach closed 2 years ago

laurelhach commented 2 years ago

I just installed the latest version (v3) and when I run the *.bat file I get this error : Just before, I was with the previous version and I was running fine, but I saw the new version and cancel the generation. I installed the new version and now I get this:

d:\MicrosoftAcoustic>docker run --rm -w /acoustics/ -v "d:\MicrosoftAcoustic":/acoustics/working/ mcr.Microsoft.com/acoustics/baketools:2.0.143_Linux ./tools/Triton.LocalProcessor --configfile Acoustics_PrisonCells_config.xml --workingdir working

ERROR: Failed to deserialize config file: Acoustics_PrisonCells_config.xml ERROR: Exception: XML Parsing failed - provided NVP (ProbeInfo) not found

PS: The problem is that the baketools is now using 3.0.Linux instead of the 2.0.143. I had to manually change the value to make it work. But I am not sure why it doesn't update correctly when I export the local bake data.

PS: I had to clear the toolset version in Unity (delete the info), then the info repopulated itself with the correct version. Maybe this is something that could be updated automatically to avoid these kind of issues :)

NoelCross commented 2 years ago

@laurelhach with the latest tools, marked as 3.0, there were breaking changes to the file format for the input to the baking process. You'll need to go through the pre-bake process again with the 3.0 plugin integrated into your project in order to generate new .vox and _config.xml files. If you don't want to upgrade to the latest plugin, you can still continue referencing the 2.0 bake tools from the container registry.

laurelhach commented 2 years ago

@NoelCross, thanks for the explanation. But I'm fine moving to the v3. Actually it builds much faster than before (well .. I've also upgraded my computer ... so ... ) I was just wondering why it was not working with the new version :)

All is well ;)

MikeChemi commented 2 years ago

Glad you got this sorted out. I'll go ahead and close this issue. We will improve the upgrade path for our next release so you won't need to manually reset the tools string.