Thread: Skin IGO NextGen LUNA by Pongo (DISCUSSION)

Yes, the file name and folder name must be identical.

speedcam_mod_eur_3dfv12.zip
plugin.ini � ux\speedcam_mod_eur_3dfv12

If the names don't match, the UX plugin won't work.
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: +

[Only registered and activated users can see links. ]

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.

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.

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).

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.

If you're using Lockito for route tracking, adding new coordinates to the map may cause incorrect notifications, especially for average speed. If you want to test average speed, all data must be in speedcam.txt; only then will the test be accurate. Regarding section closing, using OSC solves all problems. You don't need to have all the data; just code 4 is sufficient.

[Only registered and activated users can see links. ]

OK. I finally finish the reverse engineering of the speedcam plugin, and I can explain what is happening :


The speedcam icon visibility is triggered by PropLayer.ShowSpeedCam (speedcam_mods.ui)
PropLayer.ShowSpeedCam is linked to MODEL.lua.Speedcam_FirstClick.

MODEL.lua.Speedcam_FirstClick is changed by sc_ResetFirstSpeedcamClick() in speedcam.lua.
sc_ResetFirstSpeedcamClick() is called by sc_ResetFirstSpeedcamClick_new()
sc_ResetFirstSpeedcamClick_new() is called on events when speedcam starts and speedcam ends.

By pressing on speedcam icon on cockpit to mute it, function sc_SpeedcamClick() in speedcam.lua is called.
sc_SpeedcamClick() is calling twice, with a delay, the function sc_ToggleSpeedcamSound(). Twice with a delay, because it's acting like off/on actions.
In sc_ToggleSpeedcamSound() the current speedcam id is saved in the local data gSkippedSpeedcamID of speedcam.lua.


So, when the speedcam "A" has been muted previously, if this speedcam "A" raises again, the speedcam icon in cockpit will not be displayed again. This is voluntary done and I don't understand the reason, because notification, alarm, approach sound, overspeed of this speedcam will work.
And important to notice : when this speedcam "A" will be "on back" phase, the speedcam icon will be displayed !! It has no sense to display it now and not before.

Could be that this code is a rest of an old part of code when the functionnality was completed. Or if PONGO can explain why this code is always existing, I'm curious to know.


In case of an average speedcam : When doing the manual stop of the average speedcam alert, the speedcam id is always 0.
This is because MODEL.navigation.curr_speedcam.id() is only known at section begin and end positions. Outside of the speedcam position, id is 0. So, id 0 is saved in gSkippedSpeedcamID.

On the next average speedcam zone, the beginning of the speedcam is detected and the icon is displayed at this moment because MODEL.navigation.curr_speedcam.id() exists and is different than gSkippedSpeedcamID = 0.
But few meters later, when the speedcam is on back, MODEL.navigation.curr_speedcam.id() is 0 again, and now is equal to gSkippedSpeedcamID. Then, the speedcam icon disappears, even if the average zone is always correctly detected and sounded.

On speedcam end position, if the end of the section is correctly detected, function sc_ToggleSpeedcamSound() is called twice by function sc_SetLastSpeedcamSpeedLimit(). Because we are at a speedcam position, MODEL.navigation.curr_speedcam.id() is valid and is saved in gSkippedSpeedcamID

This is explaining why the icon of speedcam section will appear again in the next section if the section end is correctly detected, and why not if the section end is not detected.


I would propose to apply the following changes in speedcam.lua to delete this weird reaction. It's just deleting some few parts of the code.

Spoiler: +

../..
gFirstSpeedcamClick = true
--gSkippedSpeedcamID = ""

function sc_ToggleSpeedcamSound()

if gFirstSpeedcamClick and not MODEL.navigation.curr_speedcam.skipped() then

gFirstSpeedcamClick = false

if MODEL.navigation.curr_speedcam.speed_warning_sound_active() then

MODEL.navigation.curr_speedcam.speed_warning_sound_active = false

elseif MODEL.warning["speedcam_soundtype_" .. MODEL.navigation.curr_speedcam.category()]() == 0 then

MODEL.navigation.curr_speedcam.skipped = true

end

--gSkippedSpeedcamID = MODEL.navigation.curr_speedcam.id()

else

MODEL.navigation.curr_speedcam.speed_warning_sound_active = false

MODEL.navigation.curr_speedcam.skipped = true

MODEL.lua.Speedcam_FirstClick = false

gFirstSpeedcamClick = true

end

end

function sc_ResetFirstSpeedcamClick()
--if MODEL.navigation.curr_speedcam.id() == gSkippedSpeedcamID then
--MODEL.lua.Speedcam_FirstClick = false
--else

gFirstSpeedcamClick = true

MODEL.lua.Speedcam_FirstClick = true

--end
end
../..

I also made some other corrections in speedcam.lua :

- Avoid the speedcam icon in cockpit blinking when an average speedcam section is starting
- Detecting the average speedcam end, even if the speed of the end point is not 5km/h (it works with 5 or without).

If you are interresting of this changes, please let me know.

I'm also working on the case of speedcam without speed. Problem is, especially in town, that the speed at the beginning of the alarm can be different than the speed at the speedcam position. It's bad to announce "50 km/h" to the driver if 10m later, it's 30km/h. I think it's better to announce a speedcam without speed information in that case.