Re: [PATCH 0/2] MR131: vkd3d: Persistently map host-visible heaps on creation.

[Henri Verbeet (＠hverbeet)]

Do we need to worry about 32-bit address space considerations here along the lines of MAX_PERSISTENT_MAPPED_BYTES in wined3d?

This does seem unfortunate in the sense that it's somewhat counter to the whole "explicit API" concept; you'd hope that in an API like Direct3D 12 calling Unmap() actually unmapped things.
> Resident Evil 2 accesses a resource immediately after unmapping it.

And presumably that's the last mapped resource on the heap, like in this test, or the heap would already stay mapped, right?