Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.4.1f1
Issue ID
1041546
Regression
No
[Windows, Terrain] Error messages generated for every crunched terrain texture on scene load or entering/leaving play mode
To reproduce:
1. Open the attached project
2. Make sure the Terrain's texture is using Crunch Compression
3. Play the scene
Expected result: Loading a Terrain with crunched texture works with no issues
Actual result: Few errors are shown:
- GetPixels32 failed: insufficent pixel buffer size (1), must be at least 4 x 4
- Failed to get pixels of splat texture
Reproduced with: 2017.2.3f1, 2017.4.4f1, 2018.1.2f1, 2018.2.0b6, 2018.3.0a1
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
Resolution Note (2018.3.X):
There's no easy fix for this; as stated in the Manual, "GetPixels32 is not available on Textures using Crunch texture compression.", and the old Terrain CPU base map blending requires GetPixels32. The base map blending is done on GPU in 2018.3+, so it works with crunch compression (as well as being a ton faster and not requiring a CPU copy of the texture)