Age | Commit message (Collapse) | Author |
|
File handling APIs are typically considered part of I/O, and we did have most
`FileAccess` implementations in `core/io` already.
|
|
|
|
|
|
|
|
Also _transform to _transform3d
|
|
|
|
Fix issue when two skeletons end up directly parented.
Prevent animating TRS for skinned Mesh node.
Fix animating weights on meshes with targets but no weights.
|
|
|
|
Fix incorrect skin deduplication when using named binds
|
|
|
|
|
|
When one invalid image fails, it should only fail that single image.
|
|
Move to a more graceful degradation 3d asset import model.
|
|
|
|
|
|
We've been using standard C library functions `memcpy`/`memset` for these since
2016 with 67f65f66391327b2967a20a89c3627e1dd6e84eb.
There was still the possibility for third-party platform ports to override the
definitions with a custom header, but this doesn't seem useful anymore.
|
|
Rename get_surface_material to get_surface_override_material
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Co-authored-by: Lcbx <luc.courbariaux@gmail.com>
|
|
* Added option for importers to show an Advanced settings dialog
* Created advanced settings dialog for Scene Importer
* Cleaned up importers (remove many old/unused options)
* Added the ability to customize every node, material, mesh and animation individually
* Saving to animations and meshes to files is now a manual process, making it more predictable
* Added the ability for materials to be replaced by external files (or to be made external, up to you).
* When doubleclicking an impoted scene in the filesystem dock, it automatically shows the import settings instead of asking to open it.
WARNING: Lightmap UV unwrap is not working, it needs to be re-made.
|
|
GLTF importer: Prevent quick accumulation of significant numerical errors in keyframe times
|
|
Keyframe times shift slowly in imported animations, starting with a zero shift
at the beginning and increasing and becoming erratic slowly farther into an
animation, reaching significant levels at times after about 3 minutes into an
animation. This commit fixes the issue by increasing the precision of the
floating point numbers used for keyframe time calculations. Only the most
significant cases that cause fast accumulation of errors over a short animation
duration are fixed. Other cases that would have a marginal benefit from
switching to double precision numbers are left for another PR/further analysis.
Note that this change has no impact on the runtime performance of games/apps
created using Godot. It only affects the GLTF importer.
Fixes #47127.
|
|
And move GLTF docs to its module folder.
|
|
|
|
Relaxes node name sanitization in gltf documents.
|
|
|
|
And fix various bogus bindings following previous PRs.
|
|
Fixes #45371.
|
|
|
|
Restore gltf node animation export.
|
|
|
|
Misc style changes.
|
|
|
|
|
|
|
|
We should first attempt loading as external files, thus creating a dependency.
Loading as a buffer should only be used as fallback to support manually loading
as PNG or JPEG depending on the defined mimeType.
Fixes #44309, was a regression from #42504.
|
|
Happy new year to the wonderful Godot community!
2020 has been a tough year for most of us personally, but a good year for
Godot development nonetheless with a huge amount of work done towards Godot
4.0 and great improvements backported to the long-lived 3.2 branch.
We've had close to 400 contributors to engine code this year, authoring near
7,000 commit! (And that's only for the `master` branch and for the engine code,
there's a lot more when counting docs, demos and other first-party repos.)
Here's to a great year 2021 for all Godot users 🎆
|
|
|
|
Rename Math::stepify to snapped
|
|
|
|
|
|
|
|
|
|
|
|
* Support KHR_texture_transform.
* Support exporting glTF2
* Support exporting instanced scenes
* Extract into a gltf state and gltf document
* Add a tools menu for exporting gltf2
|