Revision 41b3388 by Hans Goudey (temp-geometry-nodes-attribute-domain-conversion, temp-geometry-nodes-normal-attribute) January 22, 2021, 21:23 (GMT) |
Refactor the "normal" attribute reading and writing |
January 22, 2021, 18:30 (GMT) |
Merge branch 'blender-v2.92-release' |
January 22, 2021, 18:30 (GMT) |
Cleanup: remove unused render camera code |
January 22, 2021, 18:24 (GMT) |
Fix T84745: more build errors with TBB 2021 * tbb::blocked_range moved to a different namespace and since the fix is non-trivial, remove some unused code that used this. * Task group priorities are no longer supported. It's unclear if they are useful at all right now and even set correctly, for now all tasks are equal priority with TBB 2021. |
January 22, 2021, 18:24 (GMT) |
Fix vertex color baking using wrong color space Now light baking should match the render. |
Revision b280d53 by Hans Goudey (temp-geometry-nodes-attribute-domain-conversion, temp-geometry-nodes-normal-attribute) January 22, 2021, 18:09 (GMT) |
Merge branch 'master' into temp-geometry-nodes-normal-attribute |
January 22, 2021, 17:28 (GMT) |
Merge branch 'blender-v2.92-release' |
January 22, 2021, 17:08 (GMT) |
Fix: Mouse presses in some areas do not set active modifier There are a couple of operations that are meant to set the active modifier that currently don't. The first is a mouse press on the drag icon on the right of the header, and the second is mouse presses on modifier sub-panels headers. This was an oversight in the implementation, especially the second, because the blank space on the right of a sub-panel header often looks just like the blank space elsewhere on the modifier's panel that *does* set the active modifier. Note that this purposefully doesn't include collapsing and expanding the modifier as operations that set the active, since regardless of whether that makes sense, it wasn't in the agreed upon design, which would ideally not need changing for 2.92. Differential Revision: https://developer.blender.org/D10155 |
January 22, 2021, 16:37 (GMT) |
Fix crashes from recent refactor rB131a758b6f88. Much better to add a relation entry for all IDs, even if they are not connected to any other ID. |
January 22, 2021, 15:58 (GMT) |
Fix memory leak when opening file browser The name string of each file was duplicated but not freed. The new flag to ensure the file-list frees the name wasn't set. Mistake in ca475479eb26. |
January 22, 2021, 15:08 (GMT) |
Cycles: optimize device updates This optimizes device updates (during user edits or frame changes in the viewport) by avoiding unnecessary computations. To achieve this, we use a combination of the sockets' update flags as well as some new flags passed to the various managers when tagging for an update to tell exactly what the tagging is for (e.g. shader was modified, object was removed, etc.). Besides avoiding recomputations, we also avoid resending to the devices unmodified data arrays, thus reducing bandwidth usage. For OptiX and Embree, BVH packing was also multithreaded. The performance improvements may vary depending on the used device (CPU or GPU), and the content of the scene. Simple scenes (e.g. with no adaptive subdivision or volumes) rendered using OptiX will benefit from this work the most. On average, for a variety of animated scenes, this gives a 3x speedup. Reviewed By: #cycles, brecht Maniphest Tasks: T79174 Differential Revision: https://developer.blender.org/D9555 |
January 22, 2021, 15:05 (GMT) |
Refactor BMain relations temp data. `bmain.relations` is used to store temp data of relations between IDs, to speed-up some complex processes heavily relying on such information. Previous implementation was failry unclear/confusing, and required a not-so-nice hack to 'tag' some ID as processed. New code changes as such: * Using `from`/`to` naming (instead of `user`/`used`). * More clear separation between `to` `id_pointer` and `from` one, using an union instead of hacking around difference between `ID *` and `ID **` pointers. * Adds storage of `session_uuid` informations (mainly useful as debug/ensuring proper consistency of data currently). * Adds a structure per ID in the mapping. This enables possibility of storing tags (and potentially more data in the future) per-ID, without polluting the IDs themselves with very short-life info. Differential Revision: https://developer.blender.org/D10164 |
January 22, 2021, 14:33 (GMT) |
EEVEE: Depth Of Field: Fix issue with slight focus filtering perf. The issue was caused by wrong tile values. |
January 22, 2021, 14:32 (GMT) |
EEVEE: Depth Of Field: Fix issue with neighborhood comparison The filter was not using the correct UVs. |
January 22, 2021, 14:31 (GMT) |
LibOverride: Add an 'post apply' callback to IDTypeInfo. Currently this is needed to properly tag PointCache's for info update (fixes an issue reported in T82503). Suspect we may need this in more cases in the future though, RNA assign/update processes are not always 100% enough to deal with complicated corner cases. |
Revision 178405e by Hans Goudey (temp-geometry-nodes-attribute-domain-conversion, temp-geometry-nodes-normal-attribute) January 22, 2021, 14:14 (GMT) |
Test derived normals write attribute |
January 22, 2021, 13:32 (GMT) |
Merge branch 'blender-v2.92-release' |
January 22, 2021, 13:31 (GMT) |
Cycles: Fix usage of double floating precision in CNanoVDB Double floating point precision is an extension of OpenCL, which might not be implemented by certain drivers, such as Intel Xe graphics. Cycles does not use double floating point precision, and there is no need on keeping doubles unless there is an explicit decision to use them. This is a simple fix from Cycles side to replace double floating point type with a type of same size and alignment rules. Inspired by Brecht and Patrick. Tested on NVidia Titan V, Radeon RX Vega M, and TGL laptop. Differential Revision: https://developer.blender.org/D10143 |
Revision 3d712fb by Hans Goudey (temp-geometry-nodes-attribute-domain-conversion, temp-geometry-nodes-normal-attribute) January 22, 2021, 13:20 (GMT) |
Merge branch 'master' into temp-geometry-nodes-normal-attribute |
January 22, 2021, 12:46 (GMT) |
Functions: use better conversion from float2 to float3 Previously float2 was converted to float3 by implicitly converting to a float pointer first, which was then passed to the float3 constructor. This leads to uninitialized memory in the z component of the new float3. Ideally this should be solved in float2/float3 itself, but my first fix for that resulted in a compile error: rB6ac0a3d83c8e5a39bd5356aa0d68e3166bd91e82 This is an alternative fix that can be used for now. Will have to look into the conversion in more detail again. |
|
|
|


Master Commits
MiikaH:n Sivut a.k.a. MiikaHweb | 2003-2021