-
Notifications
You must be signed in to change notification settings - Fork 6
Intel HD Graphics Incompatbility #89
Comments
[INFO 2016/12/26 16:34:41 PM] [Voxel-Client] Starting Client This comment was edited by @HACKhalo2 to highlight relevant information to the bug |
@matiuri what Intel chipset do you have? |
@HACKhalo2 I'm not completely sure, but I think it's an Intel HD Graphics 4600 |
@matiuri that works and is what I was looking for. Thank you. Do you have access to a Windows machine with the same chipset to make sure it isn't a Mesa issue? |
@HACKhalo2 Yes, my computer is dual-booted. However, I won't boot Windows now because it's a waste of time, as I'm running Linux. I'll check that tomorrow when I turn on the computer again. |
@HACKhalo2 I've just run Voxel in Windows. Here is the output of gradlew.bat run: :utils:compileJava UP-TO-DATE
[INFO 2017/01/02 11:51:01 AM] [Voxel-Client] Registering State: Crash BUILD SUCCESSFUL Total time: 21.891 secs |
@matiuri I found the cause of this issue. ARB_shading_language_include is a nVidia-only extension, and it will cause other platforms to crash. I've began working on a custom implementation that will fix all of these issues. Thank you for testing, though! I greatly appreciated it. |
@matiuri could I have you test the newest commit and report your findings? |
The screen isn't white in Windows. Furthermore, the shaders work well. |
Closing for now, will reopen if more issues come up with the Intel chipsets |
All related to Intel HD incompatibly issues.
Extensions:
ARB_shading_language_include<-- nVidia-only extensionWhite screen on HD Graphics 4600<-- Won't FixPlease submit the crashlog (either in a pastie/pastebin or here) and what version of chipset you are using (Intel HD 3k, 4k, etc)
The text was updated successfully, but these errors were encountered: