DirectX12 Minumum Allocation size.

for a buffer with a width 1 ID3D12Device::GetResourseAllocationInfo always returns the size/aligment as 64K. That is not a problem. The issue i am having is that any resource created on that heap needs to respect the aligment. So if put a resource at Offset 0 and try to put another resource at 32k for example. The resource at 0 will work but when i try to put something at 32k, it generates an error that say all resource needs to respect the boundary.

I don't understand... You say that it's not a problem that the API tells you that you need use 64k alignment, but then you try and use 32k alignment instead anyway, which fails, as expected?

But i kind of find it very annoying that the API does not let you insert the data into any location in a Heap.

It's because GPUs have alignment requirements, and will crash if given misaligned pointers.

My beef was that I cannot insert object anywhere I want on that heap of 64k. For example on the cpu side when you write your own memory manager you can put things anywhere you want. So I was not expecting the gpu to have that kind of limitation. But just like I said it is no biggie because you can create a memory management system that works around that.

The CPU side has alignment limitations as well, they're just usually smaller. When trying to allocate an object of type T in C++, you should make sure that the memory address that you give it is a multiple of alignof(T).

It's just that GPU's tend to have (much) larger alignment requirements than CPU's. e.g. The biggest CPU-side alignment requirement that's commonly seen is 16-bytes, whereas GPU requirements are often measured in kilobytes

DX11 code (and earlier) didn't have to deal with this as the driver hid all the memory allocations from you. This is good as before, you were completely unaware that you might have been wasting loads of VRAM by making small buffers, but now, it's extremely obvious that 32KB buffers are wasteful!

In theory, these requirements would change from GPU to GPU, so the point of GetResourseAllocationInfo is that you can ask the API for information on the alignment requirements at runtime.

I have gotten around it by creating a single buffer of 64k then just pass back a pointer that points to the current location in that buffer that i want to put the info. So the first object uses the first 32k and the second object uses the starting address+offset. Whenever i Map my resource i automaticaly add the offset to the starting address depending on the object i want to change. That way the resource is bound once and i can draw the two objects without any issues. That is what i meant when i say that you can write a system that can work around the limitation, you just have to managed it which is not a problem for me. I have written a ton of memory management system. . To be honest i really like

the way they have it, because now you can tell exactly how much memory you are using.