Issues:
1) Texture coords are specified by user.
2) Texture dimension is unknown at mesh creation.
3) Mesh can be referred to by multiple textures or update with different textures.
Possible Solutions (listed by Kevin):
1) Only support 3D on system that is NPOT capable, i. e. system without NPOT support will not run 3D.
2) Expose NPOT support as a ConditionalFeature (such that if NPOT support was false, we would not accept a texture that was not power-of-two).
3) To compensate in SW, but that will be expensive and complex (and almost certainly out of scope for FX 8 given all of the other things we need to do).
1) Texture coords are specified by user.
2) Texture dimension is unknown at mesh creation.
3) Mesh can be referred to by multiple textures or update with different textures.
Possible Solutions (listed by Kevin):
1) Only support 3D on system that is NPOT capable, i. e. system without NPOT support will not run 3D.
2) Expose NPOT support as a ConditionalFeature (such that if NPOT support was false, we would not accept a texture that was not power-of-two).
3) To compensate in SW, but that will be expensive and complex (and almost certainly out of scope for FX 8 given all of the other things we need to do).
- relates to
-
JDK-8090325 ES2Texture: create() remove padding; uploadPixels() caches buffer as static
-
- Open
-
-
-
- Resolved
-