Feedback Improve "Processing Addressable Group" popup

Every time I press Play in the editor, I see this popup appear for a brief moment.



It's quite annoying and I would like to suggest to find a way to prevent that.

A common technique to filter these quick tasks is to display the popup only, after it's busy for a while. For example, rather than displaying the popup immediately, display it after Unity is "processing addressable group" for 1s or so. This would prevent the dialog to popup when it only takes 100ms to process anyway.

 

Any way to bypass this? Everytime i press play it just freeze for 5 minutes

 

Yes, please tell us how to bypass this window. This question has lasted for three months now.

 

I think you can't bypass that. "Use asset database" mode needs to process all assets as configured in your groups so they can be used in play mode. Naturally this happens as you enter play mode.

 

Would be great if this wouldn't update every time I hit play, for example when nothing changed in-between

 

I guess they can keep data from last play if, for example, no asset was changed. On my project I used similar approach for a resource system (built on top of addressables). It caches data but invalidates cache every time something is changed in project window. They could probably do something similar. Especially useful when you iterate on code, but asset didn't change.

On current project this process takes not more than 2-3 seconds (with Domain reload disabled) so not a problem for me yet.

 

Would be great if this wouldn't update every time I hit play, for example when nothing changed in-between

 

I just updated to 2020.1.4 from 2019.3, and also notice this. It's very quick, but it's still kinda annoying to see it. Any updates here, or is this the intended behavior?

 

I still have this problem, it seems like it deletes/rebuilds addressable every now and then, causing it to stick for around 10 seconds. On my friends machine it's much slower.

Can we disable this and rebuild them manually somehow?

 

Update to the latest version 1.16.x fixed it for me so I thought I'd post it here too in case someone was on an older version too.

 

Thanks, that helped!