Does Addressable build log show Build Report?

Unity Engine
1

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

5368755--543207--download.png
5368755--543207--download.png942×665 26.1 KB

2 Likes
2

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.

3

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!

4

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.

1 Like
5

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 :frowning:

1 Like
6

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

7

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.

8

Bump. Any update on this?

2 Likes
9

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?

10

Bump. Any update on this?

11

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 :/).

1 Like
12

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…

3 Likes
13

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.

1 Like
14

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.
1 Like
15

So this depends on your setting, in my case, I use default setting for my android build. My addressable build file is located in /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

16

Bump! Unity Team, we miss you

17

Hey all! I’m going to flag this thread with the team again, see if I can chase down some insight to share.

2 Likes
18

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

19

Hey all, so I wanted to give a couple of suggestions.

  • Diagnostic tools | Addressables | 1.16.19 has info on the Build layout report that you can turn on and might be useful

  • There’s also a callback BuildScript.buildCompleted that you can subscribe to and get the result of a build. You can then write it to a file or whatever.

I understand this option won’t work for those of you having issues during the build. Unfortunately I don’t have good solutions for those of you facing that problem. At the very least I’d file a bug so the Scriptable Build Pipeline team can look at it. If the build is hanging indefinitely or crashing or something it could very well be a SBP problem.

3 Likes
20

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.

1 Like