| Age | Commit message (Collapse) | Author |
|---|
|
Loading XML module, registering etree namespaces... etc
on startup for everyone on chance someone may want to export
an SVG from Freestyle is unacceptable.
This shouldn't have got through the review.
also disable loading when built without freestyle.
|
|
|
|
|
|
|
|
Convention for existing export modules
|
|
|
|
|
|
Features:
* Both still image and animation rendering, as well as polygon
fills are supported.
* The exporter creates a new SVG layer for every Freestyle line
set. The different layers are correctly sorted.
* SVG paths use data from line styles, so the base color of a
line style becomes the color of paths, idem for dashes and
stroke thickness.
* Strokes can be split at invisible parts. This functionality is
useful when exporting for instance dashed lines or line styles
with a Blue Print shader
* The exporter can be used not only in the Parameter Editor mode,
but also from within style modules written for the Python
Scripting mode.
Acknowledgements:
The author would like to thank Francesco Fantoni and Jarno
Leppänen for their [[ https://github.com/hvfrancesco/freestylesvg | Freestyle SVG exporter ]].
Differential revision: https://developer.blender.org/D785
Author: flokkievids (Folkert de Vries)
Reviewed by: kjym3 (Tamito Kajiyama)
|
|
its own PLAYER_TARGETDIR_VER
|
|
|
|
|
|
(reported on bf-python mailing-list and in my github (!), let's hope in
the future we get more reports in developer.blender.org instead ;))
|
|
|
|
* Fill brush did not do proper srgb conversion for byte images (reported
by Sebastian Koenig, thanks!)
* Color sampling for palettes did not refresh the toolbar.
|
|
trash with float images.
Issue is uninitialized alpha in the clone brush + a clamping issue for
float images. There's still some 'swimming' and brightness issue here
but I have to do work for the weekly, will investigate further later.
|
|
|
|
That's rather harmless in the master, just could cause some issues with the patches.
|
|
actually use them, thanks to Kevin Dietrich for noticing.
|
|
|
|
Useful because it's effectively the start-point for any strip which is obscured.
|
|
|
|
|
|
|
|
|
|
This was supposed to be an experimental commit, shouldn't be in master at all, sorry for that
This reverts commit 0750e4c4c7eee9ad8f57ebf1243960bd46c7c1f9.
|
|
|
|
|
|
'PROP_XYZ_LENGTH' subtype was missing from list of valid '.x/y/z/w' ones.
|
|
space when only using parent's rotation and parent is rotated.
Just do not use crazyspace correction with childof constraints in this case.
Note this is only a very partial fix (partial use of parent loc on some axes
is still broken in transform), a real fix would probably require a full rewrite
of constraints handling in transform code (a mere static correction matrix
just cannot work in all possible cases, we'd need a full dynamic correction system here).
Anyway, transform code as a whole is horrible. :/
|
|
Replace old code for area lamps which was more like incorrect with more correct
one using the following paper as a reference:
Carlos Urena et al.
An Area-Preserving Parametrization for Spherical Rectangles.
https://www.solidangle.com/research/egsr2013_spherical_rectangle.pdf
Implementation is straight from the paper, currently the rectangle constants are
calculated for each of the samples. Ideally we need to pre-calculate them.
Some comparison images are available there
http://wiki.blender.org/index.php/Dev:Ref/Release_Notes/2.73/Cycles
Reviewers: brecht, juicyfruit
Subscribers: dingto, ton
Differential Revision: https://developer.blender.org/D823
|
|
Avoid using roundf function, since it's oly defined in C99
|
|
|
|
Old behavior of shuffling the meta made it hard to use metas
in a complex edit since you couldn't be sure if exiting a meta would move it in the stack.
|
|
preferences.
After discussion with Campbell left the explicit angle property in for
use with NDOF devices.
|
|
This is so-called GPU limitation boundary hit, told compiler to NOT include
volume bound function, otherwise some real weird things used to happen.
We actually might want to do the same for CPU, inlining everything is not
the way to get fastest code.
|
|
|
|
Explicitly disable SSE kernels in Cycles when this option is used.
|
|
selected.
The bone group colors are not actually used _unless_ when the set is
"custom colors". But they were still editable, which is very confusing.
|
|
|
|
|
|
to dedicated folder
|
|
|
|
Noise function's significant bits are up to 31st bit. This should now
give the same visual result as before, minus the stripes.
Issue pointed out by Anthony Edlin, thanks!
|
|
The flag is called WITH_CPU_SSE, it is ON by default so no one should
be affected by the change really.
This should hopefully fix https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763755
|
|
can otherwise give 0.0 object scale.
|
|
|
|
|
|
|
|
This was way too verbose, heavily factorized the code.
Also made sure only changed data are applied (was not always the case,
especially for curves and lattices), and that we always use raw value
when only one element is affected (was only that way for coordinates).
Note I checked performances, they seem to be roughly the same as previously.
|
|
verts/edges.
Afaik, a hidden BMesh element should never be selected. And this check was done in an
awfully inconsistent way! If it should really be needed, should be added back as a macro
used everywhere!
|
