Metal doesn't "map".
More...
#include <OgreMetalDynamicBuffer.h>
Metal doesn't "map".
You can directly access the unsynchronized contents For performance we keep many buffers as one big buffer, but for compatibility reasons (with GL3/DX10 HW) we treat them as separate buffers.
- This class treats mapping in a GL-style. The most usefulness is that in OS X we need to inform what regions were modified (flush). On iOS it serves no real purpose and is just a pass through with some asserts for consistency checking.
◆ MetalDynamicBuffer()
Ogre::MetalDynamicBuffer::MetalDynamicBuffer |
( |
id< MTLBuffer > |
vboName, |
|
|
size_t |
vboSize |
|
) |
| |
◆ ~MetalDynamicBuffer()
Ogre::MetalDynamicBuffer::~MetalDynamicBuffer |
( |
| ) |
|
◆ flush()
void Ogre::MetalDynamicBuffer::flush |
( |
size_t |
ticket, |
|
|
size_t |
start, |
|
|
size_t |
count |
|
) |
| |
Flushes the region of the given ticket. start is 0-based.
◆ getVboName()
id<MTLBuffer> Ogre::MetalDynamicBuffer::getVboName |
( |
| ) |
const |
|
inline |
◆ map()
void* RESTRICT_ALIAS_RETURN Ogre::MetalDynamicBuffer::map |
( |
size_t |
start, |
|
|
size_t |
count, |
|
|
size_t & |
outTicket |
|
) |
| |
◆ unmap()
void Ogre::MetalDynamicBuffer::unmap |
( |
size_t |
ticket | ) |
|
Unmaps given ticket (got from.
- See also
- map). The ticket becomes invalid after this.
The documentation for this class was generated from the following file: