Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to build after uploading the addon with Collaborate to second computer #12

Open
filipbergqvist opened this issue Nov 26, 2016 · 3 comments

Comments

@filipbergqvist
Copy link

Since the files are in the assets folder, they automatically sync with Unity Collaborate. It seemed to work fine, but when I wanted to build the game it couldn't and I got a "Error building Player because scripts had compiler errors" error but not in any script, just in general. Deleting the addon fixed this issue. I would really like it if this addon wasn't in the assets folder so that it wouldn't sync.

@filipbergqvist
Copy link
Author

I would like to update this post by saying that I now can't even build on the first computer. I get the same error so I have had to uninstall the addon completely. I really like the customization in this so I would really appreciate if this issue was fixed so that you can actually use it. The UI also gets pretty slow while using this, but I presume that you already know that or that you can't fix that.

@bradsmithee
Copy link
Collaborator

bradsmithee commented Dec 14, 2016

Sorry for the late response, Zufixx. Build issues should be fixed if you are using the latest version, but if not, check for this solution #8.

The UI shouldn't be too slow (in general) if you have hover response set to none. It is a little clunky on load and while transitioning between play/edit mode, of course, due to the system reloading.

I'd love to be able to decouple the required assets for the system, but as of right now they need to be loaded into the project's asset database in the editor for me to use them properly. The best solution I could do is some kind of disclusion flag/setting to prevent them from being in builds/collab or centralizing them cross-project in a neutral directory via a symlink. The latter introduces some per-platform complications and both still expose the files in searches, however.

@bradsmithee
Copy link
Collaborator

bradsmithee commented Feb 22, 2017

Does the r549 release resolve your issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants