=-A*C-=NicO

I'm talking about it with Code ATM, he says it's an unusual bug that caused the log files to grow like this. So all of you may run the mission without any issue. By the way, it's important to fix the bug ASAP.

Hi everyone. We've got a script error in the latest WIT (1.18) that causes log files to explode (we currently have more than 20Gb of logs). Code seems to have found what goes wrong and is working hard to solve the problem. We'll post a new version as soon as everything's fine. We're really sorry for this bug and we apologize for the damages that could be done on your servers. Please use the previous version meanwhile. =[A*C]= NicO

I've mirrored the patch on our server, try : http://serveur.air-commando.org/public/ARMA2_OA_Build_77819.zip It's a 100Mb line, it should be fast. Nico

Now you're addicted dudes: -try a good'ol Domi or any other coop mission. -see how the AI is dumb. -Profit ^^ NicO

Hi, I've ran some tests with the new Atoc option, and I must say that it's quite impressive!! The new rendering is more realistic, and the overhead is manageable. But there is a problem with user-made maps (at least with Lingor), there is no change between Atoc ON / OFF. I suppose that you changed some LODS / 3D models / textures with the new patch, so here is my question : could you post some instructions for map makers to update their content, so that we can have the same result, whatever map we use? Thanks a lot for this huge improvement, hope that every map will be able to profit from this!! NicO

You should either : -change your pilot -reconsider your landing zones Or both!!! :p

Best level is 1- Elite, we've reached it 2 or 3 times. It stops the mission, you win ^^ The worst level stops the mission too, but then you loose !

Both version are included in the file ! :)

Wow a lot of questions, I'll try to answer to everything : Hehehe thanks for =[Air Commando]= Team' date=' we've worked a lot on this map (especially Code34) and we've fine tuned it to meet our requirements. The base has been made by Ei8ght and posted on Armaholic. Be patient, we're testing a Lingor version, maybe it will be released some day (Lingor is a very sexy map, after having travelled for monthes on Takistan - it gives more close combat). I thinks that every ennemy object / unit disapears when you leave the red zone, so yeah stealing things won't work. Thanks for your reports everyone, we'll try to improve things to make WIT a very good dynamic teamplay experience.

Don't forget to share it with us on this thread! Maybe other teams are interested by air patrols. Hum well of course you can get Elite (it will end the mission), it happened to us a few times. We play regularly on level 2 or 3. Here are some tricks to reach the top : -Teamplay : that's the main point. Play with your teammates, use revive, strike quickly and strongly, get out of the zone when objective is completed. If you play with more than 10-12 teammates, split in two teams : attack and support. The latter will stay a good distance to burn armored and snipe mortars / static defenses / snipers. -Be elite! It seems obvious, but don't get killed, always check your six (even 3 and 9), don't be static. Every AI moves a lot, and reinforcements come often while the antenna is active. If you're down, wait for a medic, do not use Return to Base. Moreover, be careful when moving in vehicles, there are some ambushes and IEDs. As an example, if each player has been shot down more than 6 or 7 times for 10 missions, you will have a bad score. The "killed" parameter is more important than "frags". -Don't kill civilans -Do not rush the objective, keep a good formation to protect you and your team. This mission is very different from a Domi, that's why you must adapt your way of thinking and acting. On a Domi, every player rushes the objective as a lone wolf, AI is very dumb and you can get very high frags in a few minutes. Moreover it is not important if you take risks because you can come back on the battlefield with mobile respawns / parachutes. Here, you have to take into account that a death is not normal, and that the AI is more subtle than you are used to.

Would do it if I knew how to develop scripts ^^ It must exist some script that can do that for you, take a look on armaholic in the script section, or in the Domi. Or ask someone who knows how to do =)

WIT is meant to be played on the ground. We don't really use air items (except for transport). You can try to add this feature in your own version, but I don't think you'll get support from Code34. Maybe you should take a look at Domi's scripts. Ei8ght... no comment :p

We've had this problem too, we're looking for a solution ATM. Radio -> no more reinforcements from the main ennemy base (infantry) Other -> only points if my memory is OK The public game is "smoother" on negative points. If players do not behave correctly (ie teamplay), you will lose less points and the team score won't fall as quick as in private game - you cannot ask the average player to understand all the rules immediately. Private game is meant to be played by a well trained team, using TS or Mumble for comms. Basically, a team shouldn't use the RTB button, only medics on the battlefield. Hope this will help. I belong to Code34's team, as a result I've played a lot on this mission, so if you have any other question regarding gameplay / behaviour / bugs I'll be glad to share my experience. PS : I'd like to put some emphasis on a very cool feature, it's the automatic weapon crate generation. If you use a mod like Hexagon, BWmod or RH for example, the crate will be filled with all the weapons available. You do not have to edit scripts to get what you want. It's pretty cool with Robert Hammer's work for example, you just have to activate it on the server (and the clients of course), and voila! Everything is inside the box. It helps to make some "themes" for a play, ie "tonight guys we're playing FAMAS" or "tonight G36 party!!" ^^

How can you explain that multithreading is really better on Windows? Amdahl's law is the same on both platform...

I remember I heard that it was an issue with multithreading librairies, do you confirm? If this is it - it will be hard to solve, right?