first of all: loving the new 4.7 features thus far and stability also made a great step forward! so thx for all that, good job!
one feature that just bit us in the back really hard is the auto import feature. i can see why you think its a great feature, and for single devs or new starters its probably a good time saver. but it certainly isnt for teams which have an established pipeline and workflow; its just too inflexible and does make too many false assumptions.
- we use p4 as source control
- we have multiple people working on multiple files at the same time
- we have files in the working folder, that are wip and are not subject to go into the game immediately
- we have files in the working folder that we wish to NOT import at all, e.g. our artists using jpgs for previews in max
- we store source files in subfolders prefixed with “_” to be able to exclude them easily by tools
- we want to import assets to a different folder than the source files (usually one folder up the “_” prefixed source folder)
- we regularly submit and sync a good bunch of files at once (e.g. one section of a level or more complex assets; goes in line with point 3)
you probably can see, why the auto import in its current state does not work for us…
- currently we have to work through internet, which means syncing several hundreds MB takes a few minutes. problem: a source file might be on disk already, while its uasset file is still downloading, but the editor thinks its not imported yet so does start the import process…only fixable by closing the editor every single time before syncing. you forgot to close the editor? you’re screwed and have to manually cleanup afterwards!
- after you synced a good bunch of files and start the editor, it starts importing all the unneccessary files, creating dozens of uasset files in source folders even though those assets will never be used; also the editor is blocked while that happens, so you get quite a coffee break everytime…waste of disk space and time
so as you perhaps can see, we had quite some headaches with this, until everyone turned off auto import. it would’ve been a lot easier ride, if auto import would’ve had the backwards compatible behavior, meaning: OFF for existing projects. maybe turning it only on for NEW projects would’ve worked…or only turn on REIMPORTING existing assets should their sources have changed, but not create new ones unintentionally. maybe. but auto importing everything everytime for everyone was not the best choice, imho!
to make this feature usable for US, it would need to be a lot more flexible.
like: allow to exclude certain patterns (like folders/files prefixed with “_*”) and defining WHERE an asset should be imported to (even though i see why that would be a hard thing to do in a generic way).
well, that became quite a wall of text…sorry 'bout that
but hopefully it helps making things better and less intrusive in future iterations