Jump to content

kman

Donator
  • Posts

    193
  • Joined

  • Last visited

  • Donations

    30.00 GBP 

Posts posted by kman

  1. Just played LYTHIUM whe mission won't end.

     

    Gauntlet version: 54_103_LYTHIUM

     

    mission: destroy ammunition depot and clear enemies.

     

    The ammo depot was blown up multiple times by explosives - the stack of crates representing it was smoking.

    AO was cleared (althou ambient spawns keep poping back in)

     

    I'm not sure if the crates representing ammo are bugged, or if there was some lone enemy hiding.

     

    PS: LYTHIUM does not seem to have any CAS hellicopters - not sure if intended.

  2. Noticed the same pattern lately - unfortunately A LOT.

     

    1) MAT filled even when not warranted
    People log in lobby and have to see, that Aplha squad looks like Swiss cheese, yet they fill MAT.
    Worse - sometimes fill MAT even when ASL is not present.

     

    2) Overuse of HE.
    MAT purpose is to deal primarily with enemy armored vehicles, not to play line-of-sight mortar support, unless SPECIFICALY instructed to by command.

     

    3) Giving sh** about command structure
    If you joined MAT - a support unit - when ASL is not present, then you are under command of Alpha1 Team Lead.
    You are not independent kaboom squad.

     

     

    I can't stress enough, how does presence of MAT on almost empty server discourages me from logging in as Teamlead, and I bet its the same for others who want to help with more organised gameplay.

  3. It's fine man :)

     

    Just dont get too riled up by comms-overloads. Its without a doubt most annoyning part of being ASL.

     

    Too many ppl talking on short-range? Remind Team leaders they should instruct their team to talk to them directly and ideally only TL's should use short-range to talk to each other and SL.

     

    Too many chat on long-range? Well, there its up to you to shout down vortex pilots that long-range is primarily YOUR channel to call upon other elements, not THEIR channel to vent every idea or comment.

  4. It's a radio frequency jammer. It is supposed to jamm transmissions in vicinity, making RCIED (remote controlled IEDs) triggered by radio/wi-fi/mobile phone unable to receive detonation signal, while jamming source (vehicle) is in vicinity.

     

    It *MIGHT* protect against IEDs triggered by passive sensors (pressure plate, movement detection, laser trigger), but only if the sensor delivers trigger signal to the IED by wireless. If it's by metalic wire - which is more likely - it will not help.

     

    I am not sure, if DUKE can IRL interferre with comm systems of vehicle's crew. I suppose it depends on how aggressively it's currently configured.

    In ARMA, there is no configuration and it does not interfere with comms AFAIK.

  5. 3 hours ago, Blue-958- said:

    All it usually takes is someone giving a loud 'Lets get going' to give everyone the kick up the arse they need. Most of the time people are procrastinating because they think they are waiting for a plan or transpot etc, when everyone does this is when the problem starts. Of course it helps if teamleads and squad leads hurry everyone along as well.

     

    I agree.

     

    When the troops are slacking around its 8/10 because command is slacking around. But remember, they too sometimes need to go AFK..

     

    Rest 2/10 are disconnects in command structure / vortex or re-slotting due to multiple players leaving/joining, that can't be rly prevented.

  6. Great mission, thx Benjamin

     

    for a feedback:

    • there were some resupply issues (mostly when we ran out of AT) and that radio bug, where radios taken from spawned Arsenal did not worked - I would probably avoid spawning Arsenal during missions altogether, it creates various problems. Resupply crates are safer. Can they be perhaps pre-prepared as part of mission file and placed somewhere out of AO, so Zeus can just drag&drop them when deemed appropriate?
    • I don't like friendly AI troops. They create confusion on battlefield because you can't tell them from enemy at distance.
      • they move like AI
      • they don't communicate
      • they are not on CTAB

    Other than this, all went smooth.

     

     

  7. some of my thoughts:

     

    AR Assistant

     

    should carry Entrenching Tool and Rangefinder.

     

    When entrenching is needed, assistant digs while AR covers.

    When long-range supression is needed, assistant calls target(s), their bearing, their range and wind direction/strength to maximise AR's effectivity.

    (technicaly the same as spotter does for Sniper)

     

    AR

    should in my opinion carry sidearm - directly oposite to what Retivis said ;)

    If the AR loses teamates during fighting, he becomes extremely vulnerable during reloading / weapon jamms, much more so than standard rifleman

     

     

    PS: TBH the entrenching tool in ACE seems very lightweight to me (too much?), so I include it in all loadouts, althou technicaly I think that FTL and AR should never be the ones digging trechnes unless unit is completely out of combat and other members are able to do so

    ..and I'm always breaking this rule while FTLing - against my own better judgement - because I'm compulsive-obsessive manic miner.. :ph34r:

  8. Personaly, I find biggest problems with ASL to be comms overload.

    If ASL would only hear his FTLs on short range and Vortex+MAT on long range it would be much better.

     

    I have seen some ASL to do this by requesting FTLs to join secondary channel - usually 50.1

    The problem is, the procedure to do this with radio isn't very user friendly and it would have to be repeated by every FTL joining game.

     

    Since default frequencies are assigned to radio by script, would it be possible to make Alfa FTLs automaticaly get secondary 50.1 and Bravo FTLs 51.1 presets?

     

    Is it possible to give different radio presets depending to where did person slotted to?

     

     

     

     

  9. Thx for the event Cryo, also to Benjamin and Copey for helping.

     

    If you ever plan to do some follow-up, I would be interested in CAS training in Enhanced server environment.

     

    While "dumb" missile choppers like Littlebird are pretty straithforward, I still dunno how to fire guided missiles from the other Littlebird(the 4+1 hellfire variant) and AH-64.

  10. This was great mission. The limited comms capabilities combined with very bad visibility made it pretty hectic but fun.

     

    I would definitely like to see something like this again.

    Perhaps not so dark, but I felt like the limited comms made for much better teamwork and fireteams sticking together.

  11. Nice round-up Radek.

     

    Do you also have some stats on their armor an vulnerability zones?

    It seems that unlike vanila ARMA, AWE mods do care where you hit the vehicle - often BRD survives suprising amount of AT where other times it goes down after just one.

     

     

  12. Shield is very nice indeed.

     

    As for the tweaking, apart from the civilian spawns, I noticed one other thing that seem to be not so much Shield problem but general AWE(gauntlet) also.

     

    There is some bug with armor granted to MMG gunner on opfor technical vehicles (pickup with mounted Machinegun).

    They seem extremely resilient. Apart from Shield, we noticed the same thing yesterday on Isla Duala gauntlet. The gunner repeatedly eaten up hail of bullets even from AR but did not die. Eventualy Nicolai had to blast the technical with AT launcher.

     

    Maybe the gunner's protection is calculated as if he was sitting in the armored vehicle turret and not standing "naked" in the back of a pickup.

     

    I have tried to test this in editor when AWE addons were loaded, but its not standard setting of these units, because in editor, gunner goes down in 1-3 hits from 5.56 every time.

     

  13. lets sum up:

     

    30 minutes waiting for server start&latecomers

    45 minutes connecting & dress-up to scavenge some mis-matched OPFOR leftover gear

    15 minutes driving truck throu the woods

    15 minutes coming close to the objective

     

    The moment we enter the village, walking with 2 teammates in front of me and 2 behind me - bang bang, instakill from god knows where.

    Thou I wouldn't be suprised if that was blue-on-blue, I did had OPFOR PKM in hands.

     

    spectator mode bugs after 30 seconds and no longer works with nighvision (only pitch black is seen)

     

    10/10, will come to help save resistance again

     

     

    If I can plead for some changes with Ryko:

    • Please spawn players with pre-loaded gear.
    • Please don't wait for players who are not online in time, or did not downloaded their MODS in advance. Give the slots to replacements right away.
      If necessary, latecomers filling primary slots can be teleported by Zeus to join the rest.

    just these two things will cut at least 45 minutes from the starting delay

  14. I would try those TS Server settings recommended by TFAR developers:

    Quote

     

    To TeamSpeak servers admins

    To be on the safe side, reduce the level of flood protection: Right-click on the server> Edit Virtual Server> More> Anti Flood, set 30, 300, 3000 values (top to bottom).

     

     

    Both ACRE and TFAR are communicating with TS Servers on behalf of user - which is "not as humans". This could lead into server sometimes detecting it as spammbot attempts. Likely your IP address is then put to temporary blacklist that is recycled in certain intervals.

     

    Anyway, those changes are worth a shot if the TS is managed by Ahoyworld admins and not third party.

  15. Hi

     

    as you probly know me and at least 2 other guys run into the "spamm protection" bug in TS again today when using TFAR. It has happened to people before and usualy clears out when you are out of TS for extended period of time.

     

    But it needs to be fixed more properly

     

    Don Cambio and me googled it, all seems to point to TS "flood protection feature" as in:

    http://forum.teamspeak.com/threads/73725-Action-currently-not-possible-due-to-spam-protection

     

    aslo suggestion on TFAR page:

     

    To TeamSpeak servers admins

    To be on the safe side, reduce the level of flood protection: Right-click on the server> Edit Virtual Server> More> Anti Flood, set 30, 300, 3000 values (top to bottom).

     

×
×
  • Create New...