@Bastien Montagne (mont29) I'm afraid this issue is still there on my OpenGL 3.1 laptop as well with twice the RAM and an i5 CPU. :( It is running Arch Linux with the latest drivers. But then again, Blender has historically had issues with my Intel GPUs. But things _have_ been getting better at least! :) I was actually testing 2D grease pencil on my Chromebook as it runs really well! Just thought I'd report it in case it would help! ;)

@LazyDodo (LazyDodo) Has this been brought up with the 2.8 team? I've just fixed lots of bugs so it's probably the best time to test it. Otherwise, it may be much longer before the next release. If it is too late, they can just use version 1f693aefca0 instead.

Changes on GitHub

TODO: For version 0.6 get light probes working in Cycles. The tab appears empty. This should be an easy fix.

Changes on GitHub.

BGE bug reports are redundant at this point. The next version of Blender (2.8) will not have a game engine so reporting bugs will not be beneficial. I'd suggest you use UPBGE, although I'm pretty sure that the project is dead now because all the developers have left. You may need to look into developing on a new platform such as Godot Engine, Unreal Engine, or Unity. Farewell BGE!

I've created a GitHub for the project too. That way it may be easier to contribute if anyone is interested.

@LazyDodo (LazyDodo) Thank you then! And obviously the actual developers could do this much better than me. I guess this is mainly to lay out the groundwork for them to come back in and clean up later. I still have some design ideas for the project like maybe using the 3D view header sort of like the "shading" or "overlays" panel. I just don't know how because there's no documentation yet.

@LazyDodo (LazyDodo) Why has this task been reassigned to @Dalai Felinto (dfelinto)? Does this mean that the addon is going to be merged with the actual Blender 2.8 project?

Changes on GitHub.

Blender crashed here before I could finish but basically, I was showing off the unified shader system and render properties system.

Changes on GitHub.

Changes on GitHub.

Right. Sorry! Where is a good place to ask these kinds of questions? Also, can I report actual 2.8 bugs without them being taken down because I found a major one!

Hmmm. Make sure that your camera isn't scaled. Select your camera and press Alt+S. Also, is your door part of the wall or is it a separate object?

Try entering edit mode on the wall and selecting everything and pressing Ctrl+T. It will triangulate everything. The Blender Game Engine converts everything to tris before the game starts and it uses a bad method.

I get the EXCEPTION_ACCESS_VIOLATION error every time on Linux with HD 3000 GPU on laptop. This crashes my computer completely (not just Blender) and I have to power off with power button. This is a problem on Manjaro KDE, Kubuntu, Ubuntu Gnome, and Zorin OS 12. Most of the time this only happens with a high poly object and being close to it with perspective. If using orthographic view it never crashes for me. This may be the best solution for Intel users at least for now.

Okay! I will check and let you know if it starts running faster!

I get this error on 2.8 when using cell fracture.

Okay! Thank you. I didn't know that there was a new version out already!

It's like this in previous versions too.

That's strange. I swear I have a reflection plane right by the front of the building, right by the trees. I tried to point it out in this one as the plane is a bit hidden. I also have it selected so that it can be more easily found.

This is not an error with Windows only, entering edit mode on Linux with Intel HD 3000 also crashes.

This wall disappears if you turn on only render in the display panel.

When using this version entering edit mode and entering the object it gives me this error:

Performance is very good on my big project however. ;)

When I run in terminal I get this error:

Thank you. I didn't realize that that was what was causing it.

Okay. Could this just be because my machine is only OpenGL 3.0. Thanks for the fast reply anyways! ;)