Page 1 of 1
[SOLVED] no hit location shown
Posted: Wed Oct 24, 2018 8:32 pm
by UP844
Taking advantage of the new LOS check improvement, I attempted playing CG003 - Bled white (the scenario is strongly advised if you like bashing your head against a reinforced concrete wall)
A strange thing happens during Ordnance/AFV to AFV fire: when a hit is achieved, no hit location appears (regardless of the effectiveness of the hit)
In the case shown in the screenshot below (and in the next one) a strange text string appeared.
Case #1 a StuG destroyed a T-34/76

RE: Possible bug: no hit location shown
Posted: Wed Oct 24, 2018 8:33 pm
by UP844
Case #2: another StuG destroyed a SU-152. The same string appearing in case #1 is shown.

RE: Possible bug: no hit location shown
Posted: Wed Oct 24, 2018 8:35 pm
by UP844
Case #3: a 45mm AT gun destroyed a Pz III L. No text showing the hit location and penetration appeared [&:]

RE: Possible bug: no hit location shown
Posted: Wed Oct 24, 2018 8:38 pm
by UP844
In a previous case, which I didn't capture, a 45mm AT gun destroyed an Elefant (!!!) with a front hit, and a "\0" string appeared instead of the hit location/penetration string.
P.S. I am sorry to be such a pest, but these days looks like I am the only one playing ToTH [:(] (or, at least, admitting in public I do [:D])
RE: Possible bug: no hit location shown
Posted: Thu Oct 25, 2018 8:00 am
by Peter Fisla
I will try to fix issues even if there is just one active customer left
I think in one of the Pirates of the Caribbean, someone says: “No cause is lost if there is but one fool left to fight for it.” I like that

RE: Possible bug: no hit location shown
Posted: Thu Oct 25, 2018 12:30 pm
by UP844
You found at least one, even though he's a huge annoyance [:D]
I am sorry I have not provided a saved game: I can try saving before each time one of my AFVs fires, but I doubt it would be useful, as the bug appears to strike while the fire is resolved and a hit is achieved.
RE: Possible bug: no hit location shown
Posted: Thu Oct 25, 2018 5:07 pm
by UP844
Some good news: the failure to penetrate string works fine (see #6 below). Unfortunately, it is the only one.
Cases #1 to #4 show the strange strings appearing when an AFV is destroyed. #3 and #4 show the same string, so I presume they refer to the same hit type (e.g. Turret Side), but I have not noticed this when I took the screenshots.
Case #5 does not show any string (just like a miss), but the AFV was killed anyway, so I suppose it has been hit and penetrated.
On a side note, when OBA hits a tank, the hit location is shown as intended.

RE: Possible bug: no hit location shown
Posted: Sat Oct 27, 2018 1:56 am
by technikzauberer
ORIGINAL: UP844
P.S. I am sorry to be such a pest, but these days looks like I am the only one playing ToTH [:(] (or, at least, admitting in public I do [:D])
Rest assured, you're not the only one. Although, I will be looking closer to see if I have the same issues … I hadn't noticed but then again can flash through those messages in favor of simply cheering an outcome.
RE: Possible bug: no hit location shown
Posted: Thu Dec 13, 2018 10:36 am
by Peter Fisla
Hopefully the just released build 1.1.19 will address this text corruption issue...
RE: Possible bug: no hit location shown
Posted: Thu Dec 20, 2018 10:09 pm
by UP844
Issue solved in v.1.1.19.
Thanks a lot, Peter [&o]
RE: Possible bug: no hit location shown
Posted: Fri Dec 21, 2018 11:27 pm
by Magpius
Peter, this is by far my favourite game.
I'm just not good enough to contribute nuanced observations.
Keep up the great work.