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

[TRACKER] Main bugs to fix before first official 3.0-alpha build #8805

Closed
48 of 52 tasks
akien-mga opened this issue May 18, 2017 · 24 comments
Closed
48 of 52 tasks

[TRACKER] Main bugs to fix before first official 3.0-alpha build #8805

akien-mga opened this issue May 18, 2017 · 24 comments

Comments

@akien-mga
Copy link
Member

akien-mga commented May 18, 2017

This tracker issue is meant to list the main bugs that should be handled in priority before we can release a public alpha build.

That alpha build is not meant to be bug free, but these objectives should be met:

  • The renderer should work (at least run, not all features need to be perfect) on most hardware supporting OpenGL 3.3 (desktop).
  • OSX, Windows and X11 platforms should compile and run. It's OK for the first alpha if the other platforms don't work yet.
  • The editor should be usable, i.e. the basic features should work as expected. The new theme should be polished for a better usability, as it currently has many outstanding usability regressions.
  • Rendering features advertised in the progress reports should work. They don't have to be perfect, but they should be usable so that testers can start seeing how the 3.0 will be like (and give feedback to improve it).
  • The various outstanding bugs linked to compatibility breakage should be fixed or at least mitigated.
  • C# integration is not a requirement for that build. If it's ready, that's great, but it's not a blocker.
  • The rendering features planned for 3.0 and not implemented yet can be left for after that first build. There are enough outstanding issues to fix before adding new ones.

High priority bugs


Edit: Previous list, archived on 24 July.

High priority bugs

Nice to fix // can be for next alpha

@Corruptinator
Copy link
Contributor

looking forward to see progress in 3.0! :)

@ghost
Copy link

ghost commented May 24, 2017

#8886 and #8377 maybe? Also metallic workflow is not working properly, I'm not sure if there is an issue for that.

@SirPigeonz
Copy link
Contributor

Input class broken, probably after InputEvent rewrite #8914

@bojidar-bg
Copy link
Contributor

I think #8931 is also good to have here.

@ficoos
Copy link
Contributor

ficoos commented Jun 1, 2017

I think #8409 should also be here. Fixing this requires non trivial changes to Variant and also it changes the semantic of GDScript meaning that it's can't be fixed in a backward compatible way.

@bojidar-bg
Copy link
Contributor

Added #8033 to the list, since it doesn't look good (and since we are getting lots of duplicates...)

@bojidar-bg
Copy link
Contributor

Adding #9123, as it might crash the editor.

@DimitriyPS
Copy link

Why is this:
#8811
not included in the mandatory fixes to 3.0?

Godot 3.0 announced as a development engine for 3D. What if 3D basic physics does not work? You can forgive the outdated renderer, relatively poor performance... but the bug collisions kills any full project 3D games!

@akien-mga
Copy link
Member Author

Why is this:
#8811
not included in the mandatory fixes to 3.0?

It is, see its milestone. This tracker here is about the alpha, not about 3.0-stable.

@vnen
Copy link
Member

vnen commented Jun 15, 2017

Adding #9183, makes the editor quite unusable.

@rubenjavier
Copy link

@bojidar-bg #9143 also crashes the editor, and maybe its related to #9123 , since canvas_items shaders got broken

@vnen
Copy link
Member

vnen commented Jun 19, 2017

I think #9021 would be nice to fix.

@Zireael07
Copy link
Contributor

#9254 is a physics regression, would be nice to see fixed before alpha so that I could actually test instead of wondering why do all cars end up belly up

@Corruptinator
Copy link
Contributor

Would #9311 count as one of the bugs to fix? s3tc.stex could use a bit of a checkup because I found out that one of the slightly old 3.0 build where the Intel graphic lag and debug spam is fixed (https://github.com/godotengine/godot/tree/47b34bf79be1ba2fe4a99c8931732efac68a0b87)
actually has a fully functional, unbugged s3tc.stex file import process that does not leave the normalmap completely glitched.

Just pointing it out in case before the Alpha is uploaded.

@Grosskopf
Copy link
Contributor

8711 seems fixed from my point of view :)

@kubecz3k
Copy link
Contributor

kubecz3k commented Jul 26, 2017

#9861 would be nice to have fixed

@akien-mga
Copy link
Member Author

#9861 would be nice to have fixed

Not a bug :)

@Zireael07
Copy link
Contributor

The list looks like it hasn't been updated in a month, and the vehicle physics thing still looks like a blocker...

@akien-mga
Copy link
Member Author

The list looks like it hasn't been updated in a month, and the vehicle physics thing still looks like a blocker...

Look better, it was updated yesterday. And that list is still only about the alpha stage, not all bugs are meant to be in it. All bugs with the 3.0 milestone will be reviewed before 3.0 is released.

@djrm
Copy link
Contributor

djrm commented Jul 26, 2017

@akien-mga i closed #9803

@ghost
Copy link

ghost commented Aug 6, 2017

How about #10074? Something is making angular velocity NaN in physics.

@HummusSamurai
Copy link
Contributor

HummusSamurai commented Aug 8, 2017

This should probably be here. #10149

@HummusSamurai
Copy link
Contributor

HummusSamurai commented Aug 16, 2017

This was closed #9143, but it references #9263 as being the follow-up, not sure if you want to substitute it as it's less critical.

@akien-mga
Copy link
Member Author

Closing as this tracker outlived its purpose (3.0-alpha1 is published already).

Let's see if we need another tracker for high priority issues in the master branch or if the 3.0 milestone is enough.

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