| Age | Commit message (Collapse) | Author |
|---|
|
|
|
Happy new year to the wonderful Godot community!
We're starting a new decade with a well-established, non-profit, free
and open source game engine, and tons of further improvements in the
pipeline from hundreds of contributors.
Godot will keep getting better, and we're looking forward to all the
games that the community will keep developing and releasing with it.
|
|
Print a warning message if `OS.exit_code` is set to a non-portable value
|
|
This also improves the related documentation.
|
|
The ord() function was recently added in GDScript and VisualScript,
but was missed in the Expression class.
|
|
The calculation used to be wrong when exactly at a power of 2.
`nearest_shift` always return the "next" power of 2
`nearest_shift(4) == 3 # 2^3 = 8`.
On the other hand `next_power_of_2` returns the exact value if that
value is a power of 2 (i.e. `next_power_of_2(4) == 4`).
I.e. :
```
WARN_PRINT(itos(next_power_of_2(4)) + " " + itos(1 << nearest_shift(4)));
// WARNING: ... : 4 8
```
Is this by design?
|
|
|
|
Fix build warning in ustring.cpp on Windows/MSVC platform
|
|
Closes #34443.
|
|
|
|
Fixed issues with using a relative path in the export window.
|
|
|
|
|
|
Before this fix, opening relative export paths inside of an EditorFileDialog was not possible. This was fixed by modifying String::path_to_file() to save relative paths in EditorExportPreset::set_export_path() more appropriately and changing EditorFileDialog::set_current_dir() to open relative paths.
|
|
|
|
Acquire MulticastLock on Android when using broadcast/multicast
|
|
Add method `set_broadcast_enabled` to allow enabling broadcast via
GDScript.
|
|
We now use `thirdparty/misc/triangulator.h` for all physics-related
(collision, navigation) triangulation needs.
Follow-up to #34293.
|
|
Don't allow to use too big or too small shift count
|
|
|
|
Fixes being unable to use the Quat(Vector3) constructor
|
|
|
|
Removed unused variables, add some constants numbers
|
|
|
|
Those arguments aren't required for most common use cases,
so making them optional should help with code readability.
|
|
Near matching was not implemented like in TranslationServer, so a
resource remapped for 'ru' (but not 'ru_RU') would not be used as
fallback if the system locale was 'ru_RU'.
Fixes #34058.
|
|
The previous code only parsed the first two characters (potentially reading
out of bounds if input was invalid), but some locales use a 3-letter language
code (e.g. 'nah_MX').
So I refactored the logic a bit to properly parse the locale and extract the
part left of the regional code, if provided (supports both 'en_US' and 'en-US'
style).
I made TranslationServer::get_language_code() public as I'll use it in a
follow up commit.
|
|
|
|
Underscaled arc tolerance produced very small values so that changes
to this parameter were negligible when scaled internally, hence significant
performance drop (lots of intermediate points inserted in an arc). Now the
performance is mostly the same compared to other types of offsetting
(SQUARE, MITER).
|
|
fixed pitch bend value and MIDI running status on the InputEventMIDI.
|
|
|
|
Fixed antialiased option for Polygon2D
|
|
Fix HTTP HEAD requests
|
|
Polygon2D:
The property wasn't used anymore after switching from canvas_item_add_polygon() to canvas_item_add_triangle_array() for drawing.
Line2D:
Added the same property as for Polygon2D & fixed smooth line drawing to use indices correctly.
Fixes #26823
|
|
|
|
get loaded with two backslashes"
This reverts commit 1342551664091c1ceb931ee45d9c43f09df5f1ff.
|
|
Add download_chunk_size property to HTTPRequest.
|
|
This allows setting the `read_chunk_size` of the internal HTTPClient.
This is important to reduce the allocation overhead and number of file
writes when downloading large files, allowing for better download speed.
|
|
Fix HTTPClient::poll crash when connection set to null
|
|
|
|
Fix some overflows and unitialized variables
|
|
|
|
s * edge0 = -d / a * edge0 = -edge0⋅v0 / (edge0⋅edge0) * edge0 = vector projection of -v0 onto edge0
By incorrectly using -e/c instead of -d/a, Face3::get_closest_point_to was returning the wrong point in certain cases. Specifically, I noticed it returning vertex[0] when it should have been returning vertex[1].
|
|
Messages coming from ERR_EXPLAIN / ERR_*_MSG macros used to strip the
error explanation in release builds and was changed in a recent
refactoring.
This commit restores the old behaviour (fixing release builds).
|
|
Send *_MSG macros' explanations directly to the _err_print_error().
|
|
|
|
|
|
|
|
This makes it possible to change it at runtime in projects.
|
|
Fix incomplete binding.
|