| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
C++11 doesn't need the space between '> >' in a nested templated
declaration, so instead of `std::vector<std::pair<a, b> >` we can now
write `std::vector<std::pair<a, b> >`.
|
|
It's now possible to export curves and NURBS as mesh data to Alembic.
This allows artists to do any crazy thing on curves and export the
visual result to Alembic for interoperability with other software (or
caching for later use, etc.). It's an often-requested feature.
This works around T60503 and the fixes export part of T51311.
Note that exporting zero-width curves is currently not supported, as
exporting a faceless mesh (e.g. just edges and vertices) is not
supported by the mesh writer at all.
To test, create a curve with thickness (for example extruded), export to
Alembic and check the 'Curves to Mesh' checkbox in the export options.
Reviewers: sergey
Differential Revision: https://developer.blender.org/D4213
|
|
I moved most of the `AbcMeshWriter` code to a new class
`AbcGenericMeshWriter`. The latter is an abstract class and does not
make any assumptions about the type of Blender object being written.
This makes it possible to write metaballs, curves, nurbs surfaces, etc.
as mesh to Alembic files.
The `AbcMeshWriter` class now is the concrete implementation of
`AbcGenericMeshWriter` for writing mesh objects.
Reviewers: sergey
Differential Revision: https://developer.blender.org/D4213
|
|
|
|
|
|
Related to error exposed by T59640
Would have fixed crash too, but we want to ignore hidden verts.
|
|
|
|
Snapping verts for eg would use these values uninitialized.
|
|
Don't call operator when entering sculpt modes.
|
|
|
|
|
|
The weight was used only for position.
|
|
|
|
|
|
|
|
Removed AbcMeshWriter::getMeshInfo() and AbcMeshWriter::getMaterialIndices().
|
|
There are some things that need to be done in Alembic for Blender 2.8 to
make all the 'visible/renderable/selected only' options work.
|
|
If the triangulated mesh was in itself a new mesh that should be freed this
should happen before the function returns (as it only returns a single mesh,
and thus the caller can only free one).
|
|
Without this clang-format may wrap them onto a single line.
|
|
Matches `BASE_FROM_SET`.
|
|
Prevents clang-format wrapping text before comments.
|
|
Prevents clang-format wrapping text before comments.
|
|
Prevents clang-format wrapping text before comments.
|
|
|
|
|
|
|
|
Useful for calling from lower level code.
|
|
|
|
|
|
Has been disabled for nearly two years now, think we can safely assume
new, quicker code is working properly now. :)
|
|
BKE_id_free(_ex) ones.
|
|
|
|
|
|
Add 'missing' bpy code from BKE_libblock_free_ex(), now both functions
do exactly the same thing, only the later is less flexible (fewer
'exotic' behaviors supported, like handling IDs outside of bmain etc.).
Next step: nuke usages of BKE_libblock_free functions, makes no sense to
have twice the same code around!
|
|
|
|
Regression in 579c01da600dd
Move values_modal_offset use out of applyMouseInput
to resolve order of initialization issue.
|
|
|
|
|
|
|
|
|
|
|
|
The issue is that the edge fix geometry goes on top of the actual drawn
points.
This commit reduce the edge fix size to the strict minimum but does not
get rid of it.
Related to T60139
|
|
|
|
Differential Revision: https://developer.blender.org/D4206
|
|
Before this Blender always needed the Wintab driver. This adds support for the
native pressure API in Windows 8+, making it possible to get pressure sensitivity
on e.g. Microsoft Surface hardware without any extra drivers.
By default Blender will automatically use Wintab if available, and if not use
Windows Ink instead. There is also a new user preference to explicitly specify
which API to use if automatic detection fails.
Fixes T57869: no pressure sensitivity with Surface pen or laptop.
Code by Christopher Peerman with some tweaks by Brecht Van Lommel.
Differential Revision: https://developer.blender.org/D4165
|
|
Was caused by a missing vbo attachement.
Also fix said Vbo refreshing when selecting.
|
|
Base outline is 2px wide (because of how we detect them).
And since inflating this outline will only produce outlines that are 2*x
thick we map the UI scalling and the outline width setting to the closest
match.
Do note that thicker outlines have a performance cost since they need more
texture fetches and passes.
This fixes T60252 3D View Outline Width not working
|
|
|
