Search Issue Tracker

Fixed in Unity 5.1.0

Votes

0

Found in

5.0.0f4

Issue ID

678039

Regression

No

Plugin Importer settings do not persist when exporting a .unitypackage

Assets Management

-

-

Priority: 3Not yet prioritized for a release

-

Severity: 2Core functionality majorly impacted

How to reproduce:

1. Open attached project
- Package has 3 different Release channels (Debug, Profile, Release) for a single plugin
- The import settings for the plugin folder in each channel are set to not execute on any platform
- They may be set to execute on a specific platform
2. Export the Wwise folder into a package
3. Open a new project
4. Import the package exported in step 2
- [OSX] Note how Unity throws errors that the plugin with that name already exists and that there can only be one plugin with that name
- Checking the import settings for each plugin folder reveals that they are set to execute on any platform, regardless of what they were set to execute on before

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.