- Rename all instances of `capture_start()` and `capture_end()` to their new
names. Fixes#72892.
- More internal renames to match what was started in #69120.
- Use `override` consistently so that such refactoring bugs can be caught.
- Harmonize the order of definition of the overridden virtual methods in each
audio driver.
- Harmonize prototype for `set_output_device` and `set_input_device`.
Co-authored-by: Rémi Verschelde <rverschelde@gmail.com>
When using avoidance, if you set the same velocity for the agent, you won't get an update from the avoidance system.
This changes both the `set_target_position` and `set_velocity` setters to always accept user provided values, even if they are the same. This ensures that repathing and avoidance logic is always run when the user expects.
With the 4.x-introduction of Windows the previous method for
color picking was no longer working.
This PR uses the following approach to reintroduce color-picking.
When the Color-Picking-Button is pressed, a quasi-screenshot of the
Window-content is created and displayed in a new Popup-Window.
This new Window allows selecting colors by Mouse-Click.
A Preview of the targeted Color is also displayed.
It's been 3 years since the release of Godot 3.2 and the start of the
major overhaul of the codebase for Godot 4.0.
And the work on that new version had started even 6 months before with
Juan working on the Vulkan renderer and various core changes in a
feature branch. This got merged in #36098 on Feb 11, 2020, oh well, we
3 days early ;)
Close to 15,000 pull requests have been merged for the 4.0 milestone,
which is half of the total amount of PRs in Godot's open source
lifetime. This is our biggest release by far, and it's finally time to
let it loose.
A huge thankyou to all the contributors who were involved over the
years, with contributions of any kind. Now's the final stretch to iron
out the remaining blocking bugs and release 4.0-stable.
This addresses issues where some drivers are reporting they don't meet the vulkan hardware level 1 support requirements even though they render as expected when the check is removed.
The hard limit is set at 2048 depth which seems sensible between
legitimate recursive calls while still avoiding a crash because of a
stack overflow in most of the cases.
Note that it is still possible to reach the stack limit and get an
overflow before reaching a call depth. This is intended as a half-way
measure to stop crashing in most cases, since there's no reliable nor
portable way to check the amount of stack memory left.
George Marques
Rémi Verschelde
Rémi Verschelde
Haoyu Qiu
Ninni Pipping
Emmanouil Papadeas
Josh Jones
Hendrik Brucker
Markus Sauermann
Dmitrii Maganov
Jan Haller
clayjohn
smix8
JoJoX
kobewi
Yuri Sizov
bruvzg
Gilles Roudière
Danil Alexeev
Fredia Huya-Kouadio
RedworkDE
Jay Mehta
quinnyo