This is a message i've sent to the support some time ago, but i guess it was sent during the Support Is Down peroid. :)

I never had this problem with the physical copy my friend once borrowed me, but whenever i kill a few units in combat, i can barely see how many units i've killed.

Usually when i deal damage and kill a few units, i should see 2 numbers [damage and kills] one below the other, but with the GOG's 1.7 version both numbers are displayed on top of each other, as if there was no line break between the two, or no delay between displaying both numbers.

I've really hoped the Interface mod would fix this, but it didn't. I can't seem to see an answer, or a similar problem on the 1C KB tech. sup. thread.;(

I've played around with the compatibility tab to no avail.
Also, i've played around with camera angles, and that is not the case.

Attaching an image of Snakes getting an arrow between the eyes for 55 damage, killing one.
The "1" is barely readable.
[i don't think i have this image anymore, but i'll look]

Entered hardware information:
Operating system: Win7x64
Processor type and speed: Athlon X2 4400+
RAM memory: 3 GB
Graphics card: MSI NV 7600GT
Sound card: SoundMAX integrated HD Audio
Graphics driver version: 196.21
DirectX version: 11

Are you certain there are two numbers? Not just the red one?

One of KB patches (1.2, I think) added ability to toggle between displaying damage or kills count. It it 'showflyingdead=' line in game.ini.
Since then you can see only one floating number. Both damage and kills are still listed in combat log window, however.

Personally I use 'showflyingdead=1' to see kills and enabled health bars (pressing ALT) to see how much damage the troops caused.

I can see both, just that they're "glued" together. And they're not really readable.;>

When i played this game [1.0? 1.1?] both numbers were visable.
I liked to see DMG and kills in separate lines, flowing above kills.

I'll play around with the .ini and report if it helped, and see if i have that screenshot. Or perhaps i'll make a new one. Thanks.:)

I know what you mean, in AP you can still see both.
Screenshot would be helpful, I have retail version patched to 1.7 and I can get only one number to show.

Sorry for the delay, appears i don't have enough space.. Over 2TB full of sh..t.
I guess i'll check it out at night or tomorrow, for today is Cluedo and beer day. That is EXACTLY my problem. :)

Oh, is that what's going on? I thought it was a graphic corruption of some sort. I had no idea I was seeing two numbers overlapped.

Anyone found solution for this ? Having the same problem.

Oh, hell, i was supposed to post a screenshot for Thiev!
Then i forgot... I feel like Dimitri [JA2] now..;(
I'll try to find some space AGAIN, install KB and make a screenshot. As far as i know, nobody solved it, and only one number should be displayed. I'd prefer to see both though.

That's great! Apparently, i got so excited, i've misclicked and marked Your post as solution.
F@#K!;/

Anyhow, check it out, and see the anomaly Yourself. ;)

Please, I can see right through this sneaky try to guilt me into finding the soultion ;) Unfortunately, I don't have good news.

showflyingdead= setting works like that:
0 (shows damage dealt)
1 (shows units killed)
2 (shows both, but overlapped) <- that is GOG default, which causes the issue

Digging through the game files I can change the size or colour of overhead display, but it applies to both numbers; there is no way to separate them, at least not in the accesible files.
Considering that the 'switch' was added to .ini file, I think the answer may be in the .exe itself, but I don't have old 1.0 file to compare.

Well, it wasn't intentional, i assure You. The bloody button is hidden, and jumps out in the middle, it's easy to click.

Anyhow, thanks for the information, i remember playing this years ago, having but numbers shown. If it's the exe i don't think GOG can do much.

Which was true for pre-1.2 version. it is now almost impossible to get, so I can't check this .exe theory.

It's a shame this isn't solved. It's an annoying bug.