With the new launcher the way to launch the game with my dedicated amd gpu( instead of the intergrated intel one) has changed. It used to be that all I had to do was to pass DRI_PRIME=1 before the launch command. Now the launcher doesn't pass these arguments to the game so I have made this script instead.
#! /bin/sh
export DRI_PRIME=1
exec java "$@"
and use the custom java executable to launch with it.
Now, something is happening because the game doesn't launch at all when I use this. The error from the launcher log is this
[0422/190550:WARNING:x11_util.cc(1404)] X error received: serial 773, error_code 180 (GLXBadWindow), request_code 154, minor_code 32 (X_GLXDestroyWindow)
[0422/190550:WARNING:x11_util.cc(1404)] X error received: serial 779, error_code 3 (BadWindow (invalid Window parameter)), request_code 4, minor_code 0 (X_DestroyWindow)
Keep in mind, the game launches just fine with the integrated gpu. Also the game is still running in the background as the launcher gives me a warning about it if I try to launch it again. I also assume this is a launcher bug as the error appears on launcher_log.txt
Linked issues
Comments 10
headsuphigh@desktop-kn6dbnn ~]$ rpm -qa | grep java
javapackages-tools-5.0.0-14.fc28.noarch
java-1.8.0-openjdk-headless-1.8.0.201.b09-5.fc28.x86_64
java-1.8.0-openjdk-1.8.0.201.b09-5.fc28.x86_64
tzdata-java-2019a-1.fc28.noarch
abrt-java-connector-1.1.1-1.fc28.x86_64
[headsuphigh@desktop-kn6dbnn ~]$ sudo alternatives --config java
[sudo] password for headsuphigh:
There is 1 program that provides 'java'.
Selection Command
-----------------------------------------------
*+ 1 java-1.8.0-openjdk.x86_64 (/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.201.b09-5.fc28.x86_64/jre/bin/java)
Also looking at my package manager I can't find any openjdk jre at version 1.8 so I don't know about that.
GPUs are an intel hd4600 and an AMD R9M265X( Cape Verde) with the default kernel drivers.
There are no proprietary drivers for AMD, at least not for this card. Besides this is up to date on the opengl version supported.
I uninstalled the headless version but it basically uninstalled the entirety of java. I reinstalled openjdk 1.8.0 and alternatives --config shows 1 version available only. The headless and the normal one come in one package in fedora, there isn't a unique option for the jre. Basically nothing changed in the commands. Could this be a case of openjdk messing up and redirecting to the headless version on it's own?
I have an issue with this as well on two instances of Linux Mint 19. On one computer, I fixed the issue by installing the IBM version of Java 8 from the Linux Mint repo (ibm-java80-jdk, jre & plugin). On the other computer, which I had this problem on today, I tried to do the same thing and it isn't working at all.
I just did, made no difference. I made sure to switch it with alternatives and also verify the version used. Also there doesn't appear to be any repo for the ibm java as the other comment suggested for fedora and I can't find what tool is needed to extract their weird archive filetype.
I have to go around the world to actually install Java 8 from Oracle since it isn't in the Mint repos (it only has the more recent versions of Java) but that doesn't work either. There used to be a Ubuntu PPA for older Java versions including 8 that had to be ended after Oracle's new policy. HeadsUpHigh, is it a .bin? I was curious and just checked and I have no idea, either. That may explain why it's in the Mint repos because it needed to be converted to a .deb and also the fact there's no other way to get Java 8 easily. I'm not familiar enough with Fedora, but it's unfortunate someone hasn't converted it into an RPM-compatible format.
EDIT: I also forgot to mention my computer has an integrated GPU that also has this problem.
After trying pretty much everything I could think of I managed to launch 1.14 with my dedicated gpu using multiMC. Under settings -> Custom Commands -> Wrapper command I input
env DRI_PRIME=1
and that's it. The game runs fine( with the usual complaining about flite missing, see my older bug report). Java version used is the openjdk one.
This is definitely a launcher bug. None of this would have happened if I could parse commands like it was possible before( and the launcher then sorted out the rest on it's own like it does when no executable is set).
Can you try the instructions in MCL-9795?
What GPU are you using and which drivers?