Thread: iGO Speedcam (DISCUSSION)

FAQ iGO Truck speedcam

So, the content/speedcam folder

What do truck drivers use when installing iGO? The answer is usually speedcam.spc.
Why spc? A long-hauler's answer: "Well, they come with the maps."

Spc files are usually old; even by the time the maps were published, they were already six months old. Not to mention that speedcam.spc isn't iGO; they're made by map providers HERE and TomTom, since they have licenses to publish maps for iGO. Spc files usually have speed limits for passenger cars. Doesn't that bother anyone? When your maximum speed is 90, and the screen limit is 130, they still manage to be used, because they come with the maps.

speedcam.spc + speedcam.txt, It's generally accepted that SPC files have an advantage over TXT files. Of course, yes, but that's only if the same type is in the same place. If the types are different, two alerts are guaranteed.

speedcam.spc (speed for cars + speedcam.txt (speed for trucks) — that's a killer combination. Anyone using this setup should be prepared for changes, and may even have to ditch iGO altogether. Pay particular attention when using the Arimi or Pongo skin in iGO. The Pongo skin, due to the fact that it completely rebuilt the entire alert system, moving all settings to TXT files, doesn't play nice with SPC and TXT files. SPC dominates TXT files and prevents the skin from working, causing alerts to freeze—a difficult choice. Average speed cameras refuse to open sections. The Arimi skin, since it's the only skin that hasn't been modified for average speed cameras, happily starts a section at 130 km/h and shuts off after 60 seconds (depending on your timer settings). Speedcam.txt, which uses truck speed, is completely unusable.

Conclusions,
Is speedcam.spc at 130 km/h acceptable? Use Only content/speedcam - speedcam.spc.
If you are using speedcam_Truck.txt or speedcam_iTruck.txt, consider not using speedcam.spc.