rtcw linux - signal 11 in wolfmp

[pinkname]

Yes, I copied all mp paks. (didn't read any readme whatsoever, just ran it...) Btw it's nice to see it uses alsa properly :)

Outputs are coming soon.

J.

[pinkname]

nondev output: http://pastebin.com/e6thdfsm
dev output: http://pastebin.com/FfMzBzk9

Both were created without autoexec or wolfconfig_mp.cfg.

thanks:

J.

[pinkname]

I nearly forgot:

sometimes I get signal 4, but I don't yet know how to reproduce it.


And now I see I pasted dev twice :X Sry for the inconvinience :D


J

[MAN-AT-ARMS]

Please try removing all pk3's except for stock:

pak0.pk3
mp_pak0.pk3-mp_pak5.pk3
mp_pakmaps0-mp_pakmaps6.pk3

Also try adding +set r_mode 6 on the commandline

[pinkname]

Nothing changed. Mkay, shell output now contains only the remaining paks, but that's it (with or without r_mode). It sets the given mode then quits.

:(


J.

[MAN-AT-ARMS]

Can you do an md5sum on all your files and check them against mine?

7651d02fe51fc8a949536f3e0cfa8dd6 mp_bin.pk3
62641cffd9a8ad0f62cc1cca867d51f8 mp_pak0.pk3
22b972974f499a237c96a2200b0d019e mp_pak1.pk3
30f29ffa81748a957e0441af8c14cb56 mp_pak2.pk3
fdc00dfd72b888e92a4387e1933826e4 mp_pak3.pk3
c5f76bbde262eba577a00bebe9cd4f8f mp_pak4.pk3
d17df62d6c71078ed137aefc69d80f30 mp_pak5.pk3
f2d361a0082ed9bc1e26d2327b4f22db mp_pakmaps0.pk3
d1856aa9bc62f719a400428b9ec27ebb mp_pakmaps1.pk3
a0ee8714c6f7ee72680293778c22d6ee mp_pakmaps2.pk3
01bb7c4fb3b11273d75ae658fb4de0cc mp_pakmaps3.pk3
a39525809f7a0780f5546063dad1e5d1 mp_pakmaps4.pk3
bb24fb011b0f4b84335c66a869d1ab1c mp_pakmaps5.pk3
397e0b48673a1a8e0ec25eb0f3ccae9d mp_pakmaps6.pk3
ce92b11df889cb0a045762bb5fd7cde5 pak0.pk3

e178273bfa552212f24caf0a5fd538a7 cgame.mp.i386.so
90d46cbfd45b3261170f2c69660f904b qagame.mp.i386.so
5326db91f9272fcee47341fcbb40a19d ui.mp.i386.so

86227f299245466f65943005d405eced wolf.x86

[pinkname]

Checked against your list also, all sums are fine.

A question: can we be sure there are no sound issues if I turn initsound to 0 (as I already tried)? The machine has an unusual sound setup and I was wondering if... Also I'm using (ofc?) et-sdl-sound. I'm trying to not exlude anything even if sounds irrelevant at first glance. As I see sound init would come only later, but... Arrrgh.

thanks again:

J.

[MAN-AT-ARMS]

I'm not using sdl sound, im just using the oss-compat modules.

Then I have this in an init script:
echo "wolf.x86 0 0 direct" > /proc/asound/card0/pcm0p/oss