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.
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
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.