MVDSV

You are using too old sources.

Get the newest sources from SVN (for both MVDSV and KTX if you use them both), then configure and compile.

(make dl32 with KTX, MVDSV compiles fine without extra care)

You are using too old sources.

ok. i didn't realize that never wersion is available. i thought i downladed latest version.

You are using too old sources.

i tried 0.29b build 885 from svn and the same effect, frequent coredumps while running as daemon (-d). i'll try normal launching mode and let you know if it helps.

mvdsv_0.29b-885: ELF 64-bit LSB executable, x86-64, version 1 (FreeBSD), for FreeBSD 7.1 (701106), dynamically linked (uses shared libs), FreeBSD-style, stripped

it might be because 64-bit gives some warnings during compilation. it crashes as -d and normal launch under screen. works for some time and crashes randomly.

i also tried to make 32-bit version which do not give any warnings during compilation but it gives worse effect. it crashes always right after the start (segmantation fault).

both tried from 0.29b885 (/trunk catalog)

No no no. r885 and r886 are broken (segfaults galore), r887 is probably fixed (not tested yet). So using r883 at this point is recommended, and it shouldn't segfault.

883    27/03/2009    19:04    qqshka    &r and &c not allowed in names now. hf

MVDSV can compile both 32bit and 64bit (it ALWAYS defaults to 32bit unless you give options during ./configure) but QVM does not support 64bits and also native builds of KTX can't be 64bit.

no mods. just plain mvdsv. i have now r883 64-bit. i'll drop some info in case of any problems. thanks for help.

stupid question. any idea why my rcon password no longer works? server.cfg didn't change. before 0.29b833 i was using pre compiled 0.175 binaries and there were no problem with password.

hmmm, client didn't change either?
check value of sv_crypt_rcon

hmmm, client didn't change either? check value of sv_crypt_rcon

it was both client and server problem :)
both started crypting from certain versions.

btw: r833 is also dumping core.

Damnit...
Does compiling it 32bits work?

th wrote:

no mods. just plain mvdsv. i have now r883 64-bit. i'll drop some info in case of any problems. thanks for help.
This is where you are wrong. MVDSV can't be used as stand-alone server, it always requires a mod. So again, what mod are you using?

Indeed, it always requires (qw)progs.*

What are you using it with? qwsv progs?

Does compiling it 32bits work?

i tried r883 as 64 bit only so far.

This is where you are wrong. MVDSV can't be used as stand-alone server, it always requires a mod. So again, what mod are you using?

right. in that sense of mod i'm using qwprogs.dat from qwsv era. it probably came with qwsv binary package.

Might be interesting to test 2 things: 32bits compilation with qwprogs.dat and 64 bits with ktx.
That might give us a better idea of what doesn't work.

deurk wrote:

Might be interesting to test 2 things: 32bits compilation with qwprogs.dat and 64 bits with ktx. That might give us a better idea of what doesn't work.
Actually no. If the old qwprogs from qwsv doesn't work then it won't work, the protocol in MVDSV has changed enough times to make it incompatible with something that is not being updated.

On that note, also mismatching 32/64bit builds and especially KTX is not generally a good idea since it will cause segfault immediately. Why is that? 32bit and 64bit builds have different pointers, they can't be used mismatched so if you have 64bit MVDSV then you have to have 64bit compiled progs too.

KTX does not compile 64bits at all, KTX QVM does not compile 64bits at all either. This is why both MVDSV and KTX has to be compiled 32bits on 32bit system or using -m32 flags (MVDSV defaults, KTX requires make dl32) on 64bit systems, KTX FAQ will tell you what libs you need for that.

Solution to this particular problem is:

1) Ditch that old qwprogs, unless you specifically want to use qwsv progs. In this case you have to use older MVDSV.
2) Use KTX instead, it is mostly based on KTPro and KTeams and is the most used "mod" for QW out there these days.

We can not, and we will not waste time for supporting something from 1999 that is not being developed anymore, so expect MVDSV to support only the newer mods like KTX, KTPro, CA, RA, FBCA and some CTF mods.

The issue will be rejected soon, I see no bug in MVDSV unless proven otherwise with recent MODs.

Rejected

Reason: No additional info was given if the MVDSV segfaults with newer mods like KTX or KTPro on 64bit FreeBSD. MVDSV works with KTX on my FreeBSD and VVD must have had his time with his FreeBSD and MVDSV.

Note: MVSDV will support mods that are still being developed, mods that have been forgotten a long time ago (qwsv progs for example) can't be supported because sometimes with new features the protocol changes. Also it's up to the mod authors to follow changes that has been made in MVDSV.