Unity 5.5 got out, I was excited and updated my project from 5.4.3f1 to 5.5.0f3 and didn’t made a backup. When I start my project there is those errors in the console :
InitializeUnityExtensions: Must have a valid path for plugin
Extension was not registered, that means it relies on default UnityExtensions settings, please register extension and apply neccessary settings for it in the callback.
Each of them are repeted 10 times. When I start playing in the editor, even with all scripts disable, the editor disappear without giving me the possibility to report this bug.
Alright, it looks like this has been fixed in 5.6.
The error is caused by importers which have a zero length asset path name. This happens when you have a Unity version installed with an addon, it’s calling for an asset’s physical location, and if you save the project and open with a Unity version without the addon it will return an empty string since the physical location of this asset doesn’t exist. So in the fix in 5.6 Unity will skip initialization for these plugins. If you later add the addon, upon project opening it will return a valid path and settings for it will be initialized.
Last time I checked 5.6 will be released in Mach 2017, and because of this issue on 5.5.0p3 I had to download 5.6.0b3 but my computer hangs when trying to open my big size project.
Also, I noticed in General that starting around the middle of Unity 4 Cycle and increasing for Unity 5 cycle, I see many version numbers popping up in the forums for people are asking for solutions , and I get the feeling for me that upgrading to a newer version will most probably break something in my project. I know it is a hard-work Unity engineers are doing, and hopefully Unity find a way to add new features and fixes without breaking previously achieved milestones.
Also, I with that downgrading from one sub-version of Unity to a lower one is achievable, since sometimes after upgrading and working for a while, I discover some issue then if I want to use my backup I will need to redo what I did.
Developing on 2 computers here (mac and pc) and everytime, I move the project from pc to mac or vice versa I get those extension-problem and have to reimport all to fix it (which takes very long)… this is annoying…
Which “addon” do you mean? I have two identical Unity installations on mac and pc and this problem occurs everytime I move the project from pc to mac or vice versa. I never installed (as far as I know!) any “Addon”… So at the moment I don’t get the problem…
Any type of extension/plugin to the editor. I’m trying to get ahold of the developer to see what the plans are for backporting to 5.5, it’s taking a bit longer atm due to the holidays.
Edit:
No plans for backporting atm. Is this issue affecting your project currently besides listing those errors in the console?
Not public on issue tracker, just tracked internally. Is this affecting your project right now other than the console listing those errors? There are no plans for backporting at the moment and the error should not be causing any harm, but let me know if this is not the case.
At the moment you are not able to enter Play mode without the editor crashing, am I understanding this correctly? This issue is not supposed to affect your project or the editor, so I need to double check with you all if this is not the case.
I had the same issue.
For me, personally, it happened this way: I had a project that I was working on in Unity 5.5beta-something. I upgraded to Unity 5.5f3. Everything went well, I saved my project.
But I still had an old shortcut to Unity 5.5beta and opened my project in beta instead. So, when I opened the same project with beta, I got these errors. Luckily, I made backup.
When I fixed all the shortcuts and opened the project with 5.5f3, everything was working properly, as expected.
Do not know if it`ll help someone, just wanted to share my experience with this error.
I’m able to fix it with a “Reimport all”. This takes quite a while but it works everytime. After the reimport the console is empty and I’m able to start the project inside the editor.
Have to do this every day because I work on a pc half the day and later I move to a mac, next day to pc again. The change from pc to mac is the problem, mac to pc seems to work.
I’m using version 5.5.0f3 Personal and have been transferring my folder between a Win7 and Win10 computer when I see these problems. I tried the Reimport all command and this worked for me as well. My guess this may have something to do with the Assembly-CSharp.csproj file in the root folder, since I’ve been seeing some error messages with it’s name in it.
Yes the editor crash everytime I try to enter playmode. One thing sure it’s that it’s related to the 5.5 update since it works perfectly on 5.3 and 5.4
After installing and trying multiple versions of Unity 5, I reverted back to Unity 5.4.3p4, but my scene is missing the names of the objects. So, I started from scratch by importing the only necessary assets and I’ll try to keep the project size to a minimum.
But, I have a question; if someone asks me “What version of Unity 5 I shall use, that is stable and builds projects with no errors?”, I do not know what to tell him; because there are many Unity versions and subversions and many Unity Patches. This was not the case with Unity 2,3 or 4.
For me, especially with the subscription plan of Unity is ongoing, getting a stable and build-proof version is better than releasing subversions and patches with new small sets of features. Unity ,with subscription and a huge community, does not need to hurry to release a MAJOR version every one or 2 years like Unity 2,3 and 4. You can combine feature-sets and release them after extensive testing.
I know that Unity is doing great job to be available on many platforms as an editor and as a player, but no one can master everything.
I’m talking to the team to get a backport of this fix for 5.5 in place, but in order to get this moving we will now need bug reports from you all as well. Let me know the report numbers once you’ve submitted the reports.
