Camoed AT not firing?
Posts: 688
I've had it happen in two 3v3+ games now that some of my camoed AT didn't fire and couldn't be accessed. I.e. I could neither move them nor remove their camo. And above all: they didn't fire, which kind of made my whole plan of positioning camoed AT come crushing Down.
This could in theory be due to lag - I'm not sure? But it does strike me as odd that this particular kind of unit should lag more than other units. If the game as such is flowing allreight, why should AT in particular be lagging?
I could provide a replay, but how can a replay show that a unit was inaccessible?
Posts: 829
Posts: 934
I don't think I have ever had the issue your describing but I have felt no fire effects before when using camo.
If one of the guys responsible for firing the gun dies whilst in camo mode, it takes like 5-10seconds for one of the other guys to walk over and fill his place. The whole squad movements/animations is slowed when in camo mode. Hence, the moment I fire that first shot I immediately take off camo just incase one guys dies.
Not the same issue, but might shead some insight maybe.
Posts: 2838 | Subs: 3
I only used camo twice, I thought it doesn't fire by design until the camo is removed......
The guns will fire automatically while in camo, unless you give them a Hold Fire order.
Posts: 829
The guns will fire automatically while in camo, unless you give them a Hold Fire order.
It was a while ago, I may have used Hold Fire and forgot about it. Or had that issue, that Stephen is describing..
Either way, thanks for clearing up that for me.
Posts: 688
And thanks to Stephen for the hint. It makes sense and I'll be looking for it as a possible cause.
At a related topic, I noticed how LOS doesn't always Work in an intuitive way. If you position a unit behind a bush or something, it may pe pixels deciding if the units has LOS or not. If it doesn't fire, it may mean it doesn't have LOS. And in such cases I have been able to give them LOS by moving the unit a tiny bit.
While this may make sense IRL, I think it's bad for gameplay. A terrain cover entity should either allow or deny LOS in all it range.
Posts: 50
You're in for a pleasant surprise, Baba. Camo is very, very helpfull.
And thanks to Stephen for the hint. It makes sense and I'll be looking for it as a possible cause.
At a related topic, I noticed how LOS doesn't always Work in an intuitive way. If you position a unit behind a bush or something, it may pe pixels deciding if the units has LOS or not. If it doesn't fire, it may mean it doesn't have LOS. And in such cases I have been able to give them LOS by moving the unit a tiny bit.
While this may make sense IRL, I think it's bad for gameplay. A terrain cover entity should either allow or deny LOS in all it range.
I've seen a similar LOS issue with TrueSight a lot lately and it's cost me heavily in several major engagements. It can be tough to tell if a specific unit actually has LOS when there are other units providing vision in the area. If you're dealing with a fragile/ranged unit and you think it has LOS and try to force it to attack a specific unit, it could end up trying to run up and punch it in the nose because it didn't actually have LOS. I'm not talking about the obvious things like buildings, more like when it's low grass or a tree branch.
I'd like to see a small indicator on the cursor perhaps if you have a unit selected and mouse over an enemy unit that the selected unit doesn't have LOS on.
Posts: 688
I'd like to see a small indicator on the cursor perhaps if you have a unit selected and mouse over an enemy unit that the selected unit doesn't have LOS on.
Good idea. Or simply something in the cone display of MGs and AT that show what parts are in and out of LOS/true sight.
Posts: 50
Good idea. Or simply something in the cone display of MGs and AT that show what parts are in and out of LOS/true sight.
That would be an improvement, but the units I'm most concerned with are ones like the sniper or SU-85. If you think your sniper has a clear shot and you tell it to force fire on a high priority target in the middle of a large battle, it sometimes decides to run up in the face of the target and usually ends up dead. Same with the SU-85 which depends on its range and doesn't have the best mobility. It can turn the tide of a battle when one of these units wigs out unexpectedly because a pixel gets in the way of their sight!
Posts: 307
That would be an improvement, but the units I'm most concerned with are ones like the sniper or SU-85. If you think your sniper has a clear shot and you tell it to force fire on a high priority target in the middle of a large battle, it sometimes decides to run up in the face of the target and usually ends up dead. Same with the SU-85 which depends on its range and doesn't have the best mobility. It can turn the tide of a battle when one of these units wigs out unexpectedly because a pixel gets in the way of their sight!
I agree. This is an issue that Relic has to fix. The units that run up and die can ruin the whole game. Something has to be changed...
When I order my ZiS or SU-85 to fire, I always have to make sure they won't start running into the enemy. This is the waste of seconds that I need for microing something else.
I wonder if Relic will ever do anything about it.
Posts: 688
It sort of requires a whole new set of interface and display. I doubt they'd do that by now. There's no money in it.
Posts: 44
This issue is also frustrating when you click an HMG to attack an infantry squad and it begins packing up instead of firing, allowing the infantry squad to rush in and kill you. Especially with the long set-up time of the MG42.
Posts: 50
But how would you display where a sniper has LOS or not?
It sort of requires a whole new set of interface and display. I doubt they'd do that by now. There's no money in it.
That is why my suggestion is that the cursor change to indicate the unit doesn't have LOS. for example if you have a sniper selected and you move the cursor over a gren squad that the sniper doesn't actually have LOS on the cursor would change to something that would indicate the lack of LOS. That shouldn't be THAT hard or costly to implement.
Posts: 135
Posts: 688
That is why my suggestion is that the cursor change to indicate the unit doesn't have LOS. for example if you have a sniper selected and you move the cursor over a gren squad that the sniper doesn't actually have LOS on the cursor would change to something that would indicate the lack of LOS. That shouldn't be THAT hard or costly to implement.
Oh, now I get it. That's a good one.
Livestreams
2 | |||||
167 | |||||
10 | |||||
5 |
Ladders Top 10
-
#Steam AliasWL%Streak
- 1.831222.789+37
- 2.615220.737+9
- 3.35057.860+15
- 4.1110614.644+11
- 5.276108.719+27
- 6.306114.729+2
- 7.918405.694+2
- 8.262137.657+3
- 9.722440.621+4
- 10.1041674.607-2
Replay highlight
- cblanco ★
- 보드카 중대
- VonManteuffel
- Heartless Jäger
Board Info
5 posts in the last week
33 posts in the last month
Welcome our newest member, Constant
Most online: 2043 users on 29 Oct 2023, 01:04 AM