| Age | Commit message (Collapse) | Author |
|---|
|
2016 GSOC project by @nathanvollmer, see D2150
- Mirrored painting and radial symmetry, like in sculpt mode.
- Volume based splash prevention,
which avoids painting vertices far away from the 3D brush location.
- Normal based splash prevention,
which avoids painting vertices with normals opposite the normal
at the 3D brush location.
- Blur mode now uses a nearest neighbor average.
- Average mode, which averages the color/weight
of the vertices within the brush
- Smudge mode, which pulls the colors/weights
along the direction of the brush
- RGB^2 color blending, which gives a more accurate
blend between two colors
- multithreading support. (PBVH leaves are painted in parallel.)
- Foreground/background color picker in vertex paint
|
|
Differential Revision: https://developer.blender.org/D2857
|
|
Replace iroundf with round_fl_to_int, add other types
|
|
|
|
|
|
|
|
Only lock tri's facing different directions.
Needed because scanfill creates zero area faces.
|
|
mistakenly considering the state as degenerated"
This reverts commit a8f11f5422afa01608817755eea310e987f896be.
Result is no longer symmetrical, will investigate a different fix.
|
|
|
|
|
|
obscured
by the transform constraint lines
Ported over e7395c75d504af2c2f720f43ea27b93e04a378e4 from the
greasepencil-object branch. I should've fixed this ages ago, but
couldn't figure out why at the time.
|
|
|
|
Make it clear that the packed file could not be saved back out to disk
at the specified path (e.g. destination directory doesn't exist).
|
|
Avoids having to repeat obfuscating castings everywhere...
|
|
Even if pointer assignment may be atomic, it does not prevent reordering
and other nifty compiler tricks, we need a memory barrier to ensure not
only that transferring pointer from wip array to final one is atomic,
but also that all previous writing to memory are “flushed” to
(visible by) all CPUs...
Thanks @sergey for finding the potential (though quite unlikely) issue.
|
|
Useful for baking, so UV's can be moved outside the image
and not used to bake pixels (but still used for display).
D2801 by @Zuorion
|
|
|
|
considering the state as degenerated
|
|
tracking
|
|
|
|
|
|
Was a dangling pointer to a freed memory left behind.
|
|
This fixes a mistake in rBefd5e3c25401b43cbd7f909418835bb570db1ab3
|
|
It has been deprecated since at least macOS 10.9 and fully removed in 10.12.
I am unsure if we should remove it only in 2.8. But you cannot build blender with it supported when using a modern xcode version anyway so I would tend towards just removing it also for 2.79 if that ever happens.
Reviewers: mont29, dfelinto, juicyfruit, brecht
Reviewed By: mont29, brecht
Subscribers: Blendify, brecht
Maniphest Tasks: T52807
Differential Revision: https://developer.blender.org/D2333
|
|
|
|
Apparently, we already had some code to deal with this. So for now just
added some extra dependencies needed for latest requests.
|
|
|
|
Matches text-editor, console & text-button.
|
|
|
|
|
|
exported
|
|
This reverts commit 8ad479a3227e36b201f740a127c08e29950bb219.
|
|
|
|
|
|
Wrong condition in asserts...
|
|
Spotted by Joshua Leung (@aligorith), thanks!
Should probably be backported to 2.79a should we do it.
|
|
Required to generate valid doc for such arrays!
|
|
Allows for multiple sentences not to look strange.
Convention not to include in RNA remains.
|
|
|
|
|
|
`depth_get` is called in most of the time. So not worth going through so many conditions
|
|
|
|
Forgot some initialization.
|
|
Tentative fix, since I cannot reproduce thenissue for some reason here
on linux.
Core of the problem is pretty clear though, thanks to Germano Cavalcante
(@mano-wii): another thread could try to use looptris data after worker
one had allocated it, but before it had actually computed looptris.
So now, we use a temp 'wip' pointer to store looptris being computed
(since this is protected by a mutex, other threads will have to wait on
it, no possibility for them to double-compute the looptris here).
This should probably be backported to 2.79a if done.
|
|
The issue was caused by threading conflict around looptris: it was possible
that DM will return non-NULL but non-initialized array of looptris.
Thanks Campbell for second pair of eyes!
|
|
|
|
|
|
This allows to have different macro headers without them sharing
similar names to regular C modules.
|
|
Only show & use when running in debug mode.
|
|
|
