Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

REMINDER: 3.0 BETA APPROACHING #12899

Closed
reduz opened this issue Nov 13, 2017 · 25 comments
Closed

REMINDER: 3.0 BETA APPROACHING #12899

reduz opened this issue Nov 13, 2017 · 25 comments
Milestone

Comments

@reduz
Copy link
Member

reduz commented Nov 13, 2017

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!

image

@RiverMesa
Copy link

Is this fancy logo going to be used for the beta or was that just done For Fun:tm:?

@reduz
Copy link
Member Author

reduz commented Nov 13, 2017

@NullConstant It's just meant as a reminder image to focus on 3.0 beta :) Actual release will probably have something else.

@akien-mga akien-mga added this to the 3.0 milestone Nov 13, 2017
@sersoong
Copy link
Contributor

Good!

@ghost
Copy link

ghost commented Nov 14, 2017

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 :)

@eon-s
Copy link
Contributor

eon-s commented Nov 15, 2017

Beta is going to need a full list of features and changes to make bug hunts easier, also to start with new demos.

@blurymind
Copy link

alpha2 plugin system is broken. Godot fails to load custom nodes- is that a bug or a missing feature that will make a comeback?

@vnen
Copy link
Member

vnen commented Nov 16, 2017

@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.

@Zylann
Copy link
Contributor

Zylann commented Nov 17, 2017

Could this be fixed? How hard would it be? #11030
Fixing this would give a huge boost to the whole editor experience/UX.

@yuyoDev
Copy link

yuyoDev commented Nov 19, 2017

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!

@Calinou
Copy link
Member

Calinou commented Nov 19, 2017

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…

@LikeLakers2
Copy link
Contributor

LikeLakers2 commented Nov 20, 2017

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.

@Zylann
Copy link
Contributor

Zylann commented Nov 20, 2017

@LikeLakers2
image

@sersoong
Copy link
Contributor

Yeah,today is November 20.
Can you release beta today?
We are looking faward to it.

@akien-mga
Copy link
Member

The beta build will be released when it's ready, no ETA. Nov 20 is only the date for the feature freeze.

@sersoong
Copy link
Contributor

Oh, all right

@RedwanFox
Copy link
Contributor

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?

@blurymind
Copy link

blurymind commented Nov 20, 2017 via email

@ghost
Copy link

ghost commented Nov 20, 2017

What does "feature freeze" mean exactly?

@neikeq
Copy link
Contributor

neikeq commented Nov 20, 2017

It means today we are adding a freezing feature for games. Whatever this feature entails is out of my knowledge.

@Sslaxx
Copy link

Sslaxx commented Nov 20, 2017

No new features will be added. So nothing like Mono support, GDNative or VR/AR. Focus will be on fixing bugs.

@mrezai
Copy link
Contributor

mrezai commented Nov 20, 2017

@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.

@HummusSamurai
Copy link
Contributor

This is very important to fix because it causes broken scenes that are tricky to fix #13172

Most users will give up.

@akien-mga
Copy link
Member

@neikeq
Copy link
Contributor

neikeq commented Nov 30, 2017

I can still reproduce this.

@bojidar-bg
Copy link
Contributor

Update to latest master and try again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests