Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider using WS_EX_NOREDIRECTIONBITMAP #6230

Open
2 tasks
smoogipoo opened this issue Mar 28, 2024 · 1 comment
Open
2 tasks

Consider using WS_EX_NOREDIRECTIONBITMAP #6230

smoogipoo opened this issue Mar 28, 2024 · 1 comment

Comments

@smoogipoo
Copy link
Contributor

smoogipoo commented Mar 28, 2024

As mentioned in https://learn.microsoft.com/en-us/archive/msdn-magazine/2014/june/windows-with-c-high-performance-window-layering-using-the-windows-composition-engine, using WS_EX_NOREDIRECTIONBITMAP eliminates some GPU->GPU or GPU->CPU copies.

Tasks:

  • Add the WS_EX style to SDL. It looks like SDL2 doesn't use CreateWindowEx, but SDL3 does, so it might be easier to wait for SDL3 rather than try to upstream WS_EX styles into SDL2.
  • Potentially change Veldrid to use FlipSequential. The article mentions only this presentation mode is supported, but will have to check on the effect of this.

Usages in the wild: https://grep.app/search?q=WS_EX_NOREDIRECTIONBITMAP

@Susko3
Copy link
Member

Susko3 commented Mar 28, 2024

Better to upstream and wait for SDL3, it's releasing soon so the API will be stabilised. I've also been working on getting "SDL3-CS" bindings automatically generated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants