[ToolKit.Graphics] Multisampled BackBuffer's TextureView size are wrong #425
Comments
|
The pull request has been merged. @AvengerDr, can you please confirm if it resolves this issue? |
|
@ArtiomCiumac @jwollen Yes it does work fine now, thanks! Though I'm wondering whether there's something wrong in the DirectX object since the number assigned to MipLevel looks like uninitialized memory. |
|
It is uninitialized. It's part of a union of structs and the valid data depends on the type of texture, so some memory might remain unused. For texture arrays it contains FirstArraySlice and ArraySize. For textures supporting mipmapping there's also MipLevel, etc. Multisampled textures can't have mipmaps, so they don't have that field. The code reads the MipLevel as if the texture were 1D, since that field is in the same memory location for other textures as well. Except when it's not there at all, which caused this bug :) |
Hi all,
today I was experimenting with a multisampling. I found out that the TextureView object in its Tag property has the wrong width and height. If AutoViewport is set to true, when you set the RenderTarget in the beginning it will create a viewport of size 1,1 (or whatever value is in memory).
The problem lies in the TextureView's Initialization method. On the line:
Size = new Size2(Math.Max(1, Texture.Width >> mipLevel), Math.Max(1, Texture.Height >> mipLevel));On a multisampled texture the "mipLevel" value is not 0 but some random number, thus the resulting TextureView object does not have the correct size. These wrong mipLevel values seem to come directly from the RenderTargetView object in
rtv = new TextureView(this, new RenderTargetView(Device, Resource, rtvDescription));inRenderTarget2D.GetRenderTargetViewafter the creation of that DX object, those values are all wrong.
The problem does not seem to occur on a MultiSampleCount of 1,0.
The text was updated successfully, but these errors were encountered: