Official SEOW

S~:

For those of you that enjoy bombing bridges to either stop an opponents advance or to cut off the enemy supply lines there is a bug that has been discovered that will effect your campaigns in SEOW. This is in the IL2 game engine not an SEOW bug.

Each bridge in a map (both Road Bridges and Railway bridges) is assigned a unique number in the IL2 game. The bridge #'s start with zero (0 to whatever number the game assigns). Many of the maps especially large maps have more than 255 bridges (bridges numbered 0-255). If an AI plane or Client plane bombs and destroys any bridge# 0-255, the bridge destruction is visually displayed correctly in the IL2 game and the eventlog accurately reflects the correct bridge# destroyed. Therefore when the SEOW DCS analyzes the eventlog those events are accurately captured in the SEOW Mission Planner and stats pages.

The problem occurs when a client player (human) bombs a bridge that has a bridge # greater than 255, for example bridge # 256 this bridge will not be destroyed in the IL2 game. Visually it will be undamaged however bridge # 0 will be destroyed. Bridge # 0 will be in a totally different location, this is recorded in the eventlog. So when this is analyzed with the SEOW DCS it records the event and a destroyed bridge at the location according to the eventlog which is not correct. This only occurs with a client player (human), the AI planes will destroy the bridge #256 and the correct bridge # will be displayed destroyed visually in the IL2 game and the eventlog will show bridge # 256 destroyed. A host human that is playing as the host (not using the host seat) will be able to bomb bridge 256 and the eventlog will show bridge 256 destroyed just as the AI plane does.

So the problem is any client that bombs bridges # > 255, the bridge # that will appear destroyed both in the eventlog and visually in the IL2 game will be that (bridge# - 256). As you can see this is a serious problem. It seems this is an IL2 game bug that is causing problems for bridge bombing in SEOW.

Testing of this has been done with StG77_Countzero, =VARP=Thor, and myself. Hope this is helpful.

S~
JG26_Badger

Here are just few examples of this Bug

Test #1, i am host, Badger is client player
I am going for bridge #256
AI is going for bridge #255
Badger is going for bridge #259

Test #1 eventlog data:
[11.03.2015 0:51:01] Mission: net/coop/1/testbridges256.mis is Playing
12:00:00 Mission BEGIN
12:00:00 R_StG77_CountZero is trying to occupy seat g01010(0)
12:00:00 OKL_JG26_Badger is trying to occupy seat g01020(0)
12:00:00 g01010(0) seat occupied by R_StG77_CountZero at 107154.31 74494.58
12:00:00 g01010 loaded weapons '2xSC1000_2xSC500' fuel 100%
12:00:00 g01020(0) seat occupied by OKL_JG26_Badger at 124754.28 76289.8
12:00:00 g01020 loaded weapons '2xSC1000_2xSC500' fuel 100%
12:00:01 g01010 in flight at 107069.18 74493.76
12:00:01 g01020 in flight at 124696.26 76227.555
12:00:44 Bridge255 destroyed by g01000 at 132200.0 75300.0
12:03:20 Bridge256 destroyed by g01010 at 99100.0 74500.0
12:08:01 Bridge3 destroyed by g01020 at 1100.0 381700.0
12:09:39 Mission END

Me as host have correct bridges destroyed, AI also have correct bridge destroyed.
For Badger as client, even though we both saw that he drop bomb on bridge #259, and we saw bombs explode on bridge #259, bridge #259 is intact and bridge #3 gets destroyed in game and in eventlog. 259-256=3
We had static camera placed in mission on position of bridge #3, and we saw in game that bridge is destroyed.


Same mission, Test #2, i am host, Badger is client player
Me as host now will bomb bridge #259
AI is again going on bridge #255
Badger is going for bridge #256 this time

