Closed Ybalrid closed 5 years ago
Currently relying on an Ogre::v1::HardwareBuffer to access texture has a pixel array CPU-side.
Ogre::v1::HardwareBuffer
See if there's a way of doing that using only Ogre v2 interfaces for future-proofness. And v2 is supposed to be faster than v1.
This require to fiddle with the async interfaces of Ogre 2. I have better things to do for 0.4 and this will not improve the engine that much
Actually, theses interfaces will be gone in Ogre 2.2
Currently relying on an
Ogre::v1::HardwareBuffer
to access texture has a pixel array CPU-side.See if there's a way of doing that using only Ogre v2 interfaces for future-proofness. And v2 is supposed to be faster than v1.