Search Issue Tracker
By Design
Votes
0
Found in
2017.3.0f3
Issue ID
982305
Regression
No
Mesh Filters within Blender files are not recognized in Cloud Builds making some gameobjects invisible
Steps to reproduce:
1. Open QA's attached project
2. Open scene "1" in Assets folder
3. Add the opened scene to the Build Settings
4. Publish changes to Collab and build the project using the Cloud Build
5. After the build has completed, download and launch it
Expected result: Cloud and local builds produce the same result
Actual result: Mesh Filters from .blend files are not recognized thus some gameobjects are invisible in the Cloud Build
Reproduced with:
- Win 64-bit Cloud Builds on latest 2017.3, 2017.2, 2017.1
- Win 32-bit Cloud Build on latest 5.6
- MacUniversal Cloud Build on latest 2017.3
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- VFX Graph particles are not culled when using URP and Frustum Culling is enabled on VFX Mesh Output
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
Add comment