I’ve been evaluating Unity the past few weeks and have settled into a groove where I use Unity Remote and the Unity editor for most of my work.
I’m finding the workflow pretty slow when working on an actual device. From a standing start in the editor it takes nearly 2mins to get from “build and run” to the app running on the device - and this is for a very simple project.
Anyone got any tips to speed this up? I’m primarily interested in being able to quickly turn around C# script changes.
Is it possible to use dll’s built in Monodevelop to shortcut some of the build process? (I did briefly try this and got “signed resource has changed” errors)
That’s the point of Unity Remote, to bypass the build process so you can test quickly. Naturally you do need to test on the actual device, but the majority of the time you should be able to use Unity Remote.
I dont like Unity Remote at all. I do use it for fast gameplay after testing the code in the device. Unity remote for me doesnt work well, debug.log for touch.end cancel don’t show at all, double tap and other touch are not correctly detected.
What i do to speed up a little its build a full copy, then i use symlink unity libraries and append to xcode project for testing in the actual device.
Symlink:
"Symlink Unity libraries means that Xcode project generated by Unity will directly reference Unity iOS runtime library from Unity Editor install location. It saves your disk space (runtime lib is ~300 MB) and Unity Editor can faster generate Xcode project, because it does not need to copy additional 300 MB.
You should not use it when:
a) you are exporting Xcode project which you are going to share with somebody else
b) you are exporting Xcode project to make final build and you want to archive it for backup purposes."
Xcode Append:
When u create ur build for the second time Unity ask if u want to replace all files or only Append the new changes.
