|
Post by jacquesolivier on Feb 20, 2015 15:22:06 GMT
Hi,
I have already test Besiege Alpha_Linux_v0_03 on both Linux, the game launch but it is not playable, too slow.
First :
Second :
|
|
|
Post by SuburbanSB on Feb 21, 2015 4:04:03 GMT
Hi jacquesolivier and welcome to the forums, Are you able to go into greater depth with this issue? You state that it is slow, however is it slow when building machines, using the machines, navigating the menu? Also, have you tried playing the game on different settings and using the time scale on the top left? Can you also upload the output_log.txt, which is located in Besiege/Besiege_Data The developers are already aware of game lag when too many blocks are placed, could this be your issue?
|
|
|
Post by jacquesolivier on Feb 21, 2015 16:32:53 GMT
Hi jacquesolivier and welcome to the forums, Are you able to go into greater depth with this issue? You state that it is slow, however is it slow when building machines, using the machines, navigating the menu? Also, have you tried playing the game on different settings and using the time scale on the top left? Can you also upload the output_log.txt, which is located in Besiege/Besiege_Data The developers are already aware of game lag when too many blocks are placed, could this be your issue? Hi SuburbanSB, It is slow on the first menu, and when i change graphics settings, i have to wait 2 or 3 seconds before it applied. I tried in Windowed mode, in a smaller resolution, 800x600 : It is better : i mean i can play, but still slowly on the two config. I can't find output_log.txt, maybe it is located in an other place on Gnu/Linux ? J-O
|
|
|
Post by spaar on Feb 21, 2015 17:36:17 GMT
I can't find output_log.txt, maybe it is located in an other place on Gnu/Linux ? I was about to reply that I'm pretty sure it's not, but I decided to just make sure again, and it seems you are correct. I can't find it either on my Arch Linux system, even though on Windows it's right where you would expect. I'll go investigate this, as it's actually kind of interesting If I find something I'll post back here.
|
|
|
Post by spaar on Feb 21, 2015 17:57:14 GMT
Alright, I didn't find an output_log.txt, but in ~/.config/unity3d/Spiderling Games/Besiege/ there is a file called Player.log. From what I can see it prints everything that would usually be in output_log plus some extra information. (Or maybe that's not even extra, but just Linux-specific) Maybe attach that instead ?
|
|
|
Post by jacquesolivier on Feb 25, 2015 12:11:22 GMT
Hi, Same place here on Debian 7 : ~/.config/unity3d/Spiderling Games/Besiege The two files : Player.log (12.87 KB) prefs (323 B)
|
|
|
Post by aleperno on Feb 25, 2015 16:28:30 GMT
Hi,
to me it sounds like a driver - library issue. Perhaps devs could enlight us if there's any shared library Besiege uses. Scrolling through your log file couldn't see anything particularly different from my log. I run Besiege on my Debian 8 (Jessie - Testing) box without any issues, not gaming-desktop-smooth but 60fps smooth.
Bear in mind I have a i3 4 Cpu 2.5 Ghz, 6Gb of Ram and a Intel HD4000.
Something I saw but dont know if it could imply any difference is the OpenGl version. Yours: OpenGL: Version: OpenGL 3.0 [3.0 Mesa 8.0.5] Mine: OpenGL: Version: OpenGL 3.0 [3.0 Mesa 10.3.2] (you can check the version with glxinfo | grep "OpenGL version")
Googling around there's some similar complaints on Debian Wheezy and Steam, some refer to a outdated version of the Mesa Lib and Linux Kernel.
See if there's any update for the Mesa Lib on Wheezy, if not check the Wheezy-Backports. Perhaps a 9.x or 10.x version will do it. If not, try installing it from testing.
Hope it helps.
|
|
|
Post by jacquesolivier on Mar 5, 2015 13:16:10 GMT
Bonjour,
Merci des infos.
Je vais attendre un peu que la version évolue avant de faire des changements de version de ces librairies sur mon système.
|
|