Setting numViews value in glFramebufferTextureMultiviewOVR call #1047
Conversation
This file contains hidden or 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
… as standard texture2d arrays
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Was just missed when you did the inital work I think.
One thing I think would be worth looking at is a way to set baseViewIndex and numViews manually. I can't think of a way though without adding new variables somewhere.
Users might have a situation where they want to render more views than the hardware is capable of in a single pass but they may also want to keep all the views in a single texture array. If they could set the baseViewIndex and numViews manually they could say render me from 0-3 in one pass then 4-7 in another pass.
Just a thought.