DrWoood

I have noticed that the dropships are much easier to shoot down than they used to be - unless I micro-manage the bots they tend to get shot down alot and I run out of drop ships. One time after I ran out of dropships, I tried inserting a Viper, but I could not insert it outside of the deployment zone. I think it should be able to be inserted outside the deployment zone - being able to fly itself. I could insert it in the deployment zone, but then it would appear at ground level and quickly get immobilized (ie by colliding with the ground and flipping over).

I was playing about 6 hours ago and the input was extremely sticky/laggy. My opponent (who was elsewhere) was having the same problem. Also just before the end of a game the bots would get very talkative.

Thanks for the tip - that would be 6am Monday morning in Australia, could be an interesting way to start the week

It might be good to have an option like 'I want to play a game' where other players can see how many people want to play game. If someone joins a server people with that setting can be alerted about it and be more likely to join the game. Might require a bit of work on the server side I guess... I miss those days (around when the public test was being done) when we would often get many players and fierce battles. Those were the days that I would sometimes not get to bed till 10am..

Unfortunately at the moment at times there are not quite enough people playing on the servers to provide the required critical mass for really good gameplay. Let me request/suggest for a little utility that runs in the background of windows/linux/OsX which alerts the user of what servers are available and how many people are on them. Hopefully this will decrease the critical mass required for readily available multiplayer games as well as really exciting games with many players and fun teamwork :cool:

It thats that with the various updates it takes more HE to take out a tower now. In a recent game it took me about 50 76mm HE, 10 120mm HE, and some 20mm HE in order to do it. The 120mm HE seems stronger than the 76mm HE compared with earlier versions.

I used to have some problems with crashes which were sometimes preceded by strange video effects. I then updated the drivers to my video card, and all these problems disappeared.

Jammers and the Hermes are the best way of not getting seen in this game, both in offence, and offensive defence. To see where the enemy is, why not take the Viper for a ride?

More a bug to do with the updating process than 1.0 per se. I ran 0.9.93 and it prompted me for an update and I clicked Yes. It downloaded about 400 files, it seemed like 1.0 was being downloaded. When I quit and restarted I got a Windows error message with the message that it couldn't fine elicen40.dll. I noticed elicen40.dll was in the DropTeams's directory and when I copied it to the bin subdirectory I got a nice little prompt with a spiel and a box for the licence key etc. So it would be wise for the Update to place the dll in the bin subdirectory so it works. Due to the potential addictive nature of DropTeam and work commitments/life, I think I'll be waiting until Combat Mission Campaigns is pretty much done before I start playing DropTeam v1.0.0

Congratulations on 0.9.90!

After the previous post I had a play for a little while before Famite stopped responding. The increased limitation on various units will make things very interesting! :cool: Look forward to playing it more! Better be careful with that Hurricane!

I saw the post and did an update to 0.9.90. Still some serious ZoneAlarm issues I am afraid. If you are a ZoneAlarm user, you have to set the program control back to ticks for the relevant things (I did them all) otherwise there is a crash on initialisation which means I must reset the computer. On initialiasation it stopped doing anything (presumably because of ZoneAlarm creating a prompt that you cannot see because DropTeam is taking over the display. I was able to get the Task Manager on the second head (I don't think I could get the task manager otherwise) but wasn't able to kill the task or the process. After setting the Program Control settings in ZoneAlarm to 'allow' for DropTeam, things worked and was able to init DropTeam, get a list of servers, and briefly log in to server at the end of the game without problems. I then quit to do this post. It is lucky I suspected it was ZoneAlarm causing the problem.

I can't help but wonder how big infantry will appear considering how large the vehicles are. At the moment the paladins back doors look like they could fit at least two fire teams (although the spec on the website says only one).

I took over a bot in an Apollo KC-H as Water on Arpinum Station on the ice map. It said I was firing AP but HEAT was getting depleted and I was blowing up bots with HEAT. When I pressed = it changed to HE and displayed the ammo type correctly. I think I was in a Hermes before I took over the bot.

I'm already plotting on ways for infantry to be used for securing drop locations...

The other day while playing water on the ice field and waiting for blood to set up I gave some bots some drop requests which were too close to some hidden turrets. So I put the bots on 'autonomous' as fast as possible and then they started dropping near the base in the red zone! It was almost like the drop requests brought back the drop location persistence issue. Another problem I noticed is that if you make a drop request and change displays (from normal to tactical or vice versa) before clicking on where to drop, then drop doesn't register. I have soetimes noticed this when using the mercury and dropping jammers/turrets.

A small feature request: disable "Cannot take control because you are currently dropping." message when dropping jammers/turrets etc and trying to take control of a bot. This will speed up the command interface, and make some things less frustrating. While making things less frustrating isn't always good, in this case I think it is

It worked the fourth time, this time I told ZoneAlarm to allow Drop Team to act as a server, I don't know if that was what did it. Previously with updates I have had ZoneAlarm become the active task when asking for DropTeam to have permissions. It seems like now during loading and the main menu DropTeam won't allow other tasks to use the display so easily so things like ZoneAlarm and Task Manager don't appear. Incidentally, when running a second monitor DropTeam will make sure that the mouse pointer stays on the screen during Loading and the Main Menu, but during play, the mouse can move off the screen running dropteam, making driving and shooting difficult ( so I generally disable the second monitor when playing Drop Team).

When I try to initialise 0.9.45 the computer stops responding during the load screen and I have to restart the computer. The third time I tried I first told ZoneAlarm to allow DropTeam to use the internet, and I got to the DropTeam menu. When I clicked 'Refresh Servers' my computer crashed again. This time I had my second monitor running and was able to bring up the task manager in the second monitor but I wasn't able to kill the DropTeam task, even ending the process didn't work (so I had to reset again). I'm about to try for a fourth time.

A few times I have connected during the setup phase and been able to see the enemies jammers on the tactical display. Usually when this happens I have previously had to disconnect during setup or had dropteam crash, then logged back in again.

It would be nice if the list of team members in the top left of the tactical display also said what vehicle they had - not having to click on each unit would speed up getting this sort of information and allow more time for driving, giving orders, observing, etc.

I think it would be really cool to have a 'drop once' request for bots which would be exactly like a drop request except the bot is set to 'autonomous' after the drop. This would be especially handy when wanting to do a drop that is a bit risky or when trying to juggle a whole lot of things at once. It would also be good so have something similar which isn't directed at a particular bot and is a once only drop request for the next available autonomous bot.

Account settings working fine with 0.9.44. Incidentally, on my computer HOMEPATH=\

I just updated to ATI technologies 8.231.0.0 (21/2/2006) and shadows is working fine :cool:

An interesting development with version 0.9.43: If I select shadows now, when a game inits (after loading cachine etc. and pressing return) the image of the battlefield and list of who is on what team is there still for a second and then I get a black screen of death! Wow! The monitor goes black and the LED goes from green to orange like it would if there was no input. Ctrl-Alt-Delete and Alt-Tab don't do anything and I have to press reset to restart the computer. I have reproduced this three times at different resolutions and it only happens when shadows is enabled. I suspect that such a spectacular crash would be something wrong with my firmware. My driver is called 'ASUS A9550 Series' with driver provider ATI Technologies, date 24/05/2005 version 6.14.10.6542 . I will try updating or replacing it and provide a post when I find out how that goes.