Skip to content

Even more tests for render-fidelity test suite#4537

Closed
bhouston wants to merge 16 commits intogoogle:masterfrom
bhouston:even-more-tests
Closed

Even more tests for render-fidelity test suite#4537
bhouston wants to merge 16 commits intogoogle:masterfrom
bhouston:even-more-tests

Conversation

@bhouston
Copy link
Contributor

In this PR I add the following glTF files to the test suite along with Goldens for filament, Babylon and model-viewer:

  • khronos-ClearCoatCarPaint
  • khronos-ClearCoatWicker
  • khronos-GlassHurricaneCandleHolder
  • khronos-GlassVaseFlowers
  • khronos-NegativeScaleTest

This builds upon my other PR here (#4535), so there is additional changes here, but if the other PR is merged then this PR becomes I think a single change.

Copy link
Contributor

@elalish elalish left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks great, thanks Ben! I'm curious why the CI is having trouble - perhaps the anisotropy renders are extra sensitive to GPU rounding differences? Can you try to render these on a couple of different machines (OS, GPU) and maybe we can figure out what the difference is? I'd love to be able to just get the generated image from the CI, but I've never figured out how to do that.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is three-gpu-pathtracer broken? I had heard it may not be keeping up with three.js versions...


git fetch origin
git reset --hard origin/master
git submodule update --init --recursive
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💯

@bhouston
Copy link
Contributor Author

I'm curious why the CI is having trouble - perhaps the anisotropy renders are extra sensitive to GPU rounding differences?

For now I am removing the problematic tests to get the good stuff merged in, and we can revisit the problematic stuff later.

@bhouston
Copy link
Contributor Author

Closing as I've merged this branch into this other related PR: #4535

@bhouston bhouston closed this Oct 27, 2023
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