Search Unity

  1. Megacity Metro Demo now available. Download now.
    Dismiss Notice
  2. Unity support for visionOS is now available. Learn more in our blog post.
    Dismiss Notice

Bug Random Static Meshes are missing in Asset Bundles

Discussion in 'Asset Bundles' started by chcheng_unity, Jul 1, 2022.

  1. chcheng_unity

    chcheng_unity

    Joined:
    Apr 12, 2018
    Posts:
    1
    Hi, we are encountering a strange problem of missing static meshes in asset bundle.

    In Editor (with which Play Mode Script of Addressables is set to "Use Asset Database"), everything is fine. But if we build the project and run on a device (Meta Quest/Quest2), sometimes some random static meshes in some scenes are missing.
    • It begins to happen since we update the Unity version to 2020.3.32f1 (Addressables 1.18.19), and it never happened before updating from Unity 2019.4.8f1 (Addressables 1.18.9).
    • We are putting each scene file (map) into individual bundle files, and the settings are as shown in the screenshot below.
      upload_2022-7-1_14-6-43.png
    Does anyone has idea about this?

    upload_2022-7-1_19-22-7.png
     
  2. Ispodwill

    Ispodwill

    Joined:
    Jan 8, 2021
    Posts:
    3
    Hi! I faced the same problem. For some reasons some random objects with "Batching Static" flag loose their mesh. Thank you for hint! Does anyone know, why does that happen?
     
  3. FPXTester

    FPXTester

    Joined:
    Sep 25, 2022
    Posts:
    1
    Any updates on this subject? It's a very frustrating bug. Random objects are just missing in some scenes.
     
  4. BelieveXiaoShuai

    BelieveXiaoShuai

    Joined:
    Nov 6, 2017
    Posts:
    20
    I also encountered this problem, is there a solution?"
     
  5. BelieveXiaoShuai

    BelieveXiaoShuai

    Joined:
    Nov 6, 2017
    Posts:
    20
    This bug has existed for long time.
     
  6. George-Ing

    George-Ing

    Unity Technologies

    Joined:
    Jan 14, 2020
    Posts:
    78
    Hey folks,

    This looks like a rotten one! If you encounter this issue and would be able to file a bug with a repo it would be really appreciated, & we'll look into it asap.