Closed NyaomiDEV closed 6 years ago
If it's not hardware related then
./mcpelauncher --scale 4
should not noticeable affect it, can you confirm?
Yep; same lag
In the interest of differential diagnosis; Gtx970 @4k fullscreen with 1.1.0.55 on the 1.1 branch I get no noticeable lag with proprietary drivers v 378.13 on Mint 18.1 (based on Ubuntu 16.04)
Most likely some compositor/driver issue, I'm not really sure what I could do about it.
I bet it's something wrong with this
libEGL warning: DRI2: failed to authenticate
EGL_VERSION = 1.4 (DRI2)
This used to appear when I didn't symlink nvidia-340 libs to /usr/lib/i386-linux-gnu/ but if I do that now the game simply crashes.
IMO the game itself should use nvidia-XXX drivers located in /usr/lib32/nvidia-XXX/ instead of mesa-egl ones
The launcher currently links to whatever the system provides by default. It's hard to find a generic solution that works for everyone.
cmake or make argument? like cmake . -USE_NVIDIA=340
maybe.. 340 is my driver version btw
@guppy42 can you do ldd to the mcpelauncher executable?
@AryToNeX Later today I can - any particular version?
@guppy42 1.2, no matter the version you use, I only want to know which libEGL.so.1 it uses
$ ldd 1.2_beta2/mcpelauncher
linux-gate.so.1 => (0xf7705000)
libdl.so.2 => /lib/i386-linux-gnu/libdl.so.2 (0xf76cd000)
libpthread.so.0 => /lib/i386-linux-gnu/libpthread.so.0 (0xf76b0000)
librt.so.1 => /lib/i386-linux-gnu/librt.so.1 (0xf76a6000)
libEGL.so.1 => /usr/lib32/nvidia-378/libEGL.so.1 (0xf7694000)
libX11.so.6 => /usr/lib/i386-linux-gnu/libX11.so.6 (0xf7549000)
libuuid.so.1 => /lib/i386-linux-gnu/libuuid.so.1 (0xf7543000)
libstdc++.so.6 => /usr/lib/i386-linux-gnu/libstdc++.so.6 (0xf73cc000)
libgcc_s.so.1 => /lib/i386-linux-gnu/libgcc_s.so.1 (0xf73ae000)
libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xf71f8000)
/lib/ld-linux.so.2 (0x5663c000)
libm.so.6 => /lib/i386-linux-gnu/libm.so.6 (0xf71a3000)
libGLdispatch.so.0 => /usr/lib32/nvidia-378/libGLdispatch.so.0 (0xf710c000)
libxcb.so.1 => /usr/lib/i386-linux-gnu/libxcb.so.1 (0xf70e6000)
libXau.so.6 => /usr/lib/i386-linux-gnu/libXau.so.6 (0xf70e1000)
libXdmcp.so.6 => /usr/lib/i386-linux-gnu/libXdmcp.so.6 (0xf70da000)
@AryToNeX what is displayed at the top of the screen as the renderer? NVIDIA something or LLVM PIPE/Gallium?
@guppy42 Yep I know the issue now. Mcpelauncher doesn't link to /usr/lib/nvidia-340/libEGL.so.1
Sent from my Xiaomi Redmi Note 3 using FastHub
It should not matter where it links, it should use the library provided by ld.
Yep but Nvidia doesn't provide its 32bit libs to ld, only 64bit ones. I tried to modify it myself but then when I recompile it tells me EGLUT: failed to create context
Sent from my Xiaomi Redmi Note 3 using FastHub
@AryToNeX actually, what was the last version when the whole thing used the proper NVIDIA drivers?
@MCMrARM as far as I can remember it was before 1.x release, when mcpelauncher didn't use system provided libraries but it guessed the correct path
Sent from my Xiaomi Redmi Note 3 using FastHub
@AryToNeX looking at the error you get, it looks like you have a version mismatch between the kernel module and the 32 bit NVIDIA library
Also, it's very likely you may be using GLVND (GL Vendor Neutral Dispatch library) which automatically uses a software renderer as a fallback. TL;DR you have an issue with nvidia drivers and perhaps it's even correct that this links to /usr/lib32/libEGL.so
Okay I got it. Since reinstalling the drivers actually does nothing how should I solve this problem?
Sent from my Xiaomi Redmi Note 3 using FastHub
@AryToNeX you can force it to use a specific library; http://tldp.org/HOWTO/Program-Library-HOWTO/shared-libraries.html#AEN80
Are you using the bumblebee nvidia thing?
@guppy42 I'm only using nvidia-340 drivers that are in ubuntu repository
After debugging with the help of @MCMrARM I just discovered that it's sufficient to tell mcpelauncher the right libs directory.
$ LD_LIBRARY_PATH=/usr/lib32/nvidia-XXX ./mcpelauncher
I'm searching a way to force Nvidia drivers at linking time instead of running time. This issue should be referenced in the wiki for those who get mcpelauncher lagging because of LLVM Pipe.
Sent from my Xiaomi Redmi Note 3 using FastHub
As I suggested you do 3 days ago xD ( the link )
@guppy42 yep; btw this isn't the fix, this is the workaround. The fix will be when mcpelauncher dinamically links to nvidia libs.
MCPELauncher will not dynamically link to the NVIDIA libs, that's troublesome on my side and no apps do that.
@MCMrARM I want to force linking when make builds the binary, by specifying library path. I'm not sure how
Sent from my Xiaomi Redmi Note 3 using FastHub
I don't think fixing this is within the scope of the project, so I'm closing it. This is a messed up system config, any system with libglvnd should not have issues.
Log:
Using NVIDIA drivers (nvidia-340) and a 9400 GT. Lag isn't hardware-related (last time I played with master branch build the gameplay was fluid)