On 30/11/2010 20:20, Nerius Landys wrote: > Dominic, you seem to be a tad out of the loop as far as Urban Terror > 4.1 binaries go. This is understandable if you're not a hardcore UrT > fan like me. :-)
Actually, I used to play it a lot back when I was looking for a decent Action Quake 2 successor. Compared to baseq3 the performance in UT sucks (mostly unplayable on my notebook), even though the perceived visual quality of plain old Q3 is superior. I think rq3 might be my thing. I didn't take a thorough look, yet. > People on Linux now are using mitsubishi's "ioq3-urt" client (the > "plain vanilla" version mostly, _not_ "bumpy"). The source code for > this is distributed as one big patch file that you apply to ioquake3 > trunk (revision 1803 currently). > > http://www.www0.org/w/Optimized_executable%3b_builds_of_ioq3_engine_for_urt > > I have not used this client on FreeBSD, however. You may need to > adjust the sound stuff, like for example change some of the defaults > to turn specific sound features off for FreeBSD. I think I saw that before and I even tried to find some kind of official source distribution. It appears every feedback that does not consist of pure hero worship will be met with burning hate. Release engineering is their enemy. I don't think I'll ever stick my nose in there again. I'll try that patch, but I don't expect it will meet acceptable standards. > Now I _am_ running server binaries on FreeBSD and in fact I pretty > much maintain the UrT server code (I like to think of myself that way, > and in fact quite a few UrT servers use my code). For server admins > it's important to apply some hacky patches to ioquake3 so that > exploits would not be triggered. There are 2 versions of the server > code that I'm maintaining currently: ioUrTded (older, tried and > proven, based on original source released with 4.1) and ioq3ded-UrT > (newer, not tested for an extended period of time, based on ioquake3 > 1.36). I'm now moving all of my servers over to use ioq3ded-UrT (my > servers are running FreeBSD of course :-) ). > > More info about ioUrTded is here: http://daffy.nerius.com/urtserver/ > More info about ioq3ded-UrT is here: > http://forums.urbanterror.info/topic/24118-ioq3ded-urt-improved-server-binary/ I don't understand this separation of server and client. They /should/ all contain the same game logic, shouldn't they? What's the reason behind this? > The 64 bit binaries for the server will run on FreeBSD, but they will > consume twice as much CPU as the 32 bit binaries running on a 64 bit > OS. Don't ask me why, but it's true (and the same applies to Linux > from my tests). When I hypothesized my theories on the IRC channel as > to why this might be happening, I nearly got castrated. :-P Well, there's been a discussion about pointer handling here. There's some optimization potential, I even intended to give it a go, it shouldn't be a lot of work, but its priority on my TODO list is not high enough. > One last thing. That Frozen Sand announced closing the source - that > will only apply far into the future, probably. Don't expect them to > release the next version of closed-source UrT anytime soon. Even when > they do release the new closed-source version, the old 4.1 may still > remain popular for some months. So I wouldn't drop any kind of > support for UrT 4.1 in the near future. Recent ioq3 is way better what was in the ports before (something from 2007?). I might spice it up with patches later - or not. Quality must be sufficient so that I won't have to deal with these people. Any way, I don't intend to drop UrT 4.1 support. In deed I feel that my move was is large improvement. However, I strongly doubt that there will be 4.2 support. > By the way, I compile all of my FreeBSD server binaries by hand, not > using ports. Are you talking about urban terror or about server binaries generally? Regards _______________________________________________ ioquake3 mailing list ioquake3@lists.ioquake.org http://lists.ioquake.org/listinfo.cgi/ioquake3-ioquake.org By sending this message I agree to love ioquake3 and libsdl.
