You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm having a issue importing assets since about a month, getting the error The Asset system didn't catch asset quickly enough - skipping auto-compile for asset '{quixelAsset.Name}'
And getting a warning in the error list of sandbox (and visual studio) about the async task ImportFrom not having an await operator
I solved both problems inserting a await Task.Delay(500); below the line 44 of this file
Yeah the s&box asset system propagates changes really slowly.. I don't think there's any events either for it unfortunately. It might be worth me asking for some and then just hooking this up to those.
Not having auto-compile isn't a huge deal right now so it's not worth hacking around.. assets will compile whenever they're needed, this is just a convenience thing for people importing lots of assets at once
Just found out "assetsystem.changes" exists while I was doing something completely unrelated, it's undocumented for whatever reason, I'll have a look into using that
I'm having a issue importing assets since about a month, getting the error
The Asset system didn't catch asset quickly enough - skipping auto-compile for asset '{quixelAsset.Name}'
And getting a warning in the error list of sandbox (and visual studio) about the async task
ImportFrom
not having an await operatorI solved both problems inserting a
await Task.Delay(500);
below the line 44 of this filesbox-quixel-bridge/code/BridgeImporter.cs
Lines 44 to 54 in 6533172
but didn't created a PR before because I don't feel that's the correct approach to that problem.
what do you think?
The text was updated successfully, but these errors were encountered: