Skip to content

Conversation

anderslanglands
Copy link
Collaborator

Just enough of optix to get example 02 working - setting up a pipeline and a ShaderBindingTable, launching an optix kernel.

Copy link
Member

@RDambrosio016 RDambrosio016 left a comment

Choose a reason for hiding this comment

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

Looks great as a first prototype edition. There is obviously a lot to change, especially in terms of docs, but as a start it is great 👍

@RDambrosio016 RDambrosio016 mentioned this pull request Oct 31, 2021
11 tasks
This switches out *T for CUdeviceptr in DevicePointer. This has the
knock-on effect of removing a lot of "pretend we're a CPU pointer" stuff
from downstream types like DeviceSlice.
Generate an animated pattern in the raygen and display it in a window using glfw
@RDambrosio016
Copy link
Member

Having to rebase this and fix conflicts every couple of weeks is pretty annoying, so i will probably merge this then finalize the cust changelog and release 0.3. Then OptiX work can be done later

@RDambrosio016 RDambrosio016 added C-cust Category: CPU-side CUDA Driver API C-OptiX (Device) Category: Device (GPU)-side OptiX C-OptiX (Host) Category: Host (CPU)-side OptiX enhancement New feature or request labels Jan 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-cust Category: CPU-side CUDA Driver API C-OptiX (Device) Category: Device (GPU)-side OptiX C-OptiX (Host) Category: Host (CPU)-side OptiX enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants