After installation of games/iourbanterror the client starts calling ioUrbanTerror but the list of selectable hosts keeps empty. Refreshing the server list for gameplay lists at top of the window ~ 750 servers (confirmed with a working 4.1 installation on the same box), but the server seletor windows stays empty. Trying to start a server with a fresh installation taking a working 4.1 configuration server.cfg ends up in "Engine linkage error #31". I also realized that with the new 4.2.014 client/server, there is no installation of zpak000.pk3, zpak000_assets.pk3 and zpak0001_assets.pk3 in the user's .ioUrbanTerror/q3ut4 folder. When copying those files over from 4.1 installation on the same box, I'm able to get servers in the cleint's server list, but the client reports top be version 4.1 and fails with "Engine linkage error #31" when selecting a 4.2 remote server. What is wrong? Where to pick the proper zpak-files (they are ~ 1GB alltogether)?
Maintainer of games/iourbanterror, Please note that PR ports/181819 has just been submitted. If it contains a patch for an upgrade, an enhancement or a bug fix you agree on, reply to this email stating that you approve the patch and a committer will take care of it. The full text of the PR can be found at: http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/181819 -- Edwin Groothuis via the GNATS Auto Assign Tool edwin@FreeBSD.org
State Changed From-To: open->feedback Awaiting maintainers feedback (via the GNATS Auto Assign Tool)
I have no idea what's the problem so far (I can reproduce it, though). To get an upstream reaction I'll have to reproduce it using vanilla Q3A. The Urban Terror folks have decided that Open Source is the enemy. -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail?
What kind of sense does it make to have this port still "alive" even if one isn't able to start a local server? Please mark it "broken" until it is working again. I find it inappropriate having a useless port without warning the users about some flaws. It seems to be a FreeBSD specific problem, since on some Linux Ubuntu and Suse boxes version 4.0.14 (and the new 4.0.15) seem to work as expected.
ohartman@ has a point. Is this report still valid? If so, it sounds like we do need to mark it valid. Dominic, please respond quickly to this. If I don't hear anything in a short time or if I get confirmation from ohartman, I'll mark it broken if it's indeed busted.
s/mark it valid/mark it broken/
This issue was fixed with the latest update by switching to an older base engine.
Thanks! Oliver, that just saved you some time. Closing this...