Test #2 eventlog data:
[11.03.2015 1:04:44] Mission: net/coop/1/testbridges256.mis is Playing
12:00:00 Mission BEGIN
12:00:00 R_StG77_CountZero is trying to occupy seat g01020(0)
12:00:00 OKL_JG26_Badger has connected
12:00:00 OKL_JG26_Badger is trying to occupy seat g01010(0)
12:00:00 g01020(0) seat occupied by R_StG77_CountZero at 124754.28 76289.8
12:00:00 g01020 loaded weapons '2xSC1000_2xSC500' fuel 100%
12:00:00 g01010(0) seat occupied by OKL_JG26_Badger at 107154.31 74494.58
12:00:00 g01010 loaded weapons '2xSC1000_2xSC500' fuel 100%
12:00:00 g01010 in flight at 107091.69 74494.24
12:00:00 g01020 in flight at 124702.93 76234.945
12:00:42 Bridge255 destroyed by g01000 at 132200.0 75300.0
12:01:14 Bridge259 destroyed by g01020 at 119700.0 71100.0
12:05:44 Bridge0 destroyed by g01010 at 2400.0 386800.0
12:06:38 Mission END

In game Badger drops bombs on bridge #256, bombs explode on that bridge but that bridge is intact for both of us to see (externals are ON), and bridge #0 explodes, and no one is next to it. 256-256=0
We see that eventlog will credit him with bridge #0 destroyed even though he drop bombs on bridge #256.
And for me as host this bridge #259 is credited correctly and both of us saw it explode and that is destroyed.

Bug cycles every 256 bridges only if client player is bombing bridges, so for bridge #511, bridge #255 gets destroyed in game (511-256=255), for bridge #512 bridge #0 gets destroyed ( 512-256-256=0) and for #513 bridge #1 gets destroyed ( 513-256-256=1) and so on. If AI or Host is bombing them correct bridges will get destroyed.
Thats why to see how and when this bug hapends we had to test it with atleat 2 guys.

So in SEOW even if bridge table and highway and railroad tables are correct for that sector, eventlog will give wrong information on what bridge is destroyed if client player bombs bridges higher then #255

On this link is one replay of 3rd test ( History mod+Expert mod ):
http://www.fileconvoy.com/dfl.php?id=gc ... 8870720acc

On that recording I am host, and going for bridge #257, this is on WestFront40 map, and Badger as client and he is going for bridge #256. We have static cameras looking at bridges #0 and #1 and at moment when Badger drops bombs on bridge #256 and bombs explode, bridge #0 explodes and not #256.

Cheers
CZ

Thor was host on 4.12.2 clean game with mission on Normandy3 map when we tested it just now, and same bug happends on bridges with numbers 256 and more. I drop bombs on bridge #257 and game destroyed bridge #1. No mods in JSGME.
So the bug probably can not be fixed by HSFX team, as it seams it is problem of clean 4.12.2 game.
Dont know if this is known bug or not to TD.

Great report guys!

Hi all ^^

I'm in vacation, I cannot check this but it seems to me that we had not this issue in our Dieppe 1942 campaign (HSFX7.0.3 without Expert mode, SEDB71, map WestFront44)....
As you can see here (at the end of this page)

http://www.flibusteairline.com/MP4publi ... osses.html

Bridge 269 1
Bridge 346 1
Bridge 347 1
Bridge 350 1
Bridge 655 1
Total Destructions Infrastructures par Alliés 5

I will check this when I will be at home. Is it a new issue?

Dore this bug only happends if client (human player) bombs the bridge in game.

In your campaign i see thouse bridges were destroyed by Engineer in MP so thats wahy it was ok.

347. 10:00:00 Allied Engineer 101st Airborne Division, Bgd. 1, Regt 4, Btn 4 demolished AI-13 Bridge Bridge 347
182. 12:00:00 Allied Engineer 101st Airborne Division, Bgd. 1, Regt 3, Btn 3 demolished AI-18 Bridge Bridge 350
183. 12:00:00 Allied Engineer 101st Airborne Division, Bgd. 1, Regt 4, Btn 1 demolished AJ-18 Bridge Bridge 269
167. 14:00:01 Allied Engineer 101st Airborne Division, Bgd. 1, Regt 3, Btn 4 demolished AG-14 Bridge Bridge 346...

for bridge 655 i could not fined log, so maybe AI airplane destroy it or engineers also?

