True : real situation is different than simulation, but simulation is a way to reproduce very specific situation.

The scenario for standard speedcam could be weird. But with a database where the end of average speedcams are not identified with a speedlimit = 5km/h, the driver has to stop it manually. This is a real case.
And after a manual stop, on the next average speedcam zone, the display will be wrong. The speedcam will be detected, the notifications will be sounded, the overspeed will be alarmed but the display will be wrong.

And this will happen until an average end section is not automatically detected

In fact, at the next average zone control, the display will be correct just at the speedcam entry point ( sc_OnSpeedcam() / sc_OnSection() ) during some milliseconds, and after, it will be wrong.

Let see the short video screen record I made when the previous average zone has been stopped manually. You will see the display icon briefly.
Spoiler: +
[Only registered and activated users can see links. ]


I found that it's because ui_PropLayer.ShowSpeedCamera is false. The reason is the same for all other speedcams which have be manually stopped.