-
-
Notifications
You must be signed in to change notification settings - Fork 18.7k
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
GL context errors on OpenGL 3.3-able hardware [Windows 7, Radeon HD 3650 and 3200] #12596
Comments
#9027 was "solved" at some point then? |
I may have some of this hardware to test, need to set up in one of the computers.. |
I believe that #14861 is probably related. I get many of the same errors. |
I will not get test hardware to test this before 3.0, so moving to 3.1 unless anyone wants to give it a try |
If you just need someone to test, I can do so. If you want remote access to the box, we can arrange something; it's just sitting idle. |
Kicking to 3.2, where it will probably be closed, given this hardware does not support Vulkan and will likely have to use the GLES2 backend. |
Well, I have same issue on my radeon hd 4650. It will be fixed on 3.2? |
@spikestheraccon The GLES3 renderer is no longer really maintained, so you'll have to switch to the GLES2 renderer. (Your graphics card doesn't support Vulkan, so the Vulkan renderer in Godot 4.0 won't be an option.) |
On GLES2 Godot gives me same errors. Projects still opening and lauching on GLES2 and GLES3, but much slower than on linux. |
@spikestheraccon Do you get the same errors when using a binary compiled from the |
I use Stable 3.1.1 |
@spikestheraccon I'd like to know whether this is fixed in more recent pre-release versions 🙂 |
So, I tried to open my project on last build and errors on GLES2 is gone. But it still running and launching slowly, and I think there is another bug on the console. I also tried to disable 3d editor(my project is 2d), but result is same. |
Unfortunately, this is kind of expected on such an old, low-end GPU 🙁 You can speed up rendering in 2D projects by setting Rendering > Quality > Intended Usage > Framebuffer Allocation to 2D in the Project Settings. Also, try removing the
This is unrelated to the rendering issue. It was introduced by the integer overflow checks added in #31513, which exposed some underlying issues in the editor. |
I'll close this issue because we're unlikely to be able to fix issues for those old GPUs. The Windows drivers are notoriously bad for those cards and while they claim OpenGL 3.3 support, the above shows that they even struggle with OpenGL 2.1. If you have one of these cards, your best shot is to use the GLES2 version of Godot, and if that's not working well enough, try Linux as the Mesa drivers should have much better support for this hardware. |
Since raising this issue, Godot has received many fixes. and the GLES2 moment in 3.2. beta 2 works with almost the same efficiency as on versions 2.1.5, which I used before. |
Operating system or device, Godot version, GPU Model and driver (if graphics related):
Issue description:
I just uploaded Godot Alfa2 Win x64 and tried running, demo projects, it happens everywhere! The simplest 3D projects, such as the (GUI in 3D). are imported about 15 minutes. and then load about 10 minutes look nightmarish, and do not react either. And projects as a (platformer 3D) even worse they are just starting and freezing. A demonstration of new (materials TESTER) does not load at all, even can not be imported in the editor. 3d scenes are terribly slow if you add at least one 3D object.
Steps to reproduce:
In the first snapshot, the indicators taken from the (OpenGL Extensions Viewer) in the morning are what happens when you start (project manager). On the third of what happens when I try to run a demo project - (Material Tester). on the fourth already running demo project (platformer 3d).
Link to minimal example project:
Official demo projects.
The text was updated successfully, but these errors were encountered: