mirror of
https://github.com/godotengine/godot-website.git
synced 2026-01-06 14:09:58 +03:00
2661 lines
279 KiB
XML
2661 lines
279 KiB
XML
<?xml version="1.0" encoding="utf-8"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>Godot Engine Official</title><link/><description/><atom:link href="https://godotengine.org/rss.xml" rel="self" type="application/rss+xml"/><item><title>Dev snapshot: Godot 4.4 beta 1</title><link>https://godotengine.org/article/dev-snapshot-godot-4-4-beta-1/</link><summary>Godot 4.4 is on its way! Please lend a hand by testing this beta release and reporting your findings.</summary><description><p>We have reached the first beta release for the 4.4 release cycle. This officially marks the start of feature freeze for 4.4. This means contributors are encouraged to focus their efforts on fixing <a href="https://github.com/godotengine/godot/issues?q=is%3Aopen+is%3Aissue+label%3Aregression+milestone%3A4.3">regressions</a> and other outstanding bugs. We won’t risk merging any new features or risky bug fixes until after we release 4.4 and begin preparing for 4.5.</p>
|
||
<p>We will aim to release 4.4 in around a month, but as usual, this timeline will depend on how quickly we are able to fix the outstanding bugs and what new bugs are identified in the beta process. We ask that users test these beta releases and report bugs as soon as you spot them to help us ensure a quick beta period and a timely release of 4.4.</p>
|
||
<p>Please, consider <a href="#support">supporting the project financially</a>, if you are able. Godot is maintained by the efforts of volunteers and a small team of paid contributors. Your donations go towards sponsoring their work and ensuring they can dedicate their undivided attention to the needs of the project.</p>
|
||
<p><a href="#downloads">Jump to the <strong>Downloads</strong> section</a>, and give it a spin right now, or continue reading to learn more about improvements in this release. You can also <a href="https://editor.godotengine.org/releases/4.3.beta1/">try the <strong>Web editor</strong></a> or the <strong>Android editor</strong> for this release. If you are interested in the latter, please request to join <a href="https://groups.google.com/g/godot-testers">our testing group</a> to get access to pre-release builds.</p>
|
||
<hr />
|
||
<p><em>The cover illustration is from</em> <a href="https://store.steampowered.com/app/3146520/WEBFISHING/"><strong>WEBFISHING</strong></a>, <em>a multiplayer online casual fishing game where you relax, hang out, make friends, and catch fish! You can buy the game <a href="https://store.steampowered.com/app/3146520/WEBFISHING/">on Steam</a>, and follow the development on <a href="https://x.com/westthewerst">Twitter</a>.</em></p>
|
||
<h2 id="highlights">Highlights</h2>
|
||
<p>Many features originally intended for 4.3 ended up making it into 4.4 meaning that Godot 4.4 is jam-packed with new features
|
||
despite having a much shorter development period than 4.3.</p>
|
||
<ul>
|
||
<li><a href="#new-in-beta-1">New in Beta 1!</a></li>
|
||
<li><a href="#breaking-changes">Breaking changes</a></li>
|
||
<li><a href="#animation">Animation</a></li>
|
||
<li><a href="#audio">Audio</a></li>
|
||
<li><a href="#c">C#</a></li>
|
||
<li><a href="#core">Core</a></li>
|
||
<li><a href="#editor">Editor</a></li>
|
||
<li><a href="#gdscript">GDScript</a></li>
|
||
<li><a href="#import">Import</a></li>
|
||
<li><a href="#input">Input</a></li>
|
||
<li><a href="#physics">Physics</a></li>
|
||
<li><a href="#platforms">Platforms</a></li>
|
||
<li><a href="#rendering-and-shaders">Rendering and shaders</a></li>
|
||
<li><a href="#xr">XR</a></li>
|
||
</ul>
|
||
<h3 id="new-in-beta-1">New in Beta 1!</h3>
|
||
<p>Normally our Beta 1 release notes summarize all the most exciting changes from the previous dev releases. But the team managed to merge an unusually large number of exciting PRs right before the beta this time around, so we would like to first introduce some of the exciting changes that are new in this beta.</p>
|
||
<p>A short word of warning, new means “untested”, so consider the following the most untested part of the beta release and make sure to let us know if you run into any issues!</p>
|
||
<h4 id="game-window-embedding">Game window embedding</h4>
|
||
<p>Game window embedding makes it possible to run the game while being able to interact with the full editor window, without needing to move the game window to the side of the editor window. This is particularly useful on single-monitor setups and laptops where screen real estate is at a premium. However, this was challenging to implement as Godot runs the game as a separate process from the editor for two reasons:</p>
|
||
<ul>
|
||
<li>The game process uses its own address space and therefore doesn’t have to share CPU/GPU resources with the editor (or at least, not as much as if it was the same process).</li>
|
||
<li>Most importantly, if the game crashes for any reason, the editor does not crash at the same time (which could cause data loss).</li>
|
||
</ul>
|
||
<p>The approach we decided upon relies on window management tricks instead, so that the game window is still a separate process, but it <em>looks</em> like it’s embedded within the editor. Contributor Hilderin took upon this task and implemented seamless window embedding on Windows and Linux. Support in Android is coming in Beta 2 while support in macOS will require a different approach for technical reasons.</p>
|
||
<p>Game window embedding was implemented to support our recent interactive in-game editing feature. Now you can easily run your game, override the game camera, and select objects in game, all from the editor!</p>
|
||
<p><img src="/storage/blog/godot-4-4-beta-1/embedded-editor.webp" alt="Embedding game window in main editor" /></p>
|
||
<p>For more information and a handy video, check out the PR <a href="https://github.com/godotengine/godot/pull/99010">GH-99010</a>.</p>
|
||
<h4 id="use-property-editors-instead-of-labels-to-display-keys">Use property editors instead of labels to display keys</h4>
|
||
<p>With the addition of typed dictionaries, one glaring issue quickly revealed itself in the inspector: keys were always displayed as strings! While this was the case even before typed dictionaries, the issue only became more pronounced as it undermined the benefits of static-typing. bruvzg came to the rescue with <a href="https://github.com/godotengine/godot/pull/100512">GH-100512</a>, which allows the inspector to treat ALL dictionary keys as a read-only field for their respective types.</p>
|
||
<h4 id="apple-game-controller-improvements">Apple Game Controller improvements</h4>
|
||
<p>We’ve made some improvements to how Game Controllers work on iOS and macOS. We’ve unified the code to make sure it works the same on both platforms, and we’ve fixed some bugs. These changes improve reliability of controller discovery and manipulating the rumble motors, which should make the gaming experience even better. You can learn more about these changes in <a href="https://github.com/godotengine/godot/pull/94580">GH-94580</a>.</p>
|
||
<h4 id="add-2d-shader-instance-uniforms">Add 2D shader instance uniforms</h4>
|
||
<p>Previously, Godot only supported shader instance uniforms in Spatial shaders. Thanks to KoBeWi, EIREXE, huwpascoe, and Patrick Exner this release will add support for shader instance uniforms for CanvasItem shaders (<a href="https://github.com/godotengine/godot/pull/99230">GH-99230</a>). Shader instance uniforms allow you to assign a different value to the uniform for each CanvasItem that uses it. Importantly, this works without breaking batching, so it can be used as a performant way to add unique effects to CanvasItems without having to juggle materials.</p>
|
||
<h4 id="add-visualization-of-3d-particle-emission-shapes">Add visualization of 3D particle emission shapes</h4>
|
||
<p>Up until now, users of the particle system had to guess from the emission shape properties where particles would appear. This improvement (<a href="https://github.com/godotengine/godot/pull/100113">GH-100113</a>) by Patrick Exner adds a visualization of the emission shapes for 3D CPU and GPU particle systems.</p>
|
||
<video autoplay="" loop="" muted="" playsinline="">
|
||
<source src="/storage/blog/godot-4-4-beta-1/particle-emission.webm?1" type="video/webm" />
|
||
</video>
|
||
<h4 id="add-support-for-metalfx-upscaling-on-macos-and-ios">Add support for MetalFX upscaling on macOS and iOS</h4>
|
||
<p>We’ve added support for MetalFX upscaling as an option for Apple platforms using the Metal driver. MetalFX provides a high-performance alternative to FSR1 or FSR2, leveraging Apple’s optimized GPU pipeline to deliver smooth upscaling and enhanced visual fidelity with minimal overhead.</p>
|
||
<p>This integration ensures developers targeting macOS or iOS can achieve excellent rendering quality and performance on supported Apple hardware. For more details, check out <a href="https://github.com/godotengine/godot/pull/99603">GH-99603</a>.</p>
|
||
<h4 id="add-support-for-agx-tone-mapping">Add support for AgX tone mapping</h4>
|
||
<p>AgX is the cool, new kid on the block when it comes to tone mapping algorithms. Last year Blender made waves by replacing their previous “filmic” tone mapper with AgX. We have implemented a version of AgX that closely matches Blender’s while being not quite as high quality, but much more suitable for real time. AgX is a stylized tone mapper intended to give a filmic quality to images that handles very bright scenes much better than our other tone mappers.</p>
|
||
<p><img src="/storage/blog/godot-4-4-beta-1/tonemap.webp" alt="ACES tone mapping left, AgX right" /></p>
|
||
<h4 id="add-transparency-support-for-lightmapgi">Add transparency support for LightmapGI</h4>
|
||
<p>Currently when baking lightmaps users have to choose between transparent objects casting shadows as if they were fully opaque, or not casting shadows at all. This has been a major limitation in both the quality of lightmap baking and the ergonomics of the lightmap baking workflow.</p>
|
||
<p>In <a href="https://github.com/godotengine/godot/pull/99538">GH-99538</a>, Hendrik Brucker added support for baking with transparent objects, including having tinted shadows (something that dynamic shadows don’t support yet). Since this is brand new in Beta 1, please test it carefully and report any issues.</p>
|
||
<p><img src="/storage/blog/godot-4-4-beta-1/lightmap-color.webp" alt="Lightmap shaders with color" /></p>
|
||
<h3 id="breaking-changes">Breaking changes</h3>
|
||
<p>We try to minimize breaking changes, but sometimes they are necessary in order to fix high priority issues. Where we do break compatibility, we do our best to make sure that the changes are minimal and require few changes in user projects.</p>
|
||
<p>You can find a list of such issues by filtering the merged PRs in the 4.3 milestone with the <a href="https://github.com/godotengine/godot/issues?q=milestone%3A4.4%20is%3Amerged%20label%3A%22breaks%20compat%22"><code class="language-plaintext highlighter-rouge">breaks compat</code> label</a>. Here are some which are worth being aware of:</p>
|
||
<ul>
|
||
<li><a href="https://godotengine.org/article/uid-changes-coming-to-godot-4-4/">Universal UID support.</a> This will create several <code class="language-plaintext highlighter-rouge">.uid</code> files for resources that lacked this metadata. <strong>These should be added to version control</strong>, much like <code class="language-plaintext highlighter-rouge">.import</code> files. (<a href="https://github.com/godotengine/godot/pull/97352">GH-97352</a>)</li>
|
||
<li>Floats converted to strings now display as a decimal by default, even for whole numbers. This makes printed types more explicit, which can be used to catch bugs that were previously invisible. That is: <code class="language-plaintext highlighter-rouge">print(1.0)</code> will now print <code class="language-plaintext highlighter-rouge">1.0</code> instead of <code class="language-plaintext highlighter-rouge">1</code>. (<a href="https://github.com/godotengine/godot/pull/47502">GH-47502</a>)</li>
|
||
<li>Changed <code class="language-plaintext highlighter-rouge">KEY_MODIFIER_MASK</code> to correct value. Unlikely to directly affect any projects, as the previous value was simply wrong. (<a href="https://github.com/godotengine/godot/pull/98441">GH-98441</a>)</li>
|
||
<li>Control’s <code class="language-plaintext highlighter-rouge">offset_*</code> get/set type changed from <code class="language-plaintext highlighter-rouge">int</code> to <code class="language-plaintext highlighter-rouge">float</code>. This matches the behavior described in the documentation. (<a href="https://github.com/godotengine/godot/pull/98443">GH-98443</a>)</li>
|
||
<li><code class="language-plaintext highlighter-rouge">OpenXR</code> action maps opened in Godot 4.4 aren’t compatible with earlier versions. (<a href="https://github.com/godotengine/godot/pull/98163">GH-98163</a>)</li>
|
||
<li><code class="language-plaintext highlighter-rouge">CSGMesh3D</code> now explicitly requires the mesh to be manifold. A manifold mesh must be closed, have each edge connected to only two faces, and have volume. Commonly, this means that it needs to be a “watertight” mesh without any holes and where you can never see the backside of the triangles. (<a href="https://github.com/godotengine/godot/pull/100014">GH-100014</a>)</li>
|
||
<li>StringName Dictionary keys are saved as-is, without being converted to String beforehand. For the majority of cases this shouldn’t cause breakage, as String &amp; StringName are largely interchangeable. This should only be relevant when performing type-checking (<code class="language-plaintext highlighter-rouge">is</code>, <code class="language-plaintext highlighter-rouge">is_instance_of()</code>, <code class="language-plaintext highlighter-rouge">typeof()</code>) and/or strict comparison (<code class="language-plaintext highlighter-rouge">is_same()</code>). (<a href="https://github.com/godotengine/godot/pull/70096">GH-70096</a>)</li>
|
||
<li>Remove “Raycast Normals” and associated “Normal Split Angle” settings from LOD import. We removed this because the quality is almost always better now without it and import time is much faster without it. (<a href="https://github.com/godotengine/godot/pull/93727">GH-93727</a>)</li>
|
||
<li>Make PopupMenu/Panel shadows properly visible again. This makes PopupMenu/Panel’s transparent by default now. When using non-embedded popups, you will still need to enable <code class="language-plaintext highlighter-rouge">display/window/per_pixel_transparency/allowed</code> to see the shadows. (<a href="https://github.com/godotengine/godot/pull/91333">GH-91333</a>)</li>
|
||
<li>The names of imported blend shapes and animation libraries from glTF files have changed as unsupported characters are automatically removed. All “<code class="language-plaintext highlighter-rouge">:</code>” for blendshapes are now removed, and any of “<code class="language-plaintext highlighter-rouge">/</code>”, “<code class="language-plaintext highlighter-rouge">:</code>”, “<code class="language-plaintext highlighter-rouge">,</code>”, and “<code class="language-plaintext highlighter-rouge">[</code>” are removed for animation libraries. (<a href="https://github.com/godotengine/godot/pull/94783">GH-94783</a>)</li>
|
||
<li>Change NavigationMesh to also parse collision shapes by default. This is part of an effort to encourage users to use collision shapes for NavigationMesh instead of visual meshes as collision shapes are much simpler and thus more efficient for Navigation. (<a href="https://github.com/godotengine/godot/pull/95013">GH-95013</a>)</li>
|
||
<li>XR: Disable hand tracking by default. This has a non-trivial performance cost and is not needed for many games. Users need to enable the setting if they want to use hand tracking now. (<a href="https://github.com/godotengine/godot/pull/95153">GH-95153</a>)</li>
|
||
<li>Automatically resolve initial and final action for draw lists. <code class="language-plaintext highlighter-rouge">RenderingDevice.draw_list_begin()</code> has been vastly simplified and so it will be much easier to use. The old method signature will continue to work, but we recommend using the new method since it is much simpler. (<a href="https://github.com/godotengine/godot/pull/98670">GH-98670</a>)</li>
|
||
<li>Editor camera override has moved from the editor viewport to the “Game” tab. (<a href="https://github.com/godotengine/godot/pull/97257">GH-97257</a>)</li>
|
||
</ul>
|
||
<p>UIDs in particular are a pretty massive shake-up to existing project structures, and have understandably been among the more contentious changes of the 4.4 development cycle. Read this blog post to better understand the rationale behind that change, as well as the benefits it brings to the table: <a href="https://godotengine.org/article/uid-changes-coming-to-godot-4-4/">UID changes coming to Godot 4.4</a></p>
|
||
<h3 id="animation">Animation</h3>
|
||
<p>One of our newest additions to the animator’s toolkit is markers (<a href="https://github.com/godotengine/godot/pull/91765">GH-91765</a>) by ChocolaMint. Markers allow you to create sub regions of an animation that can be jumped to, or looped without playing the entire animation. This functionality is even supported inside AnimationTree, where you can easily create an AnimationNode’s custom timeline based on the markers.</p>
|
||
<p>We’ve also added <code class="language-plaintext highlighter-rouge">LookAtModifier3D</code> (<a href="https://github.com/godotengine/godot/pull/98446">GH-98446</a>) to handle 3D model procedural animation, partially replacing the deprecated <code class="language-plaintext highlighter-rouge">SkeletonIK3D</code>. Thanks to the efforts of animation expert Silc Renew (Tokage), users no longer need to rely on specific bone structures and arbitrary layouts; this new tool allows for angle limitations, forward axis settings, etc., and is specialized for making a 3D character model look in the target direction.</p>
|
||
<p>Sneaking in right before the feature freeze, the Animation team added <code class="language-plaintext highlighter-rouge">SpringBoneSimulator3D</code>(<a href="https://github.com/godotengine/godot/pull/101409">GH-101409</a>) as well. The spring bone is an open source cross-platform module that is distributed by the <a href="https://vrm-consortium.org/en/">VRM consortium</a> under the MIT license. It has been available in Godot as an <a href="https://godotengine.org/asset-library/asset/2031">add-on</a> for a while now, but there were some difficulties in stability and complex setup due to the complicated data structure. Tokage refined it based on <code class="language-plaintext highlighter-rouge">SkeletonModifier3D</code> with some improvements by leaning on existing core functionality, so it is now much improved and easier to use!</p>
|
||
<video autoplay="" loop="" muted="" playsinline="">
|
||
<source src="/storage/blog/godot-4-4-beta-1/springbone.webm?1" type="video/webm" />
|
||
</video>
|
||
<h3 id="audio">Audio</h3>
|
||
<p>First-time contributor what-is-a-git implemented the long-requested support for runtime loading of WAV files (<a href="https://github.com/godotengine/godot/pull/93831">GH-93831</a>). This adds parity with Ogg Vorbis audio tracks, and will be a welcome addition for users who want to load user-generated content at runtime (including non-game audio applications).</p>
|
||
<h3 id="c">C#</h3>
|
||
<p>Paul Joannon and Raul Santos have put the final pieces in place for moving both the GodotSharp library and user projects to .NET 8 (<a href="https://github.com/godotengine/godot/pull/92131">GH-92131</a> and <a href="https://github.com/godotengine/godot/pull/100195">GH-100195</a>). All new projects will use .NET 8 by default and existing projects will automatically update to .NET 8 once opened with this release or any newer 4.4 build. For more details, check out the recent article on <a href="https://godotengine.org/article/godotsharp-packages-net8/">Godot C# packages moving to .NET 8</a>.</p>
|
||
<p>For C# developers targeting Android platforms, exported projects will now use the <code class="language-plaintext highlighter-rouge">android</code> runtime identifier (<a href="https://github.com/godotengine/godot/pull/88803">GH-88803</a>). This means C# Android exports now support all available architectures (arm32, arm64, x32, and x64) whereas previously it only supported 64-bit architectures. The necessary Java library to bind the .NET cryptography implementation to the Android OS functions is now also included in exported projects, which fixes issues such as crashing when using SSL with the BCL-provided <code class="language-plaintext highlighter-rouge">HttpClient</code>.</p>
|
||
<h3 id="core">Core</h3>
|
||
<p>As mentioned in our <a href="https://godotengine.org/article/dev-snapshot-godot-4-4-dev-7/">last development update</a>, the improvements to the core of our codebase have been absolutely staggering! Lukas Tenbrink has spearheaded optimizations to strings and the speed/efficiency at which they’re parsed. Adam Scott opened the door for tool makers to take advantage of temporary files and directories (<a href="https://github.com/godotengine/godot/pull/98397">GH-98397</a>). Ocean has broadened the scope in which <code class="language-plaintext highlighter-rouge">Curve</code> can be applied, allowing for domains outside of <code class="language-plaintext highlighter-rouge">[0, 1]</code> (<a href="https://github.com/godotengine/godot/pull/67857">GH-67857</a>).</p>
|
||
<p>But perhaps the biggest highlight of them all is Typed Dictionaries. After the introduction of Typed Arrays in 4.0 by George Marques (<a href="https://github.com/godotengine/godot/pull/46830">GH-46830</a>), Typed Dictionaries rapidly became one of the engine’s most requested features. Thanks to the efforts of Thaddeus Crews (<a href="https://github.com/godotengine/godot/pull/78656">GH-78656</a>), this is finally a reality! This feature being implemented at the core of the engine means that all scripting languages (GDScript, C#, C++) can take advantage by interfacing with Godot’s Dictionary type. You can now export typed dictionaries from scripts and benefit from a much improved Inspector UX to assign the right keys and values.</p>
|
||
<h3 id="editor">Editor</h3>
|
||
<p>Thanks to the contribution from YeldhamDev of Lone Wolf Technology and W4 Games we now have a new “Game” tab along with the existing “2D”, 3D”, “Script”, and “AssetLib” tabs that allows users to have fine-tuned control over the running game from the editor. This includes overriding the in-game camera and selecting objects in game.</p>
|
||
<p>Check out the PR (<a href="https://github.com/godotengine/godot/pull/97257">GH-97257</a>) and the video below to see exactly what this change enables.</p>
|
||
<video autoplay="" loop="" muted="" playsinline="">
|
||
<source src="/storage/blog/dev-snapshot-godot-4-4-dev-4/game-editor-debug.mp4?1" type="video/mp4" />
|
||
</video>
|
||
<p>See also <em>game window embedding</em> further above, which works in tandem with this feature. Note that these features can be used separately: you can still make use of interactive in-game editing even if the game is split to a separate window.</p>
|
||
<p>Manipulating Camera3Ds in the editor is also improved! With Haoyu Qiu’s new feature in <a href="https://github.com/godotengine/godot/pull/90778">GH-90778</a>, every selected 3D camera shows a preview inside the inspector. No switching cameras needed to preview anymore.</p>
|
||
<p>Hilderin valiantly fought their way through a labyrinth of dependencies and multi-threading pitfalls, and brought us back the long awaited grail: error-less first import of projects. This took a lot of effort between multiple PRs (<a href="https://github.com/godotengine/godot/pull/92303">GH-92303</a>, <a href="https://github.com/godotengine/godot/pull/93972">GH-93972</a>, and <a href="https://github.com/godotengine/godot/pull/92667">GH-92667</a>), but resolves a major annoyance faced by any user who downloaded an existing project from online.</p>
|
||
<p>Moreover, with this newfound knowledge, Hilderin also further improved the first project import experience to make the FileSystem dock more responsive while resources are being scanned (<a href="https://github.com/godotengine/godot/pull/93064">GH-93064</a>) and improve the overall editor startup speed for large projects (<a href="https://github.com/godotengine/godot/pull/95678">GH-95678</a>). Large projects can expect up to a 3× speed improvement when loading the project and a similar speedup when doing any operations that scan the filesystem.</p>
|
||
<p>HP van Braam was able to make a similar performance improvement when moving or renaming nodes in the SceneTree (<a href="https://github.com/godotengine/godot/pull/99700">GH-99700</a>). Godot should now feel much faster when editing large scenes with hundreds or thousands of nodes.</p>
|
||
<p>The debugger panel now features an expression evaluator which adds a new tab to the debugger panel that allows you to evaluate expressions using the local state of your scripts while stopped at a breakpoint. Many users are familiar with this workflow from other REPL debuggers. This feature has been a work in progress for awhile and was recently finished and merged in (<a href="https://github.com/godotengine/godot/pull/97647">GH-97647</a>). Thank you to Oğuzhan, Erik, and Tomek for bringing it across the finish line.</p>
|
||
<p>To further improve your debugging experience Hendrik introduced a checkbox that allows you to start the profiler automatically when you run your game from the editor and capture valuable profiling data immediately (<a href="https://github.com/godotengine/godot/pull/96759">GH-96759</a>).</p>
|
||
<p>The editor has become more ergonomic for everyone! Ryevdokimov added object snapping for moving 3D objects in the editor (<a href="https://github.com/godotengine/godot/pull/96740">GH-96740</a>) which allows you to snap existing objects to other objects when you move them. This can be toggled on by selecting an object and pressing Shift+G.</p>
|
||
<video autoplay="" loop="" muted="" playsinline="">
|
||
<source src="/storage/blog/dev-snapshot-godot-4-4-dev-4/physics-placement.mp4?1" type="video/mp4" />
|
||
</video>
|
||
<p>To reduce clutter in your inspector and highlight the properties you care the most about, YeldhamDev brings us the long-awaited ability to pin one’s favorite properties in the inspector! Check out the implementation in PR <a href="https://github.com/godotengine/godot/pull/97352">GH-97352</a>.</p>
|
||
<p>Thanks to Danil Alexeev, the GDScript code editor will now display a tooltip containing information about functions, variables, classes, etc. when you hover over them, including the documentation you have written using our documentation system (<a href="https://github.com/godotengine/godot/pull/91060">GH-91060</a>). This makes using the integrated documentation system even more powerful as you no longer have to bounce between the code editor and the related docs to quickly get information.</p>
|
||
<h3 id="gdscript">GDScript</h3>
|
||
<p>This release GDScript saw quite a few quality of life features to improve your development experience. For example, you can now create buttons in the inspector seamlessly using the new <code class="language-plaintext highlighter-rouge">@export_tool_button</code> annotation in <code class="language-plaintext highlighter-rouge">@tool</code> scripts. This was added by Macksaur in <a href="https://github.com/godotengine/godot/pull/96290">GH-96290</a>.</p>
|
||
<p>Danil Alexeev brings us <code class="language-plaintext highlighter-rouge">@warning_ignore_start</code> and <code class="language-plaintext highlighter-rouge">@warning_ignore_restore</code> (<a href="https://github.com/godotengine/godot/pull/76020">GH-76020</a>) to suppress warnings in a safely scoped manner across entire sections of code. Similarly, <code class="language-plaintext highlighter-rouge">@warning_ignore</code> no longer works when applied to a function. This is because it previously had undocumented functionality which applied the warning to the <em>entire function</em> unexpectedly. Now users have much more control and the annotations should function more like what you would expect.</p>
|
||
<h3 id="import">Import</h3>
|
||
<p>4.4 is coming with huge improvements to texture importing quality and speed thanks to new maintainer Bluecube3310. The import times of textures using the “VRAM Compressed” import setting have been greatly improved by integrating the GPU-based Betsy texture compressor. The biggest difference is observable when importing HDR images (such as HDRIs or lightmaps), which used to take up to several minutes before. Thanks to Betsy, as well as other optimizations to the import process (<a href="https://github.com/godotengine/godot/pull/92291">GH-92291</a> and <a href="https://github.com/godotengine/godot/pull/95291">GH-95291</a>), that time has gone down significantly. Additionally, textures not using the “High Quality” import setting should look better by default, since previously we had to trade the quality for faster import times. Further, there have been countless improvements to the texture import process to improve compatibility across devices and the number of texture formats supported. Overall, texture importing should feel faster and more stable than ever before.</p>
|
||
<p>The new retargeting method, RetargetModifier3D, a new feature from Tokage allows users to use animation retargeting without discarding the original bone rests that were set in the external DCC (<a href="https://github.com/godotengine/godot/pull/97824">GH-97824</a>).</p>
|
||
<p>Godot now supports the <a href="https://github.com/KhronosGroup/glTF/tree/main/extensions/2.0/Khronos/KHR_animation_pointer"><code class="language-plaintext highlighter-rouge">KHR_animation_pointer</code></a> glTF extension thanks to the efforts of Aaron Franke (<a href="https://github.com/godotengine/godot/pull/94165">GH-94165</a>). This allows imported animations to target custom properties in addition to position, rotation, scale, and mesh blend shape weights (which were all it previously supported). For example, you can now animate the color of a light, the FOV of a camera, the albedo color of a material, the UV offset of a material, and more.</p>
|
||
<h3 id="input">Input</h3>
|
||
<p>Input saw a lot of incremental improvements and polish this dev cycle. Notably, rptfrg made their first contribution by lowering the default deadzone for new actions from 0.5 down to 0.2 (<a href="https://github.com/godotengine/godot/pull/97281">GH-97281</a>). This should make input feel much more responsive by default. And, after several years of diligent effort, Markus Sauermann has expanded the Drag-and-Drop system to support dragging and dropping across different <code class="language-plaintext highlighter-rouge">Viewports</code> and even <code class="language-plaintext highlighter-rouge">Windows</code>. For more information, see <a href="https://github.com/godotengine/godot/pull/67531">GH-67531</a>.</p>
|
||
<h3 id="navigation">Navigation</h3>
|
||
<p>Navigation contains some of the oldest code in the engine. While it continues to serve its purpose, much of it is getting dated and needs to be cleaned up. Accordingly, the Navigation team, especially smix8, have bravely stepped up and begun the difficult process of improving legacy code. Fortunately, their work has already begun to bear fruit in the form of a cleaner codebase and faster Navigation features.</p>
|
||
<p>Notably, the navigation map synchronization now happens asynchronously and in a background thread so it has a much smaller impact on framerate. Instead of making the entire game slow down on lower end systems, updates will just happen less frequently.</p>
|
||
<p>There have also been many quality of life improvements such as debug indicators to show the direction of NavigationLinks (<a href="https://github.com/godotengine/godot/pull/101010">GH-101010</a>) and support for transforming NavigationObstacle nodes using the node’s transform (<a href="https://github.com/godotengine/godot/pull/96730">GH-96730</a>).</p>
|
||
<h3 id="physics">Physics</h3>
|
||
<p>Ever since its inception in late 2022, godot-jolt has slowly become the de-facto 3D physics engine for many of our developers. So it is no surprise that the Godot Jolt maintainers, Mikael Hermansson and Jorrit Rouwe, have taken things a step further and integrated Jolt as part of the engine directly. There was already a symbiosis between their team and Godot, with many features being added to Godot and Jolt to accommodate both, but the integration of an official module was no small feat; their pull request (<a href="https://github.com/godotengine/godot/pull/99895">GH-99895</a>) ended up adding over 500 files and 115 thousand lines of code!</p>
|
||
<p>Note: At time of writing, this does not replace Godot Physics as the default 3D physics engine. The Jolt Physics integration in Godot is considered experimental, and may change in future releases. It also lacks some features of Godot Physics, so it isn’t a full drop-in replacement. If your interests/use-case are supported, the tool can be enabled by changing the <strong>Physics &gt; 3D &gt; Physics Engine</strong> project setting to <strong>Jolt Physics</strong>.</p>
|
||
<p>Our hope is that many users opt to use Jolt as their 3D physics backend and give us valuable feedback so we can improve our integration with Jolt and eventually make it the default physics engine for all new projects.</p>
|
||
<h3 id="platforms">Platforms</h3>
|
||
<h4 id="linux">Linux</h4>
|
||
<p>pkowal1982’s long-running pull request, <a href="https://github.com/godotengine/godot/pull/53666">GH-53666</a>, was finally merged adding camera support for the Linux platform, allowing developers to access connected cameras from within their game.</p>
|
||
<h4 id="android">Android</h4>
|
||
<p>Thanks to the tireless efforts of Fredia Huya-Kouadio and Anish Mishra (our newest Android maintainer), the development experience on Android devices for Android devices has become significantly better. In <a href="https://github.com/godotengine/godot/pull/93526">GH-93526</a> Fredia added support for exporting games from the Android editor. Previously developers had to leave their Android device when they exported their game. Fredia also added support for launching the Play window in PiP mode (in <a href="https://github.com/godotengine/godot/pull/95700">GH-95700</a>) allowing developers to more easily take advantage of the tight integration between the editor and running game while developing on Android devices.</p>
|
||
<p>To further improve the development experience on Android, Anish added support for the native file picker (in <a href="https://github.com/godotengine/godot/pull/98350">GH-98350</a>) so now Android game and app developers can benefit from using the file picker that Android provides and Android users are accustomed to. Similarly, Fredia added the new AndroidRuntime plugin which exposes the Android Runtime, making it easier to access Android libraries and SDKs in games/apps. For example, for APIs bundled in the Android OS, no additional setup is required and they can be accessed directly using this new plugin. For more details, see <a href="https://github.com/godotengine/godot/pull/97500">GH-97500</a>.</p>
|
||
<h3 id="rendering-and-shaders">Rendering and shaders</h3>
|
||
<p>Many monumental rendering changes were finished towards the end of the 4.3 dev cycle slightly too late to be included in 4.3. As a result, 4.4 contains a massive amount of exciting features, too many to include here, but here are a few.</p>
|
||
<p>For Apple users, Stuart Carnie has been hard at work ensuring that you get the benefit of the best performance by incorporating the Metal rendering backend (<a href="https://github.com/godotengine/godot/pull/88199">GH-88199</a>, <a href="https://godotengine.org/article/dev-snapshot-godot-4-4-dev-1/">Dev snapshot: Godot 4.4 dev 1</a>) and the MetalFX upscaler (mentioned above).</p>
|
||
<p>DarioSamo spent several months last year perfecting the Ubershader system which was earlier designed by Juan Linietsky and Clay John in the early days of building Godot 4. The Ubershader allows the engine to compile a flexible, but slow version of shaders at load time which can be used as a fallback while the optimized shaders compile in the background. The technique allows users to ship games <strong>without shader stutter</strong> and without resorting to manually displaying every possible material and object combination behind a loading screen.</p>
|
||
<p>Shadow caster masks, a long awaited improvement from EMBYRDEV, allow users to apply a mask on Light3Ds to select what rendering layers will be considered when casting shadows (<a href="https://github.com/godotengine/godot/pull/85338">GH-85338</a>). Previously, it was only possible to disable shadows from a GeometryInstance (for all Light3Ds) or a Light3D (for all GeometryInstances). This allows much more fine-grained control that allows users to further optimize dynamic lights and control where shadows appear in their games.</p>
|
||
<p>After tackling the Metal rendering backend merged in an earlier snapshot, Stuart took on another impressive rendering contribution: 2D batching! Batching has been implemented in the Compatibility renderer since the release of 4.0. This release brings the same performance benefits to the other backends by implementing batching when using the Forward+ and Mobile backends (<a href="https://github.com/godotengine/godot/pull/92797">GH-92797</a>). Now 2D performance is comparable between all backends.</p>
|
||
<p>Continuing their excellent work on texture import and the Betsy texture compressor, BlueCube has made huge improvements to the lightmapper by adding:</p>
|
||
<ul>
|
||
<li>Support for bicubic sampling to smooth out the results of low resolution lightmap bakes (<a href="https://github.com/godotengine/godot/pull/89919">GH-89919</a>)</li>
|
||
<li>Shadow masks, to allow falling back on baked lighting when outside of the range of dynamic lights (<a href="https://github.com/godotengine/godot/pull/85653">GH-85653</a>)</li>
|
||
<li>Compression for lightmap textures to reduce the memory use and rendering overhead of large lightmap textures (<a href="https://github.com/godotengine/godot/pull/100327">GH-100327</a>).</li>
|
||
</ul>
|
||
<p>Hendrik Brucker, a long time contributor, also decided that lightmaps deserved some attention this release and carried the work of Hugo Locurcio and Guerro323 over the finish line by implementing lightmap supersampling (which bakes the lightmap at a higher resolution to reduce aliasing and capture finer details) and adding support for transparent objects to lightmap baking (including semi-transparent shadows).</p>
|
||
<p>Ricardo Buring continued his amazing work in bringing physics interpolation to Godot 4. This time around he added support for 3D objects (include Multimesh!). Physics interpolation is a technique that allows you to run your physics update at a very low FPS while maintaining smooth movement. This allows you to both save CPU overhead and make your game look much smoother.</p>
|
||
<video autoplay="" loop="" muted="" playsinline="">
|
||
<source src="/storage/blog/dev-snapshot-godot-4-4-dev-1/physics-interpolation.mp4?1" type="video/mp4" />
|
||
</video>
|
||
<p>After pointing out the many limitations that exist with ReflectionProbes, Lander-vr decided to take matters into his own hands and personally overhaul the blending logic for ReflectionProbes in <a href="https://github.com/godotengine/godot/pull/100241">GH-100241</a> to make smaller probes automatically take priority over larger probes, which avoids the “double reflection” effects that can look strange. Additionally, in <a href="https://github.com/godotengine/godot/pull/99958">GH-99958</a>, he added a blend distance property so you can now configure the distance at which the reflection starts fading. The default distance at which reflections start fading is now much lower than before, which ensures the full reflection can be seen when inside the ReflectionProbe’s bounds.</p>
|
||
<p>Not content to stop there, Lander-vr also significantly improved the editor UX for ReflectionProbe and VoxelGI by making their gizmos less intrusive (in <a href="https://github.com/godotengine/godot/pull/99920">GH-99920</a>, <a href="https://github.com/godotengine/godot/pull/99969">GH-99969</a>, and <a href="https://github.com/godotengine/godot/pull/100370">GH-100370</a>).</p>
|
||
<p><img src="/storage/blog/godot-4-4-beta-1/reflection-probes.webp" alt="Sponza with reflective floor" /></p>
|
||
<p>After many requests and years of patient waiting from many within the community, we have finally re-introduced vertex shading which is both a significant performance optimization and and integral part of recreating PSX-style graphics (<a href="https://github.com/godotengine/godot/pull/83360">GH-83360</a>). This turned out to be a significant endeavor for ywmaa who enlisted the help of veteran rendering contributor Clay John to get the feature over the finish line.</p>
|
||
<p>Currently when trying to run Godot with the Forward+ or Mobile backend on a device that doesn’t support Vulkan, D3D12, or Metal, the engine will provide the user with an OS alert notifying them that they don’t have support for the needed graphics API and they need to try again with the Compatibility backend. This alert has proven to be confusing for users and the process of opening the scene ends up being cumbersome. Now with <a href="https://github.com/godotengine/godot/pull/97142">GH-97142</a>, the first contribution from SheepYhangCN, the engine will automatically fall back to using OpenGL (the Compatibility backend) when the other backends are not available. This should provide the smoothest possible experience for users on older devices.</p>
|
||
<p>Rendering contributors have been relentless in identifying and implementing performance enhancements this release cycle. Many areas of the renderers, both 2D and 3D have been optimized and we expect that many users will notice an improvement to performance this release cycle, especially for 2D lighting, rendering on mobile devices, and general 2D rendering.</p>
|
||
<h3 id="xr">XR</h3>
|
||
<p>Thanks to Godot’s unique feature of its editor being made with the engine itself, we’ve been able to bring the Godot editor to unconventional places, such as the web and Android devices. Building upon the latter, Fredia Huya-Kouadio completed the proof of concept started by Bastiaan Olij years ago, to add support for using the Android editor on XR devices using OpenXR (<a href="https://github.com/godotengine/godot/pull/96624">GH-96624</a>)! The XR editor is currently available on the Meta Quest 3 and Quest Pro through the <a href="https://www.meta.com/experiences/godot-game-engine/7713660705416473/">Horizon Store</a>. Support for the PICO 4 Ultra is also in progress and will be available soon.</p>
|
||
<p>OpenXR support for Metal (<a href="https://github.com/godotengine/godot/pull/98872">GH-98872</a>) has been added, improving the developer experience for MacOS developers using the Meta XR Simulator.</p>
|
||
<p>Some OpenXR runtimes support applying modifiers to the action map, for example, applying thresholds or haptic triggers, and now you can configure those in Godot as well (<a href="https://github.com/godotengine/godot/pull/97140">GH-97140</a>)!</p>
|
||
<p>Support for OpenXR composition layers was added in Godot 4.3, allowing developers to show crisp and clear 2D panels that show content from a Godot <strong>SubViewport</strong>. Now, in Godot 4.4, we’ve added the ability to show content from an Android surface as well, allowing for performant media playback in XR on Android (<a href="https://github.com/godotengine/godot/pull/96185">GH-96185</a>).</p>
|
||
<h2 id="changelog">Changelog</h2>
|
||
<p><strong>140 contributors</strong> submitted <strong>406 improvements</strong> for this release. See our <a href="https://godotengine.github.io/godot-interactive-changelog/#4.4-beta1"><strong>interactive changelog</strong></a> for the complete list of changes since the 4.4-dev7 snapshot. You can also review <a href="https://godotengine.github.io/godot-interactive-changelog/#4.4">all changes included in 4.4</a> compared to the previous 4.3 feature release.</p>
|
||
<p>This release is built from commit <a href="https://github.com/godotengine/godot/commit/d33da79d3f8fe84be2521d25b9ba8e440cf25a88"><code class="language-plaintext highlighter-rouge">d33da79d3</code></a>.</p>
|
||
<h2 id="downloads">Downloads</h2>
|
||
<div class="card card-download">
|
||
<a class="card-download-link" href="/download/archive/4.4-beta1">
|
||
Download Godot 4.4 beta1
|
||
</a>
|
||
<div class="card-download-details">
|
||
<img class="lightbox-ignore" src="/storage/blog/covers/dev-snapshot-godot-4-4-beta-1.webp" />
|
||
<div class="card-download-platforms">
|
||
<div class="download-platform platform-linux">
|
||
<img width="24" height="24" src="/assets/images/platforms/linux.svg" title="Linux" alt="Linux" class="lightbox-ignore" />
|
||
Linux
|
||
</div>
|
||
<a href="https://github.com/godotengine/godot-builds/releases/download/4.4-beta1/Godot_v4.4-beta1_linux.x86_64.zip" class="btn btn-download btn-download-primary platform-linux">
|
||
<div class="download-title">
|
||
Standard
|
||
</div>
|
||
</a>
|
||
<a href="https://github.com/godotengine/godot-builds/releases/download/4.4-beta1/Godot_v4.4-beta1_mono_linux_x86_64.zip" class="btn btn-download btn-download-primary btn-download-primary--mono platform-linux">
|
||
<div class="download-title">
|
||
.NET
|
||
</div>
|
||
</a>
|
||
<div class="download-platform platform-macos">
|
||
<img width="24" height="24" src="/assets/images/platforms/macos.svg" title="macOS" alt="macOS" class="lightbox-ignore" />
|
||
macOS
|
||
</div>
|
||
<a href="https://github.com/godotengine/godot-builds/releases/download/4.4-beta1/Godot_v4.4-beta1_macos.universal.zip" class="btn btn-download btn-download-primary platform-macos">
|
||
<div class="download-title">
|
||
Standard
|
||
</div>
|
||
</a>
|
||
<a href="https://github.com/godotengine/godot-builds/releases/download/4.4-beta1/Godot_v4.4-beta1_mono_macos.universal.zip" class="btn btn-download btn-download-primary btn-download-primary--mono platform-macos">
|
||
<div class="download-title">
|
||
.NET
|
||
</div>
|
||
</a>
|
||
<div class="download-platform platform-windows">
|
||
<img width="24" height="24" src="/assets/images/platforms/windows.svg" title="Windows" alt="Windows" class="lightbox-ignore" />
|
||
Windows
|
||
</div>
|
||
<a href="https://github.com/godotengine/godot-builds/releases/download/4.4-beta1/Godot_v4.4-beta1_win64.exe.zip" class="btn btn-download btn-download-primary platform-windows">
|
||
<div class="download-title">
|
||
Standard
|
||
</div>
|
||
</a>
|
||
<a href="https://github.com/godotengine/godot-builds/releases/download/4.4-beta1/Godot_v4.4-beta1_mono_win64.zip" class="btn btn-download btn-download-primary btn-download-primary--mono platform-windows">
|
||
<div class="download-title">
|
||
.NET
|
||
</div>
|
||
</a>
|
||
</div>
|
||
</div>
|
||
<div class="card-download-sublinks">
|
||
<a class="card-download-other" href="/download/archive/4.4-beta1">
|
||
Export templates and other downloads
|
||
</a>
|
||
<a class="card-download-donate" href="https://fund.godotengine.org/">
|
||
Make a Donation
|
||
</a>
|
||
</div>
|
||
</div>
|
||
<style>
|
||
.thankyou-wrapper {
|
||
position: fixed;
|
||
top: 0;
|
||
left: 0;
|
||
right: 0;
|
||
bottom: 0;
|
||
background: rgba(0, 0, 0, 0.85);
|
||
display: flex;
|
||
flex-direction: column;
|
||
justify-content: center;
|
||
align-items: center;
|
||
z-index: 10;
|
||
}
|
||
.thankyou {
|
||
background: var(--base-color);
|
||
box-shadow: var(--more-shadow);
|
||
padding: 30px;
|
||
display: flex;
|
||
flex-direction: column;
|
||
align-items: center;
|
||
text-align: center;
|
||
position: relative;
|
||
border-radius: 13px;
|
||
}
|
||
.thankyou-reading {
|
||
font-size: 16px;
|
||
}
|
||
.thankyou-reading-list {
|
||
font-size: 16px;
|
||
margin: 0;
|
||
margin-left: 48px;
|
||
padding-left: 0;
|
||
}
|
||
.thankyou-donate {
|
||
margin-bottom: 24px;
|
||
text-align: center;
|
||
}
|
||
.btn.btn-donate {
|
||
background-color: var(--primary-color);
|
||
color: hsla(0, 0%, 100%, 0.9);
|
||
font-size: 22px;
|
||
font-weight: 600;
|
||
margin-bottom: 26px;
|
||
}
|
||
.thankyou h2 {
|
||
text-shadow: var(--base-shadow);
|
||
font-size: 36px;
|
||
font-weight: 800;
|
||
margin-bottom: 12px;
|
||
}
|
||
.thankyou h2 .anchored-link {
|
||
/* Hiding the anchored text automatically added on blogposts */
|
||
display: none !important;
|
||
}
|
||
.thankyou p {
|
||
max-width: 620px;
|
||
font-size: 25px;
|
||
}
|
||
@media (max-width: 768px) {
|
||
.thankyou-wrapper {
|
||
display: block;
|
||
}
|
||
.thankyou {
|
||
position: absolute;
|
||
top: 0;
|
||
left: 0;
|
||
right: 0;
|
||
bottom: 0;
|
||
overflow: scroll;
|
||
padding: 30px 40px 18px 40px;
|
||
}
|
||
.thankyou-reading-list {
|
||
margin-left: 24px;
|
||
}
|
||
.btn-close-thankyou-popup {
|
||
width: 48px;
|
||
height: 48px;
|
||
display: flex;
|
||
justify-content: center;
|
||
align-items: center;
|
||
}
|
||
}
|
||
.btn-close-thankyou-popup {
|
||
cursor: pointer;
|
||
position: absolute;
|
||
top: 12px;
|
||
right: 12px;
|
||
}
|
||
.btn-close-thankyou-popup img {
|
||
background: transparent !important; /* for overwriting the style in the blogposts img */
|
||
}
|
||
@media (prefers-color-scheme: light) {
|
||
.btn-close-thankyou-popup img {
|
||
filter: invert(1);
|
||
opacity: 0.75;
|
||
}
|
||
}
|
||
</style>
|
||
<script>
|
||
document.addEventListener('DOMContentLoaded', () => {
|
||
const thankYouWrapper = document.getElementById('thank-you');
|
||
// Close itself, when clicked outside of the popup area.
|
||
thankYouWrapper.addEventListener('click', (e) => {
|
||
if (e.target === thankYouWrapper) {
|
||
thankYouWrapper.style.display = 'none';
|
||
}
|
||
});
|
||
// Close with a close button.
|
||
const thankYouBackButton = document.querySelector('.btn-close-thankyou-popup');
|
||
thankYouBackButton.addEventListener('click', () => {
|
||
thankYouWrapper.style.display = 'none';
|
||
});
|
||
// Open from the main download buttons.
|
||
const downloadButtons = document.querySelectorAll('.btn-download');
|
||
downloadButtons.forEach((it) => {
|
||
it.addEventListener('click', () => {
|
||
thankYouWrapper.style.display = '';
|
||
document.querySelector('.btn.btn-donate').focus();
|
||
});
|
||
});
|
||
// Open from the all downloads list.
|
||
const downloadLinks = document.querySelectorAll('.download-link');
|
||
downloadLinks.forEach((it) => {
|
||
it.addEventListener('click', () => {
|
||
thankYouWrapper.style.display = '';
|
||
});
|
||
});
|
||
// Close the dialog when the user presses the escape key.
|
||
document.addEventListener('keydown', (e) => {
|
||
if (e.key === 'Escape') {
|
||
thankYouWrapper.style.display = 'none';
|
||
}
|
||
});
|
||
});
|
||
</script>
|
||
<div class="thankyou-wrapper" id="thank-you" style="display: none;">
|
||
<div class="thankyou">
|
||
<h2>Godot is downloading...</h2>
|
||
<p class="thankyou-donate">
|
||
Godot exists thanks to donations from people like you. Help us continue our work:
|
||
</p>
|
||
<a href="https://fund.godotengine.org" class="btn btn-donate">
|
||
Make a Donation
|
||
</a>
|
||
<div class="btn-close-thankyou-popup">
|
||
<img src="/assets/icons/cross.svg" width="24" height="24" alt="Close this popup" class="lightbox-ignore" />
|
||
</div>
|
||
</div>
|
||
</div>
|
||
<p><strong>Standard build</strong> includes support for GDScript and GDExtension.</p>
|
||
<p><strong>.NET build</strong> (marked as <code class="language-plaintext highlighter-rouge">mono</code>) includes support for C#, as well as GDScript and GDExtension.</p>
|
||
<ul>
|
||
<li>.NET 8.0 or newer is required for this build, changing the minimal supported version from .NET 6 to 8.</li>
|
||
</ul>
|
||
<div class="card card-warning">
|
||
<p>
|
||
While engine maintainers try their best to ensure that each preview snapshot and release candidate is stable, this is by definition <strong>a pre-release piece of software</strong>. Be sure to make frequent backups, or use a version control system such as Git, to preserve your projects in case of corruption or data loss.
|
||
</p>
|
||
</div>
|
||
<h2 id="known-issues">Known issues</h2>
|
||
<p>During the beta stage, we focus on solving both regressions (i.e. something that worked in a previous release is now broken) and significant new bugs introduced by new features. You can have a look at our current <a href="https://github.com/orgs/godotengine/projects/61">list of regressions and significant issues</a> which we aim to address before releasing 4.4. This list is dynamic and will be updated if we discover new showstopping issues after more users start testing the beta snapshots.</p>
|
||
<p>With every release, we accept that there are going to be various issues which have already been reported but haven’t been fixed yet. See the GitHub issue tracker for a complete list of <a href="https://github.com/godotengine/godot/issues?q=is%3Aissue+is%3Aopen+label%3Abug+">known bugs</a>.</p>
|
||
<ul>
|
||
<li>
|
||
<p>Baking a Lightmap3D is more prone to crash after we added support for transparency. The issue is tracked in <a href="https://github.com/godotengine/godot/issues/101391">GH-101391</a>.</p>
|
||
</li>
|
||
<li>
|
||
<p>Changes to scenes are not reflected in APK exports after the initial export in the Android editor. The issue is tracked in <a href="https://github.com/godotengine/godot/issues/101007">GH-101007</a>.</p>
|
||
</li>
|
||
</ul>
|
||
<h2 id="bug-reports">Bug reports</h2>
|
||
<p>As a tester, we encourage you to <a href="https://github.com/godotengine/godot/issues">open bug reports</a> if you experience issues with this release. Please check the <a href="https://github.com/godotengine/godot/issues">existing issues on GitHub</a> first, using the search function with relevant keywords, to ensure that the bug you experience is not already known.</p>
|
||
<p>In particular, any change that would cause a regression in your projects is very important to report (e.g. if something that worked fine in previous 4.x releases, but no longer works in this snapshot).</p>
|
||
<h2 id="support">Support</h2>
|
||
<p>Godot is a non-profit, open source game engine developed by hundreds of contributors on their free time, as well as a handful of part or full-time developers hired thanks to <a href="https://fund.godotengine.org/">generous donations from the Godot community</a>. A big thank you to everyone who has contributed <a href="https://github.com/godotengine/godot/blob/master/AUTHORS.md">their time</a> or <a href="https://github.com/godotengine/godot/blob/master/DONORS.md">their financial support</a> to the project!</p>
|
||
<p>If you’d like to support the project financially and help us secure our future hires, you can do so using the <a href="https://fund.godotengine.org/">Godot Development Fund</a> platform managed by <a href="https://godot.foundation/">Godot Foundation</a>. There are also several <a href="/donate">alternative ways to donate</a> which you may find more suitable.</p></description><category>Pre-release</category><guid>https://godotengine.org/article/dev-snapshot-godot-4-4-beta-1/</guid><dc:creator>Godot contributors</dc:creator><pubDate>Thu, 16 Jan 2025 18:00:00 +0000</pubDate><image>https://godotengine.org/storage/blog/covers/dev-snapshot-godot-4-4-beta-1.webp</image></item><item><title>UID changes coming to Godot 4.4</title><link>https://godotengine.org/article/uid-changes-coming-to-godot-4-4/</link><summary>Godot's resource UID system is changing to better support scripts and shaders. Read on to know what's required on your part to fully benefit from it.</summary><description><h2 id="why-use-uids-in-godot">Why use UIDs in Godot?</h2>
|
||
<p>Until Godot 4.0, the engine exclusively relied on file paths to refer to scenes, scripts and other resources. While this means references in scenes and scripts use human-readable paths, these paths will break if files are moved to a different location in the project (regardless of whether the move was done using the FileSystem dock or outside Godot). This is especially problematic for large projects where filesystem organization often changes regularly.</p>
|
||
<p>Since Godot 3.x, the editor already updates path references if files are moved within the FileSystem dock. This works more or less, but has drawbacks: the process is slow in large projects (as files need to be scanned and modified), file paths in scripts are left unchanged, and a single file move can result in a large amount of modified files in commits. It’s also not fully reliable, and veteran Godot users probably remember various situations where moving a file seemingly corrupted a scene or resource.</p>
|
||
<p>Additionally, it is common for users to move these files outside Godot (e.g. using the OS file manager, an IDE or the command line). If the editor is not open, it has no way to know the change happened. Even if the editor is open, when working with version control, files may change or be moved and the editor has no way to know where files have gone, resulting in all sorts of errors.</p>
|
||
<p>With the aim of making Godot better suited for large projects and significantly more resilient to external filesystem changes, ensuring this is a fully supported workflow has become a priority. External file manager programs often have more features than Godot’s own FileSystem dock, making them more convenient for many use cases. This means we need an approach that can reliably track files being moved, even if the Godot editor isn’t open.</p>
|
||
<p>Partial “Unique IDentifier” (UID) support was therefore introduced in Godot 4.0, which made it possible for users to safely move files outside Godot if they have UID support implemented. The editor will automatically store resource references as UIDs, with the path still being stored alongside for displaying in the editor UI (and as a fallback if the UID reference becomes invalid). However, UID support wasn’t completely finished by the time Godot 4.0 released, which means many file types didn’t benefit from the UID system entirely (if at all).</p>
|
||
<h2 id="limitations-of-uids-before-godot-44">Limitations of UIDs before Godot 4.4</h2>
|
||
<p>Each imported resource in Godot has a <code class="language-plaintext highlighter-rouge">.import</code> file, which allows for storing a UID. Additionally, Godot’s own scene and resource file formats store a UID in their header. However, scripts and shaders are not imported resources and they are “plain text” formats, without any Godot-specific information stored within. In practice, this meant that UIDs could be used for scenes and most resources, but not scripts and shaders. The UID implementation was therefore not covering every resource type Godot support (<a href="https://docs.godotengine.org/en/stable/classes/class_script.html">scripts</a> and <a href="https://docs.godotengine.org/en/stable/classes/class_shader.html">shaders</a> are resources too).</p>
|
||
<p>Moreover, the editor support for making use of UIDs and relying primarily on them was lacking, so UIDs didn’t yet fulfill their promise of enabling seamless refactoring of project files.</p>
|
||
<h2 id="whats-changing-with-uids-in-godot-44">What’s changing with UIDs in Godot 4.4</h2>
|
||
<p>To resolve the issue of scripts and shaders not being able to benefit from the UID system, dedicated UID files are being introduced in Godot 4.4. These files are automatically generated by Godot when saving a script or shader and are placed besides the source file with the <code class="language-plaintext highlighter-rouge">.uid</code> extension as a suffix. For example, if you have <code class="language-plaintext highlighter-rouge">some_file.gd</code> and <code class="language-plaintext highlighter-rouge">some_file.shader</code>, Godot will generate the files <code class="language-plaintext highlighter-rouge">some_file.gd.uid</code> and <code class="language-plaintext highlighter-rouge">some_file.shader.uid</code>. This avoids conflicts in case a script and shader file have the same name (but a different extension) within the same folder.</p>
|
||
<p>This now means you can use UID references in your own scripts if you wish. While using file paths is still the primary approach for now, using UIDs means that the paths to other referenced resources can safely change without breaking the script, even if the files are moved outside Godot.</p>
|
||
<div class="language-gdscript highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="k">extends</span> <span class="n">Node</span>
|
||
<span class="c1"># These references point to the same Script resource.</span>
|
||
<span class="c1"># `other_script.gd` contains a `static func greet()` that prints some text.</span>
|
||
<span class="k">var</span> <span class="n">other_script</span> <span class="o">=</span> <span class="nb">preload</span><span class="p">(</span><span class="s2">"res://other_script.gd"</span><span class="p">)</span>
|
||
<span class="c1"># TIP: You can copy any resource's UID from the FileSystem dock's context menu.</span>
|
||
<span class="k">var</span> <span class="n">other_script_uid</span> <span class="o">=</span> <span class="nb">preload</span><span class="p">(</span><span class="s2">"uid://fkjlqx8er2sg"</span><span class="p">)</span>
|
||
<span class="k">func</span> <span class="nf">_ready</span><span class="p">():</span>
|
||
<span class="n">other_script</span><span class="o">.</span><span class="n">greet</span><span class="p">()</span>
|
||
<span class="n">other_script_uid</span><span class="o">.</span><span class="n">greet</span><span class="p">()</span>
|
||
</code></pre></div></div>
|
||
<p>Thanks to <a href="https://github.com/godotengine/godot/pull/100803">GH-100803</a>, you can see the underlying <code class="language-plaintext highlighter-rouge">res://</code> path and resource type when hovering the <code class="language-plaintext highlighter-rouge">uid://</code> path with the mouse in the script editor. (This feature also works when hovering <code class="language-plaintext highlighter-rouge">res://</code> paths, so it is not exclusive to <code class="language-plaintext highlighter-rouge">uid://</code> paths.)</p>
|
||
<h2 id="what-should-i-change-in-my-project-or-workflow">What should I change in my project or workflow?</h2>
|
||
<p>The most important step is to <strong>make sure <code class="language-plaintext highlighter-rouge">.uid</code> files are committed to version control</strong>. In other words, <code class="language-plaintext highlighter-rouge">*.uid</code> should <strong>not</strong> be added to <code class="language-plaintext highlighter-rouge">.gitignore</code>.</p>
|
||
<p>Secondly, when you move a script or shader outside Godot, <strong>you should also move the <code class="language-plaintext highlighter-rouge">.uid</code> file along with it</strong>. When you remove a script or shader outside Godot, you should also remove the <code class="language-plaintext highlighter-rouge">.uid</code> file, although this is less important – not removing the <code class="language-plaintext highlighter-rouge">.uid</code> file won’t break anything.</p>
|
||
<p>Moving files externally will produce warnings when opening scenes referencing said files. You need to re-save all depending scenes to remove warnings.</p>
|
||
<p>After upgrading the project to 4.4, you should re-save all scenes and resources to add any missing UID references. The editor will add them automatically as you save scenes/resources for the first time with 4.4, but it’s better to do it all at once to avoid random diffs appearing in version control later on.</p>
|
||
<h2 id="frequently-asked-questions">Frequently asked questions</h2>
|
||
<h3 id="why-not-use-another-approach-to-track-file-references-like-checksums">Why not use another approach to track file references like checksums?</h3>
|
||
<p>Godot already keeps track of checksums in <code class="language-plaintext highlighter-rouge">.import</code> files. This is used to detect whether the file has actually changed, and can therefore reimport the file if it has changed while Godot wasn’t open.</p>
|
||
<p>Unfortunately, checksums are the wrong tool for the job to keep track of <strong>unique</strong> file references. If you have two files with the exact same content, they would have the same checksum, but these files are still separately referenced by other scenes or resources in the project (with the expectation that these remain separate). If we relied on the file’s checksum to determine file references, then the references would break once the file contents change.</p>
|
||
<p>There could still be value to computing a checksum and storing it in <code class="language-plaintext highlighter-rouge">.uid</code> files, so that Godot can automatically move the UID file if the source file was moved without its UID file. This is something that should be tackled separately though, as this approach comes with its downsides too.</p>
|
||
<h3 id="why-not-use-replace-import-files-with-meta-files-and-use-them-for-all-resources-that-have-an-uid">Why not use replace <code class="language-plaintext highlighter-rouge">.import</code> files with <code class="language-plaintext highlighter-rouge">.meta</code> files and use them for all resources that have an UID?</h3>
|
||
<p>While Godot must import many resource types before they can be used in a project, not all types actually need to be imported to be used. Resources that don’t need to be imported to be used don’t have properties that you could set on import, as they are directly loaded by Godot with no remapping system in place. Instead, everything about the file is inferred from the file itself. This approach makes more sense for files that you expect to be able to copy-paste around (or even copy directly from websites), while making sure the file remains functional without needing a separate metadata file. It’s a common workflow from users to copy scripts or shaders from websites such as <a href="https://godotshaders.com/">Godot Shaders</a> after all.</p>
|
||
<p>The main examples of resources that don’t need to be imported are scripts and shaders, hence the dedicated <code class="language-plaintext highlighter-rouge">.uid</code> files.</p>
|
||
<p>It has been suggested that we could still use <code class="language-plaintext highlighter-rouge">.meta</code> files for scripts and shaders, and use them to store more information than just UIDs, such as user-defined metadata. For the time being we prefer to focus on the problem at hand (the need of UIDs for better refactoring possibility) and not future-proof things. If we ever change our mind, it would be easy enough to migrate information from <code class="language-plaintext highlighter-rouge">.uid</code> files to whichever new container we decide to use.</p>
|
||
<h3 id="why-not-use-a-single-centralized-file-to-store-all-the-projects-uids">Why not use a single centralized file to store all the project’s UIDs?</h3>
|
||
<p>Many other programs use a centralized database to store UIDs for all files in the project. While this approach makes for a leaner filesystem, it also has several downsides:</p>
|
||
<ul>
|
||
<li>With a centralized file for all UIDs, the purpose of being able to move scripts or shaders outside of Godot would not be fulfilled. When moving a script outside of Godot, the centralized UID mapping would not be updated, and thus it would lose the connection between the previous path and its UID. For this use case to be supported, the UID needs to be close to the file being moved - either alongside it in a <code class="language-plaintext highlighter-rouge">.uid</code> or <code class="language-plaintext highlighter-rouge">.import</code> file, or embedded in it (e.g. for <code class="language-plaintext highlighter-rouge">.tscn</code> or <code class="language-plaintext highlighter-rouge">.tres</code> files).</li>
|
||
<li>This file would be subject to frequent merge conflicts in version control systems. For example, if you have two branches that add or edit different scripts/shaders, they would each add their own lines to the UID database file. Both of these branches would add these lines at the same location in the file (probably at the end). However, once you try to merge those two branches together, your version control system wouldn’t be able to know what to keep automatically. This is where a merge conflict occurs.
|
||
<ul>
|
||
<li>In contrast, using separate files ensures merge conflicts don’t happen quite as often. If conflicts do arise, they can be resolved by just including the file (or removing it if the source file has also been removed).</li>
|
||
</ul>
|
||
</li>
|
||
<li>Centralizing UID information is problematic for add-ons. For example, if a developer refactors their addon and moves files around, then someone downloads the new version of their addon into an existing project of theirs, references to files in the addon in their project get updated automatically. If UIDs are stored in a centralized fashion, there wouldn’t be a way to do this as the addon’s UIDs wouldn’t be stored in the addon. This would result in UID references breaking.</li>
|
||
</ul>
|
||
<p>While using separate UID files is not perfect by any means, we felt it was a better compromise for Godot’s design and to ensure version control remains as seamless as possible.</p>
|
||
<h3 id="why-not-embed-the-uid-directly-in-the-scripts-as-a-comment-or-annotation">Why not embed the UID directly in the scripts as a comment or annotation?</h3>
|
||
<p>We evaluated it, but we saw a lot of pushback against having this kind of magic string injected as a comment or annotation in all script files, as testers found it to be quite disruptive.</p>
|
||
<p>On the technical side, there are also implementation hurdles. All scripting languages supported by Godot (including community bindings via GDExtension) would need to implement this kind of magic comment or annotation (if they have such a concept) with an appropriate syntax. The Godot editor would need to know how to extract these UIDs from all types of scripts in an efficient manner (without having to parse it).</p>
|
||
<p>Additionally, external IDEs and tools may not play nice with such Godot-specific comments or annotations in various scripting languages, and if Godot-specific plugins want to implement UID support, they would also need to manually implement how to extract the UIDs from the scripts in an efficient manner (as opposed to just reading a file with a predictable name).</p>
|
||
<p>Finally, it’s not only scripts and shaders that need UIDs, but all resources. While most other builtin resource types can store UID information as described above, this system is also relevant for custom resource formats that users can implement. Having <code class="language-plaintext highlighter-rouge">.uid</code> files generated for such resources makes the system work out of the box.</p>
|
||
<h3 id="what-happens-if-i-dont-commit-uid-files-to-version-control">What happens if I don’t commit <code class="language-plaintext highlighter-rouge">.uid</code> files to version control?</h3>
|
||
<p>If you forget to commit <code class="language-plaintext highlighter-rouge">.uid</code> files to version control, the project will still work locally. However, as soon as you clone the project on another device, the UID references will break. Godot will still be able to resolve them if the paths haven’t changed (since paths are also saved as a fallback), but a warning will be printed for every resource where a path fallback had to be used to infer the reference. This behavior should not be relied upon intentionally, as it is possible for two resources to be swapped around without either of their paths changing. This can occur if the path of one of the resources was changed to be identical to another resource that was relocated elsewhere.</p>
|
||
<h2 id="support">Support</h2>
|
||
<p>Godot is a non-profit, open source game engine developed by hundreds of contributors on their free time, as well as a handful of part or full-time developers hired thanks to <a href="https://fund.godotengine.org/">generous donations from the Godot community</a>. A big thank you to everyone who has contributed <a href="https://github.com/godotengine/godot/blob/master/AUTHORS.md">their time</a> or <a href="https://github.com/godotengine/godot/blob/master/DONORS.md">their financial support</a> to the project!</p>
|
||
<p>If you’d like to support the project financially and help us secure our future hires, you can do so using the <a href="https://fund.godotengine.org/">Godot Development Fund</a> platform managed by <a href="https://godot.foundation/">Godot Foundation</a>. There are also several <a href="/donate">alternative ways to donate</a> which you may find more suitable.</p></description><category>Progress Report</category><guid>https://godotengine.org/article/uid-changes-coming-to-godot-4-4/</guid><dc:creator>Hugo Locurcio</dc:creator><pubDate>Wed, 15 Jan 2025 14:00:00 +0000</pubDate><image>https://godotengine.org/storage/blog/covers/uid-changes-coming-to-godot-4-4.webp</image></item><item><title>Godot C# packages move to .NET 8</title><link>https://godotengine.org/article/godotsharp-packages-net8/</link><summary>On moving to the latest .NET LTS release, and what it means for users.</summary><description><p>A new version of .NET is released in November each year, alternating Long Term Support (LTS) and Standard Term Support (STS) releases. The quality of all releases is the same. The only difference is the length of support. LTS releases are supported for 3 years, while STS releases are supported for 18 months.</p>
|
||
<p>With the release of Godot 4.0, we moved our C# packages from targeting Mono to .NET 6. This version of .NET was released on November 8, 2021 and ended support on November 12, 2024.</p>
|
||
<p>With .NET 6 ending support, Godot C# packages in 4.4 will target the current LTS release, .NET 8. Thanks to <a href="https://github.com/RedworkDE">RedworkDE</a> and <a href="https://github.com/paulloz">Paul Joannon</a> for their great work in <a href="https://github.com/godotengine/godot/pull/92131">GH-92131</a>.</p>
|
||
<figure>
|
||
<picture>
|
||
<source srcset="/storage/blog/dotnet/release-schedule-dark.svg" media="(prefers-color-scheme: dark)" />
|
||
<img class="lightbox-ignore" style="background-color: transparent;" src="/storage/blog/dotnet/release-schedule-light.svg" />
|
||
</picture>
|
||
<figcaption><small>.NET release cadence from the <a href="https://dotnet.microsoft.com/en-us/platform/support/policy/dotnet-core">.NET official support policy</a>.</small></figcaption>
|
||
</figure>
|
||
<h2 id="what-does-this-mean-for-users">What does this mean for users?</h2>
|
||
<p>Starting with Godot 4.4, your project will need to target .NET 8 or newer, otherwise it will be incompatible with the new <code class="language-plaintext highlighter-rouge">GodotSharp</code> packages. You will still be able to use other libraries that target older .NET versions.</p>
|
||
<p>Existing projects will be automatically upgraded to target <code class="language-plaintext highlighter-rouge">net8.0</code> when they are opened with Godot 4.4. If your project already targets .NET 8 or newer, nothing will change. This was implemented in <a href="https://github.com/godotengine/godot/pull/100195">GH-100195</a>.</p>
|
||
<h2 id="what-took-so-long">What took so long?</h2>
|
||
<p>The version of .NET that a library targets becomes the minimum required version for consumers of that library. That is, if the <code class="language-plaintext highlighter-rouge">GodotSharp</code> package targets <code class="language-plaintext highlighter-rouge">net7.0</code>, your game project needs to target <code class="language-plaintext highlighter-rouge">net7.0</code> or newer. We didn’t want to force our users to upgrade to a non-LTS release.</p>
|
||
<p>When .NET 8 was released in November 2023, it would’ve been a good time to bump the target version in Godot C# packages, since .NET 8 is an LTS release. Unfortunately, there were some breaking changes in .NET 7<sup id="fnref:1" role="doc-noteref"><a href="#fn:1" class="footnote" rel="footnote">1</a></sup> that prevented us from upgrading, and making the required changes took us longer than we hoped.</p>
|
||
<p>However, users could always use the latest version of .NET in their projects. Up until now, .NET 6 has been the minimum required version, but newer versions have always been supported from day one (even the pre-releases<sup id="fnref:2" role="doc-noteref"><a href="#fn:2" class="footnote" rel="footnote">2</a></sup>). In 4.4, the new minimum is now .NET 8, but as always, your projects can target the recent STS release .NET 9 and any newer version that is released in the future.</p>
|
||
<p>Libraries tend to stay on older versions of .NET to support as many consumers as possible. But upgrading to the latest version of .NET brings benefits that we want to take advantage of.</p>
|
||
<h2 id="what-about-older-godot-releases">What about older Godot releases?</h2>
|
||
<p>We encourage users to upgrade to the latest version of Godot. We work hard to prevent breaking compatibility, to ensure you can safely upgrade to new versions of Godot when they are released. Please, make sure to test the pre-releases and let us know if you find some bugs so we can fix them before the stable release.</p>
|
||
<p>Older versions of Godot will keep targeting .NET 6; we won’t change the target version in patch updates, since that would be a big breaking change. If you still need to target .NET 6, you can stay on an older version of Godot, but we strongly encourage you to update to benefit from all the fixes and improvements included in the latest version of Godot and the .NET runtime.</p>
|
||
<h2 id="what-about-future-net-releases">What about future .NET releases?</h2>
|
||
<p>Godot always supports the latest .NET version. The version targeted by Godot’s C# packages is only the minimum version that your project can target, but you are always free to target a newer .NET version. To target the latest .NET 9 release in your project, you just need to install the latest version of the .NET SDK and change the <code class="language-plaintext highlighter-rouge">TargetFramework</code> property in your <code class="language-plaintext highlighter-rouge">.csproj</code>:</p>
|
||
<div class="language-xml highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="nt">&lt;Project</span> <span class="na">Sdk=</span><span class="s">"Godot.NET.Sdk/4.3.0"</span><span class="nt">&gt;</span>
|
||
<span class="nt">&lt;PropertyGroup&gt;</span>
|
||
<span class="c">&lt;!-- Target .NET 9 --&gt;</span>
|
||
<span class="nt">&lt;TargetFramework&gt;</span>net9.0<span class="nt">&lt;/TargetFramework&gt;</span>
|
||
<span class="nt">&lt;EnableDynamicLoading&gt;</span>true<span class="nt">&lt;/EnableDynamicLoading&gt;</span>
|
||
<span class="nt">&lt;/PropertyGroup&gt;</span>
|
||
<span class="nt">&lt;/Project&gt;</span>
|
||
</code></pre></div></div>
|
||
<div class="card card-warning">
|
||
<p>You should always use the latest version of the .NET SDK even when targeting an older .NET version in your projects.</p>
|
||
</div>
|
||
<p>We’ll keep updating our C# packages to the latest LTS version as they are released. The next LTS release will be .NET 10, due in November 2025.</p>
|
||
<div class="footnotes" role="doc-endnotes">
|
||
<ol>
|
||
<li id="fn:1" role="doc-endnote">
|
||
<p>.NET 7 introduced the new <code class="language-plaintext highlighter-rouge">scoped</code> keyword. This feature breaks compatibility in some low-level scenarios that affected Godot. <a href="#fnref:1" class="reversefootnote" role="doc-backlink">&#8617;</a></p>
|
||
</li>
|
||
<li id="fn:2" role="doc-endnote">
|
||
<p>While pre-releases are usually supported by Godot, they may require users to enable them by setting the <code class="language-plaintext highlighter-rouge">DOTNET_ROLL_FORWARD_TO_PRERELEASE</code> environment variable to <code class="language-plaintext highlighter-rouge">1</code>. Keep in mind pre-releases are still a work-in-progress so there may be bugs. <a href="#fnref:2" class="reversefootnote" role="doc-backlink">&#8617;</a></p>
|
||
</li>
|
||
</ol>
|
||
</div></description><category>Progress Report</category><guid>https://godotengine.org/article/godotsharp-packages-net8/</guid><dc:creator>Raul Santos</dc:creator><pubDate>Thu, 02 Jan 2025 17:00:00 +0000</pubDate><image>https://godotengine.org/storage/blog/covers/godotsharp-packages-net8.webp</image></item><item><title>Dev snapshot: Godot 4.4 dev 7</title><link>https://godotengine.org/article/dev-snapshot-godot-4-4-dev-7/</link><summary>One last build before the holidays!</summary><description><p>Season’s greetings, everyone! As our team winds down for the holiday season, we present you with one last gift before
|
||
the new year: our final development build of the year!</p>
|
||
<p>After having a few notable regressions in dev 6, we intended to do a quick turnaround for dev 7 with high priority bug
|
||
fixes. But we got greedy and ended up making dev 7 another feature-packed new release so you will have plenty of things
|
||
to check out while we are on holidays.</p>
|
||
<p>Keep in mind that while we try to make sure each dev snapshot is stable enough for general testing, this is by
|
||
definition a pre-release piece of software. Be sure to make frequent backups, or use a version control system such as
|
||
Git, to preserve your projects in case of corruption or data loss.</p>
|
||
<p><a href="#downloads">Jump to the <strong>Downloads</strong> section</a>, and give it a spin right now, or continue reading to learn more about improvements in this release. You can also try the <a href="https://editor.godotengine.org/releases/4.4.dev7/"><strong>Web editor</strong></a>, <a href="https://www.meta.com/experiences/godot-game-engine/7713660705416473/"><strong>XR editor</strong></a>, or the <strong>Android editor</strong> for this release (join the <a href="https://groups.google.com/g/godot-testers">Android editor testing group</a> to get access to pre-release builds).</p>
|
||
<hr />
|
||
<p><em>The cover illustration is from</em> <a href="https://store.steampowered.com/app/2506810/Pest_Apocalypse/"><strong>Pest Apocalypse</strong></a>, <em>a hyper-realistic post apocalyptic physics based pizza delivery action rogue-lite! It is developed by <a href="https://www.kikimora.games/">Kikimora Games</a>. You can purchase the game <a href="https://store.steampowered.com/app/2506810/Pest_Apocalypse/">on Steam</a>, and follow the developers <a href="https://bsky.app/profile/kikimora.games">on BlueSky</a> and <a href="https://discord.com/invite/sSmGbJSa4E">Discord</a>.</em></p>
|
||
<h2 id="highlights">Highlights</h2>
|
||
<p>In case you missed them, see the <a href="/article/dev-snapshot-godot-4-4-dev-1/">4.4 dev 1</a>, <a href="/article/dev-snapshot-godot-4-4-dev-2/">4.4 dev 2</a>,
|
||
<a href="/article/dev-snapshot-godot-4-4-dev-3/">4.4 dev 3</a>, <a href="/article/dev-snapshot-godot-4-4-dev-4/">4.4 dev 4</a>, <a href="/article/dev-snapshot-godot-4-4-dev-5/">4.4 dev 5</a>, and <a href="/article/dev-snapshot-godot-4-4-dev-6/">4.4 dev 6</a> release notes for an overview of
|
||
some key features which were already in those snapshots, and are therefore still available for testing in dev 7.</p>
|
||
<p>Here are highlights of a few new features in dev 7 that you might find particularly exciting!</p>
|
||
<h3 id="jolt-physics-module">Jolt Physics module</h3>
|
||
<p>Ever since its inception in late 2022, <a href="https://github.com/godot-jolt/godot-jolt">godot-jolt</a> has become the de-facto 3D
|
||
physics engine for many of our developers. Much of the history behind why this was the case is documented in <a href="https://github.com/godotengine/godot-proposals/issues/7308">this
|
||
proposal</a> by <a href="https://github.com/adamscott">Adam Scott</a>, but
|
||
the main takeaway was a strong push for this tool to be recognized as an official addon. In doing so, users would be
|
||
able to find this amazing resource in a way that was promoted by the engine itself; an exciting prospect!</p>
|
||
<p>The Godot Jolt maintainers, <a href="https://github.com/mihe">Mikael Hermansson</a> and <a href="https://github.com/jrouwe">Jorrit Rouwe</a>,
|
||
took this idea one step further: integrating the tool as part of the engine <em>directly</em>. There was already a symbiosis
|
||
between their team and the Godot engine, with many features being added to Godot <em>and</em> Jolt to accommodate both, but the
|
||
integration of an official module was no small feat; their pull request
|
||
(<a href="https://github.com/godotengine/godot/pull/99895">GH-99895</a>) ended up adding over 500 files and 115 <strong>thousand</strong> lines
|
||
of code! So while this was one of the most rigorously tested PRs relative to the amount of time it’s been up, it’d be
|
||
impossible for any team to account for <em>everything</em> this behemoth introduced, so we eagerly await your feedback (and bug
|
||
reports) on one of the most highly-requested features of 4.x.</p>
|
||
<p><strong>Note:</strong> At time of writing, this does <strong>not</strong> replace Godot Physics as the default 3D physics engine.
|
||
The Jolt Physics integration in Godot is considered experimental, and may change in future releases. It also lacks some features of Godot Physics so isn’t a full drop-in replacement. If your interests/use-case are supported, the
|
||
tool can be enabled by changing the <code class="language-plaintext highlighter-rouge">physics/3d/physics_engine</code> project setting to <code class="language-plaintext highlighter-rouge">Jolt Physics</code>.</p>
|
||
<h3 id="net-80">.NET 8.0</h3>
|
||
<p><a href="https://github.com/paulloz">Paul Joannon</a> and <a href="https://github.com/raulsntos">Raul Santos</a> have put the final pieces in
|
||
place for moving both the GodotSharp library and user projects to .NET 8 (<a href="https://github.com/godotengine/godot/pull/92131">GH-92131</a> and
|
||
<a href="https://github.com/godotengine/godot/pull/100195">GH-100195</a>). All new projects will use .NET 8 by default and
|
||
existing projects will automatically update to .NET 8 once opened with this release or any newer 4.4 build.</p>
|
||
<h3 id="improved-scene-tree-editor-performance">Improved Scene Tree editor performance</h3>
|
||
<p>The amount of performance boosts that have been crammed in between dev 6 and dev 7 has been staggering. Of note are the
|
||
recent improvements to the engine’s core including many optimizations throughout the String class, spearheaded by
|
||
<a href="https://github.com/Ivorforce">Ivorforce</a>. But perhaps the most obvious improvement comes from <a href="https://github.com/hpvb">HP van
|
||
Braam</a> and their modifications to the SceneTree system
|
||
(<a href="https://github.com/godotengine/godot/pull/99700">GH-99700</a>). While this will prove beneficial across all projects,
|
||
these changes result in especially complex scenes having a tenfold performance in the editor when moving or renaming
|
||
nodes in the SceneTree.</p>
|
||
<h3 id="documentation-tooltips">Documentation tooltips</h3>
|
||
<p>Thanks to <a href="https://github.com/dalexeev">Danil Alexeev</a> the GDScript code editor will now display a tooltip containing
|
||
information about functions, variables, classes, etc. when you hover over them, including the documentation you have
|
||
written using our documentation system (<a href="https://github.com/godotengine/godot/pull/91060">GH-91060</a>). This makes using
|
||
the integrated documentation system even more powerful as you no longer have to bounce between the code editor and the
|
||
related docs to quickly get information.</p>
|
||
<p><img src="/storage/blog/dev-snapshot-godot-4-4-dev-7/documentation-tooltip.webp" alt="Documentation tooltip" /></p>
|
||
<h3 id="baked-shadowmasks-for-lightmaps">Baked shadowmasks for lightmaps</h3>
|
||
<p>Until now, you have always had to choose between fully baked or fully dynamic shadows when using LightmapGI. However,
|
||
sometimes you want to have dynamic shadows up close where detail matters, but use static shadows in the distance where a
|
||
low resolution is acceptable. Finally it is possible thanks to the hard work of
|
||
<a href="https://github.com/BlueCube3310">BlueCube3310</a> in <a href="https://github.com/godotengine/godot/pull/85653">GH-85653</a>. You can
|
||
now enable shadow masks while baking your LightmapGI to combine dynamic and static shadows for the best quality.</p>
|
||
<p>Additionally, this allows you to drastically shorten the range of your dynamic shadows which is a very important
|
||
optimization, especially for mobile devices.</p>
|
||
<p>This feature is still experimental and it will change in response to feedback, so please test it out and let us know
|
||
what you think!</p>
|
||
<p><img src="/storage/blog/dev-snapshot-godot-4-4-dev-7/shadowmask.webp" alt="Baked Lightmap" /></p>
|
||
<h3 id="updated-toolchains-for-official-builds">Updated toolchains for official builds</h3>
|
||
<p>We updated some of the toolchains we use for official builds in <a href="https://github.com/godotengine/build-containers/pull/150">build-containers#150</a>,
|
||
notably macOS and iOS SDKs from Xcode 16.2, and MinGW 12.0.0 with GCC 14.2.1 for Windows builds.</p>
|
||
<p>Toolchains for Linux, Android, and Web are still the same versions as for Godot 4.3.</p>
|
||
<h3 id="and-more">And more!</h3>
|
||
<p>There are too many exciting changes to list them all here, but here’s a curated selection:</p>
|
||
<ul>
|
||
<li>3D: Add 3D translation sensitivity to Editor Settings (<a href="https://github.com/godotengine/godot/pull/81714">GH-81714</a>).</li>
|
||
<li>3D: Add ruler mode to 3D (<a href="https://github.com/godotengine/godot/pull/100162">GH-100162</a>).</li>
|
||
<li>Animation: Add animation node extension (<a href="https://github.com/godotengine/godot/pull/99181">GH-99181</a>).</li>
|
||
<li>Audio: Add Web MIDI support (<a href="https://github.com/godotengine/godot/pull/95928">GH-95928</a>).</li>
|
||
<li>Buildsystem: Add loongarch64 support for Linux/*BSD (<a href="https://github.com/godotengine/godot/pull/97822">GH-97822</a>).</li>
|
||
<li>Buildsystem: Make Godot compile on <code class="language-plaintext highlighter-rouge">FreeBSD</code> (<a href="https://github.com/godotengine/godot/pull/100047">GH-100047</a>).</li>
|
||
<li>Core: Fix <code class="language-plaintext highlighter-rouge">JSON.{from,to}_native()</code> issues (<a href="https://github.com/godotengine/godot/pull/99765">GH-99765</a>).</li>
|
||
<li>Core: Optimize StringBuilder by using <code class="language-plaintext highlighter-rouge">LocalVector</code> instead of <code class="language-plaintext highlighter-rouge">Vector</code> (<a href="https://github.com/godotengine/godot/pull/99775">GH-99775</a>).</li>
|
||
<li>Core: Optimize String construction from statically known strings by evaluating <code class="language-plaintext highlighter-rouge">strlen</code> at compile-time (<a href="https://github.com/godotengine/godot/pull/100132">GH-100132</a>).</li>
|
||
<li>Core: Add move assignment and move constructor to Variant (<a href="https://github.com/godotengine/godot/pull/100426">GH-100426</a>).</li>
|
||
<li>Documentation: Document <code class="language-plaintext highlighter-rouge">_process()</code> and <code class="language-plaintext highlighter-rouge">_physics_process()</code> delta behavior at low FPS (<a href="https://github.com/godotengine/godot/pull/94636">GH-94636</a>).</li>
|
||
<li>Editor: Add ability to create a new inherited scene from code (<a href="https://github.com/godotengine/godot/pull/90057">GH-90057</a>).</li>
|
||
<li>Editor: Add profiler autostart indicator to EditorRunBar (<a href="https://github.com/godotengine/godot/pull/97492">GH-97492</a>).</li>
|
||
<li>Editor: Allow dragging to specific folders in filesystem dock (<a href="https://github.com/godotengine/godot/pull/99453">GH-99453</a>).</li>
|
||
<li>Editor: Make the Script Editor’s parser execute sooner on edit after error was found (<a href="https://github.com/godotengine/godot/pull/87542">GH-87542</a>).</li>
|
||
<li>Editor: Show String properties’ text in a tooltip in the inspector (<a href="https://github.com/godotengine/godot/pull/76231">GH-76231</a>).</li>
|
||
<li>Export: Use temp dirs instead of cache dirs for export (<a href="https://github.com/godotengine/godot/pull/100150">GH-100150</a>).</li>
|
||
<li>GDExtension: Fix <code class="language-plaintext highlighter-rouge">Variant</code> modulo operation (<a href="https://github.com/godotengine/godot/pull/99559">GH-99559</a>).</li>
|
||
<li>GDScript: Add <code class="language-plaintext highlighter-rouge">@warning_ignore_start</code> and <code class="language-plaintext highlighter-rouge">@warning_ignore_restore</code> annotations (<a href="https://github.com/godotengine/godot/pull/76020">GH-76020</a>).</li>
|
||
<li>GUI: Change default Arabic font to Vazirmatn (<a href="https://github.com/godotengine/godot/pull/100053">GH-100053</a>).</li>
|
||
<li>GUI: Fix Tree drag-and-drop scrolling having low FPS at low Physics Ticks per Second (<a href="https://github.com/godotengine/godot/pull/98766">GH-98766</a>).</li>
|
||
<li>GUI: Improve emoji SVG parsing by caching (<a href="https://github.com/godotengine/godot/pull/100300">GH-100300</a>).</li>
|
||
<li>GUI: Save color palette as resources to reuse later (<a href="https://github.com/godotengine/godot/pull/91604">GH-91604</a>).</li>
|
||
<li>Import: Consider all texture types for resource thumbnail generation (<a href="https://github.com/godotengine/godot/pull/100247">GH-100247</a>).</li>
|
||
<li>Input: Add <code class="language-plaintext highlighter-rouge">Tablet/Trackpad</code> 3D navigation preset (<a href="https://github.com/godotengine/godot/pull/97985">GH-97985</a>).</li>
|
||
<li>Navigation: Despaghettify NavigationServer path queries (<a href="https://github.com/godotengine/godot/pull/100129">GH-100129</a>).</li>
|
||
<li>Plugin: Export <code class="language-plaintext highlighter-rouge">EditorInspector::instantiate_property_editor</code> for use by plugins (<a href="https://github.com/godotengine/godot/pull/87375">GH-87375</a>).</li>
|
||
<li>Rendering: Add Blend Distance property to ReflectionProbe (<a href="https://github.com/godotengine/godot/pull/99958">GH-99958</a>).</li>
|
||
<li>Rendering: Allow changing the anisotropic filter level at run-time per Viewport (<a href="https://github.com/godotengine/godot/pull/88313">GH-88313</a>).</li>
|
||
<li>Rendering: Further performance improvements from The Forge (<a href="https://github.com/godotengine/godot/pull/99257">GH-99257</a>).</li>
|
||
<li>Rendering: Automatically compress new lightmap textures (<a href="https://github.com/godotengine/godot/pull/100327">GH-100327</a>).</li>
|
||
<li>Rendering: Optimize PointLight2D shadow rendering by reducing draw calls and RD state changes (<a href="https://github.com/godotengine/godot/pull/100302">GH-100302</a>).</li>
|
||
<li>Rendering: Implement <code class="language-plaintext highlighter-rouge">RD::buffer_get_data_async()</code> and <code class="language-plaintext highlighter-rouge">RD::texture_get_data_async()</code> (<a href="https://github.com/godotengine/godot/pull/100110">GH-100110</a>).</li>
|
||
<li>Shaders: Avoid error spam when shaders fail to compile by freeing shader_data version when compilation fails (<a href="https://github.com/godotengine/godot/pull/100128">GH-100128</a>).</li>
|
||
<li>XR: Allow locking the camera to the <code class="language-plaintext highlighter-rouge">XROrigin3D</code> for benchmarking or automated testing (<a href="https://github.com/godotengine/godot/pull/99145">GH-99145</a>).</li>
|
||
<li>XR: OpenXR: Add support for binding modifiers (<a href="https://github.com/godotengine/godot/pull/97140">GH-97140</a>).</li>
|
||
</ul>
|
||
<h2 id="changelog">Changelog</h2>
|
||
<p><strong>113 contributors</strong> submitted <strong>263 improvements</strong> for this new snapshot. See our <a href="https://godotengine.github.io/godot-interactive-changelog/#4.4-dev7"><strong>interactive changelog</strong></a> for the complete list of changes since the previous 4.4-dev6 snapshot.</p>
|
||
<p>This release is built from commit <a href="https://github.com/godotengine/godot/commit/46c8f8c5c5874c7c56ea5b1384259de9402d3449"><code class="language-plaintext highlighter-rouge">46c8f8c5c</code></a>.</p>
|
||
<h2 id="downloads">Downloads</h2>
|
||
<div class="card card-download">
|
||
<a class="card-download-link" href="/download/archive/4.4-dev7">
|
||
Download Godot 4.4 dev7
|
||
</a>
|
||
<div class="card-download-details">
|
||
<img class="lightbox-ignore" src="/storage/blog/covers/dev-snapshot-godot-4-4-dev-7.webp" />
|
||
<div class="card-download-platforms">
|
||
<div class="download-platform platform-linux">
|
||
<img width="24" height="24" src="/assets/images/platforms/linux.svg" title="Linux" alt="Linux" class="lightbox-ignore" />
|
||
Linux
|
||
</div>
|
||
<a href="https://github.com/godotengine/godot-builds/releases/download/4.4-dev7/Godot_v4.4-dev7_linux.x86_64.zip" class="btn btn-download btn-download-primary platform-linux">
|
||
<div class="download-title">
|
||
Standard
|
||
</div>
|
||
</a>
|
||
<a href="https://github.com/godotengine/godot-builds/releases/download/4.4-dev7/Godot_v4.4-dev7_mono_linux_x86_64.zip" class="btn btn-download btn-download-primary btn-download-primary--mono platform-linux">
|
||
<div class="download-title">
|
||
.NET
|
||
</div>
|
||
</a>
|
||
<div class="download-platform platform-macos">
|
||
<img width="24" height="24" src="/assets/images/platforms/macos.svg" title="macOS" alt="macOS" class="lightbox-ignore" />
|
||
macOS
|
||
</div>
|
||
<a href="https://github.com/godotengine/godot-builds/releases/download/4.4-dev7/Godot_v4.4-dev7_macos.universal.zip" class="btn btn-download btn-download-primary platform-macos">
|
||
<div class="download-title">
|
||
Standard
|
||
</div>
|
||
</a>
|
||
<a href="https://github.com/godotengine/godot-builds/releases/download/4.4-dev7/Godot_v4.4-dev7_mono_macos.universal.zip" class="btn btn-download btn-download-primary btn-download-primary--mono platform-macos">
|
||
<div class="download-title">
|
||
.NET
|
||
</div>
|
||
</a>
|
||
<div class="download-platform platform-windows">
|
||
<img width="24" height="24" src="/assets/images/platforms/windows.svg" title="Windows" alt="Windows" class="lightbox-ignore" />
|
||
Windows
|
||
</div>
|
||
<a href="https://github.com/godotengine/godot-builds/releases/download/4.4-dev7/Godot_v4.4-dev7_win64.exe.zip" class="btn btn-download btn-download-primary platform-windows">
|
||
<div class="download-title">
|
||
Standard
|
||
</div>
|
||
</a>
|
||
<a href="https://github.com/godotengine/godot-builds/releases/download/4.4-dev7/Godot_v4.4-dev7_mono_win64.zip" class="btn btn-download btn-download-primary btn-download-primary--mono platform-windows">
|
||
<div class="download-title">
|
||
.NET
|
||
</div>
|
||
</a>
|
||
</div>
|
||
</div>
|
||
<div class="card-download-sublinks">
|
||
<a class="card-download-other" href="/download/archive/4.4-dev7">
|
||
Export templates and other downloads
|
||
</a>
|
||
<a class="card-download-donate" href="https://fund.godotengine.org/">
|
||
Make a Donation
|
||
</a>
|
||
</div>
|
||
</div>
|
||
<style>
|
||
.thankyou-wrapper {
|
||
position: fixed;
|
||
top: 0;
|
||
left: 0;
|
||
right: 0;
|
||
bottom: 0;
|
||
background: rgba(0, 0, 0, 0.85);
|
||
display: flex;
|
||
flex-direction: column;
|
||
justify-content: center;
|
||
align-items: center;
|
||
z-index: 10;
|
||
}
|
||
.thankyou {
|
||
background: var(--base-color);
|
||
box-shadow: var(--more-shadow);
|
||
padding: 30px;
|
||
display: flex;
|
||
flex-direction: column;
|
||
align-items: center;
|
||
text-align: center;
|
||
position: relative;
|
||
border-radius: 13px;
|
||
}
|
||
.thankyou-reading {
|
||
font-size: 16px;
|
||
}
|
||
.thankyou-reading-list {
|
||
font-size: 16px;
|
||
margin: 0;
|
||
margin-left: 48px;
|
||
padding-left: 0;
|
||
}
|
||
.thankyou-donate {
|
||
margin-bottom: 24px;
|
||
text-align: center;
|
||
}
|
||
.btn.btn-donate {
|
||
background-color: var(--primary-color);
|
||
color: hsla(0, 0%, 100%, 0.9);
|
||
font-size: 22px;
|
||
font-weight: 600;
|
||
margin-bottom: 26px;
|
||
}
|
||
.thankyou h2 {
|
||
text-shadow: var(--base-shadow);
|
||
font-size: 36px;
|
||
font-weight: 800;
|
||
margin-bottom: 12px;
|
||
}
|
||
.thankyou h2 .anchored-link {
|
||
/* Hiding the anchored text automatically added on blogposts */
|
||
display: none !important;
|
||
}
|
||
.thankyou p {
|
||
max-width: 620px;
|
||
font-size: 25px;
|
||
}
|
||
@media (max-width: 768px) {
|
||
.thankyou-wrapper {
|
||
display: block;
|
||
}
|
||
.thankyou {
|
||
position: absolute;
|
||
top: 0;
|
||
left: 0;
|
||
right: 0;
|
||
bottom: 0;
|
||
overflow: scroll;
|
||
padding: 30px 40px 18px 40px;
|
||
}
|
||
.thankyou-reading-list {
|
||
margin-left: 24px;
|
||
}
|
||
.btn-close-thankyou-popup {
|
||
width: 48px;
|
||
height: 48px;
|
||
display: flex;
|
||
justify-content: center;
|
||
align-items: center;
|
||
}
|
||
}
|
||
.btn-close-thankyou-popup {
|
||
cursor: pointer;
|
||
position: absolute;
|
||
top: 12px;
|
||
right: 12px;
|
||
}
|
||
.btn-close-thankyou-popup img {
|
||
background: transparent !important; /* for overwriting the style in the blogposts img */
|
||
}
|
||
@media (prefers-color-scheme: light) {
|
||
.btn-close-thankyou-popup img {
|
||
filter: invert(1);
|
||
opacity: 0.75;
|
||
}
|
||
}
|
||
</style>
|
||
<script>
|
||
document.addEventListener('DOMContentLoaded', () => {
|
||
const thankYouWrapper = document.getElementById('thank-you');
|
||
// Close itself, when clicked outside of the popup area.
|
||
thankYouWrapper.addEventListener('click', (e) => {
|
||
if (e.target === thankYouWrapper) {
|
||
thankYouWrapper.style.display = 'none';
|
||
}
|
||
});
|
||
// Close with a close button.
|
||
const thankYouBackButton = document.querySelector('.btn-close-thankyou-popup');
|
||
thankYouBackButton.addEventListener('click', () => {
|
||
thankYouWrapper.style.display = 'none';
|
||
});
|
||
// Open from the main download buttons.
|
||
const downloadButtons = document.querySelectorAll('.btn-download');
|
||
downloadButtons.forEach((it) => {
|
||
it.addEventListener('click', () => {
|
||
thankYouWrapper.style.display = '';
|
||
document.querySelector('.btn.btn-donate').focus();
|
||
});
|
||
});
|
||
// Open from the all downloads list.
|
||
const downloadLinks = document.querySelectorAll('.download-link');
|
||
downloadLinks.forEach((it) => {
|
||
it.addEventListener('click', () => {
|
||
thankYouWrapper.style.display = '';
|
||
});
|
||
});
|
||
// Close the dialog when the user presses the escape key.
|
||
document.addEventListener('keydown', (e) => {
|
||
if (e.key === 'Escape') {
|
||
thankYouWrapper.style.display = 'none';
|
||
}
|
||
});
|
||
});
|
||
</script>
|
||
<div class="thankyou-wrapper" id="thank-you" style="display: none;">
|
||
<div class="thankyou">
|
||
<h2>Godot is downloading...</h2>
|
||
<p class="thankyou-donate">
|
||
Godot exists thanks to donations from people like you. Help us continue our work:
|
||
</p>
|
||
<a href="https://fund.godotengine.org" class="btn btn-donate">
|
||
Make a Donation
|
||
</a>
|
||
<div class="btn-close-thankyou-popup">
|
||
<img src="/assets/icons/cross.svg" width="24" height="24" alt="Close this popup" class="lightbox-ignore" />
|
||
</div>
|
||
</div>
|
||
</div>
|
||
<p><strong>Standard build</strong> includes support for GDScript and GDExtension.</p>
|
||
<p><strong>.NET build</strong> (marked as <code class="language-plaintext highlighter-rouge">mono</code>) includes support for C#, as well as GDScript and GDExtension.</p>
|
||
<ul>
|
||
<li>.NET 8.0 or newer is required for this build, changing the minimal supported version from .NET 6 to 8.</li>
|
||
</ul>
|
||
<div class="card card-warning">
|
||
<p>
|
||
While engine maintainers try their best to ensure that each preview snapshot and release candidate is stable, this is by definition <strong>a pre-release piece of software</strong>. Be sure to make frequent backups, or use a version control system such as Git, to preserve your projects in case of corruption or data loss.
|
||
</p>
|
||
</div>
|
||
<h2 id="known-issues">Known issues</h2>
|
||
<p>With every release we accept that there are going to be various issues, which have already been reported but haven’t been fixed yet. See the GitHub issue tracker for a complete list of <a href="https://github.com/godotengine/godot/issues?q=is%3Aissue+is%3Aopen+label%3Abug+">known bugs</a>.</p>
|
||
<p>There are currently no known issues introduced by this release.</p>
|
||
<h2 id="bug-reports">Bug reports</h2>
|
||
<p>As a tester, we encourage you to <a href="https://github.com/godotengine/godot/issues">open bug reports</a> if you experience issues with this release. Please check the <a href="https://github.com/godotengine/godot/issues">existing issues on GitHub</a> first, using the search function with relevant keywords, to ensure that the bug you experience is not already known.</p>
|
||
<p>In particular, any change that would cause a regression in your projects is very important to report (e.g. if something that worked fine in previous 4.x releases, but no longer works in this snapshot).</p>
|
||
<h2 id="support">Support</h2>
|
||
<p>Godot is a non-profit, open source game engine developed by hundreds of contributors on their free time, as well as a handful of part or full-time developers hired thanks to <a href="https://fund.godotengine.org/">generous donations from the Godot community</a>. A big thank you to everyone who has contributed <a href="https://github.com/godotengine/godot/blob/master/AUTHORS.md">their time</a> or <a href="https://github.com/godotengine/godot/blob/master/DONORS.md">their financial support</a> to the project!</p>
|
||
<p>If you’d like to support the project financially and help us secure our future hires, you can do so using the <a href="https://fund.godotengine.org/">Godot Development Fund</a> platform managed by <a href="https://godot.foundation/">Godot Foundation</a>. There are also several <a href="/donate">alternative ways to donate</a> which you may find more suitable.</p></description><category>Pre-release</category><guid>https://godotengine.org/article/dev-snapshot-godot-4-4-dev-7/</guid><dc:creator>Thaddeus Crews</dc:creator><pubDate>Thu, 19 Dec 2024 18:00:00 +0000</pubDate><image>https://godotengine.org/storage/blog/covers/dev-snapshot-godot-4-4-dev-7.webp</image></item><item><title>Godot XR community - December 2024</title><link>https://godotengine.org/article/godot-xr-community-nov-2024/</link><summary>Interesting projects from the Godot XR community.</summary><description><p>Godot has a very active XR-focused community on the XR channel of the <a href="/community/">official Godot Discord server</a>.
|
||
Today, we want to put a spotlight on a number of community projects.</p>
|
||
<h2 id="godot-xr-community-game-jams">Godot XR community Game Jams</h2>
|
||
<p>To showcase the engine capabilities and the ingenuity of the Godot XR community, game jams are now being organized twice a year.
|
||
It’s a fun way for participants to get introduced to Godot’s XR capabilities.</p>
|
||
<h3 id="godot-xr-game-jam-1">Godot XR Game Jam #1</h3>
|
||
<p>The <a href="https://itch.io/jam/godot-xr-game-jam">first Godot XR Game Jam</a> was held from 1 December until 4 December 2023.
|
||
The theme of this game jam was Vapor.
|
||
We saw both many new faces and long-time community members join, and had a total of 17 entries.</p>
|
||
<p>The #1 spot went to <a href="https://itch.io/jam/godot-xr-game-jam/rate/2402526">Cloud Shepherd</a> which won 3 out of 6 categories, including “Originality”, “User experience”, and “Audio”.
|
||
In this entry, you herd sheep on clouds in the sky by using fans to create breezes that blow the sheep to their destinations.</p>
|
||
<p>The #2 spot was taken by <a href="https://itch.io/jam/godot-xr-game-jam/rate/2402404">Super Steam Hands</a> which won 2 out of 6 categories (“Fun factor” and “Theme incorporation”).
|
||
Don’t let the thumbnail of this entry fool you. It’s a great game where you can feel like Iron Man by using jets of steam to parkour around a level.</p>
|
||
<p>The #3 spot went to <a href="https://itch.io/jam/godot-xr-game-jam/rate/2400974">Pipe Stream</a> which ranked the best in the “Haptics” category.
|
||
It’s a great little puzzle game where you need to chip away a path for vapor to reach a target. Very challenging!</p>
|
||
<p>There were far more great entries, so be sure to <a href="https://itch.io/jam/godot-xr-game-jam/entries">check out the jam page for more</a>!</p>
|
||
<h3 id="godot-xr-game-jam-2">Godot XR Game Jam #2</h3>
|
||
<p>The <a href="https://itch.io/jam/godot-xr-game-jam-july-2024">second Godot XR Game Jam</a> was held from 8 July until 15 July 2024.
|
||
We decided to give participants a full week to complete their game.
|
||
The theme this jam was Relaxation. There were a total of 26 entries and this time we scored them on the average points in all categories.</p>
|
||
<p>The #1 spot went to <a href="https://itch.io/jam/godot-xr-game-jam-july-2024/rate/2821459">Who’s a good boy</a> with 4.042 points.
|
||
This cute little game has you play fetch with a dog in a park.
|
||
It features some excellent interactions both from the player’s and dog’s points of view.</p>
|
||
<p>The #2 spot went to <a href="https://itch.io/jam/godot-xr-game-jam-july-2024/rate/2830514">Constellation Coach VR</a> with 3.974 points.
|
||
This game has you find constellations in the night sky by holding up a picture of the constellation and aligning it with the relevant stars.
|
||
Excellent haptic feedback lets you know when you’ve gotten close, and successfully aligning the constellation lights it up.</p>
|
||
<p>The #3 spot went to <a href="https://itch.io/jam/godot-xr-game-jam-july-2024/rate/2830121">Summer Pottery VR</a> with 3.938 points.
|
||
This game lets you do some clay pottery sculpting.
|
||
It’s a great and very well-executed use of physically interacting with the clay to shape and paint your creation.</p>
|
||
<iframe width="560" height="315" src="https://www.youtube.com/embed/0IxvWaj8iUo?si=em-D99NacStXyIYA" title="5 VR Games Made in Godot To Inspire You" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen=""></iframe>
|
||
<p>Again, many of the other entries were of great quality and we highly recommend <a href="https://itch.io/jam/godot-xr-game-jam-july-2024/entries">checking them out</a>.</p>
|
||
<h3 id="godot-xr-game-jam-3">Godot XR Game Jam #3</h3>
|
||
<p>The 3rd game jam will be held in the week starting 10 February 2025. <a href="https://itch.io/jam/godot-xr-game-jam-feb-2025">You can read all about it and sign up here</a>.</p>
|
||
<h2 id="universal-godot-vr-plugin">Universal Godot VR plugin</h2>
|
||
<p>Inspired by the Universal Unreal Engine VR Mod, community member TeddyBear082 has created a mod to inject VR capabilities into existing 3D games made with Godot.</p>
|
||
<p>TeddyBear082 previously made a name for himself with the excellent VR port of the popular game Cruelty Squad and has used the knowledge gained with that and similar projects to create a more universal mod.</p>
|
||
<iframe width="560" height="315" src="https://www.youtube.com/embed/Hb9BDcCZHCY?si=Zr2Jw3MV7cY00yEE" title="UGVR Demo" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen=""></iframe>
|
||
<p>You can find the plugin <a href="https://github.com/teddybear082/UGVR">on teddybear082’s GitHub profile</a>.</p>
|
||
<h2 id="body-tracking-and-motion-capture-plugins">Body tracking and motion capture plugins</h2>
|
||
<p>Core contributor Malcolm Nixon has created various plugins for Godot that use the new body tracking feature to make tracking data available from various sources.</p>
|
||
<p>He has support for Rokoko, Axis Studio and Movella.
|
||
He also has a plugin for VMC (Virtual Motion Capture), which is a standard used by a number of motion capture systems.</p>
|
||
<p>You can find the plugins <a href="https://github.com/Malcolmnixon?tab=repositories">on his GitHub profile</a>.</p>
|
||
<h2 id="meta-platform-plugin">Meta platform plugin</h2>
|
||
<p>Community member Decacis has released a few of his games on the Meta Horizon store and implemented part of the Meta platform SDK in support of this.
|
||
He has implemented support for things like in-app purchases, leaderboard, challenges, and much much more.</p>
|
||
<p>The plugin he created is open source and can be found <a href="https://github.com/decacis/godot_oculus_platform">on his GitHub profile</a>.</p>
|
||
<h2 id="godot-xr-tools">Godot XR Tools</h2>
|
||
<p>We’ve showcased XR Tools before, but with version 4.4 of the plugin nearly ready for release, it’s worth quickly looking at what’s coming.</p>
|
||
<ul>
|
||
<li>Improved support for Godot 4.2+ features such as pass through logic with both OpenXR and WebXR.</li>
|
||
<li>New objects to make games suitable for both VR and non-VR use.</li>
|
||
<li>A new gaze interaction component for controller-less experiences.</li>
|
||
<li>Various improvements to snap points.</li>
|
||
<li>Improvements to hands interacting with physics.</li>
|
||
</ul>
|
||
<iframe width="560" height="315" src="https://www.youtube.com/embed/YWdcc6r9w3E?si=BimitXSjjVQxcLrO" title="Godot XR tools demo for GodotCon 2024" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen=""></iframe>
|
||
<h2 id="godot-arcore-support">Godot ARCore support</h2>
|
||
<p>ARCore support in Godot has been a long time coming.
|
||
From an early working prototype in Godot 3, to moving this into a community maintained plugin, there have been plenty of hurdles along the way. Thanks to the persistance of Patrick Exner, Luca Junge, and Chambefort Maxime, we have nearly reached the finish line.</p>
|
||
<p>Supporting changes were recently merged into the master branch of Godot and you can find the plugin itself <a href="https://github.com/GodotVR/godot_arcore">on the plugin’s GitHub</a>.</p></description><category>News</category><guid>https://godotengine.org/article/godot-xr-community-nov-2024/</guid><dc:creator>Bastiaan Olij</dc:creator><pubDate>Wed, 18 Dec 2024 12:00:00 +0000</pubDate><image>https://godotengine.org/storage/blog/covers/december-2024-update-godot-xr-community.webp</image></item><item><title>Meet the creator behind the Godot Game Awards</title><link>https://godotengine.org/article/godot-game-awards-stayathomedev/</link><summary>StayAtHomeDev has been sharing his passion on YouTube for over two years and now he's running the awards.</summary><description><h2 id="update-the-godot-game-awards-winners-have-been-announced-you-can-watch-the-video-here">Update: The Godot Game Awards winners have been announced! You can watch the video <a href="https://www.youtube.com/watch?v=mUzAHrpjwl4">here</a>.</h2>
|
||
<hr />
|
||
<p>If you’ve watched Godot-related content on YouTube, <a href="https://www.youtube.com/@stayathomedev">StayAtHomeDev</a> needs no introduction. He’s been sharing his passion for game development and the Godot Engine through his channel. As the creator of the popular “<a href="https://www.youtube.com/playlist?list=PLEHvj4yeNfeHArSU6U2a715ssJYYCnKCg">This Week in Godot</a>” series, and the Godot Game Awards, he’s helped showcase the amazing work of the Godot community. We had the chance to talk with him about his journey, what inspired the awards, and his efforts to support the community.</p>
|
||
<h3 id="what-inspired-you-to-create-the-godot-game-awards-and-how-long-has-it-been-running">What inspired you to create the Godot Game Awards, and how long has it been running?</h3>
|
||
<p>I started the “<a href="https://www.youtube.com/playlist?list=PLEHvj4yeNfeHArSU6U2a715ssJYYCnKCg">This Week in Godot</a>” series over two years ago on my channel. At first it started as a compilation of cool projects or games I found throughout each week. About 7-8 videos in, I thought it would be cool if people could vote for their favorite each week and the engagement exploded. People would comment every week and eventually I compiled every winner into a final vote for the “<a href="https://www.youtube.com/watch?v=3_3N_nL9gIM">Best Godot Project of the Year</a>” in 2023.</p>
|
||
<p>This year I wanted to expand that into multiple categories, highlighting certain achievements like art design and music, and give attention to other things like plugins, tutorials, even devlogs. From that came the Godot Game Awards, a compilation of the best Godot-based games, plugins, and projects as voted by viewers on my channel.</p>
|
||
<h3 id="how-can-people-get-involved-in-this-years-edition">How can people get involved in this year’s edition?</h3>
|
||
<p>People can get involved from now until December 15th by voting on the 20+ different categories with an official 2024 🗳️ <a href="https://forms.gle/Q4yYy82neZcKA3Ny6">Godot Game Awards Ballot</a>.</p>
|
||
<p>The winners will be announced in a premiere video on December 28th at 2:00pm EST on my channel so that everyone can watch together and help support the great work by these developers.</p>
|
||
<h3 id="tell-us-about-your-youtube-channelwhat-kind-of-content-do-you-focus-on-and-what-motivated-you-to-start-creating-videos">Tell us about your YouTube channel—what kind of content do you focus on, and what motivated you to start creating videos?</h3>
|
||
<p>I started <a href="https://www.youtube.com/@stayathomedev">StayAtHomeDev</a> over two years ago to share my passion for creating through game development. At the time, I had a potential job offer to be the Web Coordinator for a professional football team in the US. But I had just been given a grant by Meta for some VR development work with their Oculus Quest 2 headset so I used that to launch the channel. It really was an exercise to create independent income so I could stay at home with my kids. That was a lifestyle choice I knew I wanted to make for them, so I took a shot at YouTube.</p>
|
||
<p>I’m very interested in sharing knowledge so the channel has had an element of teaching with tutorials or game development concept videos. With the “<a href="https://www.youtube.com/playlist?list=PLEHvj4yeNfeHArSU6U2a715ssJYYCnKCg">This Week in Godot</a>” series, the channel started to steer more towards enriching the Godot community and showcasing what people were creating with the engine. Now, it’s a mix of tutorials, QAs about general game development topics, and the newest format, interviews. I am actually most excited about the interview videos because they really give a chance for viewers to peek into real game dev life with stories and advice from developers actively breaking through the industry or those who are already successful, and of course doing it with the Godot Engine.</p>
|
||
<iframe width="560" height="315" src="https://www.youtube.com/embed/8nsJw89FG_A" frameborder="0" allowfullscreen="" style="width: 100%; aspect-ratio: 16 / 9; height: auto;"></iframe>
|
||
<h3 id="how-did-you-discover-godot-when-did-you-start-using-it-do-you-have-prior-experience-with-other-game-engines">How did you discover Godot? When did you start using it? Do you have prior experience with other game engines?</h3>
|
||
<p>If you look at the earliest videos on the channel, you’ll notice they were all focused on the Unreal Engine. I actually worked within Unreal first. Long ago…like long ago…I started making little games with an engine called 3D GameStudio.</p>
|
||
<p>When I started the channel, I knew of Godot (which I thought was called GoDot) but never tried it. After spending more time on YouTube and lurking around other game dev content, Godot kept popping up, so I took it for a test drive. I ended up making a video about it which went “viral” for a small channel while my first kid was being born. There was clearly a lot of interest in the engine so I kept playing around with it and fell in love. Not only with how streamlined it felt but also because it was open source and had such a strong sense of community and pride. I decided I wanted to help support that with the channel.</p>
|
||
<h3 id="what-advice-would-you-give-to-someone-starting-out-as-a-game-developer-or-content-creator-in-the-godot-community">What advice would you give to someone starting out as a game developer or content creator in the Godot community?</h3>
|
||
<p>I would say the WORST thing you can do is stop yourself before you even try. Game development and content creation are both difficult. They are also largely self-motivated so telling yourself you can’t do them means you likely won’t.</p>
|
||
<p>The BEST thing you can do is just try. If you are interested in making games, download the engine and try. You are going to hit walls and fail at a number of things but that’s part of the learning process. The information and tools are out there, you just need to start the climb.</p>
|
||
<p>In more applicable terms…start small, remake Pong or level 1 of Mario Bros. If something seems too difficult to understand, break it into smaller pieces. Don’t try to make an entire 2D platformer controller, make it move left and right first. And don’t think you’re going to sell your first game and make tons of money. You’ll put too much pressure on yourself and it won’t be fun anymore, you’ll get frustrated, and you’ll quit.</p>
|
||
<p>For content creation, it’s a marathon so the most important thing is don’t worry about the views. Make content that you want to make. If a video gets more views than normal, analyze why, and do it again with a small change. YouTube is sort of a constantly moving target and you won’t get a good idea of your style, your interest, or what people want to watch for a while. And even then, those things can always change. Consistency is the important variable…keep doing it and consistently try to get better. Better sound, better speaking, better editing, better pacing, better thumbnails, better topics, better storytelling. There is always something you can improve. If you create videos consistently and improve with every video, you’ll get to where you want to go and build a ton of new skills along the way.</p>
|
||
<iframe width="560" height="315" src="https://www.youtube.com/embed/C-sJarU469Y" frameborder="0" allowfullscreen="" style="width: 100%; aspect-ratio: 16 / 9; height: auto;"></iframe>
|
||
<h3 id="do-you-plan-to-continue-organizing-the-godot-game-awards-in-the-future">Do you plan to continue organizing the Godot Game Awards in the future?</h3>
|
||
<p>Absolutely! There have already been nearly 1000 ballots submitted, which is crazy to me. People comment how they enjoy finding new Godot projects every week with the weekly video series and tell me that they feel inspired to make something themselves. That is the best thing I could hope for, that people feel inspired to create. I’m also a music therapist so I have seen the effect creativity and expression can have on a person’s well-being. To me, games are an art form and within that lies the ability to create powerful feelings in other people through interactive play. If one person continues to be inspired by the games showcased in the awards, then I’ll keep making the videos.</p>
|
||
<hr />
|
||
<p><span style="font-size: 28px; font-family: var(--header-font-family); font-weight: 800;">🗳️ <a href="https://forms.gle/Q4yYy82neZcKA3Ny6">Vote now!</a> 👈<span></span></span></p>
|
||
<hr />
|
||
<p>If you want to support StayAtHomeDev you can visit his <a href="https://www.patreon.com/StayAtHomeDev_">Patreon</a>, subscribe to <a href="https://www.youtube.com/@stayathomedev">his channel</a>, or vote for your favorite Godot projects each week.</p>
|
||
<p>Good luck to all the nominees, and thank you StayAtHomeDev for all your work organizing the awards!</p></description><category>Showcase</category><guid>https://godotengine.org/article/godot-game-awards-stayathomedev/</guid><dc:creator>Emi</dc:creator><pubDate>Mon, 09 Dec 2024 18:00:00 +0000</pubDate><image>https://godotengine.org/storage/blog/covers/godot-awards-stayathomedev.webp</image></item><item><title>Dev snapshot: Godot 4.4 dev 6</title><link>https://godotengine.org/article/dev-snapshot-godot-4-4-dev-6/</link><summary>New snapshot on the road to beta, with a lot of 3D workflow goodies!</summary><description><p>Safety goggles on, people! Features and Quality-of-Life are being integrated at blinding speeds; precautions must be taken to view them head-on. Once secure, we can dive into what’s shaping up to be one of the final development snapshots before 4.4-beta builds roll out!</p>
|
||
<p>Keep in mind that while we try to make sure each dev snapshot is stable enough for general testing, this is by
|
||
definition a pre-release piece of software. Be sure to make frequent backups, or use a version control system such as
|
||
Git, to preserve your projects in case of corruption or data loss.</p>
|
||
<p><a href="#downloads">Jump to the <strong>Downloads</strong> section</a>, and give it a spin right now, or continue reading to learn more about improvements in this release. You can also try the <a href="https://editor.godotengine.org/releases/4.4.dev6/"><strong>Web editor</strong></a>, <a href="https://www.meta.com/experiences/godot-game-engine/7713660705416473/"><strong>XR editor</strong></a>, or the <strong>Android editor</strong> for this release (join the <a href="https://groups.google.com/g/godot-testers">Android editor testing group</a> to get access to pre-release builds).</p>
|
||
<hr />
|
||
<p><em>The cover illustration is from</em> <a href="https://store.steampowered.com/app/3019370/Malware/"><strong>Malware</strong></a>, <em>an installation simulator where players must navigate a minefield of circa-1999 malware! It is developed by <a href="https://store.steampowered.com/search/?developer=Odd%20Games">Odd Games</a>. You can purchase the game <a href="https://store.steampowered.com/app/3019370/Malware/">on Steam</a>.</em></p>
|
||
<h2 id="highlights">Highlights</h2>
|
||
<p>In case you missed them, see the <a href="/article/dev-snapshot-godot-4-4-dev-1/">4.4 dev 1</a>, <a href="/article/dev-snapshot-godot-4-4-dev-2/">4.4 dev 2</a>,
|
||
<a href="/article/dev-snapshot-godot-4-4-dev-3/">4.4 dev 3</a>, <a href="/article/dev-snapshot-godot-4-4-dev-4/">4.4 dev 4</a>, and <a href="/article/dev-snapshot-godot-4-4-dev-5/">4.4 dev 5</a> release notes for an overview of
|
||
some key features which were already in those snapshots, and are therefore still available for testing in dev 6.</p>
|
||
<p>Here are highlights of a few new features in dev 6 that you might find particularly exciting!</p>
|
||
<h3 id="camera3d-preview-in-inspector">Camera3D preview in inspector</h3>
|
||
<p>Previously, adjusting the view of a <code class="language-plaintext highlighter-rouge">Camera3D</code> in a scene could be a chore to handle. It required activating the camera you wanted to preview, and then reverting it back if it wasn’t the main camera. You could pin a preview of a camera in a dedicated viewport, but that meant reducing the real-estate of your main viewport.</p>
|
||
<p>Now, with <a href="https://github.com/timothyqiu">Haoyu Qiu</a>’s feature (<a href="https://github.com/godotengine/godot/pull/90778">GH-90778</a>), every selected 3D camera shows a preview inside the inspector. No switching cameras needed to preview anymore.</p>
|
||
<video autoplay="" loop="" muted="" playsinline="">
|
||
<source src="/storage/blog/dev-snapshot-godot-4-4-dev-6/camera3d-inspector.mp4?1" type="video/mp4" />
|
||
</video>
|
||
<h3 id="collisionshape3d-debug-color-customization">CollisionShape3D debug color customization</h3>
|
||
<p>3D collision shapes now have parity with their 2D counterparts with the newly added <code class="language-plaintext highlighter-rouge">debug_color</code> and <code class="language-plaintext highlighter-rouge">debug_fill</code> properties, which lets you customize the appearance of debug collision shapes in the editor, or at runtime if “Visible Collision Shapes” is enabled in the Debug menu. Thanks to first-time contributor <a href="https://github.com/BattyBovine">BattyBovine</a> for implementing this much-requested proposal (<a href="https://github.com/godotengine/godot/pull/90644">GH-90644</a>).</p>
|
||
<p><img src="/storage/blog/dev-snapshot-godot-4-4-dev-6/debug-color.webp" alt="Examples of custom debug colors" /></p>
|
||
<h3 id="replace-internal-csg-implementation-with-manifold-library">Replace internal CSG implementation with Manifold library</h3>
|
||
<p>Godot added support for CSG, or Constructive Solid Geometry, <a href="/article/godot-gets-csg-support/">back in 3.1</a>. This is a great tool for rapidly prototyping level geometry or even simple props and characters by combining 3D primitives with various boolean operations (union, intersection, subtraction).</p>
|
||
<p>Our implementation suffered from a number of bugs and stability issues, with no dedicated maintainer to tackle them. Thankfully, a great open source library has been released since then which can be used as a well-maintained replacement for our CSG internals: <a href="https://github.com/elalish">Emmett Lalish</a>’s <a href="https://github.com/elalish/manifold">Manifold</a>.</p>
|
||
<p><a href="https://github.com/fire">Ernest Lee</a> did an amazing work implementing Manifold in Godot, with help from Emmett to ensure that the library fits our requirements (<a href="https://github.com/godotengine/godot/pull/94321">GH-94321</a>). As this is a fairly big change to how Godot’s CSG works internally (but with minimal impact on the user API), you might notice differences in your projects using CSG. Please report any change that appears to have a negative impact on your usage.</p>
|
||
<h3 id="runtime-wav-file-loading">Runtime WAV file loading</h3>
|
||
<p>First-time contributor <a href="https://github.com/what-is-a-git">cherry</a> implemented the long-requested support for runtime loading of WAV files (<a href="https://github.com/godotengine/godot/pull/93831">GH-93831</a>). This adds parity with OGG Vorbis audio tracks, and will be a welcome addition for users who want to load user-generated content at runtime (including non-game audio applications).</p>
|
||
<h3 id="extend-curve-to-allow-for-domains-outside-of-0-1">Extend Curve to allow for domains outside of <code class="language-plaintext highlighter-rouge">[0, 1]</code></h3>
|
||
<p>Have you ever wished that you could edit a <code class="language-plaintext highlighter-rouge">Curve</code> in a domain that goes beyond the normalized <code class="language-plaintext highlighter-rouge">[0, 1]</code> range? <a href="https://github.com/anvilfolk">ocean</a> finally got their implementation of this feature merged (<a href="https://github.com/godotengine/godot/pull/67857">GH-67857</a>), which should give you greater flexibility in how to map your functions and data to Godot’s ubiquitous Curve resource.</p>
|
||
<video autoplay="" loop="" muted="" playsinline="">
|
||
<source src="/storage/blog/dev-snapshot-godot-4-4-dev-6/curve-extended-domain.mp4?1" type="video/mp4" />
|
||
</video>
|
||
<h3 id="temporary-file-and-directory-utilities">Temporary file and directory utilities</h3>
|
||
<p>Tool creators, <a href="https://github.com/adamscott">Adam Scott</a> cooked a little something that could be interesting for you. A brand new API lets you create and dispose of temporary files. Handy if you need to write content on disk, but without worrying about polluting user data. These temporary files and directories even dispose of themselves after use by default. For more information, see (<a href="https://github.com/godotengine/godot/pull/98397">GH-98397</a>).</p>
|
||
<h3 id="and-more">And more!</h3>
|
||
<p>There are too many exciting changes to list them all here, but here’s a curated selection:</p>
|
||
<ul>
|
||
<li>2D: Change how multi selection scale is applied to canvas item (<a href="https://github.com/godotengine/godot/pull/99506">GH-99506</a>).</li>
|
||
<li>2D: Ensure primitive meshes are created before connected to changed signal (<a href="https://github.com/godotengine/godot/pull/99740">GH-99740</a>).</li>
|
||
<li>3D: Add ShadowCastingSetting to MeshLibrary / GridMap items (<a href="https://github.com/godotengine/godot/pull/85443">GH-85443</a>).</li>
|
||
<li>3D: Add CollisionShape3D custom debug colors (<a href="https://github.com/godotengine/godot/pull/90644">GH-90644</a>).</li>
|
||
<li>3D: Add Camera3D preview in Inspector (<a href="https://github.com/godotengine/godot/pull/90778">GH-90778</a>).</li>
|
||
<li>3D: Allow tool scripts to alter transform of Node3DEditorViewport camera (<a href="https://github.com/godotengine/godot/pull/93503">GH-93503</a>).</li>
|
||
<li>3D: Fix mesh corruption of CSG by using elalish/manifold (<a href="https://github.com/godotengine/godot/pull/94321">GH-94321</a>).</li>
|
||
<li>3D: Adjust VoxelGI gizmo opacity (<a href="https://github.com/godotengine/godot/pull/99969">GH-99969</a>).</li>
|
||
<li>Animation: Add persistent folding to Animation Library Editor (<a href="https://github.com/godotengine/godot/pull/86481">GH-86481</a>).</li>
|
||
<li>Animation: Fix crash when re-importing model with AnimationPlayer panel open and node selected (<a href="https://github.com/godotengine/godot/pull/95795">GH-95795</a>).</li>
|
||
<li>Animation: Add RetargetModifier3D for realtime retarget to keep original rest (<a href="https://github.com/godotengine/godot/pull/97824">GH-97824</a>).</li>
|
||
<li>Animation: Prioritize proximity to green arrow when selecting overlapping transitions in AnimationNodeStateMachine (<a href="https://github.com/godotengine/godot/pull/98401">GH-98401</a>).</li>
|
||
<li>Audio: Add runtime file loading to <code class="language-plaintext highlighter-rouge">AudioStreamWAV</code> (<a href="https://github.com/godotengine/godot/pull/93831">GH-93831</a>).</li>
|
||
<li>Audio: Fix AudioStreamPlayer2D/3D’s <code class="language-plaintext highlighter-rouge">get_playback_position</code> returning <code class="language-plaintext highlighter-rouge">0</code> right after calling <code class="language-plaintext highlighter-rouge">seek</code> (<a href="https://github.com/godotengine/godot/pull/99759">GH-99759</a>).</li>
|
||
<li>C#: Preserve no-hint behavior for unmarshallable generics in dictionaries (<a href="https://github.com/godotengine/godot/pull/99485">GH-99485</a>).</li>
|
||
<li>Core: RegEx: Fix handling of unset/unknown capture groups (<a href="https://github.com/godotengine/godot/pull/73973">GH-73973</a>).</li>
|
||
<li>Core: FileAccess: Return error codes from <code class="language-plaintext highlighter-rouge">store_*</code> methods (<a href="https://github.com/godotengine/godot/pull/78289">GH-78289</a>).</li>
|
||
<li>Core: Avoid duplicating signals from scene instances into packed scenes (<a href="https://github.com/godotengine/godot/pull/97303">GH-97303</a>).</li>
|
||
<li>Core: Make loading translations from threads safe (<a href="https://github.com/godotengine/godot/pull/99527">GH-99527</a>).</li>
|
||
<li>Core: Do not generate <code class="language-plaintext highlighter-rouge">*.uid</code> files for JSON, certificates, and translations (<a href="https://github.com/godotengine/godot/pull/99540">GH-99540</a>).</li>
|
||
<li>Core: Convert line breaks to <code class="language-plaintext highlighter-rouge">\n</code> and strip line break from the end of string returned by <code class="language-plaintext highlighter-rouge">OS::read_string_from_stdin</code>/<code class="language-plaintext highlighter-rouge">OS::get_stdin_string</code> (<a href="https://github.com/godotengine/godot/pull/99542">GH-99542</a>).</li>
|
||
<li>Core: Fix <code class="language-plaintext highlighter-rouge">OS::has_feature()</code> skipping custom features (<a href="https://github.com/godotengine/godot/pull/99864">GH-99864</a>).</li>
|
||
<li>Core: Add temp utilities (alias <code class="language-plaintext highlighter-rouge">OS::get_temp_dir()</code>, <code class="language-plaintext highlighter-rouge">FileAccess::create_temp()</code>, and <code class="language-plaintext highlighter-rouge">DirAccess::create_temp()</code>) (<a href="https://github.com/godotengine/godot/pull/98397">GH-98397</a>).</li>
|
||
<li>Editor: Extend Curve to allow for domains outside of <code class="language-plaintext highlighter-rouge">[0, 1]</code> (<a href="https://github.com/godotengine/godot/pull/67857">GH-67857</a>).</li>
|
||
<li>Editor: Implement zooming and panning in the profiler (<a href="https://github.com/godotengine/godot/pull/76055">GH-76055</a>).</li>
|
||
<li>Editor: Fix jumping to editor help does not scroll correctly sometimes (<a href="https://github.com/godotengine/godot/pull/96449">GH-96449</a>).</li>
|
||
<li>Editor: Show file names in remove files confirmation dialog (<a href="https://github.com/godotengine/godot/pull/98539">GH-98539</a>).</li>
|
||
<li>Editor: Add editor setting to stop the bottom panel from switching to the Stack Trace (<a href="https://github.com/godotengine/godot/pull/98657">GH-98657</a>).</li>
|
||
<li>Editor: Don’t tint editor bottom panel icons when hovered or pressed (<a href="https://github.com/godotengine/godot/pull/98765">GH-98765</a>).</li>
|
||
<li>Editor: Add copy button to toast notification (<a href="https://github.com/godotengine/godot/pull/98778">GH-98778</a>).</li>
|
||
<li>Editor: Enable editing of controls inside viewports in editor (<a href="https://github.com/godotengine/godot/pull/99401">GH-99401</a>).</li>
|
||
<li>Editor: Improve appearance of external links in built-in docs (<a href="https://github.com/godotengine/godot/pull/99480">GH-99480</a>).</li>
|
||
<li>Editor: Make the alt selection menu available for all modes (<a href="https://github.com/godotengine/godot/pull/99795">GH-99795</a>).</li>
|
||
<li>Export: Ensure excluded GDExtension files are not included in <code class="language-plaintext highlighter-rouge">extension_list.cfg</code> (<a href="https://github.com/godotengine/godot/pull/97216">GH-97216</a>).</li>
|
||
<li>Export: Write text server data from memory, instead of using temporary file (<a href="https://github.com/godotengine/godot/pull/99164">GH-99164</a>).</li>
|
||
<li>GDExtension: Register Engine, OS, ProjectSettings, and Time singletons in time for <code class="language-plaintext highlighter-rouge">INITIZATION_LEVEL_CORE</code> (<a href="https://github.com/godotengine/godot/pull/98862">GH-98862</a>).</li>
|
||
<li>GDExtension: Support extension icons in ScriptCreateDialog (<a href="https://github.com/godotengine/godot/pull/98914">GH-98914</a>).</li>
|
||
<li>GDScript: Fix crash when division by zero/modulo by zero happen on vectors (<a href="https://github.com/godotengine/godot/pull/95172">GH-95172</a>).</li>
|
||
<li>GDScript: Improve GDScript autocompletion for methods (<a href="https://github.com/godotengine/godot/pull/99102">GH-99102</a>).</li>
|
||
<li>GDScript: LSP: Fix spec violations that break the VSCode outline (<a href="https://github.com/godotengine/godot/pull/99295">GH-99295</a>).</li>
|
||
<li>GDScript: Core: Fix built-in enum constant bindings (<a href="https://github.com/godotengine/godot/pull/99424">GH-99424</a>).</li>
|
||
<li>GDScript: Support tracking multiple analyzer and runtime errors in tests (<a href="https://github.com/godotengine/godot/pull/99490">GH-99490</a>).</li>
|
||
<li>GUI: Add a Viewport method to get automatically computed 2D stretch transform (<a href="https://github.com/godotengine/godot/pull/80965">GH-80965</a>).</li>
|
||
<li>GUI: Make <code class="language-plaintext highlighter-rouge">FileDialog</code> filtering case insensitive (<a href="https://github.com/godotengine/godot/pull/85789">GH-85789</a>).</li>
|
||
<li>GUI: Make TextEdit autocompletion replace word unless Shift is held (<a href="https://github.com/godotengine/godot/pull/90723">GH-90723</a>).</li>
|
||
<li>GUI: Reshape and update button on oversampling change (<a href="https://github.com/godotengine/godot/pull/95511">GH-95511</a>).</li>
|
||
<li>GUI: Prevent infinite recursion in first <code class="language-plaintext highlighter-rouge">_draw</code> (<a href="https://github.com/godotengine/godot/pull/97328">GH-97328</a>).</li>
|
||
<li>GUI: Add theme type variations for secondary Trees and ItemLists (<a href="https://github.com/godotengine/godot/pull/97884">GH-97884</a>).</li>
|
||
<li>GUI: RTL: Add support for vertical alignment (<a href="https://github.com/godotengine/godot/pull/97963">GH-97963</a>).</li>
|
||
<li>GUI: Introduce a <code class="language-plaintext highlighter-rouge">SubViewportContainer</code> config for drag-and-drop target locations (<a href="https://github.com/godotengine/godot/pull/99270">GH-99270</a>, <a href="https://github.com/godotengine/godot/pull/99691">GH-99691</a>).</li>
|
||
<li>GUI: Fix SVG font rendering (<a href="https://github.com/godotengine/godot/pull/99459">GH-99459</a>).</li>
|
||
<li>GUI: Add tooltip support to meta/url tag (<a href="https://github.com/godotengine/godot/pull/99481">GH-99481</a>).</li>
|
||
<li>Import: Generate thumbnails on imported scenes (<a href="https://github.com/godotengine/godot/pull/96544">GH-96544</a>).</li>
|
||
<li>Import: Blend file import: Don’t keep original files when not unpacking them (<a href="https://github.com/godotengine/godot/pull/96782">GH-96782</a>).</li>
|
||
<li>Import: Betsy: Add BC3 and BC5 support (<a href="https://github.com/godotengine/godot/pull/99537">GH-99537</a>).</li>
|
||
<li>Multiplayer: Fix UID support in MultiplayerSpawner (<a href="https://github.com/godotengine/godot/pull/99712">GH-99712</a>).</li>
|
||
<li>Navigation: Improve <code class="language-plaintext highlighter-rouge">NavMeshQueries3D::polygons_get_closest_point_info</code> performance (<a href="https://github.com/godotengine/godot/pull/97928">GH-97928</a>).</li>
|
||
<li>Navigation: Make NavMap objects request sync only on demand (<a href="https://github.com/godotengine/godot/pull/99646">GH-99646</a>).</li>
|
||
<li>Network: Add half precision floating point support to <code class="language-plaintext highlighter-rouge">StreamPeer</code> and <code class="language-plaintext highlighter-rouge">FileAccess</code> (<a href="https://github.com/godotengine/godot/pull/97716">GH-97716</a>).</li>
|
||
<li>Network: Allow disabling UPNP implementation on the Web (<a href="https://github.com/godotengine/godot/pull/99597">GH-99597</a>).</li>
|
||
<li>Physics: Fix <code class="language-plaintext highlighter-rouge">GodotSpace3D::test_body_motion()</code> not setting <code class="language-plaintext highlighter-rouge">local_shape</code> (<a href="https://github.com/godotengine/godot/pull/99901">GH-99901</a>).</li>
|
||
<li>Porting: Android: Fix immersive mode issue (<a href="https://github.com/godotengine/godot/pull/98917">GH-98917</a>).</li>
|
||
<li>Porting: macOS: Change the shortcut for Align Transform with View (<a href="https://github.com/godotengine/godot/pull/94026">GH-94026</a>).</li>
|
||
<li>Porting: Unix: Don’t create world-writable files when safe save is enabled (<a href="https://github.com/godotengine/godot/pull/96399">GH-96399</a>).</li>
|
||
<li>Porting: Windows: Fix restoring fullscreen window (<a href="https://github.com/godotengine/godot/pull/98631">GH-98631</a>).</li>
|
||
<li>Porting: Windows: Fix Inspector tooltips blinking on Windows (<a href="https://github.com/godotengine/godot/pull/99988">GH-99988</a>).</li>
|
||
<li>Porting: Windows: Improve frame pacing by busy waiting as needed (<a href="https://github.com/godotengine/godot/pull/99833">GH-99833</a>).</li>
|
||
<li>Porting: Implement <code class="language-plaintext highlighter-rouge">DisplayServer.beep</code> (<a href="https://github.com/godotengine/godot/pull/99371">GH-99371</a>).</li>
|
||
<li>Rendering: Optimize <code class="language-plaintext highlighter-rouge">RenderForwardClustered::_setup_render_pass_uniform_set</code> by reducing Vector allocations (<a href="https://github.com/godotengine/godot/pull/94368">GH-94368</a>).</li>
|
||
<li>Rendering: Deprecate the pointless unsafe threading model for rendering (<a href="https://github.com/godotengine/godot/pull/98383">GH-98383</a>).</li>
|
||
<li>Rendering: Automatically resolve initial and final action for draw lists (<a href="https://github.com/godotengine/godot/pull/98670">GH-98670</a>).</li>
|
||
<li>Rendering: Fix occlusion culling for double builds by enforcing float conversion for Embree (<a href="https://github.com/godotengine/godot/pull/98770">GH-98770</a>).</li>
|
||
<li>Rendering: Mask out shadows on CanvasItems that don’t have a matching <code class="language-plaintext highlighter-rouge">item_shadow_mask</code> (<a href="https://github.com/godotengine/godot/pull/98835">GH-98835</a>).</li>
|
||
<li>Rendering: Add lightmap bake cancelling (<a href="https://github.com/godotengine/godot/pull/99483">GH-99483</a>).</li>
|
||
<li>Rendering: Add VoxelGI bake cancelling and progress UI improvement (<a href="https://github.com/godotengine/godot/pull/99562">GH-99562</a>).</li>
|
||
<li>Rendering: Fix ReflectionProbe AABB (<a href="https://github.com/godotengine/godot/pull/99802">GH-99802</a>).</li>
|
||
<li>Shaders: Allow <code class="language-plaintext highlighter-rouge">SCREEN_UV</code> to be used in light function of spatial shader (<a href="https://github.com/godotengine/godot/pull/94981">GH-94981</a>).</li>
|
||
<li>Shaders: VisualShader: Add LinearToSRGB and SRGBToLinear to ColorFunc node (<a href="https://github.com/godotengine/godot/pull/97388">GH-97388</a>).</li>
|
||
</ul>
|
||
<h2 id="changelog">Changelog</h2>
|
||
<p><strong>114 contributors</strong> submitted <strong>259 improvements</strong> for this new snapshot. See our <a href="https://godotengine.github.io/godot-interactive-changelog/#4.4-dev6"><strong>interactive changelog</strong></a> for the complete list of changes since the previous 4.4-dev5 snapshot.</p>
|
||
<p>This release is built from commit <a href="https://github.com/godotengine/godot/commit/1f47e4c4e3a09a422e96880a7918d986dd575a63"><code class="language-plaintext highlighter-rouge">1f47e4c4e</code></a>.</p>
|
||
<h2 id="downloads">Downloads</h2>
|
||
<div class="card card-download">
|
||
<a class="card-download-link" href="/download/archive/4.4-dev6">
|
||
Download Godot 4.4 dev6
|
||
</a>
|
||
<div class="card-download-details">
|
||
<img class="lightbox-ignore" src="/storage/blog/covers/dev-snapshot-godot-4-4-dev-6.webp" />
|
||
<div class="card-download-platforms">
|
||
<div class="download-platform platform-linux">
|
||
<img width="24" height="24" src="/assets/images/platforms/linux.svg" title="Linux" alt="Linux" class="lightbox-ignore" />
|
||
Linux
|
||
</div>
|
||
<a href="https://github.com/godotengine/godot-builds/releases/download/4.4-dev6/Godot_v4.4-dev6_linux.x86_64.zip" class="btn btn-download btn-download-primary platform-linux">
|
||
<div class="download-title">
|
||
Standard
|
||
</div>
|
||
</a>
|
||
<a href="https://github.com/godotengine/godot-builds/releases/download/4.4-dev6/Godot_v4.4-dev6_mono_linux_x86_64.zip" class="btn btn-download btn-download-primary btn-download-primary--mono platform-linux">
|
||
<div class="download-title">
|
||
.NET
|
||
</div>
|
||
</a>
|
||
<div class="download-platform platform-macos">
|
||
<img width="24" height="24" src="/assets/images/platforms/macos.svg" title="macOS" alt="macOS" class="lightbox-ignore" />
|
||
macOS
|
||
</div>
|
||
<a href="https://github.com/godotengine/godot-builds/releases/download/4.4-dev6/Godot_v4.4-dev6_macos.universal.zip" class="btn btn-download btn-download-primary platform-macos">
|
||
<div class="download-title">
|
||
Standard
|
||
</div>
|
||
</a>
|
||
<a href="https://github.com/godotengine/godot-builds/releases/download/4.4-dev6/Godot_v4.4-dev6_mono_macos.universal.zip" class="btn btn-download btn-download-primary btn-download-primary--mono platform-macos">
|
||
<div class="download-title">
|
||
.NET
|
||
</div>
|
||
</a>
|
||
<div class="download-platform platform-windows">
|
||
<img width="24" height="24" src="/assets/images/platforms/windows.svg" title="Windows" alt="Windows" class="lightbox-ignore" />
|
||
Windows
|
||
</div>
|
||
<a href="https://github.com/godotengine/godot-builds/releases/download/4.4-dev6/Godot_v4.4-dev6_win64.exe.zip" class="btn btn-download btn-download-primary platform-windows">
|
||
<div class="download-title">
|
||
Standard
|
||
</div>
|
||
</a>
|
||
<a href="https://github.com/godotengine/godot-builds/releases/download/4.4-dev6/Godot_v4.4-dev6_mono_win64.zip" class="btn btn-download btn-download-primary btn-download-primary--mono platform-windows">
|
||
<div class="download-title">
|
||
.NET
|
||
</div>
|
||
</a>
|
||
</div>
|
||
</div>
|
||
<div class="card-download-sublinks">
|
||
<a class="card-download-other" href="/download/archive/4.4-dev6">
|
||
Export templates and other downloads
|
||
</a>
|
||
<a class="card-download-donate" href="https://fund.godotengine.org/">
|
||
Make a Donation
|
||
</a>
|
||
</div>
|
||
</div>
|
||
<style>
|
||
.thankyou-wrapper {
|
||
position: fixed;
|
||
top: 0;
|
||
left: 0;
|
||
right: 0;
|
||
bottom: 0;
|
||
background: rgba(0, 0, 0, 0.85);
|
||
display: flex;
|
||
flex-direction: column;
|
||
justify-content: center;
|
||
align-items: center;
|
||
z-index: 10;
|
||
}
|
||
.thankyou {
|
||
background: var(--base-color);
|
||
box-shadow: var(--more-shadow);
|
||
padding: 30px;
|
||
display: flex;
|
||
flex-direction: column;
|
||
align-items: center;
|
||
text-align: center;
|
||
position: relative;
|
||
border-radius: 13px;
|
||
}
|
||
.thankyou-reading {
|
||
font-size: 16px;
|
||
}
|
||
.thankyou-reading-list {
|
||
font-size: 16px;
|
||
margin: 0;
|
||
margin-left: 48px;
|
||
padding-left: 0;
|
||
}
|
||
.thankyou-donate {
|
||
margin-bottom: 24px;
|
||
text-align: center;
|
||
}
|
||
.btn.btn-donate {
|
||
background-color: var(--primary-color);
|
||
color: hsla(0, 0%, 100%, 0.9);
|
||
font-size: 22px;
|
||
font-weight: 600;
|
||
margin-bottom: 26px;
|
||
}
|
||
.thankyou h2 {
|
||
text-shadow: var(--base-shadow);
|
||
font-size: 36px;
|
||
font-weight: 800;
|
||
margin-bottom: 12px;
|
||
}
|
||
.thankyou h2 .anchored-link {
|
||
/* Hiding the anchored text automatically added on blogposts */
|
||
display: none !important;
|
||
}
|
||
.thankyou p {
|
||
max-width: 620px;
|
||
font-size: 25px;
|
||
}
|
||
@media (max-width: 768px) {
|
||
.thankyou-wrapper {
|
||
display: block;
|
||
}
|
||
.thankyou {
|
||
position: absolute;
|
||
top: 0;
|
||
left: 0;
|
||
right: 0;
|
||
bottom: 0;
|
||
overflow: scroll;
|
||
padding: 30px 40px 18px 40px;
|
||
}
|
||
.thankyou-reading-list {
|
||
margin-left: 24px;
|
||
}
|
||
.btn-close-thankyou-popup {
|
||
width: 48px;
|
||
height: 48px;
|
||
display: flex;
|
||
justify-content: center;
|
||
align-items: center;
|
||
}
|
||
}
|
||
.btn-close-thankyou-popup {
|
||
cursor: pointer;
|
||
position: absolute;
|
||
top: 12px;
|
||
right: 12px;
|
||
}
|
||
.btn-close-thankyou-popup img {
|
||
background: transparent !important; /* for overwriting the style in the blogposts img */
|
||
}
|
||
@media (prefers-color-scheme: light) {
|
||
.btn-close-thankyou-popup img {
|
||
filter: invert(1);
|
||
opacity: 0.75;
|
||
}
|
||
}
|
||
</style>
|
||
<script>
|
||
document.addEventListener('DOMContentLoaded', () => {
|
||
const thankYouWrapper = document.getElementById('thank-you');
|
||
// Close itself, when clicked outside of the popup area.
|
||
thankYouWrapper.addEventListener('click', (e) => {
|
||
if (e.target === thankYouWrapper) {
|
||
thankYouWrapper.style.display = 'none';
|
||
}
|
||
});
|
||
// Close with a close button.
|
||
const thankYouBackButton = document.querySelector('.btn-close-thankyou-popup');
|
||
thankYouBackButton.addEventListener('click', () => {
|
||
thankYouWrapper.style.display = 'none';
|
||
});
|
||
// Open from the main download buttons.
|
||
const downloadButtons = document.querySelectorAll('.btn-download');
|
||
downloadButtons.forEach((it) => {
|
||
it.addEventListener('click', () => {
|
||
thankYouWrapper.style.display = '';
|
||
document.querySelector('.btn.btn-donate').focus();
|
||
});
|
||
});
|
||
// Open from the all downloads list.
|
||
const downloadLinks = document.querySelectorAll('.download-link');
|
||
downloadLinks.forEach((it) => {
|
||
it.addEventListener('click', () => {
|
||
thankYouWrapper.style.display = '';
|
||
});
|
||
});
|
||
// Close the dialog when the user presses the escape key.
|
||
document.addEventListener('keydown', (e) => {
|
||
if (e.key === 'Escape') {
|
||
thankYouWrapper.style.display = 'none';
|
||
}
|
||
});
|
||
});
|
||
</script>
|
||
<div class="thankyou-wrapper" id="thank-you" style="display: none;">
|
||
<div class="thankyou">
|
||
<h2>Godot is downloading...</h2>
|
||
<p class="thankyou-donate">
|
||
Godot exists thanks to donations from people like you. Help us continue our work:
|
||
</p>
|
||
<a href="https://fund.godotengine.org" class="btn btn-donate">
|
||
Make a Donation
|
||
</a>
|
||
<div class="btn-close-thankyou-popup">
|
||
<img src="/assets/icons/cross.svg" width="24" height="24" alt="Close this popup" class="lightbox-ignore" />
|
||
</div>
|
||
</div>
|
||
</div>
|
||
<p><strong>Standard build</strong> includes support for GDScript and GDExtension.</p>
|
||
<p><strong>.NET build</strong> (marked as <code class="language-plaintext highlighter-rouge">mono</code>) includes support for C#, as well as GDScript and GDExtension.</p>
|
||
<ul>
|
||
<li>See also <a href="https://docs.godotengine.org/en/latest/tutorials/scripting/c_sharp/index.html#c-platform-support">C# platform support</a>.</li>
|
||
</ul>
|
||
<div class="card card-warning">
|
||
<p>
|
||
While engine maintainers try their best to ensure that each preview snapshot and release candidate is stable, this is by definition <strong>a pre-release piece of software</strong>. Be sure to make frequent backups, or use a version control system such as Git, to preserve your projects in case of corruption or data loss.
|
||
</p>
|
||
</div>
|
||
<h2 id="known-issues">Known issues</h2>
|
||
<p>With every release we accept that there are going to be various issues, which have already been reported but haven’t been fixed yet. See the GitHub issue tracker for a complete list of <a href="https://github.com/godotengine/godot/issues?q=is%3Aissue+is%3Aopen+label%3Abug+">known bugs</a>.</p>
|
||
<p>Here are some known regressions introduced in this snapshot:</p>
|
||
<ul>
|
||
<li>Occlusion culling randomly occluding things completely in the open (<a href="https://github.com/godotengine/godot/issues/100032">GH-10032</a>).
|
||
<ul>
|
||
<li>A pull request is already open to fix this in the next dev snapshot (<a href="https://github.com/godotengine/godot/pull/100060">GH-100060</a>).</li>
|
||
</ul>
|
||
</li>
|
||
<li>Error “Manifold creation from mesh failed” with Plane and Quad shapes, which do not get rendered (<a href="https://github.com/godotengine/godot/issues/100014">GH-100014</a>).
|
||
<ul>
|
||
<li>Planes and Quads cannot be used with CSG, and just seemed to be usable previously. We’ll improve the usability so they cannot be selected for CSGMesh3D. Instead, use MeshInstance3D to place Planes and Quads.</li>
|
||
</ul>
|
||
</li>
|
||
</ul>
|
||
<h2 id="bug-reports">Bug reports</h2>
|
||
<p>As a tester, we encourage you to <a href="https://github.com/godotengine/godot/issues">open bug reports</a> if you experience issues with this release. Please check the <a href="https://github.com/godotengine/godot/issues">existing issues on GitHub</a> first, using the search function with relevant keywords, to ensure that the bug you experience is not already known.</p>
|
||
<p>In particular, any change that would cause a regression in your projects is very important to report (e.g. if something that worked fine in previous 4.x releases, but no longer works in this snapshot).</p>
|
||
<h2 id="support">Support</h2>
|
||
<p>Godot is a non-profit, open source game engine developed by hundreds of contributors on their free time, as well as a handful of part or full-time developers hired thanks to <a href="https://fund.godotengine.org/">generous donations from the Godot community</a>. A big thank you to everyone who has contributed <a href="https://github.com/godotengine/godot/blob/master/AUTHORS.md">their time</a> or <a href="https://github.com/godotengine/godot/blob/master/DONORS.md">their financial support</a> to the project!</p>
|
||
<p>If you’d like to support the project financially and help us secure our future hires, you can do so using the <a href="https://fund.godotengine.org/">Godot Development Fund</a> platform managed by <a href="https://godot.foundation/">Godot Foundation</a>. There are also several <a href="/donate">alternative ways to donate</a> which you may find more suitable.</p></description><category>Pre-release</category><guid>https://godotengine.org/article/dev-snapshot-godot-4-4-dev-6/</guid><dc:creator>Thaddeus Crews</dc:creator><pubDate>Thu, 05 Dec 2024 17:00:00 +0000</pubDate><image>https://godotengine.org/storage/blog/covers/dev-snapshot-godot-4-4-dev-6.webp</image></item><item><title>Beyond #100000: You're breathtaking!</title><link>https://godotengine.org/article/beyond-100000-you-re-breathtaking/</link><summary>As we reach issue #100,000 on GitHub, we celebrate with a little retrospective on our issue and pull request growth.</summary><description><div class="card card-info" style="margin-top: 1em;">
|
||
<p>This blog post was originally posted on <a href="https://github.com/godotengine/godot/issues/100000">GH-100000</a>.</p>
|
||
</div>
|
||
<p>It’s been over 10 years now that Godot has been developed in the open, with code contributions from 2,800 users.</p>
|
||
<p>The total count of people who helped build Godot is actually far greater, as it should include documentation writers, testers, bug reporters, translators, moderators, content creators, users doing community support or talking at events, folks making games that credit Godot visibly, everyone supporting the project financially, and many other types of contributions which I can’t keep enumerating.</p>
|
||
<p>All these people brought Juan and Ariel’s little-engine-that-could from this:</p>
|
||
<p><img src="/storage/blog/beyond-100000-you-re-breathtaking/godot-1-0.webp" alt="Screenshot of the isometric 2D demo in Godot 1.0" /></p>
|
||
<div class="small text-center">
|
||
<p><em>Screenshot of the isometric 2D demo in Godot 1.0.</em></p>
|
||
</div>
|
||
<p>To this:</p>
|
||
<p><img src="/storage/blog/beyond-100000-you-re-breathtaking/godot-4-3.webp" alt="Screenshot of PVKK: Planetenverteidigungskanonenkommandant in Godot 4.3" /></p>
|
||
<div class="small text-center">
|
||
<p><em>Screenshot of <a href="https://store.steampowered.com/app/2956040/PVKK_Planetenverteidigungskanonenkommandant/">PVKK: Planetenverteidigungskanonenkommandant</a> in Godot 4.3.</em></p>
|
||
</div>
|
||
<p>That’s no small achievement, so I encourage all contributors to take a minute to contemplate the progress that we’ve made together over this journey so far!</p>
|
||
<p>Amidst the daily churn of fixing issues, reviewing <abbr title="pull requests">PRs</abbr>, making releases, etc., it’s important to remind ourselves of where we are, and how we got there.</p>
|
||
<video autoplay="" loop="" muted="">
|
||
<source src="/storage/blog/beyond-100000-you-re-breathtaking/cozy-space-survivors.webm" />
|
||
</video>
|
||
<div class="small text-center">
|
||
<p><em>GIF of <a href="https://store.steampowered.com/app/2657850/Cozy_Space_Survivors/">Cozy Space Survivors</a> where asteroids form the word “GO♥DOT”.</em></p>
|
||
</div>
|
||
<h2 id="some-stats-about-godot-usage-on-github">Some stats about Godot usage on GitHub</h2>
|
||
<p>Between our usual traditions of either <a href="https://github.com/godotengine/godot/issues/10000">making silly jokes</a> or <a href="https://github.com/godotengine/godot/issues/30000">sharing some inspiring stats</a> for round issue numbers, I picked the latter for this 100,000th issue<sup id="fnref:1" role="doc-noteref"><a href="#fn:1" class="footnote" rel="footnote">1</a></sup>, and wanted to look a bit closer at our issue and <abbr title="pull request">PR</abbr> numbers over time.</p>
|
||
<p>A lot of people coming to Godot’s repository to see over 10,000 open issues and 3,000 open <abbr title="pull requests">PRs</abbr> might rightfully wonder whether this is normal, or a sign of a maintenance issue.
|
||
I will make the case that it is a bit of both :)</p>
|
||
<h3 id="issues">Issues</h3>
|
||
<p><img src="/storage/blog/beyond-100000-you-re-breathtaking/issue-history.webp" alt="Graph showing issue count over time" /></p>
|
||
<div class="small text-center">
|
||
<p><em>Visualization from OSS Insight showing issue count over time, <a href="https://ossinsight.io/analyze/godotengine/godot#issue-history">see the interactive version</a>.</em></p>
|
||
</div>
|
||
<p>The two accumulated curves show the total number of issues created over the lifetime of the repository (topmost curve), and the subset of those which have been closed (as fixed or invalid). The difference between the two curves represents the number of issues still open at a given point in time - currently exactly 11,000, out of 53,648 issues total, so roughly 20%.</p>
|
||
<p>This is a fairly normal percentage of yet-unresolved issues in software projects of this scale, but it can definitely be better.</p>
|
||
<p>I annotated the graph with some key events of Godot’s development which match peaks in either reported bugs (usually at the start of a beta phase, or shortly after a stable release), or closed issues (when we do a “spring cleaning” going through old issues to check if they are still reproducible in a newly released Godot version). You can see notably two big peaks of closed issues around the 3.2 release, when we had a coordinated effort from maintainers to go through the whole backlog and ask reporters to confirm whether their issues were still valid, or had been fixed. This reduced the percentage of open issues from 29% to 19%, and it’s been mostly stable since, with minor fluctuations.</p>
|
||
<p>We are preparing a new “spring cleaning” to properly reassess a lot of the old issues which have been opened before the 4.0 release, or in the early days of 4.0 or 4.1, and may no longer be relevant nowadays with 4.3 and soon 4.4 beta.</p>
|
||
<p>As the volume of issues keeps increasing steadily, but the number of active bug triagers doesn’t really grow as fast, we are working on improving and documenting our workflows so that we can:</p>
|
||
<ul>
|
||
<li>Onboard new volunteers to help triage new and old issues;</li>
|
||
<li>Spread the workload and be more consistent with our issue triage;</li>
|
||
<li>Be confident that while doing so, we do increase the <em>quality</em> of our open issues, which isn’t something that can be easily tracked in numbers.</li>
|
||
</ul>
|
||
<p>We will share more details here and on the Godot blog when this process is ready to welcome new volunteers.</p>
|
||
<p>In the meantime, you can already do some simple things which help greatly the existing bug triage team:</p>
|
||
<ul>
|
||
<li><a href="https://github.com/godotengine/godot/issues?q=is%3Aissue%20state%3Aopen%20author%3A%40me"><strong>Regularly re-assess your own issues</strong></a> (you can bookmark that URL). Make sure that they are reproducible in the latest stable release and dev snapshots, and that there is a minimal reproduction project that contributors can use to reproduce and fix the issue. If your issue is no longer relevant, please close it with a comment explaining why.</li>
|
||
<li>Feel free to apply the same process to other people’s issues that you stumble upon, especially if their last update was a long time ago. In this case you can’t close issues yourself, but you can suggest it by commenting that the issue is no longer reproducible in the version you tested. Bug triagers will get a notification and can double check.</li>
|
||
</ul>
|
||
<h3 id="pull-requests">Pull Requests</h3>
|
||
<p><img src="/storage/blog/beyond-100000-you-re-breathtaking/pull-request-history.webp" alt="Graph showing pull request count over time" /></p>
|
||
<div class="small text-center">
|
||
<p><em>Visualization from OSS Insight showing pull request count over time, <a href="https://ossinsight.io/analyze/godotengine/godot#pr-history">see the interactive version</a>.</em></p>
|
||
</div>
|
||
<p>I didn’t annotate this one, but a few takeaways:</p>
|
||
<ul>
|
||
<li>Godot gets almost the same number of new pull requests per month as new issues, roughly 600 of each per month (that’s 20 <abbr title="pull requests">PRs</abbr> and 20 issues per day).</li>
|
||
<li>The <abbr title="pull request">PR</abbr> volume increased a lot over the lifetime of the project to culminate at over 700 <abbr title="pull requests">PRs</abbr> per month at the end of the 4.0 development. Since then, as the Godot userbase grew a lot and we are more careful with compatibility and API design, reviews can take a bit longer and the total monthly volume seems to have plateaued around 500-600. That’s still plenty enough for a fairly small group of reviewers.</li>
|
||
<li>Someone should plot this data with relative percentages, but it seems like the size/complexity of pull requests is slightly increasing recently. Whether that trend gets confirmed or not, I can attest that reviewing 600 <abbr title="pull requests">PRs</abbr> per month is hard, and that we need more help for interested contributors and users to both test and review the <abbr title="pull requests">PRs</abbr> that get opened on a daily basis.</li>
|
||
</ul>
|
||
<hr />
|
||
<p>That’s all for now, I was already way too long and verbose while drafting this at the last minute to (try to) snatch the 100,000th issue number ;)</p>
|
||
<p>Aside from showing some cool numbers, I mostly want to convey that we are well aware that we have a significant backlog, though it’s not as dire as it might look from the outside.</p>
|
||
<p>To deal with it, we need better triage and review processes (which we are designing now), more volunteers involved in these processes, but also importantly <a href="https://fund.godotengine.org/"><strong>more funding</strong></a>. Volunteer contributors do a ton of work, but many critical parts of the workflow depend on a few paid contractors, and we need to grow that group to better manage the increasing scale of the project.</p>
|
||
<div class="footnotes" role="doc-endnotes">
|
||
<ol>
|
||
<li id="fn:1" role="doc-endnote">
|
||
<p>I’ll make a quick note that 100,000 is the combined number of issues and <abbr title="pull requests">PRs</abbr>, which share the same index system on GitHub.<br /><br />At the time of writing, we’ve actually had 53,648 issues and 45,213 <abbr title="pull requests">PRs</abbr> created. Astute minds will notice that the sum is not 100,000; the difference comes from spam issues or <abbr title="pull requests">PRs</abbr> which have been deleted by GitHub. <a href="#fnref:1" class="reversefootnote" role="doc-backlink">&#8617;</a></p>
|
||
</li>
|
||
</ol>
|
||
</div></description><category>News</category><guid>https://godotengine.org/article/beyond-100000-you-re-breathtaking/</guid><dc:creator>Rémi Verschelde</dc:creator><pubDate>Wed, 04 Dec 2024 19:00:00 +0000</pubDate><image>https://godotengine.org/storage/blog/covers/beyond-100000-you-re-breathtaking.webp</image></item><item><title>Godot Foundation Update December 2024</title><link>https://godotengine.org/article/godot-foundation-update-dec-2024/</link><summary>We’ve made progress on several key initiatives for the organization and the Godot ecosystem. Here’s what we’ve been up to.</summary><description><p>The Foundation has been working on a number of things behind the scenes that are important for the organization and for
|
||
the Godot ecosystem more broadly. We wanted to take the chance to highlight a few of them in this post.</p>
|
||
<h2 id="key-policies-and-procedures">Key policies and procedures</h2>
|
||
<p>The Foundation was formed in August 2022, but we only began operating in a full capacity in July 2023. We initially
|
||
adopted the <a href="https://sfconservancy.org/projects/policies/">member project policies</a> of the Software Freedom Conservancy.
|
||
Doing so allowed us to operate exactly as we had when we were a member project of the SFC, and maintain very high
|
||
standards.</p>
|
||
<p>In September, we adopted a modified version of those policies that is more specific to our organization. You can read the
|
||
updated version on the <a href="https://godot.foundation/policies-and-procedures/key-policies">Godot Foundation website</a>.</p>
|
||
<p>We are very happy with the policies and we hope you are too. They hold us to a very high standard and ensure that the
|
||
Foundation will always operate in a way that supports Godot.</p>
|
||
<h2 id="contractors">Contractors</h2>
|
||
<p>The Foundation currently has 10 contractors working on the engine directly (6 full time, 4 part time) and 3 contractors
|
||
working on administration and infrastructure.</p>
|
||
<p>This is the most contractors we have had at once, and even so, we feel understaffed as there is always more
|
||
work that needs to be done than we can do. Accordingly, we would like to continue hiring once funding allows for it.</p>
|
||
<h2 id="upcoming-projects">Upcoming projects</h2>
|
||
<p>The Foundation is working on 4 major projects in addition to working on Godot itself:</p>
|
||
<ol>
|
||
<li>An official asset store</li>
|
||
<li>An official job board on the Godot website</li>
|
||
<li>A public project priorities page</li>
|
||
<li>A public trademark policy</li>
|
||
</ol>
|
||
<h3 id="asset-store">Asset store</h3>
|
||
<p>We have been working towards an initial version of the asset store for a while now. It has taken us some time to get the legal aspects into place and a design agreed upon.</p>
|
||
<p>We expect to have an early access version of the site up and running this month and we will begin inviting testers to help us polish it and get it ready for a full release sometime in 2025.</p>
|
||
<h3 id="job-board">Job board</h3>
|
||
<p>We aim to have a place for people to post that are looking to hire Godot developers to add to their game team or Godot
|
||
contributors to fix high priority bugs that may be impacting your team.</p>
|
||
<p>In addition to a job board, we will be curating a list of service providers who have shown that they offer services in
|
||
the Godot ecosystem to make it easy to find someone to contract with if you need support or any other services.</p>
|
||
<p>Much of the foundational work for this has been finished, but it will likely be released after the asset store so we can
|
||
focus our efforts more on that first.</p>
|
||
<h3 id="project-priorities">Project priorities</h3>
|
||
<p>Soon we will be adding a project priorities page to our website to give the community more clarity on the direction of
|
||
development.</p>
|
||
<p>We have avoided providing a roadmap as we don’t want to promise more than we can deliver, or put too much pressure on
|
||
volunteer contributors. However, the Godot Project maintainers have agreed that it is time to at least write down what
|
||
the largest tasks are that we are working towards. This won’t be like a traditional roadmap where we have specific tasks
|
||
with expected dates. However, we believe it will answer a lot of questions that the community has about the future of
|
||
the project.</p>
|
||
<h3 id="trademark-policy">Trademark policy</h3>
|
||
<p>We registered the Godot trademark and the Godot logo trademark while still a member project of the SFC. Last year, the
|
||
SFC granted the Godot Foundation ownership over the trademarks. Now we need to have a public policy that says how and
|
||
when others can use the trademarks to protect them.</p>
|
||
<p>We are working with our lawyers to craft a policy that is fair to existing users, as permissive as possible, and still
|
||
able to protect our trademark.</p>
|
||
<p>We will have a blog post soon with more information.</p>
|
||
<h2 id="the-foundations-role-in-the-project">The Foundation’s role in the project</h2>
|
||
<p>We also wanted to take this chance to muse about the Foundation’s role in the project. In particular, we want to
|
||
contrast the size of the Foundation with the size of the Godot project contributor pool. As explained above, the
|
||
Foundation currently hires 13 contractors to work on Godot, while the total number of contributors to Godot is over
|
||
2,500 (the 4.3 release alone had over 500 contributors)! This large group of contributors is the reason why Godot is
|
||
able to improve so quickly and do so much for a fraction of the funding that the other large engines have.</p>
|
||
<p>The Foundation (meaning the Board of Directors and the people hired by the Foundation) does not determine the priorities
|
||
of the project in a top-down way. In other words, the Foundation does not dictate to individual volunteers what they
|
||
should work on. Instead, it influences the project implicitly by making hiring decisions and hiring people for specific
|
||
tasks that aren’t being done by the community.</p>
|
||
<p>Ultimately, it is the Godot community that deserves the most credit for the growth and development of Godot. While we
|
||
hope to see the Foundation grow and take on a stronger role in the project, it should be seen as a central pillar of the
|
||
project that volunteers can rally around. Donating to the Foundation is one avenue to contribute, but there are many
|
||
more and Godot needs contribution in all areas in order to continue growing at this pace. Please consider contributing
|
||
however you are able!</p>
|
||
<h2 id="support">Support</h2>
|
||
<p>Godot is a non-profit, open source game engine developed by hundreds of contributors in their free time, as well as a handful of part or full-time developers hired thanks to <a href="https://fund.godotengine.org/">generous donations from the Godot community</a>. A big thank you to everyone who has contributed <a href="https://github.com/godotengine/godot/blob/master/AUTHORS.md">their time</a> or <a href="https://github.com/godotengine/godot/blob/master/DONORS.md">their financial support</a> to the project!</p>
|
||
<p>If you’d like to support the project financially and help us secure our future hires, you can do so using the <a href="https://fund.godotengine.org/">Godot Development Fund</a> platform managed by <a href="https://godot.foundation/">Godot Foundation</a>. There are also several <a href="/donate">alternative ways to donate</a> which you may find more suitable.</p></description><category>News</category><guid>https://godotengine.org/article/godot-foundation-update-dec-2024/</guid><dc:creator>Godot Foundation</dc:creator><pubDate>Mon, 02 Dec 2024 17:00:00 +0000</pubDate><image>https://godotengine.org/storage/blog/covers/godot-foundation-update-2024.webp</image></item><item><title>Statement on GodLoader malware loader</title><link>https://godotengine.org/article/statement-on-godloader-malware-loader/</link><summary>Godot security team clarifies the risk exposed by Check Point Research's report.</summary><description><p>Security researchers at <a href="https://research.checkpoint.com/">Check Point Research</a> have <a href="https://research.checkpoint.com/2024/gaming-engines-an-undetected-playground-for-malware-loaders/">published a report</a> about GodLoader, a malware loader using Godot as its runtime to execute malicious code and infect unaware users with known malware. Based on the report, affected users thought they were downloading and executing cracks for paid software, but instead executed the malware loader.</p>
|
||
<p>As the report states, the vulnerability is not specific to Godot. The Godot Engine is a programming system with a scripting language. It is akin to, for instance, the Python and Ruby runtimes. It is possible to write malicious programs in any programming language. We do not believe that Godot is particularly more or less suited to do so than other such programs.</p>
|
||
<p><strong>If you downloaded a Godot game or the editor from a reliable source, you don’t have to do anything. You are not at risk.</strong>
|
||
We encourage people to only execute software from trusted sources – whether it’s written using Godot or any other programming system.</p>
|
||
<p>For some more technical details:</p>
|
||
<p>Godot does not register a file handler for <code class="language-plaintext highlighter-rouge">.pck</code> files. This means that a malicious actor always has to ship the Godot runtime (<code class="language-plaintext highlighter-rouge">.exe</code> file) together with a <code class="language-plaintext highlighter-rouge">.pck</code> file. The user will always have to unpack the runtime together with the <code class="language-plaintext highlighter-rouge">.pck</code> to the same location and then execute the runtime. There is no way for a malicious actor to create a “one click exploit”, barring other OS-level vulnerabilities. If such an OS-level vulnerability were used then Godot would not be a particularly attractive option due to the size of the runtime.</p>
|
||
<p>This is similar to writing malicious software in Python or Ruby, the malicious actor will have to ship a <code class="language-plaintext highlighter-rouge">python.exe</code> or <code class="language-plaintext highlighter-rouge">ruby.exe</code> together with their malicious program.</p>
|
||
<h2 id="good-security-practices">Good security practices</h2>
|
||
<p>We would like to take this opportunity to remind users about some good security practices when it comes to downloading and executing software.</p>
|
||
<ul>
|
||
<li>Only download and execute software (including game mods) from trusted sources:
|
||
<ul>
|
||
<li>Official project website. Confirm it by checking the URL, and verify with a search engine that this seems to be the most frequently referenced website for this software.</li>
|
||
<li>Trusted distribution platform: Steam, Epic Games Store, Windows Store, Google Play, Apple Store, etc.</li>
|
||
<li>People you know, after confirming that they are who they claim to be if the communication is text-based (see below).</li>
|
||
</ul>
|
||
</li>
|
||
<li>On Windows and macOS, verify that the executable is signed (and notarized, on macOS) by a trusted party.</li>
|
||
<li>Be wary of executing cracked software, which is a prime attack vector for malicious actors.</li>
|
||
<li>Be wary of executing software even from people you know, if you can’t confirm that their account hasn’t been compromised. A very common attack vector targeting specifically game developers is for Discord accounts to get hacked, and then malicious actors use them to send malicious downloads to their friends in private messages (“hey will you try my game?”). Make sure to confirm the identity of your contacts before executing such software.</li>
|
||
</ul>
|
||
<h2 id="reporting-security-issues">Reporting security issues</h2>
|
||
<p>We thank Check Point Research for following the security guidelines of responsible disclosure, which let us confirm that this attack vector, while unfortunate, is not specific to Godot and does not expose a vulnerability in the engine or for its users.</p>
|
||
<p>If you would like to report a security vulnerability or concern, please send an email to <a href="mailto:security@godotengine.org">security@godotengine.org</a>.</p></description><category>News</category><guid>https://godotengine.org/article/statement-on-godloader-malware-loader/</guid><dc:creator>Godot Security Team</dc:creator><pubDate>Thu, 28 Nov 2024 11:00:00 +0000</pubDate><image>https://godotengine.org/storage/blog/covers/statement-on-godloader-malware-loader.webp</image></item><item><title>Dev snapshot: Godot 4.4 dev 5</title><link>https://godotengine.org/article/dev-snapshot-godot-4-4-dev-5/</link><summary>With GodotCon behind us and our developers recuperated, we're thrilled to return to a more frequent release-cycle.</summary><description><p>With <a href="https://godotengine.org/article/review-godotcon24/">GodotCon</a> behind us and our developers recuperated, we’re thrilled to return
|
||
to a more frequent release-cycle. It’s only been two weeks since we last checked in, yet there’s still so much to talk about!
|
||
So buckle on in for a breakdown of what you can expect to see in 4.4 dev 5.</p>
|
||
<p>Many of the changes in this release are bug fixes that will be backported to Godot 4.3 and released in 4.3.1! So please
|
||
test this release well so we can be confident with the changes and release 4.3.1 with them as soon as possible.</p>
|
||
<p>Keep in mind that while we try to make sure each dev snapshot is stable enough for general testing, this is by
|
||
definition a pre-release piece of software. Be sure to make frequent backups, or use a version control system such as
|
||
Git, to preserve your projects in case of corruption or data loss.</p>
|
||
<p><a href="#downloads">Jump to the <strong>Downloads</strong> section</a>, and give it a spin right now, or continue reading to learn more about improvements in this release. You can also try the <a href="https://editor.godotengine.org/releases/4.4.dev5/"><strong>Web editor</strong></a>, <a href="https://www.meta.com/experiences/godot-game-engine/7713660705416473/"><strong>XR editor</strong></a>, or the <strong>Android editor</strong> for this release (join the <a href="https://groups.google.com/g/godot-testers">Android editor testing group</a> to get access to pre-release builds).</p>
|
||
<hr />
|
||
<p><em>The cover illustration is from</em> <a href="https://store.steampowered.com/app/2716400/The_Rise_of_the_Golden_Idol/"><strong>The Rise of the Golden Idol</strong></a>, <em>a mystery game where you unravel the truth behind 20 cases of crime in the 1970s! It is developed by <a href="https://www.thegoldenidol.com/">Color Gray Games</a>. You can purchase the game <a href="https://store.steampowered.com/app/2716400/The_Rise_of_the_Golden_Idol/">on Steam</a> and follow the developer on <a href="https://twitter.com/colorgray7/">Twitter</a>.</em></p>
|
||
<h2 id="highlights">Highlights</h2>
|
||
<p>In case you missed them, see the <a href="/article/dev-snapshot-godot-4-4-dev-1/">4.4 dev 1</a>, <a href="/article/dev-snapshot-godot-4-4-dev-2/">4.4 dev 2</a>,
|
||
<a href="/article/dev-snapshot-godot-4-4-dev-3/">4.4 dev 3</a>, and <a href="/article/dev-snapshot-godot-4-4-dev-4/">4.4 dev 4</a> release notes for an overview of
|
||
some key features which were already in that snapshot, and are therefore still available for testing in dev 5.</p>
|
||
<p>Here are highlights of a few new features in dev 5 that you might find particularly exciting!</p>
|
||
<h3 id="universalize-uid-support">Universalize UID support</h3>
|
||
<p>Previously, the <abbr title="Universal ID">UID</abbr> format was not supported by all Resource types. This proved to be a pain point for users wishing to reference their scripts and other resources in a manner that’s path-agnostic. This, along with a need to refactor their scripts anytime these kinds of files were moved, put a significant duty of care on the end-user that shouldn’t have been necessary.</p>
|
||
<p>Starting with dev 5, this will no longer be your burden to bear! Thanks to a long-term effort from <a href="https://github.com/reduz">reduz</a>, UIDs will now be applied universally in a way the engine can automatically track and account for. This is achieved via <code class="language-plaintext highlighter-rouge">.uid</code> files for the resource types that previously didn’t support them, functioning similarly to other metadata files that “track” a main file.</p>
|
||
<p>Note that, unlike metadata files, <code class="language-plaintext highlighter-rouge">.uid</code> files are strictly for the editor; the information is migrated to the uid database on export. Despite this, users using version control software <strong>should add these files</strong>, as they’re required to properly sync data (similar to <code class="language-plaintext highlighter-rouge">.import</code> files). For more information, see (<a href="https://github.com/godotengine/godot/pull/97352">GH-97352</a>).</p>
|
||
<h3 id="favorite-editor-items">Favorite editor items</h3>
|
||
<p>A common complaint we hear regarding the inspector is the potential for it to get cluttered. Namely, while there’s generally a wide selection of options available for a given class/script, users will usually only care about a particular subsection that suits them. To account for this, <a href="https://github.com/YeldhamDev">YeldhamDev</a> brings us the long-awaited ability to pin one’s favorite properties in the inspector! Check out the implementation from PR (<a href="https://github.com/godotengine/godot/pull/97415">GH-97352</a>) below:</p>
|
||
<video autoplay="" loop="" muted="" playsinline="">
|
||
<source src="/storage/blog/dev-snapshot-godot-4-4-dev-5/favorite-inspector.mp4?1" type="video/mp4" />
|
||
</video>
|
||
<h3 id="and-more">And more!</h3>
|
||
<p>There are too many exciting changes to list them all here, but here’s a curated selection:</p>
|
||
<ul>
|
||
<li>2D: Add a way to know when a TileMapLayer’s cell is modified (<a href="https://github.com/godotengine/godot/pull/96188">GH-96188</a>).</li>
|
||
<li>2D: Make possible to scale multiple nodes at once in the canvas editor (<a href="https://github.com/godotengine/godot/pull/98534">GH-98534</a>).</li>
|
||
<li>3D: Fix Gridmap shortcut conflicts with 3D editor (<a href="https://github.com/godotengine/godot/pull/99170">GH-99170</a>).</li>
|
||
<li>3D: Move GridMapEditor to bottom panel (<a href="https://github.com/godotengine/godot/pull/96922">GH-96922</a>).</li>
|
||
<li>Animation: Add <code class="language-plaintext highlighter-rouge">advance_on_start</code> option to <code class="language-plaintext highlighter-rouge">NodeAnimation</code> to handle <code class="language-plaintext highlighter-rouge">advance(0)</code> for each <code class="language-plaintext highlighter-rouge">NodeAnimation</code> (<a href="https://github.com/godotengine/godot/pull/94372">GH-94372</a>).</li>
|
||
<li>Animation: Fix key is deselected by changing key time in KeyEdit in FPS mode (<a href="https://github.com/godotengine/godot/pull/99319">GH-99319</a>).</li>
|
||
<li>Animation: Implement LookAtModifier3D (<a href="https://github.com/godotengine/godot/pull/98446">GH-98446</a>).</li>
|
||
<li>Animation: Sort blend shapes in the inspector by ID instead of alphabetically (<a href="https://github.com/godotengine/godot/pull/99231">GH-99231</a>).</li>
|
||
<li>Audio: Allow waveform resize (<a href="https://github.com/godotengine/godot/pull/97551">GH-97551</a>).</li>
|
||
<li>Audio: Fix <code class="language-plaintext highlighter-rouge">AudioStreamWAV::save_to_wav</code> adding extra ‘.wav’ to file if existing ext is not lower case (<a href="https://github.com/godotengine/godot/pull/98717">GH-98717</a>).</li>
|
||
<li>Buildsystem: Bump minimum version of SCons to 4.0 &amp; Python to 3.8 (<a href="https://github.com/godotengine/godot/pull/99134">GH-99134</a>).</li>
|
||
<li>Core: Add typed dictionary support for binary serialization (<a href="https://github.com/godotengine/godot/pull/98120">GH-98120</a>).</li>
|
||
<li>Core: Fix <code class="language-plaintext highlighter-rouge">Freed Object</code> booleanization (<a href="https://github.com/godotengine/godot/pull/93885">GH-93885</a>).</li>
|
||
<li>Core: Fix <code class="language-plaintext highlighter-rouge">MissingResource</code> properties being stripped on save (<a href="https://github.com/godotengine/godot/pull/86600">GH-86600</a>).</li>
|
||
<li>Core: Fix comparison of callables (<a href="https://github.com/godotengine/godot/pull/99078">GH-99078</a>).</li>
|
||
<li>Core: Provide a reliable way to see original resources in a directory (<a href="https://github.com/godotengine/godot/pull/96590">GH-96590</a>).</li>
|
||
<li>Dotnet: Add Codium support to C# external editors (<a href="https://github.com/godotengine/godot/pull/89051">GH-89051</a>).</li>
|
||
<li>Dotnet: Implement <code class="language-plaintext highlighter-rouge">[ExportToolButton]</code> (<a href="https://github.com/godotengine/godot/pull/97894">GH-97894</a>).</li>
|
||
<li>Editor: Add a pin toggle to prevent involuntary bottom editor switching (<a href="https://github.com/godotengine/godot/pull/98074">GH-98074</a>).</li>
|
||
<li>Editor: Add fuzzy string matching to quick open search (<a href="https://github.com/godotengine/godot/pull/98278">GH-98278</a>).</li>
|
||
<li>Editor: Highlight scripts used by current scene (<a href="https://github.com/godotengine/godot/pull/97041">GH-97041</a>).</li>
|
||
<li>Editor: Optimize FileSystem Dock filtering (<a href="https://github.com/godotengine/godot/pull/95107">GH-95107</a>).</li>
|
||
<li>Export: Add ability for PCK patches to remove files (<a href="https://github.com/godotengine/godot/pull/97356">GH-97356</a>).</li>
|
||
<li>Export: Display project settings splash color on web export (<a href="https://github.com/godotengine/godot/pull/96625">GH-96625</a>)</li>
|
||
<li>GDExtension: Fix method binds not saying if they are varargs (<a href="https://github.com/godotengine/godot/pull/99403">GH-99403</a>).</li>
|
||
<li>GDExtension: Improve macOS library loading/export (<a href="https://github.com/godotengine/godot/pull/98809">GH-98809</a>).</li>
|
||
<li>GDScript: Add support for <code class="language-plaintext highlighter-rouge">print</code> command in local (command line <code class="language-plaintext highlighter-rouge">-d</code>) debugger (<a href="https://github.com/godotengine/godot/pull/97218">GH-97218</a>).</li>
|
||
<li>GUI: Fix tooltip appearing in old place, on movement (<a href="https://github.com/godotengine/godot/pull/96721">GH-96721</a>).</li>
|
||
<li>Import: Allow passing UID to importer (<a href="https://github.com/godotengine/godot/pull/97363">GH-97363</a>).</li>
|
||
<li>Import: Reload cached resources in runtime on file reimport (<a href="https://github.com/godotengine/godot/pull/98710">GH-98710</a>).</li>
|
||
<li>Input: Revert “Fix <code class="language-plaintext highlighter-rouge">InputEvent</code> device id clash” and add a compatibility function (<a href="https://github.com/godotengine/godot/pull/99449">GH-99449</a>).</li>
|
||
<li>Multiplayer: Handle scene UIDs in MultiplayerSpawner (<a href="https://github.com/godotengine/godot/pull/99137">GH-99137</a>).</li>
|
||
<li>Navigation: Improve <code class="language-plaintext highlighter-rouge">NavMeshGenerator2D::generator_bake_from_source_geometry_data</code> performance (<a href="https://github.com/godotengine/godot/pull/98957">GH-98957</a>).</li>
|
||
<li>Navigation: Reduce allocations for NavMap synchronisation (<a href="https://github.com/godotengine/godot/pull/98866">GH-98866</a>).</li>
|
||
<li>Network: Split Unix/Windows IP implementation (<a href="https://github.com/godotengine/godot/pull/99026">GH-99026</a>).</li>
|
||
<li>Network: Split Unix/Windows NetSocket implementation (<a href="https://github.com/godotengine/godot/pull/98969">GH-98969</a>).</li>
|
||
<li>Plugin: Make the method selector dialog available via <code class="language-plaintext highlighter-rouge">EditorInterface</code> (<a href="https://github.com/godotengine/godot/pull/98859">GH-98859</a>).</li>
|
||
<li>Rendering: Add <code class="language-plaintext highlighter-rouge">multimesh_get_buffer_rd_rid</code> method to <code class="language-plaintext highlighter-rouge">RenderingServer</code> (<a href="https://github.com/godotengine/godot/pull/98788">GH-98788</a>).</li>
|
||
<li>Rendering: Ensure shadow material and mesh are not used with wireframe mode (<a href="https://github.com/godotengine/godot/pull/98683">GH-98683</a>).</li>
|
||
<li>Rendering: Normalize normal, tangent, and binormal before interpolating in the mobile renderer to avoid precision errors on heavily scaled meshes (<a href="https://github.com/godotengine/godot/pull/99163">GH-99163</a>).</li>
|
||
<li>Rendering: Reduce shader permutations in the compatibility backend (<a href="https://github.com/godotengine/godot/pull/87558">GH-87558</a>).</li>
|
||
<li>Shaders: Add renderer state defines to shader preprocessor (<a href="https://github.com/godotengine/godot/pull/98549">GH-98549</a>).</li>
|
||
<li>Shaders: Add swap connection option to visual shader graph (<a href="https://github.com/godotengine/godot/pull/99177">GH-99177</a>).</li>
|
||
<li>XR: Fix pose recenter signal to be omitted properly (<a href="https://github.com/godotengine/godot/pull/99159">GH-99159</a>).</li>
|
||
</ul>
|
||
<h2 id="changelog">Changelog</h2>
|
||
<p><strong>116 contributors</strong> submitted <strong>265 improvements</strong> for this new snapshot. See our <a href="https://godotengine.github.io/godot-interactive-changelog/#4.4-dev5"><strong>interactive changelog</strong></a> for the complete list of changes since the previous 4.4-dev4 snapshot.</p>
|
||
<p>This release is built from commit <a href="https://github.com/godotengine/godot/commit/9e6098432aac35bae42c9089a29ba2a80320d823"><code class="language-plaintext highlighter-rouge">9e609843</code></a>.</p>
|
||
<h2 id="downloads">Downloads</h2>
|
||
<div class="card card-download">
|
||
<a class="card-download-link" href="/download/archive/4.4-dev5">
|
||
Download Godot 4.4 dev5
|
||
</a>
|
||
<div class="card-download-details">
|
||
<img class="lightbox-ignore" src="/storage/blog/covers/dev-snapshot-godot-4-4-dev-5.webp" />
|
||
<div class="card-download-platforms">
|
||
<div class="download-platform platform-linux">
|
||
<img width="24" height="24" src="/assets/images/platforms/linux.svg" title="Linux" alt="Linux" class="lightbox-ignore" />
|
||
Linux
|
||
</div>
|
||
<a href="https://github.com/godotengine/godot-builds/releases/download/4.4-dev5/Godot_v4.4-dev5_linux.x86_64.zip" class="btn btn-download btn-download-primary platform-linux">
|
||
<div class="download-title">
|
||
Standard
|
||
</div>
|
||
</a>
|
||
<a href="https://github.com/godotengine/godot-builds/releases/download/4.4-dev5/Godot_v4.4-dev5_mono_linux_x86_64.zip" class="btn btn-download btn-download-primary btn-download-primary--mono platform-linux">
|
||
<div class="download-title">
|
||
.NET
|
||
</div>
|
||
</a>
|
||
<div class="download-platform platform-macos">
|
||
<img width="24" height="24" src="/assets/images/platforms/macos.svg" title="macOS" alt="macOS" class="lightbox-ignore" />
|
||
macOS
|
||
</div>
|
||
<a href="https://github.com/godotengine/godot-builds/releases/download/4.4-dev5/Godot_v4.4-dev5_macos.universal.zip" class="btn btn-download btn-download-primary platform-macos">
|
||
<div class="download-title">
|
||
Standard
|
||
</div>
|
||
</a>
|
||
<a href="https://github.com/godotengine/godot-builds/releases/download/4.4-dev5/Godot_v4.4-dev5_mono_macos.universal.zip" class="btn btn-download btn-download-primary btn-download-primary--mono platform-macos">
|
||
<div class="download-title">
|
||
.NET
|
||
</div>
|
||
</a>
|
||
<div class="download-platform platform-windows">
|
||
<img width="24" height="24" src="/assets/images/platforms/windows.svg" title="Windows" alt="Windows" class="lightbox-ignore" />
|
||
Windows
|
||
</div>
|
||
<a href="https://github.com/godotengine/godot-builds/releases/download/4.4-dev5/Godot_v4.4-dev5_win64.exe.zip" class="btn btn-download btn-download-primary platform-windows">
|
||
<div class="download-title">
|
||
Standard
|
||
</div>
|
||
</a>
|
||
<a href="https://github.com/godotengine/godot-builds/releases/download/4.4-dev5/Godot_v4.4-dev5_mono_win64.zip" class="btn btn-download btn-download-primary btn-download-primary--mono platform-windows">
|
||
<div class="download-title">
|
||
.NET
|
||
</div>
|
||
</a>
|
||
</div>
|
||
</div>
|
||
<div class="card-download-sublinks">
|
||
<a class="card-download-other" href="/download/archive/4.4-dev5">
|
||
Export templates and other downloads
|
||
</a>
|
||
<a class="card-download-donate" href="https://fund.godotengine.org/">
|
||
Make a Donation
|
||
</a>
|
||
</div>
|
||
</div>
|
||
<style>
|
||
.thankyou-wrapper {
|
||
position: fixed;
|
||
top: 0;
|
||
left: 0;
|
||
right: 0;
|
||
bottom: 0;
|
||
background: rgba(0, 0, 0, 0.85);
|
||
display: flex;
|
||
flex-direction: column;
|
||
justify-content: center;
|
||
align-items: center;
|
||
z-index: 10;
|
||
}
|
||
.thankyou {
|
||
background: var(--base-color);
|
||
box-shadow: var(--more-shadow);
|
||
padding: 30px;
|
||
display: flex;
|
||
flex-direction: column;
|
||
align-items: center;
|
||
text-align: center;
|
||
position: relative;
|
||
border-radius: 13px;
|
||
}
|
||
.thankyou-reading {
|
||
font-size: 16px;
|
||
}
|
||
.thankyou-reading-list {
|
||
font-size: 16px;
|
||
margin: 0;
|
||
margin-left: 48px;
|
||
padding-left: 0;
|
||
}
|
||
.thankyou-donate {
|
||
margin-bottom: 24px;
|
||
text-align: center;
|
||
}
|
||
.btn.btn-donate {
|
||
background-color: var(--primary-color);
|
||
color: hsla(0, 0%, 100%, 0.9);
|
||
font-size: 22px;
|
||
font-weight: 600;
|
||
margin-bottom: 26px;
|
||
}
|
||
.thankyou h2 {
|
||
text-shadow: var(--base-shadow);
|
||
font-size: 36px;
|
||
font-weight: 800;
|
||
margin-bottom: 12px;
|
||
}
|
||
.thankyou h2 .anchored-link {
|
||
/* Hiding the anchored text automatically added on blogposts */
|
||
display: none !important;
|
||
}
|
||
.thankyou p {
|
||
max-width: 620px;
|
||
font-size: 25px;
|
||
}
|
||
@media (max-width: 768px) {
|
||
.thankyou-wrapper {
|
||
display: block;
|
||
}
|
||
.thankyou {
|
||
position: absolute;
|
||
top: 0;
|
||
left: 0;
|
||
right: 0;
|
||
bottom: 0;
|
||
overflow: scroll;
|
||
padding: 30px 40px 18px 40px;
|
||
}
|
||
.thankyou-reading-list {
|
||
margin-left: 24px;
|
||
}
|
||
.btn-close-thankyou-popup {
|
||
width: 48px;
|
||
height: 48px;
|
||
display: flex;
|
||
justify-content: center;
|
||
align-items: center;
|
||
}
|
||
}
|
||
.btn-close-thankyou-popup {
|
||
cursor: pointer;
|
||
position: absolute;
|
||
top: 12px;
|
||
right: 12px;
|
||
}
|
||
.btn-close-thankyou-popup img {
|
||
background: transparent !important; /* for overwriting the style in the blogposts img */
|
||
}
|
||
@media (prefers-color-scheme: light) {
|
||
.btn-close-thankyou-popup img {
|
||
filter: invert(1);
|
||
opacity: 0.75;
|
||
}
|
||
}
|
||
</style>
|
||
<script>
|
||
document.addEventListener('DOMContentLoaded', () => {
|
||
const thankYouWrapper = document.getElementById('thank-you');
|
||
// Close itself, when clicked outside of the popup area.
|
||
thankYouWrapper.addEventListener('click', (e) => {
|
||
if (e.target === thankYouWrapper) {
|
||
thankYouWrapper.style.display = 'none';
|
||
}
|
||
});
|
||
// Close with a close button.
|
||
const thankYouBackButton = document.querySelector('.btn-close-thankyou-popup');
|
||
thankYouBackButton.addEventListener('click', () => {
|
||
thankYouWrapper.style.display = 'none';
|
||
});
|
||
// Open from the main download buttons.
|
||
const downloadButtons = document.querySelectorAll('.btn-download');
|
||
downloadButtons.forEach((it) => {
|
||
it.addEventListener('click', () => {
|
||
thankYouWrapper.style.display = '';
|
||
document.querySelector('.btn.btn-donate').focus();
|
||
});
|
||
});
|
||
// Open from the all downloads list.
|
||
const downloadLinks = document.querySelectorAll('.download-link');
|
||
downloadLinks.forEach((it) => {
|
||
it.addEventListener('click', () => {
|
||
thankYouWrapper.style.display = '';
|
||
});
|
||
});
|
||
// Close the dialog when the user presses the escape key.
|
||
document.addEventListener('keydown', (e) => {
|
||
if (e.key === 'Escape') {
|
||
thankYouWrapper.style.display = 'none';
|
||
}
|
||
});
|
||
});
|
||
</script>
|
||
<div class="thankyou-wrapper" id="thank-you" style="display: none;">
|
||
<div class="thankyou">
|
||
<h2>Godot is downloading...</h2>
|
||
<p class="thankyou-donate">
|
||
Godot exists thanks to donations from people like you. Help us continue our work:
|
||
</p>
|
||
<a href="https://fund.godotengine.org" class="btn btn-donate">
|
||
Make a Donation
|
||
</a>
|
||
<div class="btn-close-thankyou-popup">
|
||
<img src="/assets/icons/cross.svg" width="24" height="24" alt="Close this popup" class="lightbox-ignore" />
|
||
</div>
|
||
</div>
|
||
</div>
|
||
<p><strong>Standard build</strong> includes support for GDScript and GDExtension.</p>
|
||
<p><strong>.NET build</strong> (marked as <code class="language-plaintext highlighter-rouge">mono</code>) includes support for C#, as well as GDScript and GDExtension.</p>
|
||
<ul>
|
||
<li>See also <a href="https://docs.godotengine.org/en/latest/tutorials/scripting/c_sharp/index.html#c-platform-support">C# platform support</a>.</li>
|
||
</ul>
|
||
<div class="card card-warning">
|
||
<p>
|
||
While engine maintainers try their best to ensure that each preview snapshot and release candidate is stable, this is by definition <strong>a pre-release piece of software</strong>. Be sure to make frequent backups, or use a version control system such as Git, to preserve your projects in case of corruption or data loss.
|
||
</p>
|
||
</div>
|
||
<h2 id="known-issues">Known issues</h2>
|
||
<p>With every release we accept that there are going to be various issues, which have already been reported but haven’t been fixed yet. See the GitHub issue tracker for a complete list of <a href="https://github.com/godotengine/godot/issues?q=is%3Aissue+is%3Aopen+label%3Abug+">known bugs</a>.</p>
|
||
<h2 id="bug-reports">Bug reports</h2>
|
||
<p>As a tester, we encourage you to <a href="https://github.com/godotengine/godot/issues">open bug reports</a> if you experience issues with this release. Please check the <a href="https://github.com/godotengine/godot/issues">existing issues on GitHub</a> first, using the search function with relevant keywords, to ensure that the bug you experience is not already known.</p>
|
||
<p>In particular, any change that would cause a regression in your projects is very important to report (e.g. if something that worked fine in previous 4.x releases, but no longer works in this snapshot).</p>
|
||
<h2 id="support">Support</h2>
|
||
<p>Godot is a non-profit, open source game engine developed by hundreds of contributors on their free time, as well as a handful of part or full-time developers hired thanks to <a href="https://fund.godotengine.org/">generous donations from the Godot community</a>. A big thank you to everyone who has contributed <a href="https://github.com/godotengine/godot/blob/master/AUTHORS.md">their time</a> or <a href="https://github.com/godotengine/godot/blob/master/DONORS.md">their financial support</a> to the project!</p>
|
||
<p>If you’d like to support the project financially and help us secure our future hires, you can do so using the <a href="https://fund.godotengine.org/">Godot Development Fund</a> platform managed by <a href="https://godot.foundation/">Godot Foundation</a>. There are also several <a href="/donate">alternative ways to donate</a> which you may find more suitable.</p></description><category>Pre-release</category><guid>https://godotengine.org/article/dev-snapshot-godot-4-4-dev-5/</guid><dc:creator>Thaddeus Crews</dc:creator><pubDate>Thu, 21 Nov 2024 18:00:00 +0000</pubDate><image>https://godotengine.org/storage/blog/covers/dev-snapshot-godot-4-4-dev-5.webp</image></item><item><title>GodotCon 24: Berlin Edition</title><link>https://godotengine.org/article/review-godotcon24/</link><summary>Our biggest conference yet!</summary><description><p><br />
|
||
📋 <a href="https://forms.gle/3tALsQid32qqvu2Z8">Feedback form for visitors</a>
|
||
🎤 <a href="https://www.youtube.com/playlist?list=PLeG_dAglpVo6TS0q858NajyeglRuvb7hs">Talk &amp; workshop recordings</a>
|
||
🫙 <a href="https://godotcon.itch.io/">Jam games</a></p>
|
||
<hr />
|
||
<p>Variety was the name of the game this year. GodotCon keeps going around the globe and adds more activities to the program: the event team made up of volunteers and Godot Foundation staff put a lot work into making this more than a mere meetup occasion for the ever-growing community forming around the Godot Engine.</p>
|
||
<p>Judging by the smiley pictures taken all around the <a href="https://www.silent-green.net/">Silent Green</a> venue, and the excited chatter about what the next installments might bring to the table, we seem to have hit the sweet spot for our 574 attendees. For those of you that couldn’t be there yourself - considering both ticket batches sold out within an hour - join us on a retrospective walk through GodotCon, highlighting all the wonderful speakers, exhibitors, and sponsors that made this event possible.</p>
|
||
<h1 id="sponsor-support">Sponsor support</h1>
|
||
<p>GodotCon 2024 wouldn’t have been possible without the generosity of <a href="https://conference.godotengine.org/2024/#sponsors">our sponsors</a>, who enabled us to bring this event to life.</p>
|
||
<h2 id="critical-reflex">Critical Reflex</h2>
|
||
<p>Having a publisher with experience in Godot on-board was as exciting for us as it seemed for the audience of “Indie Publishing 101” by their business developer Daniel. Additionally, you might have spotted the goodie bags they provided us.</p>
|
||
<p>🔗 <a href="https://criticalreflex.com">criticalreflex.com</a></p>
|
||
<p><img alt="Venue picture featuring Critical Reflex goodie bag" src="/storage/blog/godotcon24/goodie-bag.webp" /></p>
|
||
<h2 id="endless-foundation">Endless Foundation</h2>
|
||
<p>“Block Coding: Making Godot Accessible to Learners Everywhere” was another well-visited talk on the agenda, as was the booth of the biggest exhibitor team onsite. Their tech demonstration drew in fellow educators as well as curious game developers looking to contribute.</p>
|
||
<p>🔗 <a href="https://www.endlessos.org/">endlessos.org</a></p>
|
||
<p><img alt="Screenshot of their block coding editor" src="/storage/blog/godotcon24/block-coding.webp" /></p>
|
||
<h2 id="w4-games">W4 Games</h2>
|
||
<p>Port your Godot games to console with ease! The company founded by Godot Engine veterans explained “W4’s role in the Godot Ecosystem” on stage and let you playtest their products and talk business at their busy booth.</p>
|
||
<p>🔗 <a href="https://w4games.com">w4games.com</a></p>
|
||
<p><img alt="Juan giving a presentation about W4 Games on stage" src="/storage/blog/godotcon24/w4-games.webp" /></p>
|
||
<h2 id="poki">Poki</h2>
|
||
<p>The provider of free online games also has shown interest in Godot before and is hoping to expand their selection with your projects. We talked with them about improving Godot for the Web together; let’s see what the future might bring!</p>
|
||
<p>🔗 <a href="https://poki.com">poki.com</a></p>
|
||
<p><img alt="Photo of the Poki booth with two of the representatives smiling and giving a thumbs up" src="/storage/blog/godotcon24/poki.webp" /></p>
|
||
<h2 id="aws">AWS</h2>
|
||
<p>After demonstrating “How to quick start a Godot Engine game on AWS”, the cloud provider team spent time answering questions on the exhibition floor.</p>
|
||
<p>🔗 <a href="https://aws.amazon.com/gametech/">aws.amazon.com</a></p>
|
||
<p><img alt="The AWS team presenting at the main stage." src="/storage/blog/godotcon24/aws.webp" /></p>
|
||
<hr />
|
||
<p>If you or your company are interested in supporting the next edition of GodotCon, we’d love to hear from you! <br />Please reach out to us at <a href="mailto:godotcon@godotengine.org">godotcon@godotengine.org</a>.</p>
|
||
<hr />
|
||
<h1 id="game-exhibition">Game exhibition</h1>
|
||
<p>For the first time ever, we tried curating a selection of projects ahead of time and invited game development teams to a showcase on the venue floors. Decorated booths and sometimes even goodies caught the eyes of many attendees, and provided the exhibitors with valuable playtest information as well as wishlists. Some told us this was the first event they participated in with their project!</p>
|
||
<div class="preview-image-container">
|
||
<img alt="Bug Off booth" src="/storage/blog/godotcon24/bug-off.webp" />
|
||
<img alt="Data Garden booth" src="/storage/blog/godotcon24/data-garden.webp" />
|
||
<img alt="Dung Slinger booth" src="/storage/blog/godotcon24/dung-slinger.webp" />
|
||
<img alt="Fogpiercer booth" src="/storage/blog/godotcon24/fog-piercer.webp" />
|
||
<img alt="Immersive Home booth" src="/storage/blog/godotcon24/immersive-home.webp" />
|
||
<img alt="In Good Faith booth" src="/storage/blog/godotcon24/in-good-faith.webp" />
|
||
</div>
|
||
<div class="preview-image-container">
|
||
<img alt="Keep The Heroes Out booth" src="/storage/blog/godotcon24/keep-out.webp" />
|
||
<img alt="Looking Up I See Only A Ceiling booth" src="/storage/blog/godotcon24/looking-up.webp" />
|
||
<img alt="PVKK: Planetenverteidigungskanonenkommandant booth" src="/storage/blog/godotcon24/pvkk.webp" />
|
||
<img alt="Robot Detour booth" src="/storage/blog/godotcon24/robot-detour.webp" />
|
||
<img alt="Voice of Flowers booth" src="/storage/blog/godotcon24/voice-of-flowers.webp" />
|
||
<img alt="Window Arcade booth" src="/storage/blog/godotcon24/window-arcade.webp" />
|
||
</div>
|
||
<p><strong>Exhibitor list:</strong></p>
|
||
<ul>
|
||
<li><a href="https://curio-compass-games.itch.io/bug-off">Bug Off</a></li>
|
||
<li><a href="https://store.steampowered.com/app/2644670/Data_Garden/">Data Garden</a></li>
|
||
<li><a href="https://s4g.itch.io/dung-slinger">Dung Slinger</a></li>
|
||
<li><a href="https://store.steampowered.com/app/3219010/Fogpiercer/">Fogpiercer</a></li>
|
||
<li><a href="https://immersive-home.org/">Immersive Home</a></li>
|
||
<li><a href="https://store.steampowered.com/app/3151800/In_Good_Faith/">In Good Faith</a></li>
|
||
<li><a href="https://store.steampowered.com/app/2592340/Keep_the_Heroes_Out/">Keep The Heroes Out</a></li>
|
||
<li><a href="https://store.steampowered.com/app/1742930/Looking_Up_I_See_Only_A_Ceiling/">Looking Up I See Only A Ceiling</a></li>
|
||
<li><a href="https://store.steampowered.com/app/2956040/PVKK_Planetenverteidigungskanonenkommandant/">PVKK: Planetenverteidigungskanonenkommandant</a></li>
|
||
<li><a href="https://store.steampowered.com/app/2666840/Robot_Detour/">Robot Detour</a></li>
|
||
<li><a href="https://schwarzeralptraum.itch.io/skyes-ducky-adventure-quest-for-gluttony">Skye’s Ducky Adventure: Quest for Gluttony</a></li>
|
||
<li><a href="https://store.steampowered.com/app/2609560/Voice_of_Flowers/">Voice of Flowers</a></li>
|
||
<li><a href="https://windowarcade.com">Window Arcade</a></li>
|
||
</ul>
|
||
<h1 id="activities">Activities</h1>
|
||
<p><img alt="The graffiti canvas full of different drawings by the visitors" src="/storage/blog/godotcon24/canvas.webp" /></p>
|
||
<p>What do you do at a conference, besides watching talks, browsing through the exhibition, or doing business? Have some fun and get to know other attendees in a casual way, of course.</p>
|
||
<p>This is exactly what we aimed to facilitate with our onsite activities, especially the <a href="https://conference.godotengine.org/2024/activities/">sticker challenge</a> tying them all together (since many of you asked: the stickers were designed by community artist <a href="https://gotibo.fr/">Tibo</a>). From networking bingo to graffiti canvas, we saw many people striking up conversations with strangers or having a great time with friends.</p>
|
||
<p><img alt="People participating in a game jam" src="/storage/blog/godotcon24/one-pc-jam.webp" /></p>
|
||
<p>One of the most popular activities turned out to be the One PC Jam (taking place at three laptops concurrently) where the conference attendees created a jam game over the course of two days. The twist: everyone only was granted one hour on the project, before having to concede their seat to the next person. This resulted in three separate, actually playable games, which you can <a href="https://godotcon.itch.io/">find on our GodotCon itch.io site</a>.</p>
|
||
<h1 id="talks-and-workshops">Talks and workshops</h1>
|
||
<p><img alt="View of the stage, with people standing behind full rows of chairs." src="/storage/blog/godotcon24/backstage.webp" /></p>
|
||
<p>The Godot community once again came through and submitted more interesting talks than we could fit on the program - resulting in us repurposing the admittedly rather small workshop room to squeeze some more of the talented speakers in. Luckily, we also invited a camera crew onsite, that took great care recording both the workshops and two talk tracks, for you to enjoy on the Godot Engine YouTube channel - some of them already available, the rest being edited as you read this blog post.</p>
|
||
<p><span style="font-size: 1.5em">
|
||
🔗 <a href="https://www.youtube.com/playlist?list=PLeG_dAglpVo6TS0q858NajyeglRuvb7hs">YouTube Playlist</a>
|
||
</span></p>
|
||
<h1 id="feedback">Feedback</h1>
|
||
<p>Considering the new additions we introduced to the event concept, and to learn from your experiences as visitors in general, we would appreciate it if you took the time to fill out this <a href="https://forms.gle/3tALsQid32qqvu2Z8">feedback survey</a> we prepared. It should only take a few minutes.</p>
|
||
<h1 id="thank-you">Thank you!</h1>
|
||
<p>And that concludes our tour through GodotCon 24. Hope you had fun reminiscing with us!</p>
|
||
<p>If you want to be notified about our next one, sign up to our mailing list and be the first to know:</p>
|
||
<form method="post" action="https://godot.news/subscription/form" class="listmonk-form">
|
||
<div>
|
||
<input type="hidden" name="nonce" />
|
||
<input type="email" name="email" required="" placeholder="E-mail" style="font-size: 18px;padding: 16px 18px;border: 1px solid var(--base-color);box-shadow: 0 4px 9px -3px #0000002e;background: var(--card-footer-color);color: var(--base-color-text);" />
|
||
<p style="display:none;">
|
||
<input id="6e6e9" type="checkbox" name="l" checked="" value="6e6e9ba4-732b-4528-b4cd-71bbe6850f8d" />
|
||
<label for="6e6e9">Godot Conference</label>
|
||
</p>
|
||
<input type="submit" class="btn" value="Subscribe" style="cursor: pointer;border: inherit; border-radius: 0;
|
||
box-shadow: none;
|
||
height: 54px;" />
|
||
</div>
|
||
</form>
|
||
<p>🌐 <a href="https://conference.godotengine.org/">https://conference.godotengine.org/</a></p>
|
||
<h3 id="-see-you-next-year">👋 See you next year!</h3>
|
||
<style>
|
||
.preview-image-container {
|
||
display: flex;
|
||
justify-content: center;
|
||
align-items: center;
|
||
gap: 5px;
|
||
/* padding: 16px; */
|
||
background-color: transparent;
|
||
}
|
||
.preview-image-container {
|
||
background-color: transparent;
|
||
}
|
||
.preview-image-container img {
|
||
max-height: 300px;
|
||
background-color: transparent;
|
||
}
|
||
</style></description><category>Events</category><guid>https://godotengine.org/article/review-godotcon24/</guid><dc:creator>Nat</dc:creator><pubDate>Wed, 13 Nov 2024 18:30:00 +0000</pubDate><image>https://godotengine.org/storage/blog/covers/godotcon-2024-post.webp</image></item><item><title>Dev snapshot: Godot 4.4 dev 4</title><link>https://godotengine.org/article/dev-snapshot-godot-4-4-dev-4/</link><summary>After a short delay due to GodotCon, we are back with another exciting update.</summary><description><p>We are back roughly a month after the release of dev3 to bring you a host of new improvements. Many of our developers
|
||
traveled to Germany in October for GodotCon and the yearly Godot contributor meeting. There they spent two days
|
||
discussing some of the biggest technical challenges and puzzling out solutions.</p>
|
||
<p>Many of the changes in this release are bug fixes that will be backported to Godot 4.3 and released in 4.3.1! So please
|
||
test this release well so we can be confident with the changes and release 4.3.1 with them as soon as possible.</p>
|
||
<p>Keep in mind that while we try to make sure each dev snapshot is stable enough for general testing, this is by
|
||
definition a pre-release piece of software. Be sure to make frequent backups, or use a version control system such as
|
||
Git, to preserve your projects in case of corruption or data loss.</p>
|
||
<p><a href="#downloads">Jump to the <strong>Downloads</strong> section</a>, and give it a spin right now, or continue reading to learn more about improvements in this release. You can also try the <a href="https://editor.godotengine.org/releases/4.4.dev4/"><strong>Web editor</strong></a>, <a href="https://www.meta.com/experiences/godot-game-engine/7713660705416473/"><strong>XR editor</strong></a>, or the <strong>Android editor</strong> for this release (join the <a href="https://groups.google.com/g/godot-testers">Android editor testing group</a> to get access to pre-release builds).</p>
|
||
<hr />
|
||
<p><em>The cover illustration is from</em> <a href="https://store.steampowered.com/app/2211170/Unrailed_2_Back_on_Track/"><strong>Unrailed 2: Back on Track</strong></a>, <em>a chaotic co-op railroad construction game where you build your track across procedurally generated worlds! It is developed by <a href="https://indoorastronaut.ch/">Indoor Astronaut</a>. You can purchase the game in early access <a href="https://store.steampowered.com/app/2211170/Unrailed_2_Back_on_Track/">on Steam</a> and follow the developer on <a href="https://x.com/IndoorAstronaut">Twitter</a>.</em></p>
|
||
<h2 id="highlights">Highlights</h2>
|
||
<p>In case you missed them, see the <a href="/article/dev-snapshot-godot-4-4-dev-1/">4.4 dev 1</a>, <a href="/article/dev-snapshot-godot-4-4-dev-2/">dev2</a>,
|
||
and <a href="/article/dev-snapshot-godot-4-4-dev-3/">dev 3</a> release notes for an overview of some key features which were
|
||
already in that snapshot, and are therefore still available for testing in dev 3.</p>
|
||
<p>Here are a few highlights that you might find particularly exciting!</p>
|
||
<h3 id="interactive-in-game-editing">Interactive in-game editing</h3>
|
||
<p>One of the most requested features is the ability to debug the running game from within the editor including pausing the
|
||
game, clicking on elements within the scene, and embedding the running game window inside the editor. Dev4 comes with
|
||
the first two of these workflows thanks to the contribution from <a href="https://github.com/YeldhamDev">YeldhamDev</a> of Lone Wolf
|
||
Technology &amp; W4 Games, users are now able to explore their project’s world freely!</p>
|
||
<p>The actual embedding of the game window into the editor will come later in a subsequent PR.</p>
|
||
<p>Check out the PR (<a href="https://github.com/godotengine/godot/pull/97257">GH-97257</a>) and the video below to see exactly what
|
||
this change enables.</p>
|
||
<video autoplay="" loop="" muted="" playsinline="">
|
||
<source src="/storage/blog/dev-snapshot-godot-4-4-dev-4/game-editor-debug.mp4?1" type="video/mp4" />
|
||
</video>
|
||
<h3 id="use-collision-detection-ray-to-reposition-an-object-already-in-the-scene">Use collision detection ray to reposition an object already in the scene</h3>
|
||
<p><a href="https://github.com/ryevdokimov">ryevdokimov</a> added object snapping for placing 3D objects in the editor (<a href="https://github.com/godotengine/godot/pull/96740">GH-96740</a>).</p>
|
||
<p>This is not a drill, see below.</p>
|
||
<video autoplay="" loop="" muted="" playsinline="">
|
||
<source src="/storage/blog/dev-snapshot-godot-4-4-dev-4/physics-placement.mp4?1" type="video/mp4" />
|
||
</video>
|
||
<h3 id="ubershaders-and-pipeline-pre-compilation-and-dedicated-transfer-queues">Ubershaders and pipeline pre-compilation (and dedicated transfer queues)</h3>
|
||
<p>This change combines 2 huge improvements (<a href="https://github.com/godotengine/godot/pull/90400">GH-90400</a>):</p>
|
||
<ol>
|
||
<li>Ubershaders: a technique that allows us to completely avoid shader stutter when objects are viewed in a scene for the first time</li>
|
||
<li>Dedicated transfer queues: by relying on special hardware functions we can dramatically improve the load time for scenes containing many graphics assets like meshes and textures.</li>
|
||
</ol>
|
||
<p>Thanks to <a href="https://github.com/dariosamo">DarioSamo</a> for months of hard work on this. The implementation of Ubershaders
|
||
is something that took a lot of design and implementation to get right, but the end result is something we are very
|
||
happy with.</p>
|
||
<p>“Ubershaders” are a version of each shader that contains all features and are compiled at load time. We pair the
|
||
ubershader with the ability to compile specialized shader pipelines in the background. This way when we draw a new
|
||
object, instead of freezing and waiting for the pipeline to compile, we fallback on the ubershader and compile the
|
||
specialized shader in the background.</p>
|
||
<p>Most games will notice the improvement from ubershaders without any content changes. However, there are certain cases
|
||
where the ubershader won’t work and some content changes will be needed to avoid shader stutter. However, the
|
||
workarounds for avoiding shader stutter are now very simple and are well documented already in the <a href="https://docs.godotengine.org/en/latest/tutorials/performance/pipeline_compilations.html">official docs</a>.</p>
|
||
<p>Taking advantage of the new ubershader infrastructure, we can now optimize our shaders by creating specialized variants
|
||
that skip unused pathways. We have already begin doing so to optimize our existing shaders
|
||
(<a href="https://github.com/godotengine/godot/pull/98825">GH-98825</a>).</p>
|
||
<h3 id="add-shadow-caster-mask-property-to-light3d">Add Shadow Caster Mask property to Light3D</h3>
|
||
<p>This long awaited improvement from <a href="https://github.com/EMBYRDEV">EMBYRDEV</a> allows users to apply a mask on Light3Ds to
|
||
select what rendering layers will be considered when casting shadows
|
||
(<a href="https://github.com/godotengine/godot/pull/85338">GH-85338</a>). Previously it was only possible to disable shadows from a
|
||
GeometryInstance (for all Light3Ds) or a Light3D (for all GeometryInstances). This allows much more fine-grained control
|
||
that allows users to further optimize dynamic lights and control where shadows appear in their games.</p>
|
||
<h3 id="always-add-decimal-when-converting-float-to-string">Always add decimal when converting float to string</h3>
|
||
<p>Currently when printing float values Godot trims trailing <code class="language-plaintext highlighter-rouge">.0</code>s as they are technically unnecessary. However, this could
|
||
lead to issues for users who need to distinguish between floating point numbers and integers.
|
||
<a href="https://github.com/kobewi">KoBeWi</a> has now changed the behavior when floats are converted to strings to always add the decimal number, even if it would be <code class="language-plaintext highlighter-rouge">.0</code>.
|
||
This makes floats always recognizable when they are converted to strings (<a href="https://github.com/godotengine/godot/pull/47502">GH-47502</a>).</p>
|
||
<p>This change in behavior may break your project if you are relying on the current serialization behavior. If this change
|
||
breaks your project, please let us know by opening an issue on GitHub.</p>
|
||
<div class="language-gdscript highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="c1"># Before:</span>
|
||
<span class="k">var</span> <span class="n">a</span><span class="p">:</span> <span class="kt">float</span> <span class="o">=</span> <span class="mf">1.0</span>
|
||
<span class="nb">print</span><span class="p">(</span><span class="n">a</span><span class="p">)</span>
|
||
<span class="c1"># Prints 1</span>
|
||
</code></pre></div></div>
|
||
<div class="language-gdscript highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="c1"># After:</span>
|
||
<span class="k">var</span> <span class="n">a</span><span class="p">:</span> <span class="kt">float</span> <span class="o">=</span> <span class="mf">1.0</span>
|
||
<span class="nb">print</span><span class="p">(</span><span class="n">a</span><span class="p">)</span>
|
||
<span class="c1"># Prints 1.0</span>
|
||
</code></pre></div></div>
|
||
<h3 id="and-more">And more!</h3>
|
||
<p>There are too many exciting changes to list them all here, but here’s a curated selection:</p>
|
||
<ul>
|
||
<li>2D: Revert unintentional rounding change when 2D transform snapping (<a href="https://github.com/godotengine/godot/pull/98195">GH-98195</a>).</li>
|
||
<li>Animation: Fix error when stopping empty animation player (<a href="https://github.com/godotengine/godot/pull/97760">GH-97760</a>).</li>
|
||
<li>Audio: Expose some AudioStreamPlayback methods (namely mix_audio()) (<a href="https://github.com/godotengine/godot/pull/86539">GH-86539</a>).</li>
|
||
<li>Buildsystem: CI: Add MinGW/GCC build to Windows GHA (<a href="https://github.com/godotengine/godot/pull/97446">GH-97446</a>).</li>
|
||
<li>Core: Implement array based hash map AHashMap (<a href="https://github.com/godotengine/godot/pull/92554">GH-92554</a>).</li>
|
||
<li>Core: Expose <code class="language-plaintext highlighter-rouge">Geometry2D.bresenham_line()</code> method (<a href="https://github.com/godotengine/godot/pull/74714">GH-74714</a>).</li>
|
||
<li>Core: Add Object support for String.format (<a href="https://github.com/godotengine/godot/pull/65962">GH-65962</a>).</li>
|
||
<li>Dotnet: Change generated <code class="language-plaintext highlighter-rouge">On{SignalName}</code> to <code class="language-plaintext highlighter-rouge">EmitSignal{SignalName}</code> (<a href="https://github.com/godotengine/godot/pull/97588">GH-97588</a>).</li>
|
||
<li>Dotnet: Generate <code class="language-plaintext highlighter-rouge">ReadOnlySpan&lt;T&gt;</code> Overloads for GodotSharp APIs (<a href="https://github.com/godotengine/godot/pull/96329">GH-96329</a>).</li>
|
||
<li>Editor: Improve UI of sun angle in the sun/preview env popup (<a href="https://github.com/godotengine/godot/pull/97747">GH-97747</a>).</li>
|
||
<li>Editor: Add submenu support to EditorContextMenuPlugin (<a href="https://github.com/godotengine/godot/pull/97292">GH-97292</a>).</li>
|
||
<li>Editor: Improve display for lightmap probes in the editor (<a href="https://github.com/godotengine/godot/pull/83863">GH-83863</a>).</li>
|
||
<li>Editor: Add missing audio bus button styles #(<a href="https://github.com/godotengine/godot/pull/93443">GH-93443</a>).</li>
|
||
<li>Editor: Add Markdown syntax highlighting to the script editor (<a href="https://github.com/godotengine/godot/pull/78312">GH-78312</a>).</li>
|
||
<li>GDExtension: Fix loss of gdextension on editor startup (<a href="https://github.com/godotengine/godot/pull/98041">GH-98041</a>).</li>
|
||
<li>GDScript: GDScript: Fix cached parser error when using typed Dictionaries (<a href="https://github.com/godotengine/godot/pull/98400">GH-98400</a>).</li>
|
||
<li>GDScript: GDScript: Fix annotation parsing adding new annotation entries (<a href="https://github.com/godotengine/godot/pull/98146">GH-98146</a>).</li>
|
||
<li>GUI: Add hover state to Tree items display (<a href="https://github.com/godotengine/godot/pull/88530">GH-88530</a>).</li>
|
||
<li>GUI: Handle scroll events in RichtTextLabel (<a href="https://github.com/godotengine/godot/pull/97730">GH-97730</a>).</li>
|
||
<li>Import: Rewrite index optimization code for maximum efficiency (<a href="https://github.com/godotengine/godot/pull/98801">GH-98801</a>).</li>
|
||
<li>Import: LOD: Remove “Raycast Normals” and associated “Normal Split Angle” settings (<a href="https://github.com/godotengine/godot/pull/98620">GH-98620</a>).</li>
|
||
<li>Import: Betsy: Implement BC4 compression (<a href="https://github.com/godotengine/godot/pull/97295">GH-97295</a>).</li>
|
||
<li>Import: Emit filesystem_changed only once per frame (<a href="https://github.com/godotengine/godot/pull/98584">GH-98584</a>).</li>
|
||
<li>Navigation: Optimize some parts of NavMap::sync (<a href="https://github.com/godotengine/godot/pull/90182">GH-90182</a>).</li>
|
||
<li>Porting: Implement native file picker support for Android (<a href="https://github.com/godotengine/godot/pull/98350">GH-98350</a>).</li>
|
||
<li>Porting: Implement has_hardware_keyboard method for Android and iOS (<a href="https://github.com/godotengine/godot/pull/97743">GH-97743</a>).</li>
|
||
<li>Rendering: Fix various issues and minor performance optimisations in 2D renderer (<a href="https://github.com/godotengine/godot/pull/98652">GH-98652</a>).</li>
|
||
<li>Rendering: Fix volumetric fog artifacts when inside the fog (<a href="https://github.com/godotengine/godot/pull/86103">GH-86103</a>).</li>
|
||
<li>Rendering: Fix updating dynamic objects in LightmapGI (<a href="https://github.com/godotengine/godot/pull/97925">GH-97925</a>).</li>
|
||
<li>Rendering: Add draw indirect to Rendering Device (<a href="https://github.com/godotengine/godot/pull/97247">GH-97247</a>).</li>
|
||
<li>Rendering: Add Swappy &amp; Pre-Transformed Swapchain (<a href="https://github.com/godotengine/godot/pull/96439">GH-96439</a>).</li>
|
||
<li>Shaders: Implement instance uniforms in Compatibility renderer (<a href="https://github.com/godotengine/godot/pull/96819">GH-96819</a>).</li>
|
||
<li>Shaders: Implement custom function overloading in shading language (<a href="https://github.com/godotengine/godot/pull/92441">GH-92441</a>).</li>
|
||
<li>XR: OpenXR: change bindings to ‘flatten’ source paths (<a href="https://github.com/godotengine/godot/pull/98163">GH-98163</a>).</li>
|
||
<li>XR: Add support for external camera feed from external plugin on Android (<a href="https://github.com/godotengine/godot/pull/96705">GH-96705</a>).</li>
|
||
</ul>
|
||
<h2 id="changelog">Changelog</h2>
|
||
<p><strong>131 contributors</strong> submitted <strong>339 improvements</strong> for this new snapshot. See our <a href="https://godotengine.github.io/godot-interactive-changelog/#4.4-dev4"><strong>interactive changelog</strong></a> for the complete list of changes since the previous 4.4-dev3 snapshot.</p>
|
||
<p>This release is built from commit <a href="https://github.com/godotengine/godot/commit/36e6207bb48fafd43b98a458d0c461ad982b4e68"><code class="language-plaintext highlighter-rouge">36e6207bb</code></a>.</p>
|
||
<h2 id="downloads">Downloads</h2>
|
||
<div class="card card-download">
|
||
<a class="card-download-link" href="/download/archive/4.4-dev4">
|
||
Download Godot 4.4 dev4
|
||
</a>
|
||
<div class="card-download-details">
|
||
<img class="lightbox-ignore" src="/storage/blog/covers/dev-snapshot-godot-4-4-dev-4.webp" />
|
||
<div class="card-download-platforms">
|
||
<div class="download-platform platform-linux">
|
||
<img width="24" height="24" src="/assets/images/platforms/linux.svg" title="Linux" alt="Linux" class="lightbox-ignore" />
|
||
Linux
|
||
</div>
|
||
<a href="https://github.com/godotengine/godot-builds/releases/download/4.4-dev4/Godot_v4.4-dev4_linux.x86_64.zip" class="btn btn-download btn-download-primary platform-linux">
|
||
<div class="download-title">
|
||
Standard
|
||
</div>
|
||
</a>
|
||
<a href="https://github.com/godotengine/godot-builds/releases/download/4.4-dev4/Godot_v4.4-dev4_mono_linux_x86_64.zip" class="btn btn-download btn-download-primary btn-download-primary--mono platform-linux">
|
||
<div class="download-title">
|
||
.NET
|
||
</div>
|
||
</a>
|
||
<div class="download-platform platform-macos">
|
||
<img width="24" height="24" src="/assets/images/platforms/macos.svg" title="macOS" alt="macOS" class="lightbox-ignore" />
|
||
macOS
|
||
</div>
|
||
<a href="https://github.com/godotengine/godot-builds/releases/download/4.4-dev4/Godot_v4.4-dev4_macos.universal.zip" class="btn btn-download btn-download-primary platform-macos">
|
||
<div class="download-title">
|
||
Standard
|
||
</div>
|
||
</a>
|
||
<a href="https://github.com/godotengine/godot-builds/releases/download/4.4-dev4/Godot_v4.4-dev4_mono_macos.universal.zip" class="btn btn-download btn-download-primary btn-download-primary--mono platform-macos">
|
||
<div class="download-title">
|
||
.NET
|
||
</div>
|
||
</a>
|
||
<div class="download-platform platform-windows">
|
||
<img width="24" height="24" src="/assets/images/platforms/windows.svg" title="Windows" alt="Windows" class="lightbox-ignore" />
|
||
Windows
|
||
</div>
|
||
<a href="https://github.com/godotengine/godot-builds/releases/download/4.4-dev4/Godot_v4.4-dev4_win64.exe.zip" class="btn btn-download btn-download-primary platform-windows">
|
||
<div class="download-title">
|
||
Standard
|
||
</div>
|
||
</a>
|
||
<a href="https://github.com/godotengine/godot-builds/releases/download/4.4-dev4/Godot_v4.4-dev4_mono_win64.zip" class="btn btn-download btn-download-primary btn-download-primary--mono platform-windows">
|
||
<div class="download-title">
|
||
.NET
|
||
</div>
|
||
</a>
|
||
</div>
|
||
</div>
|
||
<div class="card-download-sublinks">
|
||
<a class="card-download-other" href="/download/archive/4.4-dev4">
|
||
Export templates and other downloads
|
||
</a>
|
||
<a class="card-download-donate" href="https://fund.godotengine.org/">
|
||
Make a Donation
|
||
</a>
|
||
</div>
|
||
</div>
|
||
<style>
|
||
.thankyou-wrapper {
|
||
position: fixed;
|
||
top: 0;
|
||
left: 0;
|
||
right: 0;
|
||
bottom: 0;
|
||
background: rgba(0, 0, 0, 0.85);
|
||
display: flex;
|
||
flex-direction: column;
|
||
justify-content: center;
|
||
align-items: center;
|
||
z-index: 10;
|
||
}
|
||
.thankyou {
|
||
background: var(--base-color);
|
||
box-shadow: var(--more-shadow);
|
||
padding: 30px;
|
||
display: flex;
|
||
flex-direction: column;
|
||
align-items: center;
|
||
text-align: center;
|
||
position: relative;
|
||
border-radius: 13px;
|
||
}
|
||
.thankyou-reading {
|
||
font-size: 16px;
|
||
}
|
||
.thankyou-reading-list {
|
||
font-size: 16px;
|
||
margin: 0;
|
||
margin-left: 48px;
|
||
padding-left: 0;
|
||
}
|
||
.thankyou-donate {
|
||
margin-bottom: 24px;
|
||
text-align: center;
|
||
}
|
||
.btn.btn-donate {
|
||
background-color: var(--primary-color);
|
||
color: hsla(0, 0%, 100%, 0.9);
|
||
font-size: 22px;
|
||
font-weight: 600;
|
||
margin-bottom: 26px;
|
||
}
|
||
.thankyou h2 {
|
||
text-shadow: var(--base-shadow);
|
||
font-size: 36px;
|
||
font-weight: 800;
|
||
margin-bottom: 12px;
|
||
}
|
||
.thankyou h2 .anchored-link {
|
||
/* Hiding the anchored text automatically added on blogposts */
|
||
display: none !important;
|
||
}
|
||
.thankyou p {
|
||
max-width: 620px;
|
||
font-size: 25px;
|
||
}
|
||
@media (max-width: 768px) {
|
||
.thankyou-wrapper {
|
||
display: block;
|
||
}
|
||
.thankyou {
|
||
position: absolute;
|
||
top: 0;
|
||
left: 0;
|
||
right: 0;
|
||
bottom: 0;
|
||
overflow: scroll;
|
||
padding: 30px 40px 18px 40px;
|
||
}
|
||
.thankyou-reading-list {
|
||
margin-left: 24px;
|
||
}
|
||
.btn-close-thankyou-popup {
|
||
width: 48px;
|
||
height: 48px;
|
||
display: flex;
|
||
justify-content: center;
|
||
align-items: center;
|
||
}
|
||
}
|
||
.btn-close-thankyou-popup {
|
||
cursor: pointer;
|
||
position: absolute;
|
||
top: 12px;
|
||
right: 12px;
|
||
}
|
||
.btn-close-thankyou-popup img {
|
||
background: transparent !important; /* for overwriting the style in the blogposts img */
|
||
}
|
||
@media (prefers-color-scheme: light) {
|
||
.btn-close-thankyou-popup img {
|
||
filter: invert(1);
|
||
opacity: 0.75;
|
||
}
|
||
}
|
||
</style>
|
||
<script>
|
||
document.addEventListener('DOMContentLoaded', () => {
|
||
const thankYouWrapper = document.getElementById('thank-you');
|
||
// Close itself, when clicked outside of the popup area.
|
||
thankYouWrapper.addEventListener('click', (e) => {
|
||
if (e.target === thankYouWrapper) {
|
||
thankYouWrapper.style.display = 'none';
|
||
}
|
||
});
|
||
// Close with a close button.
|
||
const thankYouBackButton = document.querySelector('.btn-close-thankyou-popup');
|
||
thankYouBackButton.addEventListener('click', () => {
|
||
thankYouWrapper.style.display = 'none';
|
||
});
|
||
// Open from the main download buttons.
|
||
const downloadButtons = document.querySelectorAll('.btn-download');
|
||
downloadButtons.forEach((it) => {
|
||
it.addEventListener('click', () => {
|
||
thankYouWrapper.style.display = '';
|
||
document.querySelector('.btn.btn-donate').focus();
|
||
});
|
||
});
|
||
// Open from the all downloads list.
|
||
const downloadLinks = document.querySelectorAll('.download-link');
|
||
downloadLinks.forEach((it) => {
|
||
it.addEventListener('click', () => {
|
||
thankYouWrapper.style.display = '';
|
||
});
|
||
});
|
||
// Close the dialog when the user presses the escape key.
|
||
document.addEventListener('keydown', (e) => {
|
||
if (e.key === 'Escape') {
|
||
thankYouWrapper.style.display = 'none';
|
||
}
|
||
});
|
||
});
|
||
</script>
|
||
<div class="thankyou-wrapper" id="thank-you" style="display: none;">
|
||
<div class="thankyou">
|
||
<h2>Godot is downloading...</h2>
|
||
<p class="thankyou-donate">
|
||
Godot exists thanks to donations from people like you. Help us continue our work:
|
||
</p>
|
||
<a href="https://fund.godotengine.org" class="btn btn-donate">
|
||
Make a Donation
|
||
</a>
|
||
<div class="btn-close-thankyou-popup">
|
||
<img src="/assets/icons/cross.svg" width="24" height="24" alt="Close this popup" class="lightbox-ignore" />
|
||
</div>
|
||
</div>
|
||
</div>
|
||
<p><strong>Standard build</strong> includes support for GDScript and GDExtension.</p>
|
||
<p><strong>.NET build</strong> (marked as <code class="language-plaintext highlighter-rouge">mono</code>) includes support for C#, as well as GDScript and GDExtension.</p>
|
||
<ul>
|
||
<li>See also <a href="https://docs.godotengine.org/en/latest/tutorials/scripting/c_sharp/index.html#c-platform-support">C# platform support</a>.</li>
|
||
</ul>
|
||
<div class="card card-warning">
|
||
<p>
|
||
While engine maintainers try their best to ensure that each preview snapshot and release candidate is stable, this is by definition <strong>a pre-release piece of software</strong>. Be sure to make frequent backups, or use a version control system such as Git, to preserve your projects in case of corruption or data loss.
|
||
</p>
|
||
</div>
|
||
<h2 id="known-issues">Known issues</h2>
|
||
<p>With every release we accept that there are going to be various issues, which have already been reported but haven’t been fixed yet. See the GitHub issue tracker for a complete list of <a href="https://github.com/godotengine/godot/issues?q=is%3Aissue+is%3Aopen+label%3Abug+">known bugs</a>.</p>
|
||
<h2 id="bug-reports">Bug reports</h2>
|
||
<p>As a tester, we encourage you to <a href="https://github.com/godotengine/godot/issues">open bug reports</a> if you experience issues with this release. Please check the <a href="https://github.com/godotengine/godot/issues">existing issues on GitHub</a> first, using the search function with relevant keywords, to ensure that the bug you experience is not already known.</p>
|
||
<p>In particular, any change that would cause a regression in your projects is very important to report (e.g. if something that worked fine in previous 4.x releases, but no longer works in this snapshot).</p>
|
||
<h2 id="support">Support</h2>
|
||
<p>Godot is a non-profit, open source game engine developed by hundreds of contributors on their free time, as well as a handful of part or full-time developers hired thanks to <a href="https://fund.godotengine.org/">generous donations from the Godot community</a>. A big thank you to everyone who has contributed <a href="https://github.com/godotengine/godot/blob/master/AUTHORS.md">their time</a> or <a href="https://github.com/godotengine/godot/blob/master/DONORS.md">their financial support</a> to the project!</p>
|
||
<p>If you’d like to support the project financially and help us secure our future hires, you can do so using the <a href="https://fund.godotengine.org/">Godot Development Fund</a> platform managed by <a href="https://godot.foundation/">Godot Foundation</a>. There are also several <a href="/donate">alternative ways to donate</a> which you may find more suitable.</p></description><category>Pre-release</category><guid>https://godotengine.org/article/dev-snapshot-godot-4-4-dev-4/</guid><dc:creator>Clay John</dc:creator><pubDate>Fri, 08 Nov 2024 12:00:00 +0000</pubDate><image>https://godotengine.org/storage/blog/covers/dev-snapshot-godot-4-4-dev-4.webp</image></item><item><title>Dev snapshot: Godot 4.4 dev 3</title><link>https://godotengine.org/article/dev-snapshot-godot-4-4-dev-3/</link><summary>We haven't slowed down and are bringing you another feature-packed update!</summary><description><p>We are back with another big dev update with over 330 commits merged in the last few weeks! Contributors continue to
|
||
work on amazing new things while we continue to merge our backlog of important features that missed the 4.3 cutoff. The
|
||
combined result is a lot of great stuff compressed into a short amount of time.</p>
|
||
<p>Many of the changes in this release are bug fixes that will be backported to Godot 4.3 and released in 4.3.1! So please
|
||
test this release well so we can be confident with the changes and release 4.3.1 with them as soon as possible.</p>
|
||
<p>Keep in mind that while we try to make sure each dev snapshot is stable enough for general testing, this is by
|
||
definition a pre-release piece of software. Be sure to make frequent backups, or use a version control system such as
|
||
Git, to preserve your projects in case of corruption or data loss.</p>
|
||
<p><a href="#downloads">Jump to the <strong>Downloads</strong> section</a>, and give it a spin right now, or continue reading to learn more about improvements in this release. You can also try the <a href="https://editor.godotengine.org/releases/4.4.dev3/"><strong>Web editor</strong></a>, <a href="https://www.meta.com/experiences/godot-game-engine/7713660705416473/"><strong>XR editor</strong></a>, or the <strong>Android editor</strong> for this release (join the <a href="https://groups.google.com/g/godot-testers">Android editor testing group</a> to get access to pre-release builds).</p>
|
||
<hr />
|
||
<p><em>The cover illustration is from</em> <a href="https://store.steampowered.com/app/3219010/Fogpiercer/"><strong>Fogpiercer</strong></a>, <em>a turn-based card battler where your deck is a train! It is developed in Godot 4.3 by <a href="https://x.com/MadCookiesGames">Mad Cookies Studio</a>. You can wishlist the game <a href="https://store.steampowered.com/app/3219010/Fogpiercer/">on Steam</a> and follow the developers on <a href="https://x.com/MadCookiesGames">Twitter</a>.</em></p>
|
||
<h2 id="highlights">Highlights</h2>
|
||
<p>In case you missed them, see the <a href="/article/dev-snapshot-godot-4-4-dev-1/">4.4 dev 1</a> and <a href="/article/dev-snapshot-godot-4-4-dev-2/">dev 2</a> release notes for an overview of some
|
||
key features which were already in that snapshot, and are therefore still available for testing in dev 3.</p>
|
||
<p>Here are a few highlights that you might find particularly exciting!</p>
|
||
<h3 id="export_tool_button-annotation"><code class="language-plaintext highlighter-rouge">@export_tool_button</code> annotation</h3>
|
||
<p>Being able to create a button in the inspector from tool scripts was a highly requested feature, and many contributors
|
||
took it upon themselves to make it happen in <a href="https://github.com/godotengine/godot/pull/96290">GH-96290</a>: new
|
||
contributors <a href="https://github.com/jordi-star">jordi-star</a> and <a href="https://github.com/Macksaur">Macksaur</a>, and maintainers
|
||
<a href="https://github.com/fire">Ernest</a> and <a href="https://github.com/dalexeev">Danil</a>!</p>
|
||
<p>This new feature allows you to be even more expressive with the dev tooling that you can easily create with <code class="language-plaintext highlighter-rouge">@tool</code>
|
||
scripts.</p>
|
||
<p>Let’s take a look at an example:</p>
|
||
<div class="language-gdscript highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="err">@</span><span class="k">tool</span>
|
||
<span class="k">extends</span> <span class="n">Sprite2D</span>
|
||
<span class="c1"># With a callable (could also be a local function).</span>
|
||
<span class="err">@</span><span class="n">export_tool_button</span><span class="p">(</span><span class="s2">"Toot"</span><span class="p">,</span> <span class="s2">"Callable"</span><span class="p">)</span>
|
||
<span class="k">var</span> <span class="n">print_action</span> <span class="o">=</span> <span class="nb">print</span><span class="o">.</span><span class="n">bind</span><span class="p">(</span><span class="s2">"toot"</span><span class="p">)</span>
|
||
<span class="c1"># With a lambda.</span>
|
||
<span class="err">@</span><span class="n">export_tool_button</span><span class="p">(</span><span class="s2">"Randomize Color"</span><span class="p">,</span> <span class="s2">"ColorRect"</span><span class="p">)</span>
|
||
<span class="k">var</span> <span class="n">color_action</span> <span class="o">=</span> <span class="k">func</span><span class="p">():</span> <span class="n">self_modulate</span> <span class="o">=</span> <span class="kt">Color</span><span class="p">(</span><span class="nb">randf</span><span class="p">(),</span> <span class="nb">randf</span><span class="p">(),</span> <span class="nb">randf</span><span class="p">())</span>
|
||
</code></pre></div></div>
|
||
<p><img src="/storage/blog/dev-snapshot-godot-4-4-dev-3/export_tool_button.gif" alt="Export tool button examples" /></p>
|
||
<h3 id="massively-optimized-scene-startup-for-large-projects">Massively optimized scene startup for large projects</h3>
|
||
<p>Work has not slowed down on improving the scene startup experience, still thanks to amazing contributions by
|
||
<a href="https://github.com/Hilderin">Hilderin</a>. This dev snapshot introduces a massive improvement to editor load speed for
|
||
large projects (<a href="https://github.com/godotengine/godot/pull/95678">GH-95678</a>). Large projects can expect up to a 3×
|
||
speed improvement when loading the project and a similar speedup when doing any operations that scan the filesystem.</p>
|
||
<h3 id="vertex-shading">Vertex shading</h3>
|
||
<p>This dev release re-introduces the long-awaited vertex shading option for materials
|
||
(<a href="https://github.com/godotengine/godot/pull/83360">GH-83360</a>), thanks to contributor <a href="https://github.com/ywmaa">ywmaa</a>
|
||
landing their second major feature in Godot, after export support for
|
||
<a href="https://github.com/godotengine/godot/pull/87735">Blender Geometry Nodes</a>.
|
||
Vertex shading is used primarily to achieve an early PSX style and to optimize performance on older and lower-end
|
||
devices.</p>
|
||
<p>You can enable vertex shading either from within an existing <code class="language-plaintext highlighter-rouge">StandardMaterial3D</code>, <code class="language-plaintext highlighter-rouge">ORMMaterial3D</code>, <code class="language-plaintext highlighter-rouge">ShaderMaterial</code>,
|
||
or by force enabling it on all materials using the <code class="language-plaintext highlighter-rouge">rendering/shading/overrides/force_vertex_shading</code> project setting.</p>
|
||
<p><img src="/storage/blog/dev-snapshot-godot-4-4-dev-3/vertex_shading.webp" alt="Two spheres, one is vertex shaded" /></p>
|
||
<h3 id="add-batching-to-renderercanvasrenderrd">Add batching to RendererCanvasRenderRD</h3>
|
||
<p>After tackling the <a href="https://godotengine.org/article/dev-snapshot-godot-4-4-dev-1/#metal-rendering-backend">Metal rendering backend</a>
|
||
merged in an earlier snapshot, <a href="https://github.com/stuartcarnie/">Stuart</a> took on another impressive rendering
|
||
contribution: 2D batching!</p>
|
||
<p>Batching has been implemented in the Compatibility renderer since the release of 4.0. This release brings the same
|
||
performance benefits to the other backends by implementing batching when using the Forward+ and Mobile backends
|
||
(<a href="https://github.com/godotengine/godot/pull/92797">GH-92797</a>). Now 2D performance is comparable between all backends.</p>
|
||
<p>Batching is a performance optimization that drastically reduces the number of draw calls in a scene. The benefits of
|
||
batching will be particularly noticeable in scenes with a lot of text rendering or repeated sprites that share a texture
|
||
(e.g. when using tilemaps or making a bullet hell).</p>
|
||
<p>We have further improvements planned for batching on the RD backends that should allow it to be even faster than the
|
||
Compatibility backend. Stay tuned for updates in later dev releases!</p>
|
||
<h3 id="expression-evaluator-repl-in-the-debugger">Expression evaluator (REPL) in the debugger</h3>
|
||
<p>The expression evaluator adds a new tab to the bottom panel that allows you to evaluate expressions using the local
|
||
state of your scripts while stopped at a breakpoint. Many users are familiar with this workflow from other
|
||
<a href="https://en.wikipedia.org/wiki/Read%E2%80%93eval%E2%80%93print_loop">REPL</a> debuggers.</p>
|
||
<p>This feature has been a work in progress for awhile and was recently finished and merged in
|
||
(<a href="https://github.com/godotengine/godot/pull/97647">GH-97647</a>), thank you to <a href="https://github.com/rohanrhu">Oğuzhan</a>,
|
||
<a href="https://github.com/rxlecky">Erik</a>, and <a href="https://github.com/KoBeWi/">Tomek</a> for bringing it across the finish line.</p>
|
||
<p><img src="/storage/blog/dev-snapshot-godot-4-4-dev-3/repl.webp" alt="Evaluate tab in the debugger" /></p>
|
||
<h3 id="implement-autostart-for-all-profilers">Implement autostart for all profilers</h3>
|
||
<p>A common complaint from users is that they need to go back to the editor once they start their game in order to enable
|
||
the profiler. This made it hard to measure performance in the first few seconds of loading a scene and was an overall
|
||
hassle for developers.</p>
|
||
<p><a href="https://github.com/Geometror">Hendrik</a> introduced a checkbox that allows you to set the profiler to automatically start
|
||
when you run the engine and capture valuable profiling data immediately
|
||
(<a href="https://github.com/godotengine/godot/pull/96759">GH-96759</a>).</p>
|
||
<p><img src="/storage/blog/dev-snapshot-godot-4-4-dev-3/auto-start.webp" alt="Auto start checkbox in profiler" /></p>
|
||
<h3 id="add-markers-to-animation">Add markers to Animation</h3>
|
||
<p>Markers allow you to create sub regions of an animation that can be jumped to, or looped without playing the entire
|
||
animation.</p>
|
||
<video autoplay="" loop="" muted="" playsinline="">
|
||
<source src="/storage/blog/dev-snapshot-godot-4-4-dev-3/markers.mp4?1" type="video/mp4" />
|
||
</video>
|
||
<p>Markers are even supported inside the Animation Tree, where you can easily select animation markers for looping or to
|
||
begin playback.</p>
|
||
<video autoplay="" loop="" muted="" playsinline="">
|
||
<source src="/storage/blog/dev-snapshot-godot-4-4-dev-3/markers2.mp4?1" type="video/mp4" />
|
||
</video>
|
||
<p>For more details check out the pull request <a href="https://github.com/godotengine/godot/pull/91765">GH-91765</a>, which was one
|
||
of the first Godot contributions of <a href="https://github.com/chocola-mint">ChocolaMint</a>!</p>
|
||
<h3 id="linux-camera-support">Linux camera support</h3>
|
||
<p>Previously, Godot only supported accessing the device camera on macOS and iOS devices.
|
||
<a href="https://github.com/pkowal1982">pkowal1982</a>’s long-running pull request <a href="https://github.com/godotengine/godot/pull/53666">GH-53666</a>
|
||
was finally merged and adds support for the Linux platform, allowing developers to access connected cameras from within
|
||
their game.</p>
|
||
<h3 id="fallback-to-opengl-3-if-other-rendering-drivers-are-not-supported">Fallback to OpenGL 3 if other rendering drivers are not supported</h3>
|
||
<p>Currently when trying to run Godot with the Forward+ or Mobile backend on a device that doesn’t support Vulkan, D3D12,
|
||
or Metal, the engine will provide the user with an OS alert notifying them that they don’t have support for the needed
|
||
graphics API and they need to try again with the Compatibility backend. This alert has proven to be confusing for users
|
||
and the process of opening the scene ends up being cumbersome.</p>
|
||
<p>Now with <a href="https://github.com/godotengine/godot/pull/97142">GH-97142</a>, first contribution from
|
||
<a href="https://github.com/SheepYhangCN">SheepYhangCN</a>, the engine will automatically fall back to using OpenGL (the
|
||
Compatibility backend) when the other backends are not available. This should provide the smoothest possible experience
|
||
for users on older devices.</p>
|
||
<p>Since the Compatibility backends can look different from the other backends, game developers may not want Godot to
|
||
automatically fall back. In that case, they can disable the <code class="language-plaintext highlighter-rouge">rendering/rendering_device/fallback_to_opengl3</code> project
|
||
setting to avoid falling back, and users with OpenGL-only devices would then get notified that their hardware is not
|
||
supported.</p>
|
||
<h3 id="and-more">And more!</h3>
|
||
<p>There are too many exciting changes to list them all here, but here’s a curated selection:</p>
|
||
<ul>
|
||
<li>2D: Fix pink GradientTexture2D (<a href="https://github.com/godotengine/godot/pull/94744">GH-94744</a>).</li>
|
||
<li>2D: Fix polygon node losing its UV toolbar (<a href="https://github.com/godotengine/godot/pull/96466">GH-96466</a>).</li>
|
||
<li>3D: PathFollow3D update transform immediately by default (<a href="https://github.com/godotengine/godot/pull/96140">GH-96140</a>).</li>
|
||
<li>Animation: Update AnimationPlayer in real-time when bezier curve properties or bezier editor changes (<a href="https://github.com/godotengine/godot/pull/96753">GH-96753</a>).</li>
|
||
<li>Audio: Fix one frame overflow at the end of WAV files (<a href="https://github.com/godotengine/godot/pull/96768">GH-96768</a>).</li>
|
||
<li>Audio: Use a LocalVector to store data to optimize AudioStreamMp3 (<a href="https://github.com/godotengine/godot/pull/97026">GH-97026</a>).</li>
|
||
<li>Buildsystem: CI: Update clang-format pre-commit hook to 19.1.0 (<a href="https://github.com/godotengine/godot/pull/97483">GH-97483</a>).</li>
|
||
<li>Core: Add callable support for find and rfind Array methods (<a href="https://github.com/godotengine/godot/pull/95449">GH-95449</a>).</li>
|
||
<li>Core: Fix inability to use ResourceLoader in C# after threaded load in GDScript (<a href="https://github.com/godotengine/godot/pull/92888">GH-92888</a>).</li>
|
||
<li>Core: Add translation domain (<a href="https://github.com/godotengine/godot/pull/95787">GH-95787</a>).</li>
|
||
<li>Core: WorkerThreadPool: Revamp interaction with ScriptServer (<a href="https://github.com/godotengine/godot/pull/96959">GH-96959</a>).</li>
|
||
<li>Core: StringName: Fix empty hash (<a href="https://github.com/godotengine/godot/pull/96586">GH-96586</a>).</li>
|
||
<li>Dotnet: Generate strongly-typed method to raise signal events and fix event accessibility (<a href="https://github.com/godotengine/godot/pull/68233">GH-68233</a>).</li>
|
||
<li>Editor: Fix MeshInstance3D gizmo redraw performance for PlaneMesh with larger subdiv value (<a href="https://github.com/godotengine/godot/pull/96934">GH-96934</a>).</li>
|
||
<li>Editor: Fix error reopening non existing scene on startup (<a href="https://github.com/godotengine/godot/pull/97028">GH-97028</a>).</li>
|
||
<li>GDExtension: GDExtension: Allow class names to be unicode (<a href="https://github.com/godotengine/godot/pull/96501">GH-96501</a>).</li>
|
||
<li>GDScript: Fix issue with GDScript binary tokens being non-deterministic (<a href="https://github.com/godotengine/godot/pull/96855">GH-96855</a>).</li>
|
||
<li>GDScript: Fix Dictionary.merge() type validation (<a href="https://github.com/godotengine/godot/pull/96864">GH-96864</a>).</li>
|
||
<li>GDScript: Fix operator[] for typed dictionaries (<a href="https://github.com/godotengine/godot/pull/96797">GH-96797</a>).</li>
|
||
<li>GUI: GraphEdit: Improve dotted pattern grid performance (<a href="https://github.com/godotengine/godot/pull/96910">GH-96910</a>).</li>
|
||
<li>GUI: Fix TabContainer minimum size (<a href="https://github.com/godotengine/godot/pull/97132">GH-97132</a>).</li>
|
||
<li>Import: Add BC1 compression support to Betsy (<a href="https://github.com/godotengine/godot/pull/95915">GH-95915</a>).</li>
|
||
<li>Navigation: Fix AStar2D, AStar3D, AStarGrid2D from not returning a path when the destination is disabled/solid even with allow_partial_path option (<a href="https://github.com/godotengine/godot/pull/94246">GH-94246</a>).</li>
|
||
<li>Physics: Move Godot Physics 2D into a module; add dummy 2D physics server (<a href="https://github.com/godotengine/godot/pull/95261">GH-95261</a>).</li>
|
||
<li>Physics: Move Godot Physics 3D into a module; add dummy 3D physics server (<a href="https://github.com/godotengine/godot/pull/95252">GH-95252</a>).</li>
|
||
<li>Physics: Add forgotten get_space() check in GodotArea3D::remove_soft_body_from_query() (<a href="https://github.com/godotengine/godot/pull/97130">GH-97130</a>).</li>
|
||
<li>Porting: Fix project manager stealing focus on i3 (<a href="https://github.com/godotengine/godot/pull/96829">GH-96829</a>).</li>
|
||
<li>Rendering: Use distance to AABB surface to calculate Mesh LOD instead of using supports (<a href="https://github.com/godotengine/godot/pull/92290">GH-92290</a>).</li>
|
||
<li>Rendering: Fix BaseMaterial3D refracting objects located in front of the material (<a href="https://github.com/godotengine/godot/pull/93449">GH-93449</a>).</li>
|
||
<li>Rendering: Fix incorrect Reinhard tonemap operator (<a href="https://github.com/godotengine/godot/pull/93324">GH-93324</a>).</li>
|
||
<li>Rendering: Use temporal accumulation to improve the quality of shadows (<a href="https://github.com/godotengine/godot/pull/97428">GH-97428</a>).</li>
|
||
<li>Rendering: Fix region_filter_clip_enabled to avoid sprite bleeding for interpolated sprite sheets (<a href="https://github.com/godotengine/godot/pull/97602">GH-97602</a>).</li>
|
||
<li>Visual Shaders: Add vector operations to Remap node (<a href="https://github.com/godotengine/godot/pull/97314">GH-97314</a>).</li>
|
||
<li>Thirdparty: mbedTLS: Enable TLS 1.3 support (<a href="https://github.com/godotengine/godot/pull/96394">GH-96394</a>).</li>
|
||
<li>XR: Fix launching XR apps from the Android editor (<a href="https://github.com/godotengine/godot/pull/96868">GH-96868</a>).</li>
|
||
</ul>
|
||
<h2 id="changelog">Changelog</h2>
|
||
<p><strong>136 contributors</strong> submitted <strong>332 improvements</strong> for this new snapshot. See our <a href="https://godotengine.github.io/godot-interactive-changelog/#4.4-dev3"><strong>interactive changelog</strong></a> for the complete list of changes since the previous 4.4-dev2 snapshot.</p>
|
||
<p>This release is built from commit <a href="https://github.com/godotengine/godot/commit/f4af8201bac157b9d47e336203d3e8a8ef729de2"><code class="language-plaintext highlighter-rouge">f4af8201b</code></a>.</p>
|
||
<h2 id="downloads">Downloads</h2>
|
||
<div class="card card-download">
|
||
<a class="card-download-link" href="/download/archive/4.4-dev3">
|
||
Download Godot 4.4 dev3
|
||
</a>
|
||
<div class="card-download-details">
|
||
<img class="lightbox-ignore" src="/storage/blog/covers/dev-snapshot-godot-4-4-dev-3.webp" />
|
||
<div class="card-download-platforms">
|
||
<div class="download-platform platform-linux">
|
||
<img width="24" height="24" src="/assets/images/platforms/linux.svg" title="Linux" alt="Linux" class="lightbox-ignore" />
|
||
Linux
|
||
</div>
|
||
<a href="https://github.com/godotengine/godot-builds/releases/download/4.4-dev3/Godot_v4.4-dev3_linux.x86_64.zip" class="btn btn-download btn-download-primary platform-linux">
|
||
<div class="download-title">
|
||
Standard
|
||
</div>
|
||
</a>
|
||
<a href="https://github.com/godotengine/godot-builds/releases/download/4.4-dev3/Godot_v4.4-dev3_mono_linux_x86_64.zip" class="btn btn-download btn-download-primary btn-download-primary--mono platform-linux">
|
||
<div class="download-title">
|
||
.NET
|
||
</div>
|
||
</a>
|
||
<div class="download-platform platform-macos">
|
||
<img width="24" height="24" src="/assets/images/platforms/macos.svg" title="macOS" alt="macOS" class="lightbox-ignore" />
|
||
macOS
|
||
</div>
|
||
<a href="https://github.com/godotengine/godot-builds/releases/download/4.4-dev3/Godot_v4.4-dev3_macos.universal.zip" class="btn btn-download btn-download-primary platform-macos">
|
||
<div class="download-title">
|
||
Standard
|
||
</div>
|
||
</a>
|
||
<a href="https://github.com/godotengine/godot-builds/releases/download/4.4-dev3/Godot_v4.4-dev3_mono_macos.universal.zip" class="btn btn-download btn-download-primary btn-download-primary--mono platform-macos">
|
||
<div class="download-title">
|
||
.NET
|
||
</div>
|
||
</a>
|
||
<div class="download-platform platform-windows">
|
||
<img width="24" height="24" src="/assets/images/platforms/windows.svg" title="Windows" alt="Windows" class="lightbox-ignore" />
|
||
Windows
|
||
</div>
|
||
<a href="https://github.com/godotengine/godot-builds/releases/download/4.4-dev3/Godot_v4.4-dev3_win64.exe.zip" class="btn btn-download btn-download-primary platform-windows">
|
||
<div class="download-title">
|
||
Standard
|
||
</div>
|
||
</a>
|
||
<a href="https://github.com/godotengine/godot-builds/releases/download/4.4-dev3/Godot_v4.4-dev3_mono_win64.zip" class="btn btn-download btn-download-primary btn-download-primary--mono platform-windows">
|
||
<div class="download-title">
|
||
.NET
|
||
</div>
|
||
</a>
|
||
</div>
|
||
</div>
|
||
<div class="card-download-sublinks">
|
||
<a class="card-download-other" href="/download/archive/4.4-dev3">
|
||
Export templates and other downloads
|
||
</a>
|
||
<a class="card-download-donate" href="https://fund.godotengine.org/">
|
||
Make a Donation
|
||
</a>
|
||
</div>
|
||
</div>
|
||
<style>
|
||
.thankyou-wrapper {
|
||
position: fixed;
|
||
top: 0;
|
||
left: 0;
|
||
right: 0;
|
||
bottom: 0;
|
||
background: rgba(0, 0, 0, 0.85);
|
||
display: flex;
|
||
flex-direction: column;
|
||
justify-content: center;
|
||
align-items: center;
|
||
z-index: 10;
|
||
}
|
||
.thankyou {
|
||
background: var(--base-color);
|
||
box-shadow: var(--more-shadow);
|
||
padding: 30px;
|
||
display: flex;
|
||
flex-direction: column;
|
||
align-items: center;
|
||
text-align: center;
|
||
position: relative;
|
||
border-radius: 13px;
|
||
}
|
||
.thankyou-reading {
|
||
font-size: 16px;
|
||
}
|
||
.thankyou-reading-list {
|
||
font-size: 16px;
|
||
margin: 0;
|
||
margin-left: 48px;
|
||
padding-left: 0;
|
||
}
|
||
.thankyou-donate {
|
||
margin-bottom: 24px;
|
||
text-align: center;
|
||
}
|
||
.btn.btn-donate {
|
||
background-color: var(--primary-color);
|
||
color: hsla(0, 0%, 100%, 0.9);
|
||
font-size: 22px;
|
||
font-weight: 600;
|
||
margin-bottom: 26px;
|
||
}
|
||
.thankyou h2 {
|
||
text-shadow: var(--base-shadow);
|
||
font-size: 36px;
|
||
font-weight: 800;
|
||
margin-bottom: 12px;
|
||
}
|
||
.thankyou h2 .anchored-link {
|
||
/* Hiding the anchored text automatically added on blogposts */
|
||
display: none !important;
|
||
}
|
||
.thankyou p {
|
||
max-width: 620px;
|
||
font-size: 25px;
|
||
}
|
||
@media (max-width: 768px) {
|
||
.thankyou-wrapper {
|
||
display: block;
|
||
}
|
||
.thankyou {
|
||
position: absolute;
|
||
top: 0;
|
||
left: 0;
|
||
right: 0;
|
||
bottom: 0;
|
||
overflow: scroll;
|
||
padding: 30px 40px 18px 40px;
|
||
}
|
||
.thankyou-reading-list {
|
||
margin-left: 24px;
|
||
}
|
||
.btn-close-thankyou-popup {
|
||
width: 48px;
|
||
height: 48px;
|
||
display: flex;
|
||
justify-content: center;
|
||
align-items: center;
|
||
}
|
||
}
|
||
.btn-close-thankyou-popup {
|
||
cursor: pointer;
|
||
position: absolute;
|
||
top: 12px;
|
||
right: 12px;
|
||
}
|
||
.btn-close-thankyou-popup img {
|
||
background: transparent !important; /* for overwriting the style in the blogposts img */
|
||
}
|
||
@media (prefers-color-scheme: light) {
|
||
.btn-close-thankyou-popup img {
|
||
filter: invert(1);
|
||
opacity: 0.75;
|
||
}
|
||
}
|
||
</style>
|
||
<script>
|
||
document.addEventListener('DOMContentLoaded', () => {
|
||
const thankYouWrapper = document.getElementById('thank-you');
|
||
// Close itself, when clicked outside of the popup area.
|
||
thankYouWrapper.addEventListener('click', (e) => {
|
||
if (e.target === thankYouWrapper) {
|
||
thankYouWrapper.style.display = 'none';
|
||
}
|
||
});
|
||
// Close with a close button.
|
||
const thankYouBackButton = document.querySelector('.btn-close-thankyou-popup');
|
||
thankYouBackButton.addEventListener('click', () => {
|
||
thankYouWrapper.style.display = 'none';
|
||
});
|
||
// Open from the main download buttons.
|
||
const downloadButtons = document.querySelectorAll('.btn-download');
|
||
downloadButtons.forEach((it) => {
|
||
it.addEventListener('click', () => {
|
||
thankYouWrapper.style.display = '';
|
||
document.querySelector('.btn.btn-donate').focus();
|
||
});
|
||
});
|
||
// Open from the all downloads list.
|
||
const downloadLinks = document.querySelectorAll('.download-link');
|
||
downloadLinks.forEach((it) => {
|
||
it.addEventListener('click', () => {
|
||
thankYouWrapper.style.display = '';
|
||
});
|
||
});
|
||
// Close the dialog when the user presses the escape key.
|
||
document.addEventListener('keydown', (e) => {
|
||
if (e.key === 'Escape') {
|
||
thankYouWrapper.style.display = 'none';
|
||
}
|
||
});
|
||
});
|
||
</script>
|
||
<div class="thankyou-wrapper" id="thank-you" style="display: none;">
|
||
<div class="thankyou">
|
||
<h2>Godot is downloading...</h2>
|
||
<p class="thankyou-donate">
|
||
Godot exists thanks to donations from people like you. Help us continue our work:
|
||
</p>
|
||
<a href="https://fund.godotengine.org" class="btn btn-donate">
|
||
Make a Donation
|
||
</a>
|
||
<div class="btn-close-thankyou-popup">
|
||
<img src="/assets/icons/cross.svg" width="24" height="24" alt="Close this popup" class="lightbox-ignore" />
|
||
</div>
|
||
</div>
|
||
</div>
|
||
<p><strong>Standard build</strong> includes support for GDScript and GDExtension.</p>
|
||
<p><strong>.NET build</strong> (marked as <code class="language-plaintext highlighter-rouge">mono</code>) includes support for C#, as well as GDScript and GDExtension.</p>
|
||
<ul>
|
||
<li>See also <a href="https://docs.godotengine.org/en/latest/tutorials/scripting/c_sharp/index.html#c-platform-support">C# platform support</a>.</li>
|
||
</ul>
|
||
<div class="card card-warning">
|
||
<p>
|
||
While engine maintainers try their best to ensure that each preview snapshot and release candidate is stable, this is by definition <strong>a pre-release piece of software</strong>. Be sure to make frequent backups, or use a version control system such as Git, to preserve your projects in case of corruption or data loss.
|
||
</p>
|
||
</div>
|
||
<h2 id="known-issues">Known issues</h2>
|
||
<ul>
|
||
<li>“Attempting to use an uninitialized RID” error is printed when opening the editor (<a href="https://github.com/godotengine/godot/issues/97694">GH-97694</a>). This is a harmless error, and should have no noticeable impact on your project.</li>
|
||
</ul>
|
||
<p>With every release we accept that there are going to be various issues, which have already been reported but haven’t been fixed yet. See the GitHub issue tracker for a complete list of <a href="https://github.com/godotengine/godot/issues?q=is%3Aissue+is%3Aopen+label%3Abug+">known bugs</a>.</p>
|
||
<h2 id="bug-reports">Bug reports</h2>
|
||
<p>As a tester, we encourage you to <a href="https://github.com/godotengine/godot/issues">open bug reports</a> if you experience issues with this release. Please check the <a href="https://github.com/godotengine/godot/issues">existing issues on GitHub</a> first, using the search function with relevant keywords, to ensure that the bug you experience is not already known.</p>
|
||
<p>In particular, any change that would cause a regression in your projects is very important to report (e.g. if something that worked fine in previous 4.x releases, but no longer works in this snapshot).</p>
|
||
<h2 id="support">Support</h2>
|
||
<p>Godot is a non-profit, open source game engine developed by hundreds of contributors on their free time, as well as a handful of part or full-time developers hired thanks to <a href="https://fund.godotengine.org/">generous donations from the Godot community</a>. A big thank you to everyone who has contributed <a href="https://github.com/godotengine/godot/blob/master/AUTHORS.md">their time</a> or <a href="https://github.com/godotengine/godot/blob/master/DONORS.md">their financial support</a> to the project!</p>
|
||
<p>If you’d like to support the project financially and help us secure our future hires, you can do so using the <a href="https://fund.godotengine.org/">Godot Development Fund</a> platform managed by <a href="https://godot.foundation/">Godot Foundation</a>. There are also several <a href="/donate">alternative ways to donate</a> which you may find more suitable.</p></description><category>Pre-release</category><guid>https://godotengine.org/article/dev-snapshot-godot-4-4-dev-3/</guid><dc:creator>Clay John</dc:creator><pubDate>Thu, 03 Oct 2024 12:00:00 +0000</pubDate><image>https://godotengine.org/storage/blog/covers/dev-snapshot-godot-4-4-dev-3.webp</image></item><item><title>Godot XR update - October 2024</title><link>https://godotengine.org/article/godot-xr-update-oct-2024/</link><summary>Looking back at a year of XR development.</summary><description><p>It has been a very busy year on the XR front and seeing we haven’t given a proper update for well over a year, it’s time to look back at what has happened since our last update post.
|
||
We touched on some of these in the Godot 4.3 release blog but we’re doing a bit of a deep dive here.</p>
|
||
<p>We’re planning on publishing more articles about XR in the near future. We recently <a href="https://godotengine.org/article/godot-editor-horizon-store-early-access-release/">announced the XR editor</a> but we have more news on the way!</p>
|
||
<h2 id="improvements-in-godots-xr-architecture">Improvements in Godot’s XR architecture</h2>
|
||
<p>A lot of work has gone into improving the XR implementation in Godot.</p>
|
||
<h3 id="improved-frame-timing-logic">Improved frame timing logic</h3>
|
||
<p>When OpenXR was originally implemented in Godot 3 there were limitations on the order in which certain actions took place. Most of the communication with OpenXR was tied into the rendering engine resulting in Godot relying more on predictive algorithms to position tracked entities such as controllers. Originally Godot 4 inherited this approach.</p>
|
||
<p>As part of the Godot 4.3 release much of this logic was redone to interface with OpenXR correctly. Godot now correctly informs OpenXR when it starts processing a new frame and obtains pose data for tracked entities with predicted positioning for the current frame.</p>
|
||
<h3 id="preparing-to-support-rendering-on-a-separate-thread">Preparing to support rendering on a separate thread</h3>
|
||
<p>As part of implementing the improved frame timing logic, we did a large cleanup of the XR code to make sure it runs properly when rendering happens on a separate thread. Especially for XR applications this brings us closer to ensuring a steady framerate, even on stand alone devices.</p>
|
||
<p>There is more work that needs to be done in Godot 4.4 to make this fully viable but the foundations are in place.</p>
|
||
<h3 id="standardisation-for-ar-and-passthrough">Standardisation for AR and passthrough</h3>
|
||
<p>Passthrough is a mechanism where video cameras on a VR headset record the real world and present this real world view as the background inside of our HMD turning the headset into an AR device. Different headsets implement this feature in different ways and this caused difficulties for developers who were targeting multiple devices.</p>
|
||
<p>While passthrough allows some neat things not possible with optical AR devices, for most AR focussed application developers should not be tasked with writing different code to support all these devices.</p>
|
||
<p>We have thus standardized this approach through utilising OpenXRs environment blend modes and moving platforms specific code into the OpenXR vendors plugin.</p>
|
||
<h3 id="standardisation-of-hand-face-and-body-tracking">Standardisation of hand, face and body tracking</h3>
|
||
<p>Hand tracking has been supported in Godot for a long while now, however improvements have been made to ensure better cross platform support, including standardisation between OpenXR and WebXR. The <code class="language-plaintext highlighter-rouge">OpenXRHand</code> node has been deprecated, in favour of the new <code class="language-plaintext highlighter-rouge">XRHandModifier3D</code> node which is designed to work with any XR system - not just OpenXR.</p>
|
||
<p>Face tracking support has been added with face tracking data being sourced from several devices. Godot now supports the Unified Expressions standard for handling face tracking data.</p>
|
||
<p>Body tracking support has been added using Godots Humanoid Skeleton as a base which allows various body tracking devices to leverage Godots retargeting logic.</p>
|
||
<p>While these 3 systems have been implemented under the XR name, their use cases are not limited to XR. Already several plugins have been created using this system to bring in body tracking data from various body tracking solutions ranging from optical Mocap to full body tracking suits.</p>
|
||
<h3 id="improved-webxr-support">Improved WebXR support</h3>
|
||
<p>WebXR support in Godot is seeing continuous improvement, most notably the addition of hand tracking support, but also support for MSAA and a number of smaller bug fixes and improvements.
|
||
Our WebXR implementation now also supports AR applications.</p>
|
||
<h3 id="improved-opengl-support">Improved OpenGL support</h3>
|
||
<p>While technically not specific to XR, several improvements to the compatibility renderer directly impact the ability to create XR experiences using Godot.</p>
|
||
<p>The new MSAA implementation in the compatibility renderer has support for OpenGL extensions specifically targeting TBDR GPUs found on modern standalone headsets.
|
||
When available enabling MSAA 2x or 4x has a very low cost while providing worth while improvement in the visuals.</p>
|
||
<p>The new lightmapping capabilities of the compatibility renderer, where the Vulkan implementation is leveraged to bake the lightmaps, provides a viable solution for improved lighting on standalone XR hardware.</p>
|
||
<h3 id="improved-foveated-rendering-support-in-the-vulkan-engine">Improved foveated rendering support in the Vulkan engine</h3>
|
||
<p>The compatibility renderer uses OpenXRs foveated rendering support directly but this comes with various limitations and is not applicable outside of OpenXR.</p>
|
||
<p>In the Vulkan renderer we have had Variable Rate Shading support for a while which allows foveated rendering to be applied in Godot without the same drawbacks.</p>
|
||
<p>In the latest release various improvements have been applied that provide more control over the density map used and allow for eye tracking to impact the density map and ensure quality rendering at the users focal point.</p>
|
||
<h2 id="collaboration-between-w4-games--meta">Collaboration between W4 Games &amp; Meta</h2>
|
||
<p>The past year saw W4 Games and Meta join forces to improve Godot’s support for the Quest line of devices.</p>
|
||
<h3 id="core-functionality-improvements">Core functionality improvements</h3>
|
||
<p>The team at W4 has worked closely together with several core Godot XR contributors to improve the core functionality in Godot, improving the experience not just for Meta Quest users, but also for other XR systems. Several of the items mentioned in the previous sections benefited greatly from the help provided here.</p>
|
||
<p>These improvements also include various rendering optimisations and fixes.</p>
|
||
<h3 id="enhanced-passthrough-and-hand-tracking-support">Enhanced passthrough and hand-tracking support</h3>
|
||
<p>On top of the standardisation of passthrough and hand-tracking in Godot, support for many extra features Meta provides was implemented in the <a href="https://github.com/GodotVR/godot_openxr_vendors">Godot OpenXR Vendors plugin</a>.</p>
|
||
<p>For passthrough, this includes applying various filters to the passthrough imagery, like adjusting the brightness, contrast and saturation, mapping the colors to other values, or even projecting passthrough onto custom geometry, in order to bring only specific objects from the user’s physical environment into an otherwise VR experience. See the <a href="https://godotvr.github.io/godot_openxr_vendors/manual/meta/passthrough.html">Meta Passthrough tutorial</a> for more information.</p>
|
||
<p>For hand-tracking, developers can now access hand meshes, collision shapes for the hands, and do some simple gesture tracking, like detecting pinches between the user’s thumb and any of the other fingers. See the <a href="https://godotvr.github.io/godot_openxr_vendors/manual/meta/hand_tracking.html">Meta Hand Tracking tutorial</a> for the full details about these features.</p>
|
||
<h3 id="composition-layer-support">Composition layer support</h3>
|
||
<p>Composition layers are a standard feature in OpenXR, that allow developers to add floating “panels” (either flat or curved) that have 2D content rendered onto them from a Godot SubViewport.</p>
|
||
<p>The result of this approach is far sharper detail of the 2D content compared to applying this same content as a texture on a 3D mesh.</p>
|
||
<p>This is ideal for in game menus, media viewing, or heads up displays. Small text is especially more readable when using this technique.</p>
|
||
<p>W4 Games added both the <a href="https://docs.godotengine.org/en/latest/tutorials/xr/openxr_composition_layers.html">core implementation</a> and Meta-specific extensions, which allow applying further sharpening or supersampling, advanced alpha blending or marking particular composition layers as containing “secure content”. See the <a href="https://godotvr.github.io/godot_openxr_vendors/manual/meta/composition_layers.html">Meta Composition Layers tutorial</a> for more information about these Meta-specific features.</p>
|
||
<h3 id="scene-discovery-and-spatial-anchors">Scene discovery and spatial anchors</h3>
|
||
<p>These two closely related features are possibly the most exciting part of the work done so far. Meta’s Scene Discovery allows the Quest to scan your environment and provide your game with information about the real world.</p>
|
||
<p>This can allow you to place objects on your walls, on furniture, or have NPCs interact with the real environment.</p>
|
||
<p>Spatial anchors allow you to make this persistent. Create a spatial anchor that references a place on your wall, and you can show a virtual screen there anytime your user comes back to your application.</p>
|
||
<p>See the <a href="https://godotvr.github.io/godot_openxr_vendors/manual/meta/scene_manager.html">Meta Scene Manager</a> and <a href="https://godotvr.github.io/godot_openxr_vendors/manual/meta/spatial_anchors.html">Meta Spatial Anchors</a> tutorials for more information.</p>
|
||
<h2 id="newimproved-platform-support">New/Improved platform support</h2>
|
||
<h3 id="pico-4">PICO 4</h3>
|
||
<p>Godot has had support for PICO headsets for while but in the past year improvements were made to this. PICO has fully adopted the official Khronos Android Loader for OpenXR and deprecated their custom loader. Godot fully supports the new approach.</p>
|
||
<h3 id="htc-focus-3-and-xr-elite">HTC Focus 3 and XR Elite</h3>
|
||
<p>HTC provided the team with HTC Vive XR Elite units allowing us to ensure Godot runs on HTC standalone devices. We’re also working together with HTC to improve the experience on these devices.</p>
|
||
<h3 id="magic-leap-2">Magic Leap 2</h3>
|
||
<p>Support for the Magic Leap ecosystem was recently added to the vendor plugin as well. Magic Leap stands apart from other standalone Android devices being an optical AR device and running AMD hardware. On these devices you need to use the Vulkan mobile renderer.</p>
|
||
<h3 id="qualcomm-spaces">Qualcomm spaces</h3>
|
||
<p>This is still under development, we’re supporting Qualcomm’s OpenXR runtime on the Lynx R1 but we’re looking into supporting more devices in this eco system. Watch this space.</p>
|
||
<h3 id="logitech-mx-ink">Logitech MX Ink</h3>
|
||
<p>Not a new headset, but a pheripheral, the MX ink is a positionally tracked stylus that can be used with a Meta Quest.
|
||
Support was merged into master recently and this device will be supported in the upcoming Godot 4.4 release.
|
||
We’re looking into supporting this in a future 4.3 patch release.</p>
|
||
<h2 id="whats-next">What’s next</h2>
|
||
<p>Stay tuned for further blog posts focusing on XR as we start looking ahead and as new features become available.</p></description><category>Progress Report</category><guid>https://godotengine.org/article/godot-xr-update-oct-2024/</guid><dc:creator>Bastiaan Olij</dc:creator><pubDate>Wed, 02 Oct 2024 12:00:00 +0000</pubDate><image>https://godotengine.org/storage/blog/covers/october-2024-xr-progress-update.webp</image></item></channel></rss> |