Asset browser ignore files

[ivan.cuevas]

Hi all,

We work using different repositories as submodules in a parent project. These repositories contains assets but also documents and other kind of files that don't need to be added to asset browser (and copied to data folder by extent).
My suggestion is to add in Unigine Editor 2 settings menu a place to specify patterns to be ignored in assets folder. In the same way as git gonore does.

This seems a good place ;)

Regards,
Iván.

[silent]

Hi Iván,

There will be major changes in 2.7 regarding asset system behavior. In few words:

1. No more duplicates in assets and data. There will be only one directory (data). No more confusions about script editing in assets and so on.
   1. Drawbacks are: more guids in data (importing FBX will create non-human readable files and folders, but it will be looking good inside Editor).
2. Overall speed up and refinement.
3. Multithreading support for faster assets processing.
4. FBX Import will be a separate plugin (with access to the sources), so you can customize import as you want by rewriting the plugin or writing a new one.
5. Automatic migration of assets directory should work OK for the projects that's already using the new asset system.

Thanks!

[demostenes]

4 hours ago, silent said:

Hi Iván,

There will be major changes in 2.7 regarding asset system behavior. In few words:

1. No more duplicates in assets and data. There will be only one directory (data). No more confusions about script editing in assets and so on.
   1. Drawbacks are: more guids in data (importing FBX will create non-human readable files and folders, but it will be looking good inside Editor).
2. Automatic migration of assets directory should work OK for the projects that's already using the new asset system.

Thanks!

What does it mean for migration from 2.5? We are stucked on 2.5 and we desperately need to migrate.

[silent]

Hi Jirka,

There will be (probably) easier migration from 2.5 to 2.7 than from 2.5 to 2.6 :)

[demostenes]

41 minutes ago, silent said:

Hi Jirka,

There will be (probably) easier migration from 2.5 to 2.7 than from 2.5 to 2.6 :)

OK, looking forward to that.