Godot: FileSystem thumbnails display 2D scene (impressive bug!)

[RayKoopa]

3.0 master

Issue description:
Thumbnails are not displayed and instead an upside-down view on the editor 2D scene.

This bug exists since several weeks now on Windows 10 x64 (possibly more OSes) so I thought I share it :)

Steps to reproduce:
Open any project, see thumbnails getting trashed and your console filled with things like this:

ERROR: _gl_debug_print: GL ERROR: Source: OpenGL        Type: Error     ID: 3010        Severity: High  Message: glBlitFramebuffer failed because the framebuffer configurations require that the source and destination formats and sample counts match (GL_INVALID_OPERATION)
   At: drivers\gles3\rasterizer_gles3.cpp:94
REIMPORTING: res://test_dir/.dontseeme.png
mesege
ERROR: _gl_debug_print: GL ERROR: Source: OpenGL        Type: Error     ID: 3010        Severity: High  Message: glBlitFramebuffer failed because the framebuffer configurations require that the source and destination formats and sample counts match (GL_INVALID_OPERATION)
   At: drivers\gles3\rasterizer_gles3.cpp:94
REIMPORTING: res://test_dir/absolutely_hidden.png
mesege
ERROR: _gl_debug_print: GL ERROR: Source: OpenGL        Type: Error     ID: 3010        Severity: High  Message: glBlitFramebuffer failed because the framebuffer configurations require that the source and destination formats and sample counts match (GL_INVALID_OPERATION)
   At: drivers\gles3\rasterizer_gles3.cpp:94
REIMPORTING: res://test_dir/rms.png
mesege
ERROR: _gl_debug_print: GL ERROR: Source: OpenGL        Type: Error     ID: 3010        Severity: High  Message: glBlitFramebuffer failed because the framebuffer configurations require that the source and destination formats and sample counts match (GL_INVALID_OPERATION)
   At: drivers\gles3\rasterizer_gles3.cpp:94

Also, if I make the editor window smaller than the "internal minimum size" (or what that is, when it stops resizing the inner contents), everything gets worse:

[27thLiz]

I've never seen this using the master branch on linux - so tagging it as a windows bug for now.

[ni-code]

I can confirm this on Ubuntu Linux 16.10.
GPU nvidia GeForce GTS 450, using proprietary driver 367.57

compiled from master, commit: 9cdd364fc0edee407a65fbef674dcc3bcea378a9
scons p=x11 target=release_debug bits=64 tools=yes use_llvm=yes -j 4

[punto-]

"impressive bug" should be a new tag, this looks cool :p

On 14 February 2017 at 21:04, ni-code [e-mail] wrote:

I can confirm this on Ubuntu Linux 16.10.
GPU nvidia GeForce GTS 450, using proprietary driver 367.57

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/godotengine/godot/issues/7812#issuecomment-279876534,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGVmPd7O3PKBVAakD_fsicLyvsXjXr6hks5rckD4gaJpZM4MBDos
.

[bojidar-bg]

@punto- I think "feature" is a good tag for it already :stuck_out_tongue:

[RayKoopa]

I heard someone wanted to implement a live preview for the currently edited scene like this 🤣

[Zylann]

I wondered why all resource icons were grey everywhere. Now I know :p

[manokara]

Can confirm. Arch Linux, latest master. But here it displays the 3D view instead of the 2D one 😆

[algorev]

Can confirm on MacOS X El Capitan 10.11.6.

[Ahmed0425]

Lol 😂 .. Seems like many forms of only one bug ... do you encounter a crash on making a new shader?
that shader tab should not be visible
Also I think this bug was mentioned 3 other times in the tracker above #8665 #8489 #8314 .. all those testers encounter that shader crash bug
Am I wrong?

[bojidar-bg]

@Ahmed0425 Yeap, you are wrong. It is not the same bug, it is different bugs
We sometimes mark duplicates based on the fact that a commit fixing issue X would automatically fix issue Y, for some reason. If any of the above three issues are fixed, there is no guarantee that this one would get fixed as well.
And also, the symptoms are different, so it is likely that it is not the same bug 😃.

[manokara]

I have built 2e3145d and the device selection icon is doing the same thing. So whatever this issue is, it isn't only tied to the filesystem node.

Can anyone confirm this?

[akien-mga]

I love this issue feature.

[manokara]

I noticed that if you remove the device button, the filesystem icons become a solid rectangle, either red or white. With the button, the filesystem icons and the button look fine (somewhat, and only if you've resized the window), but the scene not so much. And you have a lot of these at the console:

ERROR: _gl_debug_print: GL ERROR: Source: OpenGL    Type: Error ID: 1282    Severity: High  Message: GL_INVALID_OPERATION error generated. Texture name does not refer to a texture object generated by OpenGL.
   At: drivers/gles3/rasterizer_gles3.cpp:123.

The viewport bug happens in both cases (edit: oh, RayKoopa already showed that). So from what I see, this issue must be related to the gles3 renderer, somewhere in the texture management code. The renderer is using texture data it's not supposed to. I don't know a lot about rendering though, maybe @reduz can enlighten us on this.

[reduz]

I feel terrible to have fixed this bug, but it's sadly gone :(