Technical Note - Derivation of the YY.DD as shown on the Infotainment Screen
I have now been told
how to read that YY.DD date off the files after putting out my request for some time for a bright spark into these Mib3 files. It's been delivered. If you don't want to load up the file you can look up what year the and periods the files relate to. It's important with MIB3 files you don't alter the contents because you can't they are signed and they will refuse to load. So no tampering with the files like mib2 standard maps.
Anyhow, this is how you do it thanks to C34 on the Briskoda site... only two posts popped up to tell me. You need to install
DB Browser for SQLite. This has an extension in it to read the NDS Associate files, the normal SQL Lite brower that is popular won't. Install the MSI of DB Browser for SQLite in the link above.
We now use C34's text... In this example on the file
Update OI_P119_EU_202425_Offline_Update.zip contains data from 23.12 (YY.MM).
You can check this for example in the MIB31_EU.ROOT/3D/PRODUCT.NDS file. This is a SQLite database, you can find this information in the updateRegionTable table.
You open the table up and have a look. Does
help if you have database experience
. On the VW file, for 2024/25 I got this:
View attachment 43716
So that is they, for the technically minded of where the YY.MM is stored in the files. Handy if you come across one and not sure. That's how you nose about those files not that you need to... or you can just trust websites like this.
Just a side note for those that are use to looking inside the files for release information. Dropped down here due to edit size in original post.