understanding memory mapping in directx
- by numerical25
So my question is ... " When your using the mapping feature to write into a memory buffer, are you really just saving the whole procedure into a queue so directX executes it when finished with other tasks???"
I ask this question because this is my perception of mapping when writing to a buffer. I just want to make sure my perception is correct.
I understand that the monitor moves extremely slow in compared to the processor, and I am sure the processor can execute 10 times the amount the screen can refresh. So is this one of the reason you should map when writing to a buffer. so each procedure can be done in a orderly fashion.
If someone could elaborate, that would be great. thanks