I only use this version and are more than 20 days that I'm testing the Average Speed Camera, I can tell you that with Arimi's skin it only work in one way, with the command "max_section_time = xxx", where xxx are the number of seconds that determine the duration of the stretch. In the latest speedcam.zip files by Arimi the various commands of the Speedcam categories can be found in ux / speedcam / plugin.ini, and the max_section_time is set to 100 seconds.
When you find a starting point, after a few seconds you have the TTS voice alert, (only after the start and not 500 meters before), for 100 seconds you have the window at the top with the written warning, at the bottom left the Average Speed Camera icon appears with even your average speed, (the writing is very small,almost can not be seen).
Spoiler: image
With the Pongo skin, in addition to working with max_section_time, (by default it is set this way), it also works with the starting points and the related end points of that section. Both points must have the same TYPE, (4), the starting point must have the speed limit and the end point must have speed 0.
You have to delete the line max_section_time and the stroke it is determined only by the coordinates of the start and end points.
The screen is better than the Arimi skin, the average speed is more visible.
Spoiler: image
Still neither system is perfect, with Arimi, if during the stretch there is another type of warning, like High Accident Zone, it interrupts the calculation of the average speed, but as soon as the warning is over the calculation starts again, with Pongo instead the calculation is interrupted and no longer resumes.......
This is what happens for now.... but the work is not finished yet, I'm continuing to do the tests .....



Likes: 



Reply With Quote
Bookmarks