0
Cannot Reproduce

Failed to load unit options (every time at startup)

artyrambles 2 months ago updated by Lazlo Bonin (Lead Developer) 2 weeks ago 16

Hey there!

Since yesterday, every time I start Unity this error appears:

Any idea why this happens or how to fix it?

Bolt Version:
1.4.6f
Unity Version:
2018.4.8f1 Personal
Platform(s):
Editor
Scripting Backend:
Mono
.NET Version (API Compatibility Level):
.NET Standard 2.0

Hi artyrambles,

I'm sorry you're experiencing this issue and I apologize for the late reply on this. We really appreciate you taking the time to submit a bug report.

I noticed you are using Bolt 1.4.6. We have issued many fixes since then and the newest stable version is now 1.4.7. Can please you update and let me know if that fixes your issue?

https://ludiq.io/bolt/download/1.4.7

In addition to this, if there are any other warnings/errors in your console please capture them within the screenshot.

Kind regards,
Hasan from Ludiq

Hey there!

No worries. It did not stop me from using the asset, it was just an inconvenience. 

I updated to 1.4.7 today and restarted Unity a few times and the issue seems to be gone. Thank you for the tip. :)

Cheers

Hey,

Thanks for doing that. Happy to hear that this worked! 

Cheers,

Hasan from Ludiq

Hey, unfortunately it seems I spoke too soon. The issue has returned.

Need More Information

Hi Artyrambles,

Sorry to hear that.

We'd need additional information to assist you.

Does this issue happen on a blank project, or only in a specific project?

Does it happen every time or only some times?

Can you determine conditions to make it happen (e.g. recompiling scripts, entering/exiting playmode, etc.)?

If it happens only on a specific project, can you send us the project files in private via support@ludiq.io?

I've noticed the issue as well both in the main 2019.1.9 production project and my own fresh 2019.2.9 project that has only a bunch of store assets in it. 

It does not, however, reset after every restart.But the issue seems to be related with the startup of the project. 

I kept an eye on it for a bit and it seems like it actually only happens the first time I start Unity in a day. Doesn't matter which project.

This hasn't happened to my projects anymore after I uploaded the generated units db to source control. 

Hey TowerCrow, what do you mean by that?

Previously I didn't push the generated units to my GitLab or BitBucket repo and just left it local. I haven't encountered the issue since I pushed the generated units to source control.

Ah I see. I'm not using source control, actually.

Need More Information

Hi,

We need reproduction steps or a reproduction project to be able to debug this issue, as we cannot get it to occur on our end.

Got this pop up after start up or after importing the new Doozy UI version, didn't catch the specific moment.

EDIT: Looks like it's related to importing/updating other assets perhaps?

Unity 2019.2.11f1

Bolt 1.4.9

Failed to load unit options.
Try to rebuild them with 'Tools > Bolt > Build Unit Options'.

System.Threading.ThreadAbortException
at Bolt.UnitBase.Load () [0x00108] in C:\Users\lazlo\Projects\Bolt1\Package\Bolt.Flow\Editor\Options\UnitBase.cs:105
UnityEngine.Debug:LogError(Object)
Bolt.UnitBase:Load() (at C:/Users/lazlo/Projects/Bolt1/Package/Bolt.Flow/Editor/Options/UnitBase.cs:138)
Bolt.UnitBase:AutoLoad() (at C:/Users/lazlo/Projects/Bolt1/Package/Bolt.Flow/Editor/Options/UnitBase.cs:37)
System.Reflection.MethodBase:Invoke(Object, Object[])
Ludiq.<>c__DisplayClass0_0:<.cctor>b__3() (at C:/Users/lazlo/Projects/Bolt1/Package/Ludiq.Core/Editor/Threading/BackgroundWorker.cs:49)
Ludiq.BackgroundWorker:Work() (at C:/Users/lazlo/Projects/Bolt1/Package/Ludiq.Core/Editor/Threading/BackgroundWorker.cs:115)
System.Threading.ThreadHelper:ThreadStart()
Cannot Reproduce

So it's "normal" that this error would happen under some rare circumstances where Unity forces reload of the current assemblies instantly, probably aborting all background threads along the way.

In those cases, I should add a way for it to retry. In the mean time, entering/exiting playmode or restarting Unity should fix the issue.

What I'm more interested in is if there's any setup that constantly or regularly throws this error. If so I'd need reproduction steps to fix it.