Jump to content

=-A*C-=NicO

Member
  • Content Count

    26
  • Joined

  • Last visited

  • Medals

Posts posted by =-A*C-=NicO


  1. 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


  2. 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


  3. Wow a lot of questions, I'll try to answer to everything :

    Sleep;1841489']bugs we found that I remember from yesterdays playthrough:

    One of our guys became invincible for quite some time' date=' he only realized it when a zu started bouncing him around the battlefield and he didnt die. (i was wondering how he stayed alive thru some of the situatuations we found ourselves in :P)[/quote']

    Never seen this bug before. Hope Code34 will find a reason to that (he's the coder, I'm a tester ^^).

    The teamkiller warning trumpet has to go please' date=' it is HIGHLY annoying and i had to kick a few people for accidental tks just to make it quit. Just the little pop up text is plenty of shame for them IMO.[/quote']

    There is a bug actually that makes the trumpet never stop, the TK has to Esc/Abandon to be killed and then revived, it stops the annoying thing.

    We'll try to fix this ASAP.

    The IED sound also is pretty annoying and I'm not sure where this comes from to use that in the first place. An ied is supposed to be a suprise so having a sound by one hurts the experience and is a bit confusing to new guys.

    Also on the IEd thing' date=' which Ied script are you guys using, is it the one where the engineer has to crawl up to it to deactivate it? We had one right beside one of the mh6's to be rescued only to fail the mission when the engi crawled up to the ied and it exploded. He said a very very quick menu came up with a timer then the explosion. He possibly did it wrong tho so no biggie.[/quote']

    The IED implementation is a bit special here, everyone can detect it (it's always an object), but only engineers can desactivate it. I don't really know if you have to crawl, the script used has been created from scratch AFAIK, but as I don't play enginner I won't be able to help you on this one.

    You may have been in a buggy situation last time, as every mission is randomly generated, the IED was too close from the objective.

    I'll report back with more as i remember / find them. This is an excellent mission that is very well made. The base alone is sooo sexy besides the one tower I metioned at the heli pads. Keep up the good work!:yay:

    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).

    Also if we steal enemy weapons, a.k.a. mortar tubes from them will they be cleaned up and or dissapear if we put them in boxes or vehicles?

    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.


  4. Not touching it for a while but will add in a random air patrol script in a few weeks.

    Don't forget to share it with us on this thread! Maybe other teams are interested by air patrols.

    Want to get to Team 1 1st :p

    Btw whats the highest you have got? We will still Team 5 Noob playing on veteran and private setting.

    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.


  5. Excellent mission found one bug when you have to blow up the AH you get the team killer screen and get minus points.

    We've had this problem too, we're looking for a solution ATM.

    When moving to a new mission does destroying the additional assets (radio/camps/factories) contribute to anything?

    Radio -> no more reinforcements from the main ennemy base (infantry)

    Other -> only points if my memory is OK

    Whats the difference between Private and Public game in parameters?

    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!!" ^^


  6. So there's no major benefits to upgrade? Still no fix for MP weapon selection in briefing?

    Don't know what you"re talking about, but is this a client side or server side problem? From what I can tell you, client side performances are better in 1.54 than in 1.55/56. So the overall experience is best on 1.54, but you will probably run into trouble if you use the latest ACE for example (if you're on vanilla, stay with 1.54).

    Do you have 1 core server or is it a setup problem? I run 1.54 on dualcore, server's more than willing to use both.

    Yep true, we own a corei5 750 (4 cores), and all of them are used. But the main thread of the game uses 100% of 1 core, while the others are quite unused. We ran several test : Windows dedi vs Linux dedi, and the multithreading on Linux is awful compared to Windows. That's a known issue that will probably not be fixed. The point is that we don't want to use an MS box for several reasons, so we're stuck with a bad dedi...

    Take a look at an ingame typical load :

    Charge_serveur.JPG


  7. if you start the server just with ./server you will run into this trouble, you need to overhand always the parameters. But why you start it without the startscript?

    Running directly from the binary can be interesting if you experience a startup crash / nostart, but you have to state basic parameters (check the startup script - they are defined there).

    IE (just an example, do not remember everything) :

    ./server -server -config=server.cfg -profile=xxxx -port=2302


  8. Here is what I posted about the latest beta patch :

    Hi everyone,

    I'm a member of the French team Air Commando =[A*C]=.

    So let's talk about performance : since the release of the 1.55 patch, we've been really angry towards Bohemia since our client side part of the game has became quite unplayable, with many FPS drops and a real loss in reactivity). We've tried many tweaks, we lowered our graphic specs, deleted the CFG, but we couldn't get the smoothness of the 1.54. Until yesterday.

    I own a core2duo 6400 and an ATI 4890 (not bleeding edge I admit, but powerfull enough for many things) as a lot of my teammates, and totally lost, I tried the -exThreads=7 option, as a last try before giving up. Although it is not recommanded on a dual core, that was my only remaining option. And guess what ? I was running the 1.55 on a 15 FPS basis with many drops, and know after a few tests, I can say that it is now twice the previous value : 25-30 FPS (with even 60 sometimes !!! and for the lowest 15-20 in a few zones). It is WAY MORE ACCEPTABLE THAN BEFORE. My game is now playable again!

    What I understood after a few readings is that -exThreads=7 cannot be handled by some low end dual core, but the 6400 is powerfull enough to cope with that. Other people who tried it with me told me the same, huge gain in smoothness, and in some cases in FPS too.

    Does any dual core owner can confirm this?


  9. Yes, I use it all the time...give it a try and you will be surprised.

    I'll try this tonight to update our server, thanks for the piece of advice ^^

    I think BI sees the Linux version as a needed evil, that’s why we get only betas and servers who crashing with segmentation faults instead of error handling...

    That's what I understood, but really there are only advantages of running a Linux box vs Windows. Cheap, reliable, easy to administer, fine grain for config, many tools for different needs, bash scripts etc... (no troll inside)

    I just can't imagine running Windows on our server. But a lot of dedicated server games today won't run or badly on Linux, that's really sad.

    PS : we do not encounter so many crashes (it mainly happens when a guy joins the server with a bad modset or outdated mods), but the overall performance are way behind the Windows ones


  10. Still grass blinking with official 1.56. The vehicles are also changing LODs way too quickly with normal object details, you can only step about 10m back and those are already with very low details. At the same time, soldiers walking next to it look 100% good & normal. Also with high object details the vehicle LOD changeing is too fast. There is only some few vehicles normally in missions so those distances to change LOD could be about 10 times bigger, I think.

    Confirmed. Although quality was not my main concern, because of smoothness, there are still many visual weird things. But the Z-fighting is now really reduced towards 1.54, that's a good point! Now let's fix those textures and LODs problems, and it will be fine =)


  11. rsync -avzyh –delete /home/arma/arma2server/* armauser@123.123.123.123:/home/arma/arma2server/

    Is rsync able to work with lowered case filenames on the server ? The manpage of rsync that "fuzzy" option makes it work with similar filenames if it doesn't find the same. That would be really nice, no need to manually determine which files has changed...

    why does the server not come with these 116 MB files (maybe from a p2p source) and that’s it? why is this process so complicated?

    Very good question - plus this file could be used for both Windows and Linux dedicated. Clearly we only own personnal xDSL or cable lines, with a very limited upload. Download is ok, but upload....


  12. Ok I have to fire up md5sum et let see what has changed... A 3 to 4 hours process, hum well hope this is worth it.

    Can we have a changelog, just to help us monitor improvements towards 1.55? Anything new about multithreading ? We rent a CoreI5 750 (4 physical cores) with 8G RAM, but server's FPS oscillate between 10 and 20...

    Typical load while playing (1.54 & 1.55) :

    Charge_serveur.JPG

    Hope this point will be improved!

    So I'll make tests as soon as everyone in my team has updated their game, and give you a report : 1.54-5 vs 1.56.


  13. My point of view is that if -exThreads=7 works on my modest hardware, it should work for nearly every Core2duo/quad Core-i3/5/7 (and AMD equivalent procs) - so it should probably be the default value, but we need more testing about that. But as stated before, if you have a quad the game engine should - in theory - already use the good value for this parameter.

    What I'd like to know is : do everyone feel the same as me? Is 7 the overall good value? If true, BIS should use it as a default, because with 1.55 and my old school hardware, the gaming experience is really scarying, unless I use -exThreads=7.

    PS : I could drive some tests yesterday, the game is more playable, even if I can feel huge FPS drops in some cities - but that is not a new behavior of the game engine. I prefer a drop starting from 40 FPS than starting from 15 =)


  14. I must admit, a so huge difference for a single option seems strange, but believe me, I was seriously thinking about giving up. We're continuing tests tonight so I'll be able to tell you if the magic remains.

    Here is my full config :

    Asus P5B-E Plus

    Core2duo E6400

    ATI 4890 VaporX 1GB

    2GB Corsair RAM

    Windows 7 64b

    All graphical options on normal, ViewDistance 2500m, Graphic Memory on Very High

    @rscarrab : yes true, for an i7 exThreads should be right for you

×