ToME: the Tales of Maj'Eyal

Everything about ToME
https://forums.te4.org/

linux startup bug fixed

https://forums.te4.org/viewtopic.php?f=38&t=45488

Page 1 of 1

linux startup bug fixed

Posted: Tue Jan 26, 2016 6:00 am
by Teber2
i'm happy to report that the game now works under debian mint cinnamon 64 bits. thank you guys!

Re: linux startup bug fixed

Posted: Sun Feb 07, 2016 12:44 am
by davidbarr
I am having an issue starting ToME on a 64 bit Linux Mint VM. When I run it I get the following error;

Code: Select all

david@mintVM ~/t-engine4-linux64-1.4.3 $ ./t-engine
WebCore config: library(/home/david/t-engine4-linux64-1.4.3/lib64/libte4-web.so) spawn(/home/david/t-engine4-linux64-1.4.3/cef3spawn64)
Loading WebCore: loaded!
[CPU] Detected 6 CPUs
ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear
ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe
ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side
ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.surround71
ALSA lib setup.c:548:(add_elem) Cannot obtain info for CTL elem (MIXER,'IEC958 Playback Default',0,0,0): No such file or directory
ALSA lib setup.c:548:(add_elem) Cannot obtain info for CTL elem (MIXER,'IEC958 Playback Default',0,0,0): No such file or directory
ALSA lib setup.c:548:(add_elem) Cannot obtain info for CTL elem (MIXER,'IEC958 Playback Default',0,0,0): No such file or directory
ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.hdmi
ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.hdmi
ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.modem
ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.modem
ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.phoneline
ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.phoneline
bt_audio_service_open: connect() failed: Connection refused (111)
bt_audio_service_open: connect() failed: Connection refused (111)
bt_audio_service_open: connect() failed: Connection refused (111)
bt_audio_service_open: connect() failed: Connection refused (111)
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
OpenAL device available: PulseAudio Software (default PulseAudio Software)
OpenAL device available: ALSA Software (default PulseAudio Software)
OpenAL device available: PortAudio Software (default PulseAudio Software)
Available video driver: x11
Available video driver: dummy
pci id for fd 9: 80ee:beef, driver (null)
OpenGL Warning: glFlushVertexArrayRangeNV not found in mesa table
OpenGL Warning: glVertexArrayRangeNV not found in mesa table
OpenGL Warning: glCombinerInputNV not found in mesa table
OpenGL Warning: glCombinerOutputNV not found in mesa table
OpenGL Warning: glCombinerParameterfNV not found in mesa table
OpenGL Warning: glCombinerParameterfvNV not found in mesa table
OpenGL Warning: glCombinerParameteriNV not found in mesa table
OpenGL Warning: glCombinerParameterivNV not found in mesa table
OpenGL Warning: glFinalCombinerInputNV not found in mesa table
OpenGL Warning: glGetCombinerInputParameterfvNV not found in mesa table
OpenGL Warning: glGetCombinerInputParameterivNV not found in mesa table
OpenGL Warning: glGetCombinerOutputParameterfvNV not found in mesa table
OpenGL Warning: glGetCombinerOutputParameterivNV not found in mesa table
OpenGL Warning: glGetFinalCombinerInputParameterfvNV not found in mesa table
OpenGL Warning: glGetFinalCombinerInputParameterivNV not found in mesa table
OpenGL Warning: glDeleteFencesNV not found in mesa table
OpenGL Warning: glFinishFenceNV not found in mesa table
OpenGL Warning: glGenFencesNV not found in mesa table
OpenGL Warning: glGetFenceivNV not found in mesa table
OpenGL Warning: glIsFenceNV not found in mesa table
OpenGL Warning: glSetFenceNV not found in mesa table
OpenGL Warning: glTestFenceNV not found in mesa table
libGL error: core dri or dri2 extension not found
libGL error: failed to load driver: vboxvideo
NO SELFEXE: bootstrapping from CWD
Creating save thread
===top 2
Booting T-Engine from: /home/david/t-engine4-linux64-1.4.3/t-engine
SelfExe gave us app directory of:	/home/david/t-engine4-linux64-1.4.3/
LuaVM:	LuaJIT 2.0.2	x64
Creating particles thread 0
Creating particles thread 1
Creating particles thread 2
Creating particles thread 3
LuaVM:	LuaJIT 2.0.2	x64
Creating particles thread 4
[DO RESIZE] Requested: 800x600 (0, 0); zoom 100%
LuaVM:	LuaJIT 2.0.2	x64
LuaVM:	LuaJIT 2.0.2	x64
LuaVM:	LuaJIT 2.0.2	x64
LuaVM:	LuaJIT 2.0.2	x64
[DO RESIZE] Got: 800x600 (0, 0)
OpenGL max texture size: 16384
OpenGL max texture size: 16384
Upgrading black texture to size 64
Running lua loader code...
Reboot using	te4	LATEST	boot	player	false
[ENGINE LOADER] available from teae: 	te4-1.4.3
[ENGINE LOADER] found engines	te4={[1]={[1]=1.000000 , [2]=4.000000 , [3]=3.000000 , [4]="te4" , [5]=17.000000 , ["load_teae"]="/engines/te4-1.4.3.teae" , } , } __byname={["te4-1.4.3"]=true , } 
[ENGINE LOADER] looked in:
	/home/david//.t-engine/4.0
	bootstrap
	/home/david/t-engine4-linux64-1.4.3//game/thirdparty
	/home/david/t-engine4-linux64-1.4.3//game
