A Unity ID allows you to buy and/or subscribe to Unity products and services, shop in the Asset Store and participate
in the Unity community.
Hi. Based on your Editor.log the converter is hitting some issue while trying to collect information about the comments in your sources:
That is unfortunate since it looks like to me that you are hitting other issues and fixing those would probably benefit more Unity users.
Adding new files should only trigger the updater if that files requires updates. When this happens again, please share your Editor.log with...
We've discussed the idea of adding such option but we decided to not do so to avoid users disabling it and then failing to realize that not...
Answered in https://forum.unity.com/threads/unityscript-2-csharp-conversion-tool.487753/page-4#post-4705841
In your post you sad that "But soon, the problem arose:" ; That is odd.
Basically that message means the converter was running...
@Loards have you reported the issue? Can you somehow still reproduce it?
@guycalledfrank I've fixed a bug recently that would prevent the...
Hi, sorry, not without changes.
That being said, depending on the amount of Boo code you have it may worth giving it a try. Basically you'd need...
It has been fixed in 2019.3 and back ported to 2019.2b5 / 2019.1.6f1.
Can you share your Editor.log with me? I want to make sure sure the ApiUpdater bug is not the cause of your problems.
That makes sense. In that version the updater only supports C# 7.1 (which does not include in keyword).
Anyway, even though ScriptUpdater log...
Which version of Unity are you using?
This should be supported (we do have tests and I can see that the change that enabled it landed around...
The problem is that the integration code is resolving the Unity installation folder to a wrong path:
> Found assemblies root...
Thanks, Nothing in the logs point to the problem.
can you run it with verbose logging and send me the logs again?
Hi, no. I want to look in Editor.log. There are lots of info that can help there.
Also, in the Editor.log file you'll find a line like:
Please share your Editor.log file when you get this error.
Try to create a new project in 2018.1 and copy over your Assets folder (a process similar to what @Mccbbi suggested above).
I suspect that the set of assemblies being passed to the converter is not correct (for instance, UnityEngine.dll & UnityEngine.CoreModule.dll...
I think it should be under Assets\Plugins\UnityPurchasing
Ok, the log shows that we have not even imported these assemblies which is inline with the behavior described in this post:...