Set Direct3D feature level 11.1 #903
Open
Conversation
This file contains 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
Dev-Taehui
force-pushed
the
upgrade-feature-level
branch
from
cf65d37 to
7d25714
Compare
Dev-Taehui
force-pushed
the
upgrade-feature-level
branch
from
096ca41 to
3f81e1d
Compare
|
I rebased to winappsdk/main. |
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.
Without Direct3D feature level array, I found that out variable (pFeatureLevel) is D3D_FEATURE_LEVEL_11_0.
In the official Direct2D documentation, featureLevels were created from 11.1 to 9.1 and provided to D3D11CreateDevice. This results out variable pFeatureLevel sets D3D_FEATURE_LEVEL_11_1.
I don't know how this will work, but it doesn't look bad using 11.1.