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
akien-mga opened this issue May 18, 2017 · 24 comments

Comments

Projects
None yet
@akien-mga
Copy link
Member

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

  • Asset Library should be able to filter plugins by compatibility with engine version #7147
  • Removing a rigidbody and re-adding it to the scene results in errors and the rigidbody disappearing #10074
  • Graphic artifacts in 3d scenes. #10149
  • Glow post effect is broken for softlight and screen blend modes (regression from 5567e89) #9106
  • Font hinting causing chunky fonts #9441
  • Godot freeze computer, when shadow contact set to 1 #9740
  • Glow seems to be broken (regression from 772485c) #9797
  • Refraction is broken (regression from 772485c) #9803

Edit: Previous list, archived on 24 July.

High priority bugs

  • InputEvent's is_action{,_pressed,_released} don't work #8914
  • Keyboard in editor unusable in latest code #8894
  • Image -> *.stex conversion is broken since it was made a Resource. #8801
  • Names of ClassDB-bound methods changed #8742
  • OBJ files and DAE (better dae) are not imported correctly. Absent in .import folder. #8741
  • Broken lighting on Collada mesh with normal map [Intel HD 3000] #8711
  • SSAO graphical issue with glitchy lines #8708
  • Using a texture in 3D always forces a re-import and makes it darker. #8684
  • Various undefined shader problems #8681
  • Color degradation with directional shadow #8683
  • Normal maps in skinned/rigged meshes fail to work correctly #8673
  • Massive lag and OpenGL error spam on Windows with Intel graphics #8665
  • Issues with the "View" menu in 3D mode #8489
  • Crash on AudioPlayer save scene #8596
  • color picker doesn't display colors properly #8372
  • The editor viewport with wrong size #8328
  • Crash making new shader in editor #8314
  • GI probes don't seem to have an effect #8194
  • Can apply CanvasItemMaterial to 3D Nodes #8121
  • Screen-space reflections issues #8119
  • Crash when opening default lighting config dialog #8082
  • TIME breaks canvas_item shaders #9123
  • Adding uniform sampler2D on shader_type canvas_item, brakes and forceclose godot #9143
  • Texture import freezes #9183

Nice to fix // can be for next alpha

  • Path editor plugin not working #8886
  • Strange effect with shadows enabled on DirectionalLight #8817
  • Particle shadows work only with directional light #8815
  • OmniLight can produce weird shadows when close to objects #8813
  • Accessing transform matrices data in shader breaks it. #8751
  • Varying in shader is not working #8749
  • Using INDEX on a particles shader, breaks the shader #8731
  • Viewport transparent background doesnt work #8703
  • Spotlights with shadows enabled cast light between mesh faces #8654
  • Collision shapes are drawn in wrong color and collision contact points are not drawn at all #8607
  • Light2D with shadows enabled near an occluder displays errors instead of shadows #8560
  • Glow affects gizmos #8485
  • Object bounding boxes are always zero #8446
  • Thumbnails not visible in filesystem dock #8377
  • Only the first sampler showing up in ShaderMaterial Shader Param list #8353
  • SSAO doesn't play well with smooth shading #8237
  • Gizmos lose their colors #8118
  • Some 2D nodes aren't visible: canvas_item_add_triangle_array() doesn't work #7840
  • FileSystem thumbnails display 2D scene (impressive bug!) #7812
  • Collision shapes and polygons not getting drawn on 2D #8033 (bojidar-bg)
@Corruptinator

This comment has been minimized.

Copy link
Contributor

commented May 21, 2017

looking forward to see progress in 3.0! :)

@ghost

This comment has been minimized.

Copy link

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.

@n-pigeon

This comment has been minimized.

Copy link
Contributor

commented May 26, 2017

Input class broken, probably after InputEvent rewrite #8914

@bojidar-bg

This comment has been minimized.

Copy link
Member

commented May 26, 2017

I think #8931 is also good to have here.

@ficoos

This comment has been minimized.

Copy link
Contributor

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

This comment has been minimized.

Copy link
Member

commented Jun 2, 2017

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

@bojidar-bg

This comment has been minimized.

Copy link
Member

commented Jun 13, 2017

Adding #9123, as it might crash the editor.

@DimitriyPS

This comment has been minimized.

Copy link

commented Jun 15, 2017

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

This comment has been minimized.

Copy link
Member Author

commented Jun 15, 2017

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

This comment has been minimized.

Copy link
Member

commented Jun 15, 2017

Adding #9183, makes the editor quite unusable.

@rubenjavier

This comment has been minimized.

Copy link

commented Jun 16, 2017

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

@vnen

This comment has been minimized.

Copy link
Member

commented Jun 19, 2017

I think #9021 would be nice to fix.

@Zireael07

This comment has been minimized.

Copy link
Contributor

commented Jun 20, 2017

#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

This comment has been minimized.

Copy link
Contributor

commented Jul 9, 2017

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

This comment has been minimized.

Copy link
Contributor

commented Jul 20, 2017

8711 seems fixed from my point of view :)

@kubecz3k

This comment has been minimized.

Copy link
Member

commented Jul 26, 2017

#9861 would be nice to have fixed

@akien-mga

This comment has been minimized.

Copy link
Member Author

commented Jul 26, 2017

#9861 would be nice to have fixed

Not a bug :)

@Zireael07

This comment has been minimized.

Copy link
Contributor

commented Jul 26, 2017

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

@akien-mga

This comment has been minimized.

Copy link
Member Author

commented Jul 26, 2017

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

This comment has been minimized.

Copy link
Member

commented Jul 26, 2017

@akien-mga i closed #9803

@ghost

This comment has been minimized.

Copy link

commented Aug 6, 2017

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

@HummusSamurai

This comment has been minimized.

Copy link
Contributor

commented Aug 8, 2017

This should probably be here. #10149

@HummusSamurai

This comment has been minimized.

Copy link
Contributor

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

This comment has been minimized.

Copy link
Member Author

commented Aug 17, 2017

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.

@akien-mga akien-mga closed this Aug 17, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.