Blender Git Commits

Usual UI messages fixes...

Fix [#36438] Adding Metaball when unit scale is smaller than 0.01 seemingly hangs Blender

Wiresize and rendersize were not handled regarding scene scale, leading to insane precision when working in cm or less...

Dyntopo:

* Actually check if normal recalculation flags exists and set it when
splitting nodes in dyntopo. Right now, nodes that need GPU buffer update
will always get in the list to get their normals generated, but to avoid
a possible future breakage better do it right now.
* Avoid keeping deleted/removed vertices in vertex-to-node and unique
vertex hashes, since some checks rely on those and may go awry if these
still exist. Also they pollute the hashes, and may hurt performance
somewhat.

Fix build with GE and WITH_CXX_GUARDEDALLOC enabledâ?¦

code cleanup: confirm include guards to our convention

Fix crash happening due to missing ob->curve_cache

It's a bit dumb to store render-time bevel list in
object's curve_cache, but that's how blender already
used to work for ages.

Proper fix is suspended for tomorrow :)

Dyntopo:

Turn off pbvh normal update flag after recalculation, saves
recalculating normals every frame when not stroking the mesh.

For this to work reliably with undo we need to support original normals
in the bm_log (was marked as a TODO already in the code), so that
undoing avoids having invalid normals in the mesh (since we don't update
every frame anymore). This was added in this commit as well.

Also added some (disabled) quite paranoid checks in the bmesh valication
code for dyntopo hoping to catch the real normal update issue. No luck
there yet.

Apparently sizeof(unsigned) is 4 bytes on both 32 and 64 bit platforms

For now assume sizeof(int) == 4 for all supported platforms, could be
changed in the future.

Added an assert to functions which depends on this this, so we'll
easily notice bad things happening.

Fix [#36454] 'Tiles' settings in Render/Performance panel don't respect keyframes

These are not animatable! Note this is the case of most (all?) render settings, maybe we should go over both Cycles and internal ones, there are still quite a bunch of them that are marked as animatable... :/

Mistake in revious PATH_MAX commit, sorry!

Attempt to fix compilation error of sort.c

Fix compilation error on platforms where PATH_MAX is not defined

Code cleanup: use bool instead of BOOL/int

Fix read past end of array when drawing tracking markers keyframes

Was introduced by plane track merge.

MCE: usability improvement

Align Clear Before/After into a row and remove
Clear button (which wasn't actually used by
artists).

Merge remained parts of r57520: use use_render argument rather than G.is_rendering

No static vars shall be in mballs now

No need in special hacks for this now :)

And for sure forgot to commit another cleaup patch

--
svn merge -r59259:59260 ^/branches/soc-2013-depsgraph_mt

Forgot this in previous commit

Solves compilation issues on Win and OSX

--
svn merge -r59180:59181 ^/branches/soc-2013-depsgraph_mt

Speedup for guarded allocator

- Re-arrange locks, so no actual memory allocation
(which is relatively slow) happens from inside
the lock. operation system will take care of locks
which might be needed there on it's own.

- Use spin lock instead of mutex, since it's just
list operations happens from inside lock, no need
in mutex here.

- Use atomic operations for memory in use and total
used blocks counters.

This makes guarded allocator almost the same speed
as non-guarded one in files from Tube project.

There're still MemHead/MemTail overhead which might
be bad for CPU cache utilization