This is needed because the final startup values for shapes may change between parenting and entering the scene tree. For instance, if the collision shape belongs to a inherited scene.
Fixes#8896.
"enable_object_picking" was linked to Viewport's set_fixed_process() and controlled processing of NOTIFICATION_FIXED_PROCESS which handles physics_object_picking, tooltips and debug drawing collision contacts. Fixes#8347
Fix 3D joint handling of collision exceptions, so that they lose effect when the joint is not valid in every case; also some redundant code removed.
Also avoid trying to create the joint when not neither body A nor body B are set.
Make 2D joints be handled like their 3D counterparts, which adds the fixes to them while also removing duplicated code.
Fixes#2383.
Fixed a bug on wall detection, now `is_on_wall/ceiling/floor` methods give the correct results.
Also added floor angle as optional parameter like on the 3.0 counterpart (floor and ceiling share the same parameter).
The 'pos' variable passed to get_color() and get_offset() can be
negative if the color ramp itself is empty. This causes a lookup in an
empty position in the color Vector which leads to a crash.
We add a check so we never do a lookup in the color Vector if the
gradient is empty.
This fixes#10501
(cherry picked from commit 67b9d6eef2)
- Change get_rect_region to return UV region instead of pixel rect
- Fixed atlas texture Sprite3D Y offsets being applied in the wrong direction and fixed Flip not adjusting the geometry.
- Changed get_rect_region name to get_rect_region_uv_rect
The change in #10524 subtly changes the behavior of set_motion_scale()
and set_motion_offset() if the ParallaxLayer does not have a parent
node. Previously it would still set the corresponding property, but
after this change the property change would be discarded.
I'm not entirely sure if this actually matters as there doesn't appear
to be any code that picks up this change if the ParallaxLayer gets
re-parented later, but it's better to not change behavior regardless.
This backports the work in #7815 and the subsequent fixes in #8393
The following program now works as expected in this branch in both
release_debug and debug mode:
```gdscript
print(sqrt(-1))
print(sqrt(-1))
var simple1=asin(10.0)
var simple2=acos(10.0)
print(simple1)
print(simple2)
```
And successfully prints -nan 4 times
This fixes#9580 and fixes#8925
So when a material is set, every tile will be rendered with that. Quadrants will not be recreated, so a `CanvasItem` will exist per material per quadrant regardless a global material is set.
This makes also __Use parent material__ work for `TileMap`s.
Based on 3bb5abbc35
Pedro J. Estébanez
Rémi Verschelde
Jakub Grzesik
volzhs
Xavier Sellier
sersoong
Rhody Lugo
Paulb23
Bartłomiej T. Listwon
Indah Sylvia
eon-s
Andreas Haas
Hein-Pieter van Braam
TwistedTwigleg
cryptonaut
elasota
Marcelo Fernandez
Juan Linietsky