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
- Texture Import Warnings are obscured by other Terrain Layer options in the Inspector
- Burst Inspector middle divider is jittering when resized with the Burst Inspector window docked
- JsonConvert conversion fails trying to call GetCallbackMethodsForType when [OnDeserialized] is used in a class
- Different text alignment in the column header in Entities "System" window
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
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.