thepolis

More of an issue with different compilers, if you used icc on linux it was less problematic than using gcc, even using gcc on windows yields a lot of interesting errors. The devs used C++ compilers rather than a stricter C compiler like gcc

You can runtime patch it, not sure if you can static patch it. I would do it for some compensation.

gcc: -mno-sse or -mfpmath=387 or -march=i386 msvc: /arch:IA32 idk about clang/llvm, haven't bothered with it.

OpenJK (by default) uses SSE FP arithmetic. Vanilla jka is x87 FP arithmetic. So go back to the original FP arithmetic model and you can have base behavior again.

Siege should be deprecated. It has been dead for years.

http://icculus.org/gtkradiant/documentation/windows_compile_guide/ "The instructions below have been executed successfully on Windows XP 32 bit (some late service pack).." I'm not going to help if you are going to be a boob.

http://icculus.org/gtkradiant/downloads.html#binaries Get 1.6 then post errors here. There is also a 1.6 binary on jkhub.

raz0r you should see if static linking readline will be an option. see this. http://acrmwww.biochem.ucl.ac.uk/software/profit/doc/node17.html

I'd like to see engine code duplication removed, right now its duplicated for SP & MP. Not sure how difficult a task this would be, but damn it would be nice.

Take a look at Q3 MultiMod [1]. It's possible to create a plugin without hacking the engine source. 1. http://sourceforge.net/projects/qmm/

Hey eezstreet could you submit a patch for linux ui & cgame? I could do it myself if I had repo access.

So for the next release in 12 months can you include a linux client? Would be appreciated. Thank you.

ctags

They will create any excuse to get out of any work, even to call bugs as features or easter eggs. It took them years to fix the hit location damage and I'm sure kyle bug hasn't been fixed yet. I remember when changing to Jedi class it would automatically switch you to Sith, that one was also known for years and may still exist. Each new version took about a year or more to release.

It's shit.

I'll do it for money.

I'm using x86_64 linux. x86_64 builds of OpenJK run poorly. i386 builds run stable enough.

You may be missing runtime dependencies. You can use ldd to see which libraries are being linked and which ones are missing. $ ldd openjk.x86_64

He deserves credit for the effort put into that mosaic. Beautiful autistic work.

You can build with SSE and SSE plays similar to JA+ SP.

Something as simple as SSE turned on which most mods compile with destroys basejka gameplay. If you browse through the disassembly SSE is obviously not used in 1.01. JA+ likely uses SSE which explains the infinite parry phenomena. I haven't bothered to look at 1.00 and I don't care too.