-
Notifications
You must be signed in to change notification settings - Fork 165
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
opengles3 #134
Comments
ms-master supports OpenGL ES 3.0 on most modern PCs and devices. Please see this section of our README for more details: https://github.com/Microsoft/angle#feature-support |
Hi Austin,
Thank you for your quick reply. Is the master branch now supporting
developing the hololens as well?. When I merged the master with
holol_experimental branch the winrt/10 angle solution, it looks the same as
holo experimental branch.
Can you confirm please that angle solution in winrt/10 is using opengles 3
Regards
Elhassan
…On 06 Oct 2017 6:52 PM, "Austin Kinross" ***@***.***> wrote:
ms-master supports OpenGL ES 3.0 on most modern PCs and devices. Please
see this section of our README for more details:
https://github.com/Microsoft/angle#feature-support
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#134 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AGliHd7J_u97ePB2LOWO5BRzW-EluLOxks5splrigaJpZM4PwgYn>
.
|
Hi Elhassan, thanks for clarifying your branch. Note that this 'Issues' section is shared between all of this repository's branches (including ms-master and ms-holographic-experimental), so an issue against a specific branch needs to say which branch it is referring to. ms-master currently doesn't support HoloLens, and it has diverged substantially from ms-holographic-experimental so I don't recommend attempting to merge them. @MikeRiches owns the ms-holographic-experimental branch and can maybe comment on its OpenGL ES 3.0 status. Thanks! |
Are there any plan to support the use of opengles3.0 instead opengles2.0 for this branch soon?
The text was updated successfully, but these errors were encountered: