Kettengrad bug

[muki_]

Has anyone had problems with ketten capturing points? In McGaechen's War and Lyon there seems to be a constant bug where Ketten goes near to a point but don't start capping. Is it just my key/mouse when i have to re-order the capping...

[Lunar100]

Dunno about that however I do notice the ketten bug when a jeep gets close by the Kettens pathing gets seriously fucked up. The jeep can be behind the ketten and the ketten will still refuse to drive forward and do a strange 180 degree turn and crap. Makes it almost impossible to escape from a jeep.

[Thirsty Camel]

Also a bug on the hill map where you order it to go at the very start and it stops half way to its first destination.Only does it when your at the bottom of the map though

[ViiKumi]

Dunno about that however I do notice the ketten bug when a jeep gets close by the Kettens pathing gets seriously fucked up. The jeep can be behind the ketten and the ketten will still refuse to drive forward and do a strange 180 degree turn and crap. Makes it almost impossible to escape from a jeep.

Wasn't this fixed in 2.301? I thought that the bug only existed on stuarts anymore...


And to OP; sounds like you were trying to capture a point secured by a british truck.

[PeterPeterson1]

Pathing bug still exists and is still annoying.

Sometimes Krad ignores shift holded commands. It looks like it touches the point and then it drive to the next one. But somtimes it is a bush or a fence which blocks pathing and the Krad jumps to the next target!

[AverageJoe]

This happens because when your shift cuing orders you think you've selected the point but instead hit the ground right under the point (This is easiest to do on strategic points since there's a small patch of grass under them where you don't select the point). This happens to me every so often with all the factions. It's no bug, just user error.

[Sturmhaubitze]

The solution is to order the Kettenkrad to move a meter closer to the point, and then issue the cap order. This problem also exists when telling a Kettenkrad to boobytrap a point.

A similar bug is with Bergetigers, as you sometimes have to force them to move closer to a vehicle before they'll start repairing properly.

[Boogem]

Also similar, engies/pios cutting wire...grrrr! Never heard of it on capturing points though. The Brit truck thing sounds like the answer.

[sensesfusion]

I confirm there is a bug on capture point, as well as the jeep bug.

I am pretty sure I click on the capping instead of "go to" the point, because I have this problem with PE way more than other faction.

[E-Bass]

Some points, for example the Eastern +16 on Lyon are not accessable to kets as they are enclosed areas accessable only by small gates etc.

[SydniasWolff]

Heh, Lyon is hell for Kettenkrads. A majority of the points are not accessible to them. Other "bugs" exist on Lyon too, like the crews of 3" Mortar Pits appearing submerged in soil.

[coreltyc]

This happens because when your shift cuing orders you think you've selected the point but instead hit the ground right under the point (This is easiest to do on strategic points since there's a small patch of grass under them where you don't select the point). This happens to me every so often with all the factions. It's no bug, just user error.

+1. It happens to me sometimes too with all the faction.

Quote:
Dunno about that however I do notice the ketten bug when a jeep gets close by the Kettens pathing gets seriously fucked up. The jeep can be behind the ketten and the ketten will still refuse to drive forward and do a strange 180 degree turn and crap. Makes it almost impossible to escape from a jeep.




Wasn't this fixed in 2.301? I thought that the bug only existed on stuarts anymore...
The Jeep-Ketten pathing issue still exist.