D3D11On12
netwake
D3D11On12 | netwake | |
---|---|---|
3 | 3 | |
255 | 53 | |
3.1% | - | |
4.0 | 0.0 | |
2 months ago | over 2 years ago | |
C++ | C | |
MIT License | BSD 2-clause "Simplified" License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
D3D11On12
-
Windows 95 went the extra mile to ensure compatibility of SimCity, other games
Intel's boards really only support DX12, which streamlines much of the compatibility work they'd have to do. Earlier DX versions are handled with wrapper libraries/drivers that translate to DX12 (eg https://github.com/microsoft/D3D11On12).
- DXVK alternative for DX11 (D3D11On12)
-
On the DirectX 11 announcement
What do you think about https://github.com/microsoft/D3D11On12 ?
netwake
-
Windows 95 went the extra mile to ensure compatibility of SimCity, other games
I wrote one to try. It also uses runtime feature detection to enable modern stuff like theming and high-DPI on Windows version that support it.
-
The Windows Malloc() Implementation Is a Trash Fire
> Ideally you'd like to build for all targets, including older systems, from a single, modern environment (this is trivial in Windows)
https://github.com/sjmulder/netwake does what you're talking about, but it does a lot of gymnastics to make it work, and it also needs to use MinGW rather than MSVC.
-
Windows 11: a survey of text boxes
> if you wrote a Windows Desktop app in the last 30 years, the only way it would still be supported today ... is if it was based directly on the old Win32 API
I thought the same and did just that to see if it holds true: https://github.com/sjmulder/netwake
By default you get Windows 95 styling and Windows 3 fonts. You have to opt into 'visual styles' (introduced in XP) with a declaration in the app manifest and have to manually query and use the system font. DPI awareness is also opt in and puts all the work (sizing/positioning, scaling/reloading fonts) on you. But when you do that, it does look fine on Windows 10.
Not so much on Windows 11. Some of the widgets have been updated to mimic the new style but when you put it together it looks messy and old fashioned (e.g. fonts + you don't get the new context menus).
I'm curious to learn how one would create a 'proper' Windows app without having to reimplement the system's widget styling.
What are some alternatives?
d912pxy - DirectX9 to DirectX12 API proxy for Guild Wars 2
TeamFortress2 - TF2 Source Code leaked on 22/4/2020