You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As I understand it, wgpuBufferGetMapState is currently not implemented. Is there any reason this functionality is unavailable, and is there any way to check if a buffer was successfully unmapped and can be used for further operations?
The text was updated successfully, but these errors were encountered:
In wgpu-py we don't use it, because in a wrapper its easy to keep track of the map-state yourself. I think its safe to assume that if wgpuBufferUnmap() successfully returns, all should be well.
So (speaking for myself) it's mostly not implemented due to a lack of need and time :) PR's to implement it are welcome though!
@almarklein Thanks for your answer! I assumed that unmapping is some kind of async operation as well, but if I can just unmap synchronously, I guess I'm fine.
As I understand it,
wgpuBufferGetMapState
is currently not implemented. Is there any reason this functionality is unavailable, and is there any way to check if a buffer was successfully unmapped and can be used for further operations?The text was updated successfully, but these errors were encountered: