Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Properly reload built-in tool scripts
|
|
Reimplement ping-pong animation and reverse playback
|
|
|
|
Display 2 decimals instead of 1 in editor frametime labels
|
|
Prevent obj importer from printing misleading error
|
|
Improve save handling for built-in scripts
|
|
Default to 30 animation fps for better quality.
|
|
When comparing different graphics settings or optimizations,
this makes precise measurements and frametime comparisons easier.
|
|
|
|
|
|
This prevents the viewport from going upside-down.
This was suggested at:
https://github.com/godotengine/godot/pull/51984#issuecomment-948614191:
> For 3.4, I think we can just clamp the angle value when using the
> camera orbiting shortcuts. We can investigate what to do with panning
> and freelook in 3.5 and 4.0.
|
|
|
|
|
|
functions.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1. Explicit and unambiguous when comparing to `GradientTexture2D`
2. Consistent with other class names where 1D is used in the engine.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Same as what is already done for shape queries, applied to point and ray
queries. Easier to document and more flexible to add more parameters.
Also expose intersect_point method to script in 3D.
Remove intersect_point_on_canvas in 2D, replaced with a parameter.
|
|
Structure button layout so there is no more overlap.
|
|
|