ClaytoniousRex

Yes, this is because the settings files were moved to the user's home directory, so it's a one-time thing for the 0.9.43 update (not something that will happen on every update).

kmead, you may be experiencing the same kind of "empty server list" bug that nirse and poesel71 are having (see: here ). Are you, by chance, running Ubuntu or another Debian-based Linux?

Can you show us the output of iptables -L now, poesel?

Do you mean some kind of scripting so you can program the bots?

Since you have an excellent connection and it's only hitting you, we're definitely looking at a problem in the DropTeam client. Just before this happens, do you experience any kind of severe client-side freeze, like everything locks up for a few seconds or longer?

... is now available via Update. On Windows, use Start/Programs/Battlefront/DropTeam Public Test/Game Updater to get it. On Mac OS X, double click on the Update icon in /Applications. On Linux, use the runUpdate.sh script. Fixes in 0.9.43: </font> Settings are now stored in each user's home directory</font>Fixed crash when trying to continue to next scenario when running on less capable OpenGL drivers (those that provide OpenGL < 1.5)</font>Fixed incorrect "version mismatch" error</font>Fixed server crash when telling a bot to extract in a vehicle that the bot can't drive (such as the Viper)</font>Fixed server crash when bots were given some kinds of drop instructions</font>Fixed chat messages sometimes failing to reach all clients</font>Fixed getting stuck in macro and other windows</font>Fixed destroyed buildings appearing to still be standing to clients who connect after the buildings were destroyed</font>Changed text for "End Scenario" and "Quit Game" buttons</font>Bots no longer keep their drop instructions from one scenario to the next</font>Added Favorites, Last Connected, and Filtering to the server list</font>Improved reliability of server list (won't intermittently leave out servers anymore)</font>Increased audible distance of guns and some explosions</font>Dont allow votes to kick bots</font>Slightly increased penetration of 120mm HEAT</font>Slightly reduced armor for Hurricane</font>Show friendly fire with explicit "TEAMKILL" message</font>Improved images for Drop Window</font>Automatic Updating from within game</font>Escape key now exits the game while in the Lobby</font>

Your analysis of how it works is basically correct. This is of course only problematic when you're suffering from packet loss but since all of our servers for this public test are clustered in one place, there are plenty of players suffering from packet loss (the usual fix would be to pick a better server to play on). I think you're right that this is what a lot of people run into when they say they're "spinning out". I'll talk with Stan (Zen Master of all of this control/user input code) and see what we can do about it. Incidentally, what kind of packet loss do you have? Is it usually 0%? (I mean as reported by ping, for example).

You can't refresh the list in-game. I meant that, when this happens, and you can't get the server to respond and eventually end up having to quit back to the lobby, that you can then hit the refresh button once you're in the lobby and see if the server you were on is still there. It would also be very helpful to know how good (or bad) your connection to the server is. Unfortunately, all of our servers are clustered in the southwest USA for this public test, which is a real problem for some players. Can you also try a ping -t to tbg.krypt.com and to tbgsoftware.com and post the results of a good 20 or so pings to each one? Thanks!

Thanks, Yurch. It's fixed, but didn't make it in time for 0.9.43. It will be in the next update, though.

What I meant was: did you hit the "Send" button on that error report dialog? Doing that will give us the log files from your crash so we can diagnose the problem for you. If that's not working for any reason, then you can start by emailing your DropTeam.log to support@tbgsoftware.com. The chances are very high that you simply need to install the latest Catalyst drivers for your ATI card, but your DropTeam.log will help verify this.

This is not a problem with GLX itself - this just means that you don't have a mode line for an 800x600 video mode in your Xorg.conf (or XConfig-4 depending on what version of X Windows you're running). You simply need to add a 800x600 mode line. Feel free to shout if you need some more guidance on how to do this.

Reproducible is how we like 'em. Fixed for 0.9.43.

Watson (or Crick, whichever you *really* are...), have you noticed any particular situations in the game that are common when this happens to you? For example, is it when votes are in progress, when fire missions are happening, or anything like that? When this happens, if you refresh the server list, is the server you were playing on now gone from the list (you might need to refresh more than once to be sure it's gone). If so, then this is actually a server crash - the server died and left you hanging. If the server is still there, then it simply stopped communicating with you. It would be very helpful to know which of these you're running into.

Hi, Dave. Please email your DropTeam.log to support@tbgsoftware.com. If you're playing on Windows, it will be in the \bin subdirectory.

MBT's are only easy to kill when being incompetently played. But in that case, anything's easy to kill. A MBT that keeps its front armor facing you, holds a good position, and uses the right kind of ammo on you, is definitely going to defeat your Paladin-EW 100% of the time. The only way you're going to beat it is to coordinate with your team to force it to expose its flank to one of you. In that case, you've earned the kill.

Yes, some diagramming tools on the tac display are definitely on our list. One thing to keep in mind, LtCol, is that the Hermes is, in fact, a mobile sensor jammer just as you described. Attaching one of these to a platoon is *the* way to do that surprise left hook you're talking about. The Hermes (called Paladin EWV in your Drop Window) provides sensor jamming to nearby friendlies as well as air defense. These nearby friendlies: 1. Do not show up on the enemy's minimap or tac display 2. Do not have those damnable red pippers above them in the enemy's HUD In private beta testing, Harv's Golden Rule was that everyone be under Hermes cover - ALWAYS, but we're not all quite that draconian. One really useful tactic is to have part of your team engage the enemy frontally (but from a comfortable distance) with Thors while a seperate group attacks from a flank or the rear with Hermes cover. The enemy will usually focus on the Thors and be completely blindsided by the encroaching group that's jammed. People really become surprisingly dependent on those red pippers in the HUD. We couldn't agree with you more that tactics is the way to have fun - not just driving and shooting. This all makes your idea of camouflaging vehicles and turrets even better.

Hi, John. You might need to try a different mirror. It's either corrupt on the mirror that you fetched it from or your download corrupted it - in either case your best bet is to download from somewhere else.

Nirse, what kind of firewall(s) are you behind (on the router and/or in the OS?) Any ports blocked on the router or in software on your Gentoo? Port forwarding should not be required.

You shouldn't have to export LD_LIBRARY_PATH since runClient.sh is already setting LD_LIBRARY_PATH when it runs the executable (but doing your export shouldn't hurt, either). Can you post the contents of Dropteam.log (in the bin directory) after one of these failed attempts to run?

Did you send the error report, Hardail?

We're still working on this problem, Oren. The delay in fixing this is that it's hard to reproduce. In fact, none of our development machines exhibit this behavior, so we're doing "long distance" debugging with a volunteer who has the same problem you've described here. It takes a long time to isolate and fix this problem this way, but we're getting closer.

The release version contains a single player skirmish mode and a single player campaign. These play modes do not require an Internet connection. To play network games, you need to have an Internet connection.

Giminar, can you time the loading of a scenario when this happens and give us the actual number of minutes it takes to load the scenario? (We need this time when it fails, not when you get into a game without the "Server not Responding" message).

Nothing's there to prevent that at all (on the client-side anyway), because this is also the same mechanism by which players would create their own custom camouflage textures or unit insignia or whatever else they like. Neon paint schemes aren't really *that* helpful to the cheater, see-through trees would actually lie to the cheater as often as help him (depending on what angle he was looking through them from - they're not depth sorted). And no matter what you do, cheaters can always install client-side OpenGL hacks that do things like force wireframe graphics or inject new textures in place of existing ones without the program's knowledge so they can see through things regardless of how the game works.

Nirse, what's you username in DropTeam?