3 Commits

Author	SHA1	Message	Date
Patrick Mours	0091b84df0	Fix T70268: Render failures with Vector pass active with OptiX in Cycles ... Rendering would produce invalid results or crash if the Vector pass was active but motion blur was inactive. This caused the OptiX BVH to be built with motion (because objects reported motion available), but the pipeline to be built without motion support (since with disabled motion blur this is not in the list of requested features). The two are not compatible and therefore caused issues. This patch fixes that by not building the BVH with motion if motion blur is not active (which makes sense). Reviewed By: brecht Differential Revision: https://developer.blender.org/D5968	2019-10-02 13:23:29 +02:00
Patrick Mours	8dd9172aa2	Fix "motion_blur" tests with OptiX in Cycles ... Curves with motion blur produced wrong results with OptiX (T69801). This is because the AABBs for the motion steps were calculated from incorrect attribute data because the offset into the attribute data array was incorrect. Reviewed By: brecht Differential Revision: https://developer.blender.org/D5961	2019-10-01 20:01:51 +02:00
Patrick Mours	a2b52dc571	Cycles: add Optix device backend ... This uses hardware-accelerated raytracing on NVIDIA RTX graphics cards. It is still currently experimental. Most features are supported, but a few are still missing like baking, branched path tracing and using CPU memory. https://wiki.blender.org/wiki/Reference/Release_Notes/2.81/Cycles#NVIDIA_RTX For building with Optix support, the Optix SDK must be installed. See here for build instructions: https://wiki.blender.org/wiki/Building_Blender/CUDA Differential Revision: https://developer.blender.org/D5363	2019-09-13 11:50:11 +02:00