[ENGINE LOADER] sorted:	te4	1	4	3
[ENGINE LOADER] loading engine:	1	4	3	te4
[ENGINE LOADER] using archived engine:	/engines/te4-1.4.3.teae
Available resolutions: 2560x1600x32
Available resolutions: 2560x1440x32
Available resolutions: 2048x1536x32
Available resolutions: 1920x1600x32
Available resolutions: 1920x1080x32
Available resolutions: 1920x986x32
Available resolutions: 1680x1050x32
Available resolutions: 1600x1200x32
Available resolutions: 1400x1050x32
Available resolutions: 1280x1024x32
Available resolutions: 1024x768x32
Available resolutions: 800x600x32
Available resolutions: 640x480x32
Available resolutions: 2560x1600x32
Available resolutions: 2560x1440x32
Available resolutions: 2048x1536x32
Available resolutions: 1920x1600x32
Available resolutions: 1920x1080x32
Available resolutions: 1920x986x32
Available resolutions: 1680x1050x32
Available resolutions: 1600x1200x32
Available resolutions: 1400x1050x32
Available resolutions: 1280x1024x32
Available resolutions: 1024x768x32
Available resolutions: 800x600x32
Available resolutions: 640x480x32
[RESOLUTION] no configured resolution, defaulting to biggest possible: 	2560	1600
[KEYBINDER] Loaded keybinds: move
[KEYBINDER] Loaded keybinds: hotkeys
[KEYBINDER] Loaded keybinds: inventory
[KEYBINDER] Loaded keybinds: actions
[KEYBINDER] Loaded keybinds: interface
[KEYBINDER] Loaded keybinds: debug
setResolution: switching resolution to	2560x1600 Fullscreen	2560	1600	true	nil	(forced)
Setting resolution to 2560x1600 (fullscreen, with borders)
[DO RESIZE] Requested: 2560x1600 (1, 0); zoom 100%
The program 't-engine' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadValue (integer parameter out of range for operation)'.
  (Details: serial 248 error_code 2 request_code 140 minor_code 21)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
AL lib: ALc.c:1879: exit(): closing 1 Device
AL lib: ALc.c:1808: alcCloseDevice(): destroying 1 Context(s)
Any help appreciated. I am pretty inexperienced with Linux, so I am probably staring at the answer and don't even see it.

Re: linux startup bug fixed

Posted: Tue Feb 09, 2016 9:38 pm
by LemonTree
It looks like you might have a tiny bit too high screen resolution available to TOME for your system to manage.

It seems like you are running Linux in VirtualBox.
If you haven't installed VirtualBox's Guest Additions on a VM yet, then first try to install it and try to start TOME again.

If it still doesn't work, try running Linux in 1600x1200 resolution and test TOME again.

Re: linux startup bug fixed

Posted: Thu Feb 11, 2016 7:27 pm
by davidbarr
I am indeed running it in a VM, and I suspect that this is indeed the cause somewhere along the line. I have guest additions already installed, but I updated it and tried again manually setting my resolutions to a selection of them including the suggested above, but to no avail.

It is not a massive issue as I actually play this awesome game on Windows as well, but I thought I would mention it here in case it can help development in any way.

Re: linux startup bug fixed

Posted: Fri Feb 12, 2016 11:03 am
by mikekchar
I'm guessing you are running into this problem on virtualbox: https://www.virtualbox.org/ticket/12746

Basically DRI isn't supported, so I don't think you will be able to get tome to work in virtual box. Dual boot is the answer ;-)

However, mesa isn't well supported by tome and most of the shaders on Linux are disabled as a result. At one point I traced the problem down to the noise generator -- for some reason it takes many seconds to compile a shader. It is probably fixable if anyone with OpenGL experience would like to take a crack at it (it was beyond my experience / available spare time). If anyone notices that tome pauses occasionally on Linux with 100% CPU utilization when blood mages appear, it's the same problem. There is a supported shader check missing in that code ;-)

In any case, you will have better playing experience on Windows, so if you have it handy, that's what I would use.

Re: linux startup bug fixed

Posted: Fri Feb 12, 2016 8:03 pm
by LemonTree
You are of right about TOME having performance troubles on Linux. Windblade is one of those with very slow to draw effects.

Interesting fact is that TOME can run inside a VirtualBox-running Linux. Just for testing purposes I created a 64-bit Linux Mint 7.1 virtual machine with enabled 3D acceleration, running inside VirtualBox on 64-bit Ubuntu 15.04 (where I usually run TOME (from 1.3.1 to 1.4.3)). Then I put TOME 1.4.3 inside that VM and it ran quite nicely if a little slower than in non-VM Linux.

Maybe there are some hardware related issues that affect OpenGL - I have a Radeon R7 250 graphics card (about a year now) in a computer that is from 2010.
All times are UTC
Page 1 of 1

Powered by phpBB® Forum Software © phpBB Limited