Async File System Watcher Job

[K.Wagrez]

Hello everyone,

I've been debugging some problems we had with some of our plugins and a particulary big world, and I stumbled upon a curious error message.
The message doesn't seem weird, until you realize I don't have a BA folder on my computer, and I don't have this file.
I suppose it's some internal behavior for Unigine ? What does this assertion failure checks ? What could cause this ?
 

---- UnigineEditor Asset Manager ----
Assertion failed: f0.isCore() || info.isFile(), file D:\BA\work\c784dd2b49fd6367\source\editor2\apps\editor\src\assets\fswatcher\AsyncFileSystemWatcherJob.cpp, line 114

There are a lot of things going wrong on this particular project context, so I would not be surprised if it's due to some wrongness of our assets or our plugins. For context, it's a project opened in debug through a Visual studio project created to develop our plugins (the way the documentation tells us to do). And we're on Unigine 2.18.1.

Thanks in advance

[silent]

Hi Kevin,

Yes, this is assert inside Editor's code - that's why you see our build agent path here, but not yours.

Assert actually trying to warn you that you have something wrong going in <Project>/data/core directory. This specific code is trying to load file from core and check if a specific flag in engine's virtual filesystem set for that file (isCore()). And for some reason from some file it is not set.

Maybe you are trying to mount core dir from external mount to the existing data with core?

Thanks!

[K.Wagrez]

Yeah, I was toying with several mount folders, I must have made some mistake at some point. When you say "core dir", do you talk about the core.ung archive ?

[silent]

Yes, this assert can also be triggered in Debug mode if more than one core directory is mounted, or if there are any unexpected files within the core folder that the Editor does not anticipate. It is a very cautious (almost paranoid) assert, so if you are absolutely sure that you do not have multiple mounted core directories, you can safely ignore it.

The good news is that this assert has been removed in the upcoming 2.21 release, so it will no longer appear in future versions :)