Hi,
I just upgraded to 1.15.1 and now my build breaks. Here is why: I mark whole folders as addressables and package these individually (each folder corresponds to a “world” in my game). In these folders I store files for level generation from third party tools and automatically convert these files to JSONs which I put next to them.
Now in the new update, the third party files are not ignored anymore but actually break the build. How can I tell the addressables system to simply ignore unsupported files? Forcing my users to suddenly use two separate folder constructs just because of this will be impossible to sell after everything worked so smoothly up until now.
Please help ( @davidla_unity ?) to provide an option to simply ignore unsupported file types. They should definitely not fail the build. Or if there is such an option already, I am all ears 
I’ll ping @TreyK-47 as well to make sure this gets noticed
I just tried 1.16.1 and this is still happening. I am really desperate as this is a complete blocker for me to upgrade. Is there any way to get around this check and have the addressables system simply ignore unrecognized file types as it did before instead of throwing an error? @davidla_unity ?
I’ll send this over for you also @ImpossibleRobert !
I know what you mean…
We had a few placeholder files in empty folders in the project (empty text files called “empty” with no extension, generated by a powershell script).
This change also came as a bit of an annoying surprise.
Luckily for us, the number of files was not that terrible so we just changed all those files to be called “empty.txt” so that Unity doesn’t make a fuzz about them and now it works, so it was not that big of a problem. But I guess not everybody might be in a position to do that.
(We did have to downgrade afterwards anyway because of the other issue with not being able to call load more than once, but that is a different topic)
Yes, I was also contemplating moving out the files but it would be a HUGE undertaking and make life much more difficult for my users and, simply ignoring the files would be such an easy fix. In 1.14.2 it neatly states “ignoring unsupported…” and all is good.
This sounds familiar… Let me see what I can find out.
So, it looks like we’ve been discussing this and have decided to put in a toggle to turn these checks on and off. I can’t give an ETA but I imagine it’ll be fairly quick since this should be pretty straightforward for us to do.
How about to implement include/exclude wildcards rather than an all on/off toggle? This would allow us to precisely include what we want.
For example:
exclude = *.tmp;*/LightingData.asset```
This would include all files, except *.tmp and LightingData.asset files.
To me this seems to be a more useful option than just being able to globally turning this whole feature on or off.
It would even solve this issue for me (hopefully):
https://discussions.unity.com/t/780445
This is great! Thanks. Hope you can somehow fast-track this feature as I am all-in with addressables.
@ImpossibleRobert This should be implemented in SBP when Addressables 1.16.2+ comes out. (I forget the exact SBP version but they’ll get released together). Look for it sometime this week.
@Peter77 Interesting idea. The toggle has already been implemented so it’ll be what we have for the time being but that might be a good feature to add and replace the toggle in the future.
Hi @davidla_unity ,
I now tried the 1.16.6 and it indeed has a setting for ignoring invalid files! Great! What I could not figure out though is: how do I set this via script which is my main use case? It seems that the ProjectConfigData class is not public and therefore cannot be accessed. Is this an oversight or intentional?