| Age | Commit message (Collapse) | Author |
|---|
|
When scene contains only 1 armature, it will export all actions, not only active + NLA
|
|
Better management of case of multiple object with each multiple actions
|
|
|
|
|
|
|
|
|
|
When importing a .x3d file containing an empty IndexedFaceSet, like this for example:
```
Shape {
geometry IndexedFaceSet {
coord Coordinate {
point [
]
}
coordIndex [
]
}
}
```
`import_x3d.py` throws an exception, because `x_min`, `x_max`, ... are not initialized/still set to `None`.
This fixes the issue by initializing the mentioned variables to `inf`/`-inf` respectively and also further simplifies the code by utlizing the `min` and `max` builtins.
Reviewed By: mont29
Differential Revision: https://developer.blender.org/D14470
|
|
|
|
I noticed the FBX export was missing a triangulation option seen in other software and other Blender exporters such as .obj.
This feature is rather useful for example for ensuring consistent normal map baking in third party software, where tangent space gets easily messed up with tools using mikktspace that depends on triangulation choices.
This patch adds a "Triangulate Faces" option in the export options similarly to what the Wavefront OBJ exporter has. Diff-wise it's rather simple by reusing the temporary mesh creation from "Apply Modifiers".
Reviewed By: mont29
Differential Revision: https://developer.blender.org/D14352
|
|
Added an option to allow the user to export STLs
using an arbitrary (custom) coordinate-space.
This is not exposed in the UI and is intended for script authors
exporting content.
Ref D11517
|
|
Creates a new camera and "Custom Object"-type landmark from the VR
headset pose.
In contrast to the existing "Landmark from Session" operator that only
saves the headset rotation around the global z-axis, this preserves the
exact rotation of the headset by assigning it to the newly-created
camera (although the landmark itself still only inherits the z-rotation
component).
|
|
da9a50a46ed3e293146428a87a275a947a54b9fe reverted these changes.
|
|
Contributed by luzpaz.
Differential Revision: https://developer.blender.org/D14312
|
|
Contributed by luzpaz.
Differential Revision: https://developer.blender.org/D14313
|
|
|
|
New button in menu to flip view horizontally within camera by inverting x-scale
|
|
Due to API change, timeline scrub snapping crashed when setting scene frame
|
|
node tree
|
|
This is now more than a year old. Removing the back compatibility. Use can of course set again the value in UI at export
|
|
This allows user to use no indent in json, for example
Here is an example of hook:
```
def gather_gltf_encoded_hook(self, gltf_format, sort_order, export_settings):
gltf_format.indent = None
gltf_format.separators = (',', ':')
```
|
|
You can change filter tag to change default filtering
|
|
At import, this will be defined as armature/joints instead of empties
|
|
This menu (in Add > Output) will be displayed only if activated in addon preferences.
The node is sed for AO export. This is a shortcut, avoiding user to create it him/herself
|
|
|
|
Differential Revision: https://developer.blender.org/D14285
|
|
|
|
|
|
An exponent should never be negative... but FBX files being FBX files,
just add a 0.0 clamping to that value.
|
|
When importing an animation from FBX or BVH the fcurves are currently shown as a very long list in the dope sheet.
When you manually create a keyframe they are grouped by bone name, which is much more user friendly. This patch groups imported animations by bone name too.
The changes are trivial:
* In the FBX case it was falsely using the object name to group all curves rather than the bone name.
* The BVH importer simply wasn't using the grouping feature at all.
Reviewed By: mont29
Maniphest Tasks: T82472
Differential Revision: https://developer.blender.org/D11269
|
|
Also use context to ensure the file is closed properly.
|
|
Update path for the DOF distance, allow properties to be RNA paths.
|
|
|
|
- precompute tree before export
- manage collections / instances / linked
- use custom cache to avoid name collision
- animations are baked from world matrix
More info on https://github.com/KhronosGroup/glTF-Blender-IO
|
|
This has been removed from Blender.
|
|
|
|
See T95442
|
|
|
|
|
|
See T95442
|
|
From https://github.com/alessandro-zomparelli/tissue/releases/tag/v0-3-52
with https://github.com/alessandro-zomparelli/tissue/pull/131 applied.
Fixes T80702
Fixes T73136
|
|
From https://github.com/alessandro-zomparelli/tissue/releases/tag/v0-3-52
with https://github.com/alessandro-zomparelli/tissue/pull/131 applied.
Fixes T80702
Fixes T73136
|
|
|
|
See T95442
|
|
|
|
See T95442
|
|
|
|
Fixes T94443
Updates all PDT python modules to use SPDX license identifiers.
|
|
|
|
This commit aims at fixing the (very) redundant action names when importing animation data from Fbx files.
By default importing actions from an animated Fbx skeleton file leads to this:
**skeleton_name|skeleton_name|action_name|skeleton_name|action_name**
It works this way: **id_data.name|stack_name|layer_name**
These containers are generally made of the exact same strings multiple time.
This is a proposal to avoid such redundancy by stripping the "layer_name" in case it's identical to the "stack_name"
I'm not sure yet if one of them could be always skipped, I haven't experienced cases when they are different.
With this patch actions are named:
**skeleton_name|skeleton_name|action_name**
It could still be improved, since the "id_data.name" is generally the armature name, already contained in the "stack_name". But sometimes it's not (for Shape Keys for example: Key|skeleton_name|action_name)
Maybe more checks could be added to avoid redundancy even more. Just to open the discussion about it...
Reviewed By: mont29
Differential Revision: https://developer.blender.org/D14130
|
|
Load the first non-blank, non-comment line so files with licenses
are supported.
|