I hear about problem with bridges being indestructible in online gameplay in HSFX6 first time, and i saw it then when it happend to me on westfront44 map in online game.
I believe then the bug was just visual thing only, now i belive this is same Bug and is in game long time.
Now i know that bridge were not indestructible like it may seem at that time,
people saw it indestructible only because other bridge would explode on other place on map, when they would drop bombs on bridge they attacked, and probably that was bridge with number higher then 255.

Just no one i know, didnt saw why or when its happening, and i tought this bug is reported and being fixed.

And its hard to check or fined this bug alone, as when your host all is ok and when AI destroys bridge all is ok, you have to test it with 2 guys minimum, and client has to do bombing to have this bug.
Only problem happends when client destroys the bridge, and only in case when its bridge with abow 255 number.
So i think guys reported some bug with bridges being indestructible, and when some one tested it on its own he saw all was ok, and they didnt search it more, thinking its false report or guys didnt hit bridge or bomb didnt arm.

I saw today as i was looking if this bug is reported to TD in 4.12.2 de-buging topic, http://forum.1cpublishing.eu/showthread ... 39&page=52
that Baddington guy reported that he drops bombs on bridge and he dosent see it destroyed.
And idefix44 guy toled him on that topic that he tested it and saw all is ok. But he probably tested as host and then all will be ok or maybe even on bridge with number less then 256, only client have that problem and only on bridges with numbers larger then 255. So it was hard to fined when this bug happend when you dont have details.

