Toony over the top reloaded uploaded link

Materials, Physics Materials, Shaders, Textures, Meshes. It seems every asset that is a dependancy receives this treatment.

The case number is Case are you able to confirm what I am observing is correct? All assets considered a dependancy by the asset bundle system is essentially duplicated, processed for the target platform and placed into the bundle.ДЇor example, if you have a generic texture that is used in other parts of your game (ie: A generic blob shadow texture), and you load 5 different asset bundles which all contain some object that makes use of this blob shadow texture, I will have 5 identicle (yet 'different') copies of the exact same blob shadow texture loaded into memory? Each asset bundle using its own 'copy' of the source? This is what I am observing in the memory profiler. Please take a look at this Vincent, this is a huge problem on my project right now. I've already posted about this in the forums, but I'm putting it here because Zhang has replied at least once, and I know he works on Asset Bundles. There are many cases when multiple materials might share a texture, and they will need to have different names. but this is not an acceptable workaround. We're currently working around this by having each material share the name with it's texture. Resetting the shaders is easy, because the materials still have a reference to them, and you can just do Shader.Find with the name.Д«ut the textures is a big problem, because the materials are just showing Null in the MainTexture property. The problem is I have an additional issue that the materials are also losing the reference to their textures, so that I not only have to reset the shaders on materials, I also have to reassign the textures on materials. Using the Shader.Find hack that posted above does fix it, and it works properly on device without the shader hack. We've determined it is from loading shaders compiled for iOS from within OSX.

I've also experienced this problem on OSX. The forced dependency collection is just going to double up on all these Dunnett could you shed some light on this?

Or a card game like hearthstone where each card or theme of cards were an asset bundle and shared assets like the Mesh for the 3d card itself or made use of a common texture like the card backings. Imagine a car game where each car was an asset bundle, and each car used the same shader or made use of some common texture. So if I load and instantiate the prefabs in all 10 of these bundles, is this texture loaded into memory 10 times? (10x copies of the same texture).Д¬reating asset bundles which reference assets which are garunteed to exist in the project isn't such a crazy idea either. What about if I had a texture in my project that all of these prefabs were referencing? Forced dependency collection means that this texture will be copied 10 times (once for each bundle). Will this break dynamic batching since each asset bundle has its own copy of the same shader? This raises other questions too - for example, since the shader inlcuded in the bundle isn't the exact same shader as the one in my project (it is a precompiled copy), does this break batching? Imagine if I had a custom diffuse shader which I used on all of my assets, and I had 10 asset bundles all containing different meshes/prefabs with materials that used this custom diffuse shader. We need to build our asset bundles for all 3 platforms. When I loaded the bundle, it would use the shader already included in the application (and so it would always be the correct shader, since the shader was already compiled for the current platform whether it be windows, osx, ios or Android). This way, I could exclude the shader from my bundle. My shaders were included in the resources folder and I was able to make the assumption that it would always be there. In 4.x, I used to exclude shaders from my asset bundles. This means that if I am testing in the Editor and have my platgorm set to Android, any asset bundle I load in the Editor will contain pink materials. This is causing some real issues with shaders.! They turn pink, because, as mentioned above, the shader is precompiled for the target platform and included in the bundle (whether you like it or not!). Why? Why can't we disable this? I no longer feel in control of what goes in to my bundle. Now in 5.x, dependencies are always collected. We used to be able to exclude dependencies in 4.x, so we knew exactly what was in our bundles.

Toony over the top reloaded uploaded link