Forum Discussion
Changing Build Folder Name Crashes
Hi guys,
I ran into a really strange issue with our build at work.
Unity 5.1.3
Windows 7
Runtime 0.6.0.1
Direct Mode
We delivered our build to our client who said that they couldn't get it to run as it crashes.
This was odd because we tested it and it ran just fine.
By chance one of the devs renamed the build folder, by that I mean the parent folder of the Exe and Data folder and now it would crash, if we renamed it back it would run fine.
If we disable the Runtime the build runs even with the renamed folder.
We tested this on another workstation with a completely clean build of the project and clean Library and a different Parent folder name. The build would run fine until we renamed the parent folder.
There is nothing in the build that refers to a hard coded path.
I can only surmise that this has something to do with VR plugins as the build runs fine if the runtime is disabled.
Any ideas on what the could be?
One thing I am going to try on Monday is to revert back to 5.1.2 and see if the issue still exists.
I ran into a really strange issue with our build at work.
Unity 5.1.3
Windows 7
Runtime 0.6.0.1
Direct Mode
We delivered our build to our client who said that they couldn't get it to run as it crashes.
This was odd because we tested it and it ran just fine.
By chance one of the devs renamed the build folder, by that I mean the parent folder of the Exe and Data folder and now it would crash, if we renamed it back it would run fine.
If we disable the Runtime the build runs even with the renamed folder.
We tested this on another workstation with a completely clean build of the project and clean Library and a different Parent folder name. The build would run fine until we renamed the parent folder.
There is nothing in the build that refers to a hard coded path.
I can only surmise that this has something to do with VR plugins as the build runs fine if the runtime is disabled.
Any ideas on what the could be?
One thing I am going to try on Monday is to revert back to 5.1.2 and see if the issue still exists.
