Open GoogleCodeExporter opened 9 years ago
Bardia's is the 3inchmortar_AI version. The other is the standard 3inchmortar
version.
Look how much higher a view you have of the terrain in the HUD on Bardia.
Raising the viewport might be causing the issues, though not the ammo part.
I also recall the 3inchmortar_AI as having an 'extra' edit in tweak file to get
bots to raise and lower it correctly.
A numeric value was edited.
If not edited, a bot who wanted to raise the mortar, actually wound up lowering
it and vice versa.
This edit could also be the cause for the arrows glitch?
Original comment by evanthom...@gmail.com
on 24 Mar 2012 at 6:13
Then here's another example of mortar - Purple Heart Lane 64, Granatwerfer 34.
Ammo - OK, vertical dial - OK, usable by AI - yes (see 'PHL AI Mortar
Kill.jpg', first kill message).
Original comment by gavrant
on 24 Mar 2012 at 7:55
Attachments:
Edit to previous comment:
My point is that it's possible to make mortars usable by both AI (PHL mortars
have raised viewports) and humans (working dials and showing ammo). As Bardia
is quite an old map, probably it was one of the first attempts, that's why it's
not perfect.
Original comment by gavrant
on 24 Mar 2012 at 8:19
Original comment by djbar...@djbarney.org
on 28 Mar 2012 at 7:33
Original issue reported on code.google.com by
gavrant
on 24 Mar 2012 at 12:22Attachments: