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 Alimaggs, unfortunately i didn't managed to solve this issue. Didn't tried yet the 2018 version.
Just deleted Complete() from the code and yeah, seems that there is a hard sync point that complete the job. To bad there is nothing about this in...
It's a 1 frame delay job.
Ok, i made a simple project so you can check https://mega.nz/#!6QURWSaA!UZbSfiE9ZYRXRLv7rQ2JKECz-iXNPQMmd6garsvHbX0.
I still don't understand the impact of the delay.
My lifecycle is simple:
Any news on this?
I have a job dependency where i do:
1. MoveJob - move transforms
2. RotateJob - rotate transforms
3. RangeCheckJob - check distances
Same here, both on windows and mac.
There is no attached projects because it can be reproduced on newly created empty projects.
Anyone experiencing drag-and-drop issues in editor in this beta(2018.2.0b2)? I just don't understand what it's causing this. I have a success...
I can confirm this (for 2018.2.0b2). For every click on script file, unity keep opening new VS instances.
I'm using VS 7.4.3(build 10)
+1 to this, anyone with alternate solution?
Just removed Microsoft Ads from project and references. Master get compiled and application run but packaging still fail with the same errors.
No, didn't modified any unity generated file. I just added a reference to Microsoft Advertisig library because i use a plugin for it.
In short, i recently purchased microsoft dev account to migrate my project to Windows Store.
Last 2 weeks was dedicated to study all docs...
My 5 cents on this.
I'm on 2017.3.p3 and get the same errors as DeepeshMishra mentioned in 1st post.
After 2 days of ivestigations i coudn't find...
If someone is still interested in this, i recompiled the git sources of the plugin and fixed this issue. Also i did get rid of editor errors. Here...
Just delete FacebookSDK folder and install older version.
The same issue here, yesterday everything was fine. Seems that something is wrong at FB side.