Age | Commit message (Collapse) | Author |
|
Adds Metallic to spatial light input of visual shaders
|
|
|
|
Add ability to bind an unbind arguments to Callable.
|
|
Make AABB change trigger bounding box update
|
|
|
|
-Sphere Attractor
-Box Attractor
-Vector Field
-Sphere Collider
-Box Collider
-Baked SDF Collider
-Heightmap Collider
|
|
|
|
|
|
Fixed renaming/moving of nodes with exported NodePaths in the editor
|
|
|
|
1. _gen_unique_bone_name(Ref<GLTFState> state, const GLTFSkeletonIndex skel_i, const String &p_name) won't return an empty string.
2. String GLTFDocument::_sanitize_bone_name(const String &name) will keep Japanese characters. Like: "全ての親".
3. The sanitize function allows the bone name to be not just alphanumeric. The only required conditions are the ones in add_bone.
> ERR_FAIL_COND(p_name == "" || p_name.find(":") != -1 || p_name.find("/") != -1);
|
|
The glTF 2.0 spec only makes `mimeType` mandatory for `bufferView` image data,
so the previous logic to handle URIs with base64-encoded images could fail if
`mimeType` is undefined.
The logic was documented and refactored to better handle the spec, notably:
- `uri` and `bufferView` are now mutually exclusive, and only the latter fails
if `mimeType` is undefined.
- `uri` with a file path will now respect the `mimeType` if defined, and thus
attempt loading the file with the specified format (even if its extension is
not the one expected for this format). So we can support bad extensions (PNG
data with `.jpg` extension) or custom ones (PNG data in `.img` file for
example).
- `uri` with base64 encoded data will infer MIME type from `data:image/png` or
`data:image/jpeg` if it was not documented in `mimeType` initially.
- `uri` with base64 encoded data, no `mimeType` and `application/octet-stream`
or `application/gltf-buffer` will fall back to trying both PNG and JPEG
loaders.
Fully fixes #33796 (and fixes up #42501).
|
|
spatial editor will now update the bounding box if aabb or transform
changes
|
|
Updated getters and setters names for toplevel
|
|
|
|
|
|
types
See https://github.com/KhronosGroup/glTF/issues/944 for context on the
application/gltf-buffer MIME type.
The glTF 2.0 spec supports `image/jpeg` and `image/png` which can also be
base64-encoded in buffer URIs.
Fixes #33796.
|
|
Renamed toplevel to be top_level
|
|
Updates size of float constant in visual shader if empty is selected
|
|
|
|
Fix return type on EditorNode3DGizmoPlugin::get_priority.
|
|
Update all get_configuration_warning() to retrieve warnings from the parent
|
|
Fix scale cursor rotation and handle diagonal ones
|
|
|
|
|
|
|
|
|
|
Don't warp mouse when selecting tracks
|
|
|
|
Drag & drop 3d/2d array/cubemap texture to visual shader
|
|
|
|
Entering text will now start searching automatically after 0.25 seconds
have passed (debounce delay).
This removes the need for a separate Search button.
|
|
Remove unnecessary keyword
|
|
Renames Type to OpType in VisualShaderNodeMultiplyAdd
|
|
The privacy here is already private
|
|
Added inspector_only option to inspect_object in EditorInterface.
|
|
|
|
|
|
|
|
Improve rotation gizmo
|
|
iOS: Fix multiple issues with PVRTC import, disable ETC1
|
|
This closes https://github.com/godotengine/godot-proposals/issues/1576.
|
|
Draw selected item on top of everything else
|
|
|
|
|
|
|
|
|
|
|
|
See discussion in
https://github.com/godotengine/godot-proposals/issues/169.
|
|
We originally used `pt_PT` (i.e. Portuguese (Portugal)) to distinguish with
the Brazilian Portuguese variant `pt_BR`, as both are significantly different
and need separate translation files.
But Portugal's Portuguese (or "European Portuguese") is close to the variant
spoken and written in other Portuguese-speaking countries such as Angola and
Mozambique, so it makes sense for users of these countries to also have access
to the European Portuguese translation (at least until translators decide that
adding e.g. `pt_AO` and `pt_MZ` variants would make sense, taking into account
the translation effort that this duplication implies).
Godot's locale matching checks first for the full locale (e.g. `pt_AO`), and
if no translation is found, it checks for the non-regional language code
(`pt`), so this change enables translations for Portuguese speakers outside
Portugal and Brazil.
|