direct3d11-development

Create the DXGI factory and device explicitly, choose adapters via DXGI enumeration rather than vendor assumptions, and use a flip-model swap chain (FLIP_DISCARD or FLIP_SEQUENTIAL) with at least two buffers. Enable BGRA support when Direct2D, Win2D, or XAML interop is required.

Use the WinUI 3 Microsoft.UI.Xaml.Controls.SwapChainPanel with a composition swap chain created via IDXGIFactory2::CreateSwapChainForComposition, then attach it through the panel's native interop interface. Keep XAML DIP dimensions separate from render-target pixels and never block the UI thread on GPU work.

No. Direct3D 11's shader ceiling is Shader Model 5.0, even when a device reports 12_x feature levels. Shader Model 6 with DXC is a Direct3D 12 path, and feature level, API version, shader model, and DXGI version are separate concepts.

Common causes include failed device or swap-chain creation, missing RTV binding, wrong viewport, incorrect input layout, constant-buffer packing mismatches, or a removed device. Reduce the frame to a clear-only render and check the debug layer output and Present HRESULT first.

Stop submitting work, call GetDeviceRemovedReason for diagnostics, release all device-dependent resources, and recreate the full device, swap chain, and resource graph from CPU-side state. Recreating only the swap chain while keeping old-device resources is incorrect.

Not directly. Flip-model swap chains cannot be multisampled, so render into a separate MSAA color target with matching depth, resolve it into the single-sample back buffer, then present. Always verify sample counts with CheckMultisampleQualityLevels.