Blender Git Statistics -> Developers -> pmoursnv

Patrick Mours (pmoursnv)

Total Commits : 24
Master Commits : 24
Branch Commits : 0
First Commit : August 26, 2019
Latest Commit : October 21, 2019 (Yesterday)

Commits by Month

DateNumber of Commits
October, 20195
September, 20195
August, 201914

Favourite Files

FilenameTotal Edits
kernel_path.h5
device_optix.cpp5
kernel_types.h4
svm_bevel.h4
svm_ao.h3
kernel_volume.h3
svm_brick.h3
kernel_shader.h3
kernel_emission.h3
mesh.cpp2

File Changes

ActionTotalPer Commit
Added60.3
Modified1385.8

Code Changes

ActionTotalPer Commit
Lines Added1 23158.6
Lines Removed90443.0

Latest commits Feed

Revision 200267e by Patrick Mours (master)
14 hours 27 min ago
Merge branch 'blender-v2.81-release'
Revision d0cba5c by Patrick Mours (master)
15 hours 57 min ago
Fix T70937: Cycles fails in viewport when rendering with OptiX

Was caused by D6068, which did not handle "MEM_PIXELS" memory
when not in background mode. Before that it always fell back to using
generic device memory, so restoring that behavior. In future this
should be changes to use OpenGL interop for optimal performance.
Revision 8378db4 by Patrick Mours (master)
October 18, 2019, 10:23 (GMT)
Cycles: Fix out of memory when rendering some scenes with OptiX that work with CUDA

The OptiX implementation wasn't trying to allocate memory on the host if device allocation failed, while the CUDA implementation did. This copies the implementation over to OptiX to remedy that.

Differential Revision: https://developer.blender.org/D6068
Revision 0091b84 by Patrick Mours (master)
October 2, 2019, 11:23 (GMT)
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
Revision 8dd9172 by Patrick Mours (master)
October 1, 2019, 18:01 (GMT)
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
Revision b89a168 by Patrick Mours (master)
September 30, 2019, 13:38 (GMT)
Fix "denoise_animation" tests with OptiX in Cycles

The OptiX device only loads the denoising kernels when the "use_denoising" feature is active. This was not set by the calling code however and therefore they were never loaded and attempting to launch them failed (see T69801).

Reviewed By: brecht

Differential Revision: https://developer.blender.org/D5946
Revision 91f6aa6 by Patrick Mours (master)
September 30, 2019, 12:05 (GMT)
Fix memory leak after using OptiX in Cycles

The "optix_devices" array was not freed on exit, which caused a memory leak (see T69801).

Reviewed By: brecht

Differential Revision: https://developer.blender.org/D5944
Revision a1e4008 by Patrick Mours (master)
September 25, 2019, 12:22 (GMT)
Cycles: Fix undefined behavior which can causes crashes with a misaligned address error

Cycles casts a pointer from ShaderDataTinyStorage to ShaderData, these structs by default had different alignments however (the former was 1-byte aligned, the latter 16-byte). This caused undefined behavior on at least the CUDA platform. Forcing both structs to use the same alignment fixes this.

CUDA toolkits newer than 10.1 run into this because of a compiler optimization.

Reviewed By: brecht

Differential Revision: https://developer.blender.org/D5883
Revision a2b52dc by Patrick Mours / Brecht Van Lommel (master)
September 13, 2019, 09:50 (GMT)
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
Revision 53932f1 by Patrick Mours / Brecht Van Lommel (master)
September 13, 2019, 09:46 (GMT)
Cycles: add Optix support in the kernel

This adds all the kernel side changes for the Optix backend.

Ref D5363

MiikaHweb - Blender Git Statistics v1.06
By: Miika HämäläinenLast update: Nov-07-2014 14:18 MiikaHweb | 2003-2019