WebGLBackend: Fix context parameter. #30413
Merged
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.
Related issue: -
Description
While trying to fix foveation with
XRManager
, I have noticed that the WebGL 2 rendering context is always created withantialias
set totrue
. This has a side effect onXRManager
as well as performance implications.The
antialias
context parameter can always be set tofalse
since the engine applies MSAA with custom renderbuffers.With this change the framerate of the demanding SSAA demo improves from 45 to 53 FPS with a WebGL 2 backend (tested with Firefox). In fact, the overall performance of the WebGL backend has been improved since up to now the renderer applied MSAA on the fullscreen quad of the output pass.