This site uses cookies to improve your experience. To help us insure we adhere to various privacy regulations, please select your country/region of residence. If you do not select a country, we will assume you are from the United States. Select your Cookie Settings or view our Privacy Policy and Terms of Use.
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Used for the proper function of the website
Used for monitoring website traffic and interactions
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Strictly Necessary: Used for the proper function of the website
Performance/Analytics: Used for monitoring website traffic and interactions
Core: Handle corner cases for curve baking ( GH-69726 ). If you have existing scenes and resources with navigation polygons and meshes, you might want to skip beta 9 and wait for beta 10 in a few days so that your scenes and resources are ported seamlessly. See the GitHub issue tracker for a list of known bugs in the 4.0
Core: Handle corner cases for curve baking ( GH-69726 ). If you have existing scenes and resources with navigation polygons and meshes, you might want to skip beta 9 and wait for beta 10 in a few days so that your scenes and resources are ported seamlessly. See the GitHub issue tracker for a list of known bugs in the 4.0
This adds support for obstacle avoidance using the RVO2 library, and navigation meshes can now be baked at runtime. You can move the polygon with the node transform, drag the corners to reshape it, add delete points. Anything behind the polygon will be culled from view. Bug reports. back in 2020! x no longer works in 3.5
beta builds every other week to ensure that new features can be tested, bugs can be reported and bugfixes can be validated. This beta 4 is a small update with just 83 commits excluding merges, focusing on fixing bugs to stabilize the current feature set for 3.5 Anything behind the polygon will be culled from view. Bug reports.
beta builds every other week to ensure that new features can be tested, bugs can be reported and bugfixes can be validated. This beta adds what should be the last batch of new features (together with a lot of bug fixes, as that's our focus at this stage), with scene unique node names and the new SceneTreeTween backported from Godot 4.0.
beta builds every other week to ensure that new features can be tested, bugs can be reported and bugfixes can be validated. This adds support for obstacle avoidance using the RVO2 library, and navigation meshes can now be baked at runtime. Anything behind the polygon will be culled from view. Bug reports. Like with 4.0
Most of work was aimed at implementing missing features or fixing bugs which are critical for publishing 2D and 3D games with Godot 3.x, Since then, smix8 has taken over the custody of this area, fixing a lot of bugs and improving the feature set greatly, with the help of Pawel Lampe ( Scony ) and lawnjelly. Early adopters of 3.5
Then smix8 took over the custody of this area, fixing a lot of bugs and improving the feature set greatly, with the help of Pawel Lampe ( Scony ). The new NavigationServer adds support for obstacle avoidance using the RVO2 library, and navigation meshes can now be baked at runtime. Anything behind the polygon will be culled from view.
Then smix8 took over the custody of this area, fixing a lot of bugs and improving the feature set greatly, with the help of Pawel Lampe ( Scony ). The new NavigationServer adds support for obstacle avoidance using the RVO2 library, and navigation meshes can now be baked at runtime. Anything behind the polygon will be culled from view.
Then smix8 took over the custody of this area, fixing a lot of bugs and improving the feature set greatly, with the help of Pawel Lampe ( Scony ). The new NavigationServer adds support for obstacle avoidance using the RVO2 library, and navigation meshes can now be baked at runtime. Anything behind the polygon will be culled from view.
This RC 3 fixes a number of recent regressions and older bugs. The new NavigationServer adds support for obstacle avoidance using the RVO2 library, and navigation meshes can now be baked at runtime. You can move the polygon with the node transform, drag the corners to reshape it, add delete points. Bug reports.
This RC 4 fixes a number of recent regressions and older bugs. Then smix8 took over the custody of this area, fixing a lot of bugs and improving the feature set greatly, with the help of Pawel Lampe ( Scony ). You can move the polygon with the node transform, drag the corners to reshape it, add delete points. Bug reports.
This adds support for obstacle avoidance using the RVO2 library, and navigation meshes can now be baked at runtime. You can move the polygon with the node transform, drag the corners to reshape it, add delete points. Anything behind the polygon will be culled from view. Bug reports. back in 2020!
Then smix8 took over the custody of this area, fixing a lot of bugs and improving the feature set greatly, with the help of Pawel Lampe ( Scony ). The new NavigationServer adds support for obstacle avoidance using the RVO2 library, and navigation meshes can now be baked at runtime. Anything behind the polygon will be culled from view.
The new NavigationServer adds support for obstacle avoidance using the RVO2 library, and navigation meshes can now be baked at runtime. You can move the polygon with the node transform, drag the corners to reshape it, add delete points. Anything behind the polygon will be culled from view. Bug reports.
release, we decided to take the chance to look at our long list of features and bug fixes that could not be implemented because it involved breaking compatibility. Just set up the probe bounds and do a fast pre-bake of static objects. A year ago, we decided to skip the release of Godot 2.2 and that we'd better focus fully on 3.0
Weve been keeping busy these past two weeks squashing the bugs that cropped up in 4.4 feature freeze, so our energy has been focused on addressing any new regressions or the aforementioned bugs. Were still aiming for a release sometime next month, but that all depends on how effectively new bugs get reported during this period.
We organize all of the trending information in your field so you don't have to. Join 5,000+ users and stay up to date on the latest articles your peers are reading.
You know about us, now we want to get to know you!
Let's personalize your content
Let's get even more personalized
We recognize your account from another site in our network, please click 'Send Email' below to continue with verifying your account and setting a password.
Let's personalize your content