WIP: Add Texture coordinate render tests #11
No reviewers
Labels
No Label
No Milestone
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender-test-data#11
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "Alaska/blender-test-data:texture-coordinate"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
WIP: Wanted to go through a review process first before deciding to make all the relevant files.
I feel like the render tests need more tests specifically for the texture coordinate node. So I've started this PR to get that going.
At the moment there is only one file (The
Window
output), and this is for two reasons:Window
output is the most important to get a test made for it. Because it was requested by Clément (on the old Blender chat), it's currently broken in OptiX OSL, and was broken oneAPI in the past, and there is currently only one test for it, and it's "frequently" disable as it's part of a denoising test.General things I wanted to note and get feedback on.
Window
output to see what happens for non-camera rays.From Instancer
option on the Texture Coordinate node.Object
option on the Texture Coordinate node.How important do you think it is to try and include tests for these missing configurations? Should I try and merge them into a "main" test or create separate test files?
One other question I had was should I just display the output of the Texture Coordinate node directly to the camera, making it easier to see when something's wrong, or do something like what I've done now (connect the output up to some other node)?
I have attached a example image generated with
texture_coordinate_window.blend
Checkout
From your project repository, check out a new branch and test the changes.