Problem running the program

[jorgex96]

Hello, I have come to look for a solution because when I run raze it runs and automatically exits for no reason, therefore to play for example Shadow Warrior I must run the program several times to be able to play the game correctly, I don't know why and why I leave the program log, look for a solution online but they are alien to the program itself. I have to clarify that the program was compiled using the AUR package.

Code: Select all

Raze 1.2.1-m - 2021-10-16 09:05:40 +0200 - SDL version
Compiled on Nov 29 2021

Log started: 2021-11-30 12:38:55
OS: Artix Linux, Linux 5.15.5-artix1-1 on x86_64
 adding /usr/lib/raze/raze.pk3, 2711 lumps
 adding /home/jorgitox/raze/Sw.grp, 693 lumps
 adding /home/jorgitox/raze/, 22 lumps
CPU Vendor ID: GenuineIntel
  Name: Intel(R) Pentium(R) CPU 2020M @ 2.40GHz
  Family 6, Model 58, Stepping 9
  Features: SSE2 SSE3 SSSE3 SSE4.1 SSE4.2 HyperThreading
Loading "engine/widescreen.def"

I_InitSound: Initializing OpenAL
[ALSOFT] (EE) Failed to set real-time priority for thread: Operación no permitida (1)
  Opened device ALSA Default
[ALSOFT] (EE) Failed to set real-time priority for thread: Operación no permitida (1)
  EFX enabled
No GENMIDI lump found. OPL playback not available.
script parsing took 126.89 ms
SHADOW WARRIOR(tm) Version 1.2
Copyright (c) 1997 3D Realms Entertainment
Using video driver x11

That's all, thanks

[Redneckerz]

It seems to attempt to open a sound device OpenAL which it cannot do, nor does it find a GENMIDI lump.

What midi driver are you using on Raze?

[Graf Zahl]

The GENMIDI message is harmless. Just a remnant of some Doom ckecks in the music init code.

[jorgex96]

It seems to attempt to open a sound device OpenAL which it cannot do, nor does it find a GENMIDI lump.

What midi driver are you using on Raze?

Hello, I just saw in the game options in the sound section and apparently it is using fluidsynth, I do not know if that is what you mean, if it is so, would you recommend midi driver.

[jorgex96]

The GENMIDI message is harmless. Just a remnant of some Doom ckecks in the music init code.

Ok it is clear to me that it is normal for this error to appear, thank you very much.