-
Notifications
You must be signed in to change notification settings - Fork 176
First pass #1
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
First pass #1
Conversation
Generate an animated pattern in the raygen and display it in a window using glfw
field-by-field instead of transmute
Instead of having them on DeviceContext
Instead of having them on DeviceContext
There was a problem hiding this 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 👍
User catch_unwind to guard against panic in C. Remove note about lifetime of closure since it's 'static anyway. Have set_log_callback return a Result instead of panicking on error.
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
This reverts commit e858fdc.
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 |
Just enough of optix to get example 02 working - setting up a pipeline and a ShaderBindingTable, launching an optix kernel.