Implement LowLatencyDxgiSwapChain window transparency#20879
Draft
lindexi wants to merge 18 commits intoAvaloniaUI:masterfrom
Draft
Implement LowLatencyDxgiSwapChain window transparency#20879lindexi wants to merge 18 commits intoAvaloniaUI:masterfrom
lindexi wants to merge 18 commits intoAvaloniaUI:masterfrom
Conversation
…face do not set size.
Solve the `transaction` do not be disposed when CreateSurface exception.
This reverts commit da0af79.
|
You can test this PR using the following package version. |
|
You can test this PR using the following package version. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does the pull request do?
See #20615
Base on: #20757
expectedPixelSizeinDxgiRenderTarget.BeginDrawCoreWhat's the difference between this change and DirectComposition in
Transparencymode?When using
LowLatencyDxgiSwapChainwithTransparencymode, theIDXGISwapChain1object is created via theCreateSwapChainForCompositionmethod. Rendering operations are then executed using this SwapChain; once rendering is complete, theIDXGISwapChain1.Presentmethod is invoked to submit the rendered content.In contrast, DirectComposition directly acquires a texture for rendering by calling
IDCompositionVirtualSurface.BeginDraw. After finishing rendering, theIDCompositionDevice2.CommitandIDCompositionDevice2.WaitForCommitCompletionmethods are called to wait for the rendering process to finalize.Based on my practical tests, I observed that using
LowLatencyDxgiSwapChaininTransparencymode yields higher frame rates and lower rendering latency compared to DirectComposition.Testing the RenderDemo in my device:
// In RenderDemo App.xaml.cs: static AppBuilder BuildAvaloniaApp() => AppBuilder.Configure<App>() + .With(new Win32PlatformOptions + { + OverlayPopups = true, + CompositionMode = [Win32CompositionMode.LowLatencyDxgiSwapChain] + }) .UsePlatformDetect() .WithDeveloperTools() .LogToTrace();What is the current behavior?
What is the updated/expected behavior with this PR?
How was the solution implemented (if it's not obvious)?
Checklist
Breaking changes
Obsoletions / Deprecations
Fixed issues
Fixes #20615