Garmin Mapsource Product Creator v.8.2 + v.8.3

**Akaky** · 13th April 2013, 06:02 PM

Well, it did turn out to be trickier than expected. With either HGT_DP = 0 or "Disable 3D Models" option ticked the GENERIC_MANMADE polygons are not displayed at all in both navigation and explore modes on Nuvi 1300. With HGT_DP being any value =/> 1 contours are displayed in explore mode only. Decimal values between 0 and 1 are considered to be 0. The same is true for negative values. The GENERIC_MANMADE areas of different heights show up at different zoom levels in explore mode which suggests the model is aware of heights in a sense. Of all FID's of "Roads of Russia" 5.29 map only 1280 turned out to have extruded heights and on this map only footprints of 3D models are displayed in navigation mode. Checking all available FID's of the abovementioned map in the MPC_viewer confirmed the GENERIC_MANMADE has 0 elevation (that is, no elevation info at all, to be precise) in all builds except 1280 but for some reason having exactly the same parameters for object properties in a custom map does not make GENERIC_MANMADE areas be displayed the same way as in official maps. How strange...

**Cnfhbr** · 14th April 2013, 12:25 PM

@Akaky
Which firmware version and HWID in your device?

**Akaky** · 14th April 2013, 03:13 PM

Nuvi 1300; Software 6.20; HWID: 972

**adalbert1977** · 28th May 2013, 09:51 PM

Is it possible to use varoius FID (Family ID) values for different maps in MPC 8.x ?

**Cnfhbr** · 29th May 2013, 04:33 PM

Yes it's possible if you have multiple licenses with different FID.

**stuart1974** · 16th June 2013, 08:21 AM

I think someone should make a license keygen with a field to input the FID, that would be perfect.

Stuart

**Cnfhbr** · 16th June 2013, 09:03 AM

Thereafter, Garmin will likely modify the protection of license. Who stands to gain from it?

**adalbert1977** · 25th June 2013, 10:04 AM

Is there a way to force Garmin MPC to use mixture of higher and lower case characters in the labels??? Actually Garmin MPC converts every label in upper case from the shapefile inputs. This is an unpleasant restriction. I don't like it. For example: cGPSmapper is case sensitive, it respects the original labels.