Can surface pro x sq2 run Minecraft Java and install recent versions of OpenGL ?

Ok also Minecraft Java needs a OpenGL driver to run but does this means that the sq2 processor does not include OpenGL?

I'll be honest, I'm not sure if the OpenGL restriction is just for emulated apps, or if Qualcomm doesn't include OpenGL support in their drivers at all (leaving just the version 1.1 that Windows includes by default). If it's the latter, shame on them as the GPU is compliant with OpenGL 4.x from what I've been able to gather.

That said, the OpenCL and OpenGL compatibility pack (available in the store) is supposed to solve this issue either way, but it's currently limited to earlier versions (OpenCL 1.2 and OpenGL 3.3). I believe it is still also currently limited to just photoshop unless you're running an insider build. However I hope/expect as the project develops it will eventually support OpenGL 4.4+ requirement Minecraft needs. The fact that you listed OpenGL 3.3 support makes me think you've already found this and possibly are running an insiders build.

The other issue is native Java. However that is also being worked on (which is awesome!), see blog posts at Oracle and Microsoft. You can download early access release of JDK 16 from github. I've actually tried to load Minecraft using this (by modifying the launcher settings to use it instead of the bundled x86 Java binary), but it still crashes. I suspect it's because of OpenGL but I don't know for sure. Minecraft might not work on OpenJDK 16 yet.

I don't think x64 (AMD64) emulation is required to run Minecraft, as I can currently install it and the launcher will at least load. It's really the other two issues.

The other thought I've had is to use WSL (Windows Subsystem for Linux if you're not familiar with it) to run it when the GUI integration is released to stable builds of Windows (or maybe I'll give into temptation and switch to an insider build). I'm pretty sure the demos I've see of this were running GPU accelerated linux apps. There are guides to get Minecraft to run on the Raspberry Pi that I suspect would work for a WSL distro on the Surface Pro X (since it's still ARM64).

The TL;DR version is not yet, but I suspect it may be possible in the near future.

Surface Pro X uses LTE is LTE another reason why Minecraft Java can't run on Surface Pro X ?

Surface Pro X uses LTE is LTE another reason why Minecraft Java can't run on Surface Pro X ?

Well, I don't have a sim card in mine, but I wouldn't think LTE capabilities would break Minecraft.

Incidentally since my last comment Minecraft 1.17 has been released, and it actually has been upgraded to run on Java 16 from what I've read. Still no luck with it using the native ARM64 OpenJDK 16 pre-release. So either something is missing from Java on my device still, or it's back to the OpenGL issue.

This is the modified install pointing to the native java instead of the bundled:

Full path is: C:\Program Files (Arm)\Microsoft\jdk-16.0.1.9-hotspot\bin\java.exe

I've also tried the javaw.exe executable in the same folder with the same results (not 100% sure which I should use)

Results in the Latest Log file:

• [16:38:59] [Render thread/INFO]: Environment: authHost='https://authserver.mojang.com', accountsHost='https://api.mojang.com', sessionHost='https://sessionserver.mojang.com', servicesHost='https://api.minecraftservices.com', name='PROD'
• [16:39:00] [Render thread/INFO]: Setting user: <removed>
• [16:39:00] [Render thread/INFO]: [STDERR]: [LWJGL] Failed to load a library. Possible solutions: a) Add the directory that contains the shared library to -Djava.library.path or -Dorg.lwjgl.librarypath. b) Add the JAR that contains the shared library to the classpath. [16:39:00] [Render thread/INFO]: [STDERR]: [LWJGL] Enable debug mode with -Dorg.lwjgl.util.Debug=true for better diagnostics.
• [16:39:00] [Render thread/INFO]: [STDERR]: [LWJGL] Enable the SharedLibraryLoader debug mode with -Dorg.lwjgl.util.DebugLoader=true for better diagnostics.
• [16:39:01] [Render thread/INFO]: [STDERR]: java.lang.NoClassDefFoundError: Could not initialize class org.lwjgl.glfw.GLFW [16:39:01] [Render thread/INFO]: [STDERR]: at com.mojang.blaze3d.platform.GLX.getOpenGLVersionString(SourceFile:35)
• [16:39:01] [Render thread/INFO]: [STDERR]: at com.mojang.blaze3d.systems.RenderSystem.getApiDescription(SourceFile:770)
• [16:39:01] [Render thread/INFO]: [STDERR]: at ac.a(SourceFile:65)
• [16:39:01] [Render thread/INFO]: [STDERR]: at dvo.a(SourceFile:2418)
• [16:39:01] [Render thread/INFO]: [STDERR]: at dvo.a(SourceFile:2412)
• [16:39:01] [Render thread/INFO]: [STDERR]: at net.minecraft.client.main.Main.main(SourceFile:187)

Maybe someone smarter than me knows what this means...

Probably more waiting on either Java or OpenGL updates for WoA. I submitted feedback in the Feedback Hub for both Minecraft and the OpenCL and OpenGL compatibility pack requesting OpenGL support be added to Windows on ARM either via Qualcomm's drivers or the compatibility pack be upgraded to support OpenGL 4.x. Not sure what else I can do in the mean time.

I discovered that the surface pro x can be teardown and it can be fix i think so

As before the surface pro x can’t run Minecraft Java by its processor the motherboard of the surface pro x can be remove and the processor is there I want to know if the processor can be removed from the motherboard and change it to another one

I discovered that the surface pro x can be teardown and it can be fix i think so

As before the surface pro x can’t run Minecraft Java by its processor the motherboard of the surface pro x can be remove and the processor is there I want to know if the processor can be removed from the motherboard and change it to another one

You'd basically have to replace the motherboard as the SoC is soldered onto the board. From what I've read, the problem is there isn't currently an Intel or AMD cpu that would be able to fit into the thin form-factor of the Surface Pro X due to cooling requirements.

Windows on ARM is still quite new so I didn't expect Minecraft to run; actually I was 100% sure it wouldn't when I purchased my Pro X. Still, that doesn't stop me from wanting to see it happen, so I keep tinkering around with ideas or potential solutions.