Revision b60fa77 by Fabian Schempp (soc-2021-porting-modifiers-to-nodes-merge-by-distance, soc-2021-porting-modifiers-to-nodes_all) August 13, 2021, 06:26 (GMT) |
Added missing line breaks at end of files. |
Revision 4de8acc by Fabian Schempp (soc-2021-porting-modifiers-to-nodes-merge-by-distance, soc-2021-porting-modifiers-to-nodes_all) August 13, 2021, 06:19 (GMT) |
Merge branch 'master' into soc-2021-porting-modifiers-to-nodes-merge-by-distance |
Revision 7df8474 by Fabian Schempp (soc-2021-porting-modifiers-to-nodes-merge-by-distance, soc-2021-porting-modifiers-to-nodes_all) August 13, 2021, 06:18 (GMT) |
Changes based on review bv Hans Goudey (HooglyBoogly) |
August 13, 2021, 06:01 (GMT) |
Docs: tooltip update missing from 3e775a4fc57cfd48954adcf284354312f34d5412 |
August 13, 2021, 05:51 (GMT) |
PyAPI: remove the .py extension requirement for startup registration This was left over from when these scripts were loaded as modules, where their names needed to be compatible with Pythons module naming. Version patch existing files so text with register enabled without a `.py` extension wont start executing on startup. Resolves T89532. |
August 13, 2021, 05:39 (GMT) |
Mesh: replace saacos with acosf for normal calculation The clamped version of acos isn't needed as degenerate (nan) coordinates result in zeroed vectors which don't need clamping. |
August 13, 2021, 05:38 (GMT) |
Merge branch 'master' into geometry-nodes-level-set-nodes |
August 13, 2021, 05:15 (GMT) |
Docs: note that normalize_v# functions zero out input containing nan |
August 13, 2021, 04:41 (GMT) |
Cleanup: remove unused BKE_mesh_calc_normals_mapping functions This supported calculating normals for MPoly array which was copied to an MFace aligned array. Remove the functions entirely since MFace use is being phased out and these function isn't used anywhere. |
August 13, 2021, 04:37 (GMT) |
Cleanup: remove use of BKE_mesh_calc_normals_mapping_simple Use BKE_mesh_calc_normals instead of BKE_mesh_calc_normals_mapping_simple for curve modifier calculation. This only made sense for derived-mesh which is no longer used. |
August 13, 2021, 03:55 (GMT) |
Cleanup: code-comments Use capitalization, remove unnecessary ellipsis. |
August 13, 2021, 03:33 (GMT) |
Cleanup: split BKE_mesh_calc_normals_poly function in two Remove the 'only_face_normals' argument. - BKE_mesh_calc_normals_poly for polygon normals. - BKE_mesh_calc_normals_poly_and_vertex for poly and vertex normals. Order arguments logically: - Pair array and length arguments. - Position normal array arguments (to be filled) last. |
August 13, 2021, 00:21 (GMT) |
Mesh: optimize normal calculation Optimize mesh normal calculation. - Remove the intermediate `lnors_weighted` array, accumulate directly into the normal array using a spin-lock for thread safety. - Remove single threaded iteration over loops (normal calculation is now fully multi-threaded). - Remove stack array (alloca) for pre-calculating edge-directions. Summary of Performance Characteristics: - The largest gains are for single high poly meshes, with isolated normal-calculation benchmarks of meshes over ~1.5 million showing 2x+ speedup, ~25 million polygons are ~2.85x faster. - Single lower poly meshes (250k polys) can be ~2x slower. Since these meshes aren't normally a bottleneck, and this problem isn't noticeable on large scenes, we considered the performance trade-off reasonable. - The performance difference reduces with larger scenes, tests with production files from "Sprite Fight" showing the same or slightly better overall performance. NOTE: tested on a AMD Ryzen TR 3970X 32-Core. For more details & benchmarking scripts, see the patch description. Reviewed By: mont29 Ref D11993 |
August 13, 2021, 00:14 (GMT) |
Compositor: Full frame Vector blur node |
August 13, 2021, 00:14 (GMT) |
Compositor: Full frame Inpaint node |
August 12, 2021, 22:28 (GMT) |
Merge branch 'master' into xr-controller-support |
August 12, 2021, 21:44 (GMT) |
XR: Fix crash/assert on loading controller model When calculating controller model component transforms from glTF node data, it was previously wrongly assumed that the glTF nodes would always contain transform matrix values. However, nodes can instead store their transforms as separate translation/rotation/scale values, in which case the transform matrix needs to be explicitly calculated. This was the case for the Reverb G2 controller models using the Windows Mixed Reality runtime. Special thanks to Werner Trunk for help with testing/debugging. |
August 12, 2021, 21:23 (GMT) |
XR: Improve "Invalid stage ref space" warning Originally mentioned that absolute tracking was disabled, which is wrong because absolute tracking (skipping application of eye offsets) is always available, although it may not give the expected result of persistent tracking origins across sessions if the stage space is unavailable (hence the need for a warning). Now, the warning makes no mention of absolute tracking, instead informing the user that the local space fallback will be used and that they should define tracking bounds via the XR runtime if they wish to use the stage space. |
August 12, 2021, 20:32 (GMT) |
Cleanup: clang-format |
August 12, 2021, 20:28 (GMT) |
Cleanup: fix compiler warnings |
|
|
|


Master Commits
MiikaHweb | 2003-2021