GpuTextureUsages Enumeration |
Enum describing buffer usage; not mutually exclusive.
Namespace: NeoAxisAssembly: NeoAxis.Core (in NeoAxis.Core.dll) Version: 2026.1.1.0 (2026.1.1.0)
Syntax[FlagsAttribute]
public enum Usages
Members| Member name | Value | Description |
|---|
| Static | 1 |
Static buffer which the application rarely modifies once created. Modifying
the contents of this buffer will involve a performance hit.
|
| Dynamic | 2 |
Indicates the application would like to modify this buffer with the CPU
fairly often.
Buffers created with this flag will typically end up in AGP memory rather
than video memory.
|
| WriteOnly | 4 |
Indicates the application will never read the contents of the buffer back,
it will only ever write data. Locking a buffer with this flag will ALWAYS
return a pointer to new, blank memory rather than the memory associated
with the contents of the buffer; this avoids DMA stalls because you can
write to a new memory area while the previous one is being used.
|
| StaticWriteOnly | 5 |
Combination of Static and WriteOnly.
|
| DynamicWriteOnly | 6 |
Combination of Dynamic and WriteOnly. If you use
this, strongly consider using DynamicWriteOnlyDiscardable
instead if you update the entire contents of the buffer very
regularly.
|
| BlitDestination | 7 |
Texture can be used as the destination of a blit operation.
|
| DynamicWriteOnlyDiscardable | 14 |
Combination of Dynamic, WriteOnly and Discardable.
|
| AutoMipmap | 256 |
Mipmaps will be automatically generated for this texture.
|
| RenderTarget | 512 |
This texture will be a render target, ie. used as a target for render to texture
setting this flag will ignore all other texture usages except AutoMipmap.
|
| ReadBack | 1,024 |
Texture data can be read back.
|
| ComputeWrite | 2,048 | |
See Also