Blender Git Commits

Fix bevel crash #33801, when first edge of a vertex is wire.

simplify fcm_generator_verify() using MEM_recallocN

style cleanup

style cleanup

Motion Path drawing tweaks and fixes

* Green (current frame) color now extends to the segments on either side of the
current frame point. This is so that the path is more visible (especially on the
black/dark side), as those segments were prone to being interpolated such that
they became invisible

* Added padding for frame number strings so that they do not overlap the dots
anymore

* Fixed off-by-one error, which meant that the frame number for the first frame
step (white dot) didn't get shown

comment fix.

Looks like no scaling is done elsewhere on blender for this code. I hope
this bug is squashed for good.

* Fix for #31581. The issue was that we scaled the face prior to
projecting it. The original paper suggests to simply interpolate between
the two points of an edge if the distance of the point to that edge is
smaller than a threshold.

* Fixed both 3D and 2D code to utilize this. Possibly other places in
blender where this scaling is done will have to be adjusted.

* Changed vertex interpolation to use 2D interpolation, since it already
did projection on plane and 2d calculations are faster.

* Also added notifier on hard recalc when uvcalc_transfor_correction is
used. Results in instant feedback on UV editor when edge sliding.

Cycles / Tile Rendering:
* Added new option to chose the tile order.
In addition to the "Center" method, 4 new methods are available now, like Top -> Bottom and Right -> Left.

Thanks to Sergey for code review and some tweaks!

ui_lists shall be NULLed in BKE_area_region_copy

Otherwise it'll be nasty crashes when, say, adding and removing
screens with lists visible on the screen.

Thanks Ton for assisting looking into this issue :)

dont copy the mvert array in DM_to_bmesh_ex()

Make options for background gradient more organized.

This was difficult to do because we group theme colours and display them
together in user preferences. To make the background options more
presentable and keep them grouped and separate, I needed to group the
two gradient colours somehow. I added a separate ThemeSpaceGradient RNA
struct as opposed to ThemeSpaceGeneric. This struct is the same as
ThemeSpaceGeneric but it lacks the window background option (which does
nothing now) and includes the UiGradient struct which now has both
gradient colours. I modified the clear functions to use a new high
colour from the gradient. Now all options appear grouped and any other
editor that may use a gradient for the window background may do so.

Also corrected incorrect MAIN_VERSION_ATLEAST macro, it would not detect
versions correctly

minor improvement to CustomData_bmesh_merge(), allocate the correct size pool rather then always 512.

Bug fix 33778

The user pref "Mini Axis Brightness" didn't work.
Note it's only accissble via the outliner now.

Fix #33735: sequencer crash when using rendered preview

Issue was caused by preview job starting just moment before
sequencer starts rendering. This lead to threading conflicts
since renderer itself is not thread-safe.

Now all preview jobs would be killed before sequencer starts
rendering stack when final render for preview is enabled.

add error check for qtcreator&netbeans project file generators to quit early if cmake fails.

Add normal_flip() member to Python BMesh's Face.

add area_poly_v3_max() for use with area_poly_v3

Motion tracking API change

Replace Tracks.add(count, frame) with Tracks.new(name, frame)
which will return newly created track. Before there was no
reliable way to get newly created tracks.

Track.insert_frame used to create markers with zero pattern size

In most cases it's harmles since this call was intended to be used
for importers only where pattern size was overriding after creation
anyway. But better don't allow things which will work unpredictable.

split viewport clearing into its own function: view3d_main_area_clear()