Blender Git Statistics -> Developers -> pmoursnv
Patrick Mours (pmoursnv)
Total Commits : 28
Master Commits : 28
Branch Commits : 0
First Commit : August 26, 2019
Latest Commit : November 5, 2019
Commits by Month
| Date | Number of Commits | |
|---|---|---|
| November, 2019 | 4 | |
| October, 2019 | 5 | |
| September, 2019 | 5 | |
| August, 2019 | 14 | |
Favourite Files
| Filename | Total Edits |
|---|---|
| device_optix.cpp | 5 |
| kernel_path.h | 5 |
| kernel_types.h | 4 |
| svm_bevel.h | 4 |
| kernel_emission.h | 3 |
| svm_ao.h | 3 |
| svm_brick.h | 3 |
| kernel_volume.h | 3 |
| kernel_shader.h | 3 |
| device_memory.h | 2 |
File Changes
| Action | Total | Per Commit |
|---|---|---|
| Added | 6 | 0.2 |
| Modified | 141 | 5.0 |
Code Changes
| Action | Total | Per Commit |
|---|---|---|
| Lines Added | 1 240 | 53.9 |
| Lines Removed | 911 | 39.6 |
Latest commits 
November 5, 2019, 13:20 (GMT) |
Merge branch 'blender-v2.81-release' |
November 5, 2019, 13:19 (GMT) |
Fix Cycles failing to compile when "WITH_CYCLES_LOGGING" is off |
November 4, 2019, 17:10 (GMT) |
Merge branch 'blender-v2.81-release' |
November 4, 2019, 17:09 (GMT) |
Fix T71123: OptiX error in Cycles viewport when adding HDRI Cycles did not update the "is_enabled" flag on lights when they were synchronized again, which caused all lights disabled by "LightManager::disable_ineffective_light" to be disabled indefinitely. As a result the OptiX kernels were not reloaded with correct features when a change to a light was made. This fixes that by updating the "is_enabled" flag during synchronization. Differential Revision: https://developer.blender.org/D6141 |
October 21, 2019, 13:53 (GMT) |
Merge branch 'blender-v2.81-release' |
October 21, 2019, 12:23 (GMT) |
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. |
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 |
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 |
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 |
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 |
MiikaHweb - Blender Git Statistics v1.06
