Jump to content
Spartans Home

KalXen~SPARTA~

5-Spartiates
  • Posts

    3,088
  • Joined

  • Last visited

  • Days Won

    3

Posts posted by KalXen~SPARTA~

  1. so I dont think it is a Vista problem. it is a 64 bit problem. Heres an image of the error.

    User posted image

     

    Weird - look at the popup window - it says "Unsupported 16 bit application"....

     

    I guess it runs better on Windows 2.0 or MS-DOS.

  2. I would definitely like to try something in the large combat scale. I.e. one Major town/area offensive in which a single M119 or A-10 do not tip the balance of the attack... If someone can find a tried/true map that provides this, bring it forward and we can get it loaded on a server for a try.

  3. Check out these 2 articles:

    Arma 2 tested: Benchmarks on 18 CPUs

    Arma 2: Benchmarks on multiple video cards.

     

    Note: Notice that on high settings, NO video card does past 22fps. And in every forum people complain about Arma 2's performance. Crysis is the benchmark for systems nowadays it seems.

     

     

    My CPU (C2D 6400) would be listed on the very bottom of that hardware list and it runs okay when normal/low.. But I think I may move to an i7 64bit Windows 7 setup eventually because its time to upgrade and move on. I have always been a nVidia guy, but pondering ATI.

  4. I just don't see the need to Whisper to All the members of a Squad, that's why the Squad leader is there, and the can get the info they need via the Channel Commander route.

     

    The structure Durka is proposing is IMHO a sound basis for good comms, I am just not convinced that as a squad member I need to hear what the mission commander or anyone else is telling my Squad leader.

     

    The difficulty I do recognise is that the other squad leaders then become involved in Comms not necessarily intended for them, so I suppose it boils down to Information Overload at Squad or Command level.

     

    Keep in mind, Teamspeak doesn't do preferential channels and mute one while another speaks - hence the 'chatter'. If commander only speaks to the individual in channel, the others in the channel do not know he is being spoken to and may talk at the same time. In the squad leaders ear, this is all garble. By letting us her would reduce the need for someone to yell "Clear Comms" and ask the person to repeat their statement. We would all hear that commander is trying to talk and people would naturally be quieter.

  5. Durka, Medic and a handful of us did some late night tactical in hopes of calming some nerves from some Domination babysitting. I initially commanded with Durka as 2IC, but my connectivity and flu coughing fits pretty much meant he was in charge. The 1st town (and coincidentally the only town we fought) was Gorka, which wa hosting the 2009 Russian war Olympics. The amount of armor and attack helicoptors were more than I've ever seen before. Our death rate was so high it became comical. At one point we had all fallen back to a certain barn. The barn was the local armor hangout and our bodies piled high. After 2 hours and several total team wipes we were able to finish the town. It was too late for many of us and we dropped out.

     

    Want to thank Durka for keeping the plan straight and making the slaughter enjoyable romp. The best quote was frim either Durka or Medic when a new player joined and asked what kit to play - "pick Rambo 1 with the exploding arrows cus these helicoptors are insane."

  6. Once Z3no loads up the next version I will test it for ya.

     

    One thing I just noticed on my test server - The FARP message says it cannot be deployed within 1500m of main objective. Yes, I can drive up to 1800 away still not be able to deploy. Math issue?

  7. Right on, I didn't know that home computers could successfully host multiplayer, I thought servers were required. I'll try it out soon enough for an ad-hoc tactical mission.

     

    I would take the word "successfully" out of that sentence. :P

     

    While it is possible to run a server from home, there are many factors that will impact your performance to a point where it is unplayable.

     

    1) Server itself - Arma isn't very memory intensive (@700 meg resident), but it does enjoy taking over your CPU. I'd suggest at last a Core 2 Duo, or Quad if you plan to do anything else on the box.

     

    2) Network - depending on how you tweak your arma.cfg/server.cfg, Arma will gladly suck up your bandwidth. Keep in mind that download speed doesn't equate to bandwidth. So just because you can reach something with a very short ping, doesn't mean your connection or provider is going to give you enough bandwidth to host multiple sessions to your box. I'd suggest @ 50k up/down for each person connecting to the server. The Sparta server consistently uses 1Meg upload, and 1-3 Meg download in bandwidth per second.

     

    3) IP - dedicated servers have static IP addresses allowing people to always know where to go to join up. Most home internet is dynamic, and your IP could change while people are trying to use your servers causing connection issues. You could use things like dyndns.org to help with this, but I think Arma is IP based, and not hostname based.

×
×
  • Create New...