This is a reminder that 3.0 BETA is approaching. Your code must be merged before November 20 (a week from now) or it will have to wait for 3.1, as we will enter Feature Freeze!
Is this fancy logo going to be used for the beta or was that just done For Fun:tm:?
@NullConstant It's just meant as a reminder image to focus on 3.0 beta :) Actual release will probably have something else.
Good!
Glad I looked at this forum. I was JUST going to start porting my game to Godot 3 from 2.X. I guess the wait is almost over :)
Beta is going to need a full list of features and changes to make bug hunts easier, also to start with new demos.
alpha2 plugin system is broken. Godot fails to load custom nodes- is that a bug or a missing feature that will make a comeback?
@blurymind I have no issues with custom nodes. Can you try with a more recent build? If there's a problem, open a new report.
Could this be fixed? How hard would it be? https://github.com/godotengine/godot/issues/11030
Fixing this would give a huge boost to the whole editor experience/UX.
Regarding this topic #9561,
The topic is closed, but the solution will be released until version 3.1
But I have seen that this problem the "jitter-movement" in the motion demo is recurrent.
I also have the same problem(not only in motion-demo, that problem is in Godot 2.x and Godot3alpha), my suggestion is to add a function to get the refresh rate of the monitor, as suggested by @ghost
I think could be a nice solution for the Godot3.0 release until we wait for the Godot3.1 when is planned the fixed frame interpolation @reduz. Please consider it!
my suggestion is to add a function to get the refresh rate of the monitor
Not only this does not really solve the problem, but this also will cause differences in behavior between different monitor Hz (which should never impact how a game's physics and simulation runs). Not to mention that many people forget to use delta
to create physics FPS-independent simulations…
We seem to be 91% through the 3.0 milestone. Is this a bug? Should I let Github know? Or should I let reduz bask in the numbers being higher than they should be?
...You know SOMEONE had to do it. Don't actually reply to this, keep it on topic.
@LikeLakers2
Yeah,today is November 20.
Can you release beta today?
We are looking faward to it.
The beta build will be released when it's ready, no ETA. Nov 20 is only the date for the feature freeze.
Oh, all right
The beta build will be released when it's ready, no ETA. Nov 20 is only the date for the feature freeze.
So, did feature freeze officially happen?
He just said that feature freeze will be november 20th
On 20 Nov 2017 18:03, "Nickolai Korshunov" notifications@github.com wrote:
The beta build will be released when it's ready, no ETA. Nov 20 is only
the date for the feature freeze.So, did feature freeze officially happen?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/godotengine/godot/issues/12899#issuecomment-345777710,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGMbVbpRrnOneScTxXnFja0tXaGzpQPzks5s4b72gaJpZM4Qbq8W
.
What does "feature freeze" mean exactly?
It means today we are adding a freezing feature for games. Whatever this feature entails is out of my knowledge.
No new features will be added. So nothing like Mono support, GDNative or VR/AR. Focus will be on fixing bugs.
@reduz @akien-mga @bruvzg : I think PR #10546 (bidi and text shaping support) can be considered for merge because it is implemented as a separate Control without any modification in other UI nodes.
Maybe even we can have something like "Qt Technology Previews" for some incomplete features.
This is very important to fix because it causes broken scenes that are tricky to fix https://github.com/godotengine/godot/issues/13172
Most users will give up.
I can still reproduce this.
Update to latest master
and try again.
Most helpful comment
The beta build will be released when it's ready, no ETA. Nov 20 is only the date for the feature freeze.