GoDot v2.0.1 (stable) Win32

:information_source: Attention Topic was automatically imported from the old Question2Answer platform.
:bust_in_silhouette: Asked By BlenderWarrior
:warning: Old Version Published before Godot 3 was released.

Hi I am a Blender Developer User and have been referred to using the GoDot as a game engine due to significant issues with other game engines involved with blender. I Downloaded the “Godot_v2.0.1_stable_win32.exe” from the godotengine.org download tab area. After extracting, and attempting to open my GoDot Engine, I get errors from GoDot Command Line (for some reason I can’t post pictures of the issues). I also see that GoDot opens but it shows few buttons and is just blank. Anyway of fixing such issues?

The error has to do with: ERROR: _update_framebuffer: Condition ' status != 0x8CD5 ' is true. Continuing..: ← it displays that about 4 or 5 times then says for each of those times: At: drivers/gles2/rasterizer_gles2.ccp:10616. Then saays after all those errors: WARNING: viewport_data_create: Can't create framebuffer for vd then this → At: drivers/gles2/rasterizer_gles2.ccp: 4048. After all that it says “lost?”.

BlenderWarrior | 2016-03-08 08:58

Please, use “Godot” instead of “GoDot” – What is the proper letter case for spelling Godot? - Archive - Godot Forum

Bojidar Marinov | 2016-03-08 09:51

What is your GPU card? Does it support OpenGL 2.0?

Bojidar Marinov | 2016-03-08 09:52

:bust_in_silhouette: Reply From: megalomaniakaal

I also see that GoDot opens but it shows few buttons and is just
blank. Anyway of fixing such issues?

This sounds(well, reads) to be the same issue: The UI for the Godot editor doesn’t display any text..

So search the issue tracker on github to see if it’s already reported:

if so, post a reply indicating that you face the same issue, here is one still open from 2014 that looks to be possibly related:

However considering it’s date, it is probably best to make a new issue report, and give as much detail as possible. At the very least you should report what Operating System you are running, what graphics hardware you are using and the version number of graphics driver in use, etc.

I think it would be better to comment on #686 directly since it seems to be the exact same issue (including same error message). Just post as much information as possible in a new comment on this issue.

Akien | 2016-03-11 06:32