Great !
Good job : it works now : speed is displayed.
Many thanks.
Download file speedcam_mod_eur+_3dfv12 again, now it has a new name speedcam_mod_eur_3dfv12Ok, go back to my speed display issue : I installed the latest 30.09.2025 Pongo Skin with speedcam_mod_eur+_3dfv12, and I have exactly the same issue (preloads was deleted).
and speedcam.zip Mod AF
[Only registered and activated users can see links. ]
Last edited by Andrey Form; 3rd January 2026 at 12:58 PM.
Great !
Good job : it works now : speed is displayed.
Many thanks.
Lufop users always receive a notification about the start of the average speed because they don't differentiate between them. For modern skins, a finish speed of 5 km/h is sufficient.Lufop
2.2174,48.63431,4,0,1,105, start
2.25599,48.62867,4,0,1,125, finish
2.257213,48.628464,4,0,1,310, start
2.218296,48.634582,4,0,1,285, finish
OSC
2.21755,48.63433,4,110,1,103, start
2.256623,48.628401,4,5,1,120, finish
2.25694,48.628529,4,110,1,309, start
2.217895,48.634608,4,5,1,285, finish
Hi Andrey,
I've just found that the speedcam speed limit was no more spoken with the version speedcam_mod_eur_3dfv12, even if the setting say_camera_speed_limit=1 is active for this speedcam category in plugin.ini file.
The reason is because the folder of plugin.ini is ux\speedcam_mod_eur_3dfv2 in the zip file instead of ux\speedcam_mod_eur_3dfv12, like the zip filename.
I changed it, and the speed limit is spoken again now.
Yes, the file name and folder name must be identical.
If the names don't match, the UX plugin won't work.speedcam_mod_eur_3dfv12.zip
plugin.ini ux\speedcam_mod_eur_3dfv12
EUR + speedcam_mod - Mod AF have already been fixed. It's strange that the error was only discovered now. It started with EUR + 3df v2, and no one reported it. It's likely the downloaded files weren't used for their intended purpose. Your situation is understandable: you use two navigators and want to use the same encoding.
Hi Andrey,
Sorry, but I think I found a bug in the Pongo Luna skin :
Please look at this scenario :
Spoiler: +
I'm driving fast on a straight line, but I know I will turn right before the speedcam. As I'm faster than the excessive speed of 30km/h, at the white star position I click on the speedcam icon to shut it down.
Then I turn right, right again, but as I cannot see the car of my friend front of his house, I decide to continue my trip, and turn right 2 times more to and now I will pass in front of the radar.
In that specific scenario, the speedcam is announced, the overspeed is detected, the speedcam speedlimit is displayed, but the speedcam icon with the distance is no more displayed.
On another speedcam, the distance icon will appear again. But on the first speedcam, it will never appear again (until iGo is rebooted).
To appear again, the only solution is to redo the same action on another speedcam of the same type.
This bug is present also for light camera (I didn't test the other "normal" camera type).
For section camera, the bug is also present if you cancel it during the OnSection and if the end of section is never detected. When the end of section is detected, the bug is cleared.
I tested the Wal24 skin with the same Luna core, and the bug is not present. But Wal24 is displaying all information on 1 icon, and not on 2 like Pongo is doing (speed + distance/type).
I tested Pongo with different skin dates (2024 + 2024 + 2025), and the result is the same. I tested also with mod EUR or mod VB : same result.
Sound it's somewhere in data.zip.
Last edited by ppndv; 6th January 2026 at 10:16 PM.
The distance of the alert, in a straight line, is enough meters for the alert, but after leaving the adjacent street, there are not enough meters. Plugin.ini settings for the distance, specify a second alert of 50 meters and a first alert of 100 meters. And also, alerts with a route are different from alerts without a route. Perfect alerts using a route, all the dangers on the road are included in the route you are following.
Last edited by Andrey Form; Yesterday at 06:00 AM.
Hi Andrey,
This is not a matter of distance. In my simulation, the distances are enough large to re-detect the speedcam. The picture is just an illustration to explain the scenario.
If I don't shut-off the speedcam alarm by pressing on the speedcam icon of the cockpit, all is working fine. The second approach to the radar is detected and the speedcam icon in the cockpit is displayed.
But if I'm cliking the icon to shut-off the speedcam alarm, the second approach is also detected and sounded, but the speedcam icon in the cockpit is not displayed anymore for this specific speedcam.
If I'm jumping to another spot with the same speedcam type, the speedcam icon cockpit is displayed again.
But if I redo the approach the this first radar, the speedcam icon cockpit is always not displayed.
Except by rebooting iGo, the only solutions I found to display again the speedcam icon cockpit on this shutted-off speedcam is to do a shut-off manipulation on other speedcam of the same type, or, doing a complete section speedcam with end detection.
Please, try it, and let me know if you can reproduce this malfuntion.
PS : The reason of this bug is because ui_PropLayer.ShowSpeedCamera is false on the shutted off speedcam (speedcam_mods.ui).
Last edited by ppndv; Yesterday at 02:04 PM.
I don't see any errors in this situation. In reality, the skin isn't responsible for notifications, as there are numerous settings, individualized for the driver, taking into account driving habits and the terrain. It's one story in the city, and another on long distances. Stimulation doesn't provide complete information, especially the manipulation of disabling notifications and then repeating the same section. This doesn't happen in real life. Typically, the driver receives notifications even if they change their route; they don't have the time or resources to disable them.
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: +
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.
Bookmarks