Search Issue Tracker
Fixed in 2017.1.X
Votes
5
Found in
5.4.0b14
Issue ID
792609
Regression
No
[Texture3D] Allow non-power-of-two Texture3D sizes
Currently Texture3D requires POT sizes. This is not very convenient for some use cases (e.g. 3D LUTs etc.). Modern GPUs can do NPOT volume texture sizes just fine.
Comments (1)
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
- Volumetric fog shader variants are missing from build when "Strict Shader Variant Matching" is disabled
- Unnecessary modifications clutter the Scene when using a RectTransform driven by a LayoutGroup in a Prefab
- Files in the target folder are deleted without a proper warning when building an iOS project
- Character animation freezes when toggling animator on/off in a coroutine
- Certain textures are incorrectly marked in the render pass list when observed through Render Graph Viewer
andrewbasta
Oct 22, 2016 23:25
Another example: Say I have scientific data in NPOT dimensions that I want to load into a Texture3D object. I don't want to downscale the data and lose resolution, nor do I want to unnecessarily pad the data to POT and lose performance.
As OP says, modern GPUs can handle this. Please stop Unity from throwing an exception.