Direct2D 平铺限制？

Question

Is there a limitation on how much Direct2D tile size can grow?

In D2D1_RENDERING_CONTROLS I can set the tiling of the Direct2D buffering.

            D2D1_RENDERING_CONTROLS r4c = {};
            m_d2dContext->GetRenderingControls(&r4c);
            if (r4c.tileSize.width < (UINT32)wi || r4c.tileSize.height < (UINT32)he)
            {
                r4c.tileSize.width = wi;
                r4c.tileSize.height = he;
                m_d2dContext->SetRenderingControls(r4c);
                m_d2dContext->GetRenderingControls(&r4c);
                nop();
            }

When it's up to 4K resolution, the rendering of an effect gets the whole texture at one pass:

When I go up to 8K, then there's tiling, indicating that Direct2D passes the texture in more than one pass:

This is a killing for my custom HLSL effects that require the whole texture to operate, like this special lighting effect.

Is this an intended feature? A bug? An undetected issue? Would I be forced to go to OpenGL rendering eventually?

This is not related to my GF card - I tested with an RTX 2070, the same error occurs.

Edit: here is a full VS 2019 solution with a simple swirl effect.

// When you try plain 1920x1080 or 3840x2160, ok
int wi = 7680;
int he = 4320;
// With the above, the swirling is tiled x4.

Edit: On EndDraw(), I have this in debug output:

Exception thrown at 0x00007FFBE6324B89 in d2dbug.exe: Microsoft C++ exception: _com_error at memory location 0x000000EBC4D5CE58.
Exception thrown at 0x00007FFBE6324B89 in d2dbug.exe: Microsoft C++ exception: _com_error at memory location 0x000000EBC4D5CE58.
Exception thrown at 0x00007FFBE6324B89 in d2dbug.exe: Microsoft C++ exception: _com_error at memory location 0x000000EBC4D5CE58.

Answer 1

There is an answer from Microsoft.

I would recommend using a bitmap as the input to the effect rather than the image source. Simply drawing the image source into that bitmap should work. They could also create the bitmap from a WIC bitmap source using the D2D API CreateBitmapFromWicBitmap.

This works, although the output of an effect returns a ID2D1Image which then has to be converted to a ID2D1Bitmap by the code here .

I'm still discussing with them the performance issues that might occur when there are too many effects in the chain and each of them has to convert manually to an ID2D1Bitmap.