Audiokinetic's Community Q&A is the forum where users can ask and answer questions within the Wwise and Strata communities. If you would like to get an answer from Audiokinetic's Technical support team, make sure you use the Support Tickets page.

Unity project working fine on Windows but not on Mac. Lots of "Type or Namespace could not be found" errors.

0 votes
Hi

We have integrated Wwise(version 2021.1.3.7665) into our game project on Unity 2019.4.31f1. It works fine on Windows but some of our developers use Mac(Mojave 10.14.6) and they are getting a bunch of errors on the Unity console. All the errors are about types or namespaces(like AkThreadProperties, AkPlatformInitSettings etc.) not found.

From what I can make out, Wwise is not able to find runtime files for Mac. How can we fix this? It's possible that during initial Wwise integration Mac was unticked in the list of 'Deployment Platforms' but the guy who did it can't recall for sure. But anyway it should be possible to add a platform later right? Strangely, when we go to 'Modify Project' in the Wwise Launcher, the option to add Mac is greyed out.

We have added Mac as a platform using Platform Manager in the Wwise SDK but that doesn't seem to do anything. Is there any additional step needed after adding the platform?

Would appreciate any assistance. Thanks.
asked Oct 21, 2021 in General Discussion by Alo C. (130 points)

1 Answer

0 votes
 
Best answer
You can modify your integration even if the Mac option is greyed out: it indicates it has been originally selected (Windows and Mac are mandatory, for the exact scenario you encounter!)

Nevertheless, modifying your integration will recopy the necessary files, including those for Mac, so if the issue is that you have missing files this should solve it.

If you encounter file access errors:

Failure to access certain directories may be a configuration problem where files are expected at a certain place, but have been moved, or a user access right access. There should never be a need to run anything as Administrator other than at installation time when prompted by the Wwise Launcher: running as administrator may assign the wrong rights to files and leave them unaccessible later on.

You can try starting from scratch by removing the Audiokinetic folder in /Applications/Audiokinetic, the WwiseLauncher and Wwise context in $HOME/Library/Applications Support/Wwise2019 and $HOME/Library/Application Support/WwiseLauncher and finally the settings in $HOME/Library/Application Support/Audiokinetic.

Make sure you are using the latest Launcher from audiokinetic.com. Running as a normal user in all circumstances and not moving files manually on the filesystem, there should be no file access issues.
answered Oct 21, 2021 by Samuel L. (Audiokinetic) (23,300 points)
edited Oct 28, 2021 by Samuel L. (Audiokinetic)
Thank you for your response Samuel. I should mention that the Mac option was greyed out AND unchecked. But after a few changes, like removing the Wwise folder, running as admin etc. we did get the integration to run but it 'completed with errors'.

On checking the log we can see multiple errors. These are some of the first few:

- Backup: Failed to create backup for '/Applications/Audiokinetic/Data/install-table.json'. Error: ENOENT: no such file or directory, copyfile '/Applications/Audiokinetic/Data/install-table.json' -> '/var/folders/sg/4d5j6gsj58d6gnczy7lm7vqw0000gn/T/WwiseLauncher/backups/WwiseLauncher_2021.2.1.1450_1634892202241_bak/install-table.json'
- tracking backup error: Error: ENOENT: no such file or directory, open '/var/folders/sg/4d5j6gsj58d6gnczy7lm7vqw0000gn/T/WwiseLauncher/Analytics/analytics-deferred-posts-{8ebe35ce8134995e1f223149d3086c41}-{c6e2c7cac5ccd589c4ef37bf418a2b8c}.json'
- tracking backup error: Error: ENOENT: no such file or directory, open '/var/folders/sg/4d5j6gsj58d6gnczy7lm7vqw0000gn/T/WwiseLauncher/Analytics/analytics-deferred-posts-{8ebe35ce8134995e1f223149d3086c41}-{c6e2c7cac5ccd589c4ef37bf418a2b8c}.json'
- POST (0): https://www.audiokinetic.com/wwise/launcher/?action=alerts error undefined: PROXY_NOT_RESOLVED PROXY: PROXY_NOT_RESOLVED
- Error trying to remove legacy launcher: Error: Not implemented on OS X.
- Error trying to remove legacy launcher: Error: Not implemented on OS X.
- Error: Error reading or processing file /Users/mac/Downloads/bundle/bundle.json
- Error: Error reading or processing file /Users/mac/Downloads/bundle/bundle.json
- Error: Error reading or processing file /Users/mac/Downloads/bundle/bundle.json
- Error: Error reading or processing file /Users/mac/Downloads/bundle/bundle.json
- POST (8): https://www.audiokinetic.com/wwise/launcher/?action=videos error ESOCKETTIMEDOUT: ESOCKETTIMEDOUT PROXY: null
- POST (7): https://www.audiokinetic.com/wwise/launcher/?action=articles error ESOCKETTIMEDOUT: ESOCKETTIMEDOUT PROXY: null

After these errors there is this one:
- Error: Could not load signature of Rewired.Editor.ComponentControls.TouchInteractableEditor:GenerateInteractableAnimatorContoller due to: Could not load file or assembly 'UnityEngine.UI, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. assembly:UnityEngine.UI, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null type:<unknown type> member:(null) signature:<none>

Rewired is a Unity asset that helps with input abstraction. Does this indicate some kind of conflict between Wwise and Rewired? Works fine on Windows though.

Please let me know if any of these errors are significant. Thanks.
Failure to access certain directories may be a configuration problem where files are expected at a certain place, but have been moved, or a user access right access. There should never be a need to run anything as Administrator other than at installation time when prompted by the Wwise Launcher: running as administrator may assign the wrong rights to files and leave them unaccessible later on.

You can try starting from scratch by removing the Audiokinetic folder in /Applications/Audiokinetic, the WwiseLauncher and Wwise context in $HOME/Library/Applications Support/Wwise2019 and $HOME/Library/Application Support/WwiseLauncher and finally the settings in $HOME/Library/Application Support/Audiokinetic.

Make sure you are using the latest Launcher from audiokinetic.com. Running as a normal user in all circumstances and not moving files manually on the filesystem, there should be no file access issues.

If you end up in the same state, open a Support Ticket.
Starting from scratch fixed it. Thanks Samuel.
...