Does Addressable build log show Build Report?

I checked build log when build addressable asset bundle but can't find Build report like build player in log. Does Addressable 1.5 show that kind of log ? like this one

 

I would also be interested in a way of profiling addressable or asset bundle size and the assets that get built into each bundle. The Resources list that's printed when making building the Player is certainly good enough for most purposes.

 

He @PhuongND, I'll send this post over for you to see if a member of the team can point you in the right direction!

 

Addressables does indeed not show any build report and one official Unity member reply on this forum was that all APIs to make something like this should be available. But I wouldn't see how/where.

Can someone of the Addressables team please clarify how we can make a usefull build report log?
We need to see e.g. that the textures are taking up 900mb, just like in the useful default editor.log example as linked above.

 

Yes this is a huge problem for us. Addressable build gets stuck and we have no way to find out what is going wrong. This is wasting so much time

 

I'm looking for information like this as well - which assets exactly are being included and their sizes.

 

Bump, this still a major pain to miss any build size insights when using addressables.

For us this is the only missing feature when using Addressables for standalone/mobile/console builds.

 

Bump. Any update on this?

 

Unity should have a channel to report users of new features and FAQ. The forum communication is so ineffective in some cases. Any update on this?

 

Bump. Any update on this?

 

Still not available, plus Unity has never even commented on this issue.

For us this is the clearest examples of where Unity is really dropping the ball and letting Unreal beat them.
Unity clearly never uses or tests their own tools on actual games; You cannot release any professional games without bumping into this issue.

Note: I do love the Addressables system, please don't torture us by delivering the Addressables system incompletely (or even deprecating it :/).

 

Well I've got bad news for you. If you read some of their posts, they are aware of how poorly designed Addressables are and already designing version 2.0 which will replace the current version and require some kind of code rewrite. If only they tried actually using it for developing a working game (stop feeding us with these useless tech demos!!!)...

Couldn't agree more with your message. Unity is getting kicked in the gut this year by Unreal and others again and again. Yet they still continue to disappoint. Full C# support is the only thing keeping this engine from being abandoned by many...

 

I'm having the same disillusion as you guys, and it's hard to find jobs with Unity. Every decent game company build their own engine that is writing in C++ or use Unreal.
Unreal is not perfect, it has a lot of flaws, but now may be a good time to migrate.

 

Well it's a bit off-topic but in my area there are more Unity jobs now than ever. They might be loosing the game for noob-devs, or graphics-focused games, but it's still THE engine of choice for Mobile (which is now like the larger half of the whole industry). Not to mention 2D capabilities which Unreal lacks.

Unreal is great as a finished product, but for a long-term serious development, IMHO, it's a pain in the ass. The engine is very poorly designed, built upon ancient legacy code, uses weird mix of obsolete 90's style of C++ with custom "wheel reinvented" kind of preprocessing. Creating editor tools (which is a big part of any serious project) is a huge pain compared to Unity.

I might be completely wrong, but my current understanding is:

- Unreal is great right now, but doomed to fail unless they rewrite it from scratch (because modern clean code always wins in the end).
- Unity is complete crap to start with, but for a competent team it's still has no real competition for what it's good at. Everything is in flux and subject to change.
- I expect a big new player to enter the stage, because of the above flaws there are an unfulfilled demand for a project with Unreal level of quality and Unity level of productivity and customization, while being written for modern games from scratch.

 

So this depends on your setting, in my case, I use default setting for my android build. My addressable build file is located in <project path>/Library/com.unity.addressables/StreamingAssetsCopy/aa/Android. There is a .bundle file inside and its size could tell me how large the addressable build is

 

Bump! Unity Team, we miss you

 

Thanks, we still really need this badly to fix OOM issues on various platforms and download sizes mostly on mobile platforms.

 

That build report option was exactly what I needed! had no clue this was already available and a setting we'd need to find under the Preferences.

 

I thought the same thing when first looking at it, but then couldn't use it that easily in practice.

For example, I needed to find out which textures are the largest or whether it makes sense to compress audio more. I also wanted to play around with some settings and compare two builds.

To help myself I implement a hacky tool that parses the file and sorts and groups entries by their type and size. Another version of the file is ordered by asset file path so that its easier to compare to versions in a diff tool. But the custom solution is incomplete and based on some hacky assumptions.

I would hope Unity improves on this soon and provides a complete build report for Addressables.

 

A year and a half later, there's still no tool to view the build results of an addressable bundle file?

If at least the Build Layout Report was sorted by file size, that would make it so much more useable.

Is the best solution really still to do a hacky parse of the buildlayout.txt?

Why is there no way to get the data it gets generated from in c#?



Edit: I implemented it myself here: https://forum.unity.com/threads/addressable-build-analyzer.1323738/