Skip to content
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

Render combination tests #5832

Merged
merged 2 commits into from
Dec 12, 2017
Merged

Render combination tests #5832

merged 2 commits into from
Dec 12, 2017

Conversation

lbud
Copy link
Contributor

@lbud lbud commented Dec 9, 2017

This PR adds 121 render tests in various combinations of layers. I felt compelled to add these in working on #5826, mostly to ensure that that PR (which eliminates all rendering based on assumed state, and forces renders to specify their own color/depth/stencil state) doesn't cause regressions, but also led to the discovery of #5831 and 5565087#r155843772. These tests add about 22 seconds to the render suite on my (at the time of testing, very busy) machine.

The -opaque/-translucent naming refers to the pass in which a layer is drawn, not necessarily the actual opacity of the layer in question: some of the -translucent layers are actually translucent and some are not, depending on what made rendering results clearer.

@lbud lbud requested a review from jfirebaugh December 9, 2017 00:10
@lbud lbud changed the title Render combinations Render combination tests Dec 9, 2017
@lbud lbud merged commit c112237 into master Dec 12, 2017
@lbud lbud deleted the render-combinations branch December 12, 2017 23:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants