Thread: Skin iGO nextgen by pongo (DISCUSSION)

This plugin was created separately later, I can't remember who the author is. Although we can probably (for sure) find it on the forum.
Also, this plugin is not responsible for audio, at least not on its own. Language files are and additional audio warnings

@rondoan / #3972
Attaching the two UX files for users to try out...

toll_booth.zip

Spoiler: Download

This post requires you to click the "LIKE this post" button and hit F5 to read this content.

toll_button.zip

Spoiler: Download

This post requires you to click the "LIKE this post" button and hit F5 to read this content.

The TomTom icon shows that the skin supports the MapChanger feature, but for it to actually work, you must manually configure the directory structure on your device.Before asking basic questions in a development thread, you need to learn how iGO handles map files. Read this guide carefully to understand where to put your files:🔗 [Only registered and activated users can see links. ]

Thank you, Andrey_Form !
You are so detailed and straight in your instructions that there is no need to mention my question was for the mapchanger itself, i.e. which files for the map changer I have to look for (and arrange, eventually)

But you are compeltely right I have first to know the folder structure, Yes !
THX to the link you provided I'm now clear the map content of each provider have to be put in a separate folder. This is valid also for "building", "poi" and "phoneme" content as well.
To resume: if any specific content from a map provider is available - it should go to its own folder. And accordingly to the link with the respective folder structure.
So, let supppose I have already downloaded the map content by TomTom and Here (there is one by OSM too) (I did it).
Suppose I have put it in their respective folders, named accordingly.
Do I have to look out for, and put any new, additional files, (apart of the content ones) let say: ux files, .zip files, etc, somewhere within the Igo Nextgen folders assuming this nice skin here is in use ?
Do I have to add some lines in the sys.txt as well, in order to make the whole thing working properly ?

Once again: A big Thank You! for assistance !

Note: If there is more appropriate thread for my questions - please move them there and show me the path - I will follow your instructions.
Have a nice day!

Mate, you're asking too many questions.
The TomTom and "HERE" maps go into the same folder. (no separate folder needed)
Do it, and you'll see the result: the Mapchanger becomes available.
And delete the "phoneme" files, they are unnecessary on Android.

@Francisco LR
You are facing this issue because you are trying to mix two completely incompatible speedcam ecosystems: the EUR+ database and the NC (New Coding) plugin. They use entirely different encoding systems (ID mappings) and cannot be used together.
As [Only registered and activated users can see links. ] in Encodings & Compatibility FAQ, every UX plugin mod is tailored to a specific encoding standard. The "speedcam_mod_NC_..." plugin you installed is designed strictly for the NC / NC Truck structure. When you load Alain57's "A_Alain57_Alertes_EUR+_3D.txt" database into it, the NC plugin misinterprets the EUR+ data IDs. As a result, the script fails to link the coordinates to the correct visual models, completely breaking the truck animations on your map.
To fix this, you must choose one consistent setup:
1. If you want to keep Alain's EUR+ database, you must replace your current UX plugin with Andrey Form's dedicated EUR+ Mod AF plugin.
2. If you want to keep using the NC Truck plugin, you must delete that EUR+ text file and download a speedcam database compiled strictly in the NC Truck encoding format.
Once your database type matches your UX plugin type, the animated truck models will render properly from your ui_nextgen folder.