When this happend in VARP Battle of Kursk campaign, 3rd time last week (1st was bridge#270, then #282 and last week #302 bridges), me and Thor wonted to fined out why is this happening so Thor dont have to edit this as admin and fix when wrong bridge is destroyed but we know players bombed correct one. Also we wonted to be sure nothing is wrong with map mod and New Kursk map.

Then we saw that this happends only when client is bombing bridge, not when AI is destroying it or host,
and on only few bridges, not on all of them,
and that eventlog says its wrong bridge, and that bridge table or highway or railroad tables in seow database are ok.
We started to search and test why when player on server destroys bridge #302 game destroys #46, and when player destroy #270 and game destroys #14, and when player destroys #282 game destroys #26.

We didnt know when exactly this happends, on what bridge number it starts, so we could not test it on other map by just guessing and randomly test bridges.
So only when we saw that all 3 problematic bridges have this
302-46=256
270-14=256
282-26=256

So common number is 256
We tested first on Battle of Kursk what happends when bridges #255, #256 and #257 get destroyed by client player.
When we saw that when client bomb #256, game destroys #0
and when client bombe #257 game destroys #1

We could started to test what will hapend on other maps if bridge #256 gets destroyed by client, and be sure that our Map mod is not buged only.
Badger help test that yesterday on more maps, and we saw what he posted.
We are sure from thous tests that problems starts only when client bombs bridges with larger number then 255.
Why we dont know.

But its problem in clean 4.12.2 game, as we saw in tests that same bug happens.

Looks like as typecast problem in game Java, eg using a single byte int instead of a full word.
SEOW should be able to compensate by comparing x,y cords of event with bridge coords. I will investigate.

What I need is clear evidence that the bridge AND the x,y coordinates are reported incorrectly in the host eventlog. The data reported above does not identify which maps were used in which tests. Based on discussions with Badger, it seems that the client eventlog is reporting the correct data but we need to be sure about the host eventlog.

Can I suggest that some tests are repeated using some stock IL-2 maps where there have been no changes/mods for many years, e.g. Gulf of Finland (1566 bridges).

If we can establish that the host eventlog data is unreliable for some human-destroyed bridges then we have a real issue.

Cheers,
4S

Test on map Golf of Finland , bridges #256 and #257 are targets

[Mar 12, 2015 2:32:20 PM] Mission: net/dogfight/0SEOW/GolfoffinlandDF.mis is Playing
[2:32:20 PM] Mission BEGIN
[2:33:04 PM] OKL_Kopfdorfer selected army Red at 222071.86 33142.62
[2:33:09 PM] R_StG77_CountZero selected army Red at 222071.86 33142.62
[2:33:51 PM] OKL_JG26_Badger has connected
[2:33:57 PM] OKL_Kopfdorfer:Ju-88A-4(0) seat occupied by OKL_Kopfdorfer at 222270.86 33343.62
[2:33:57 PM] OKL_Kopfdorfer:Ju-88A-4 loaded weapons '4xSC500' fuel 60%
[2:33:57 PM] OKL_Kopfdorfer:Ju-88A-4 in flight at 222297.3 33341.8
[2:34:22 PM] R_StG77_CountZero:Ju-88A-4(0) seat occupied by R_StG77_CountZero at 222270.86 33343.62
[2:34:22 PM] R_StG77_CountZero:Ju-88A-4 loaded weapons '2xSC1000' fuel 30%
[2:34:23 PM] OKL_JG26_Badger selected army Red at 222071.86 33142.62
[2:34:24 PM] R_StG77_CountZero:Ju-88A-4 in flight at 222798.7 33323.434
[2:35:08 PM] OKL_JG26_Badger:Ju-87B-2(0) seat occupied by OKL_JG26_Badger at 222270.86 33343.62
[2:35:08 PM] OKL_JG26_Badger:Ju-87B-2 loaded weapons '1SC1000' fuel 50%
[2:35:08 PM] OKL_JG26_Badger:Ju-87B-2 in flight at 222354.81 33339.723
[2:35:20 PM] OKL_Kopfdorfer:Ju-88A-4(0) seat occupied by OKL_Kopfdorfer at 224655.38 32286.713
[2:35:20 PM] OKL_Kopfdorfer:Ju-88A-4(1) seat occupied by OKL_Kopfdorfer at 224593.36 32305.318
[2:35:21 PM] OKL_Kopfdorfer:Ju-88A-4(2) seat occupied by OKL_Kopfdorfer at 224526.66 32325.16
[2:35:25 PM] OKL_Kopfdorfer:Ju-88A-4(1) was heavily wounded at 224181.31 32431.7
[2:35:25 PM] OKL_Kopfdorfer:Ju-88A-4(0) was wounded at 224181.31 32431.7
[2:35:25 PM] OKL_Kopfdorfer:Ju-88A-4(1) was killed at 224181.31 32431.7
[2:35:25 PM] OKL_Kopfdorfer:Ju-88A-4(0) was heavily wounded at 224181.31 32431.7
[2:35:25 PM] OKL_Kopfdorfer:Ju-88A-4(3) was wounded at 224181.31 32431.7
[2:35:25 PM] OKL_Kopfdorfer:Ju-88A-4(0) was killed at 224181.31 32431.7
[2:35:25 PM] OKL_Kopfdorfer:Ju-88A-4(3) was killed at 224181.31 32431.7
[2:35:25 PM] OKL_Kopfdorfer:Ju-88A-4(2) was killed at 224181.31 32431.7
[2:35:26 PM] OKL_Kopfdorfer:Ju-88A-4 crashed at 224181.31 32431.7
[2:35:42 PM] OKL_Kopfdorfer entered refly menu
[2:36:05 PM] OKL_Kopfdorfer:Ju-88A-4(0) seat occupied by OKL_Kopfdorfer at 222270.86 33343.62
[2:36:05 PM] OKL_Kopfdorfer:Ju-88A-4 loaded weapons '2xSC1000' fuel 60%
[2:36:06 PM] OKL_Kopfdorfer:Ju-88A-4 in flight at 222358.06 33338.49
[2:37:01 PM] Bridge0 destroyed by OKL_JG26_Badger:Ju-87B-2 at 414024.03 12376.001
[2:37:36 PM] OKL_JG26_Badger has disconnected
[2:38:18 PM] OKL_Kopfdorfer:Ju-88A-4(0) seat occupied by OKL_Kopfdorfer at 225481.77 32100.7
[2:38:19 PM] OKL_Kopfdorfer:Ju-88A-4(1) seat occupied by OKL_Kopfdorfer at 225422.84 32100.506
[2:38:19 PM] OKL_Kopfdorfer:Ju-88A-4(2) seat occupied by OKL_Kopfdorfer at 225371.3 32100.121
[2:38:20 PM] OKL_Kopfdorfer:Ju-88A-4(3) seat occupied by OKL_Kopfdorfer at 225312.47 32099.416
[2:38:29 PM] Bridge1 destroyed by OKL_Kopfdorfer:Ju-88A-4 at 414556.0 12843.994
[2:38:32 PM] OKL_Kopfdorfer:Ju-88A-4(0) seat occupied by OKL_Kopfdorfer at 223974.83 31911.328
[2:40:05 PM] OKL_Kopfdorfer:Ju-88A-4(0) seat occupied by OKL_Kopfdorfer at 225073.14 32135.738
[2:40:06 PM] OKL_Kopfdorfer:Ju-88A-4(1) seat occupied by OKL_Kopfdorfer at 224928.12 32155.137
[2:40:07 PM] OKL_Kopfdorfer:Ju-88A-4(2) seat occupied by OKL_Kopfdorfer at 224888.08 32159.787
[2:40:26 PM] OKL_Kopfdorfer:Ju-88A-4(3) seat occupied by OKL_Kopfdorfer at 223441.5 31844.328
[2:40:28 PM] OKL_Kopfdorfer:Ju-88A-4(0) seat occupied by OKL_Kopfdorfer at 223405.64 31748.104
[2:40:28 PM] OKL_Kopfdorfer:Ju-88A-4(0) seat occupied by OKL_Kopfdorfer at 223403.6 31736.994
[2:40:29 PM] OKL_Kopfdorfer:Ju-88A-4(1) seat occupied by OKL_Kopfdorfer at 223401.1 31649.295
[2:40:30 PM] OKL_Kopfdorfer:Ju-88A-4(2) seat occupied by OKL_Kopfdorfer at 223409.06 31599.297
[2:40:31 PM] OKL_Kopfdorfer:Ju-88A-4(3) seat occupied by OKL_Kopfdorfer at 223419.47 31557.066
[2:40:31 PM] OKL_Kopfdorfer:Ju-88A-4(0) seat occupied by OKL_Kopfdorfer at 223431.89 31520.852
[2:40:57 PM] OKL_Kopfdorfer:Ju-88A-4(0) seat occupied by OKL_Kopfdorfer at 225125.5 32097.922
[2:40:57 PM] OKL_Kopfdorfer:Ju-88A-4(1) seat occupied by OKL_Kopfdorfer at 225179.31 32142.92
[2:40:58 PM] OKL_Kopfdorfer:Ju-88A-4(2) seat occupied by OKL_Kopfdorfer at 225214.31 32172.07
[2:41:16 PM] OKL_Kopfdorfer:Ju-88A-4(3) seat occupied by OKL_Kopfdorfer at 226376.5 33047.617
[2:41:17 PM] OKL_Kopfdorfer:Ju-88A-4(0) seat occupied by OKL_Kopfdorfer at 226414.11 33072.11
[2:41:17 PM] OKL_Kopfdorfer:Ju-88A-4(0) seat occupied by OKL_Kopfdorfer at 226440.47 33089.33
[2:41:19 PM] OKL_Kopfdorfer:Ju-88A-4(1) seat occupied by OKL_Kopfdorfer at 226552.94 33165.383
[2:41:19 PM] OKL_Kopfdorfer:Ju-88A-4(2) seat occupied by OKL_Kopfdorfer at 226563.95 33173.43
[2:41:20 PM] OKL_Kopfdorfer:Ju-88A-4(3) seat occupied by OKL_Kopfdorfer at 226589.33 33192.727
[2:41:20 PM] OKL_Kopfdorfer:Ju-88A-4(0) seat occupied by OKL_Kopfdorfer at 226612.36 33211.406
[2:41:48 PM] OKL_Kopfdorfer:Ju-88A-4 damaged by landscape at 225891.92 33390.652
[2:41:48 PM] OKL_Kopfdorfer:Ju-88A-4(2) was killed at 225886.52 33379.133
[2:41:48 PM] OKL_Kopfdorfer:Ju-88A-4(3) was killed at 225886.52 33379.133
[2:41:48 PM] OKL_Kopfdorfer:Ju-88A-4(1) was wounded at 225886.52 33379.133
[2:41:48 PM] OKL_Kopfdorfer:Ju-88A-4(0) was killed at 225886.52 33379.133
[2:41:48 PM] OKL_Kopfdorfer:Ju-88A-4(1) was killed at 225886.52 33379.133
[2:41:48 PM] OKL_Kopfdorfer:Ju-88A-4 shot down by landscape at 225886.52 33379.133
[2:41:50 PM] Mission END

Im host they are bombing bridges as clients:
Kampfdorfer drops bomb on #257, and in eventlog #1 gets destroyed by him, even though we see explosions on #257 in game
Badger drops bombs on #256, and in eventlog #0 gets destroyed by him, even though we see explosions on #256 in game
and coordinates in eventlog for that event are of bridges #0 and #1 not #256 and #257 where bombs hit, because thouse bridges (#0 and #1 )explode in game their coordinate is in eventlog (you see bridges #0 and #1 explode on differant side of map during the game play instantly when bombs hit and explode on #256 and #257).

In case of previous test in 2nd post, they were done on Battle of Kursk map

Also both client and host eventlog will show same wrong data in eventlog, when client bombs bridges abow 255 number.
Badgers and Kopfdorfer eventlog shows same thing i see in my eventlog in this example i posted.

I also posted recording of test on WestFront40 map in 2nd post on this topic, and if you have time 4Shades you can download it and look at it, you will see this bug there hapening in game while playing as explained. And in generated eventlog of recording you will also see it in eventlog.
In that recording when it starts, with Ctrl+F2 you can look at woden bridge #0 (its the one with 2xstatic 1-20 parked next to it). And in 2:21 in recording you should see it explode, and Badger at same time drops bomb on #256. Me as host, gets credited with correct #257 bridge.

This is eventlog from it:
[12.03.2015 22:11:33] Mission: net/coop/1/west40testmost.mis is Playing
12:00:00 Mission BEGIN
12:01:04 Bridge257 destroyed by g01020 at 69500.0 132776.0
12:01:08 g01020(1) was wounded at 69478.37 132249.62
12:01:08 g01020(1) was heavily wounded at 69478.37 132249.62
12:01:08 g01020(1) was killed at 69478.37 132249.62
12:01:08 g01020(0) was killed at 69478.37 132249.62
12:01:08 g01020(3) was wounded at 69478.37 132249.62
12:01:08 g01020(2) was killed at 69478.37 132249.62
12:01:08 g01020(3) was killed at 69478.37 132249.62
12:01:08 g01020 shot down by landscape at 69478.37 132249.62
12:02:39 Bridge0 destroyed by g01010 at 363660.0 84339.99
...

Thanks CountZero,

That is very clear. In the eventlog lines both the bridge id and the x,y coordinates are incorrectly reported by IL-2, but only for bridges destroyed by human pilots using client machines in multiplayer coops or dogfights. There is no logging error for the host pilot or for AI pilots destroying bridges.

Unfortunately because the IL-2 eventlogs are wrong in these cases, SEOW cannot compensate for the errors automatically. Until there is some fix/patch produced by TD we will have to use some kind of work-around for human-initiated bridge destruction.

Cheers,
4S

Back to home ^^

CountZero, I confirm this issue. I found in my previous campaign (Dieppe 1942 WestFront 44 map) an example of a bridge destroyed by a client:

SE-DI-194208191000.mis 10:52:11 Bridge143 Bridge destroyed by RAF_No088SQN000 RAF_No088SQN00 321144 53100

The right bridge was 143 + 256 + 256 = 655

I remember now I had modified the number in the Action_Data table after the 1st mission analyze.

Have you reported this error to the DT?

Hi Dore

Yes after we tested, and saw no one reported it on their forum, Badger and Thor posted on 1C forum in 4.12.2 de-buging topic
http://forum.1cpublishing.eu/showthread ... 39&page=78

I tested today bridge destruction on Gulf of Finland map in 4.13 game and TD fix this bridge bug. Ripgrunwald was host i was client in Ju88 and i drop bombs on bridges #256 and #257 and they were correctly destroyed in game as in eventlog.
Now we only need HSFX7 or 8 for 4.13

Good news!