iGO 64-bit for Trucks [discussion]

**Andrey Form** · 5th November 2026, 02:30 PM

As a continuation of our technical analysis regarding the NNG 9.35.2 64-bit executive core limitations, I want to introduce a brilliant, community-tested hardware-software workaround. This method was discovered and fully verified in real-world conditions by senior member @mtb57, and it completely shifts the paradigm of how we can use modern 64-bit devices on heavy commercial routes without rolling back to dead 32-bit platforms.

🛑 The Core Problem Recap

As summarized earlier, when you configure a native TRUCK profile combined with HERE Maps, the 64-bit binary algorithm panics due to a missing Truck Toll Matrix licensing layer. The engine views electronic toll checkpoints (like Germany's Toll Collect or Poland's e-TOLL) as physical concrete road blocks and calculates massive 2,500 km loops to avoid them.

🛠 The "Submarine" Inversion Workaround (by @mtb57)

Instead of forcing the broken truck routing engine to deal with financial toll restrictions, we can completely blind it to the toll layer while keeping the physical safety constraints 100% active.
The Step-by-Step Configuration:
1. Create a Passenger Car (PKW) Profile: Inside your iGO World 64-bit settings, create a brand-new vehicle profile, but select Car (PKW) or Camper/Wohnmobil as the structural base type.
2. Inject Heavy Fleet Parameters: Inside this "Passenger" profile, manually overwrite the physical parameters with your actual heavy vehicle metrics:
• Max Height: 4.0 m
• Total Weight: 40 t (or your actual weight/axle limits)
• Length & Width: Your exact trailer dimensions.
3. Map Settings: Keep HERE Maps (.fbl + .ftr data) active.

🧠 Why this closed-code logic actually works:

By transforming your 40-tonne fleet into a "chassis of a passenger car" for the core engine, you instantly trigger two internal architectural changes:
1. Toll-Blindness (No Loops): The 64-bit routing engine assumes it is guiding a car. It completely ignores the LKW Truck Toll Matrix and stops treating toll gantries on Autobahns as physical roadblocks. The engine will instantly calculate the shortest, clean highway route across the EU, even with "Avoid Tolls" enabled for regional sub-sectors.
2. Physical Gatekeeper Active: Here is the beauty of the NNG engine structure — the physical dimension layer (.ftr) remains a global priority blocker. Even when running a Car (PKW) profile, if the executive code encounters a bridge with a physical height limit of 3.6m, or an axle weight restriction on a rural road, it cross-references it with your custom profile metrics. It will strictly refuse to route your "car" under that low bridge. You will never get stuck or clip your trailer.

📋 Professional Warning & Field Logistics

While this workaround is a massive breakthrough that prevents systemic looping on modern 64-bit devices, drivers must apply standard professional caution:
• Urban Transit Restrictions: Because the core thinks you are driving a car, it will no longer care about signs that restrict entry based purely on "Heavy Goods Vehicle" classification (unless there is a hardcoded weight/height filter on that specific street attribute).
• Final Mile Reconnaissance: As always, the on-road navigation is your safety backup, but your head controls the logistics. Use this workaround to smoothly pass through highway toll nets, but keep your eyes on local municipal signs when exiting major freight corridors into industrial zones.
Kudos to @mtb57 for deep-dive testing and providing the community with a vital operational alternative in the pure 64-bit era.

**Boki** · Yesterday, 10:15 PM

Originally Posted by SlawekPiet

iGO Nextgen 64-bit – Are TomTom maps fully reliable for heavy truck navigation?

Since we have confirmed the HERE truck routing issue in both AVICSYNC 9.35.2.227616 and World 9.35.2.252374, I would like to clarify one more important point...

I remembered something
AVIC with Here maps 2025.Q2 had completely covered content, all files (fda/fpa/ftr...) active
All truck restrictions appeared in the menus

Dear colleague @AF

Spoiler: read

**Andrey Form** · Today, 05:26 AM

Let’s put the final pieces of the puzzle together based on real-world road changes in 2026, rather than blaming only the app builds.
Why did 64-bit iGO work fine in 2025, and why did the 2,500 km loops start in 2026?
In 2025, drivers used 64-bit versions (both World and Avic) with HERE 2025 maps without massive detour complaints. The reason is simple: back then, national roads in Poland and Germany still had toll-free transit corridors. Many of the gantries and poles along those roads were operating in test mode or as traffic counters.
Starting in early 2026 (specifically the major Polish e-TOLL expansion on February 1, 2026, alongside updated German Toll Collect regulations), those test poles were switched to active toll collection. Both countries closed virtually all free transit loopholes for heavy commercial vehicles to maximize budget revenue.
How 32-bit vs. 64-bit engines handle this new reality:
1. 32-bit Nextgen (Israel/PAL): When "Avoid Toll Roads" is checked, and the engine sees that no toll-free path exists, its routing weights allow it to override the restriction and route the truck straight through the toll highway anyway.
2. 64-bit Nextgen (9.35.2): Its routing algorithm treats the "Avoid Toll Roads" checkbox as a hard physical block when dealing with the updated 2026 toll attributes in HERE maps. Because free transit corridors no longer exist in Poland and Germany as of 2026, the 64-bit engine strictly obeys the setting and calculates absurd 2,500 km detours around entire countries.
What’s next for drivers:
The trend is obvious — European governments will continue expanding paid road networks for commercial transport, and toll-free transit across the EU is becoming a thing of the past.
• If you use 64-bit iGO with HERE 2026 maps, simply uncheck "Avoid Toll Roads" in your route settings. The engine will immediately stop looping and route you straight along the highways while keeping all physical .ftr restrictions (height, weight, axle load) active.
• Keep "Avoid Toll Roads" enabled on 64-bit only if you downgrade to HERE 2025.Q2 maps or switch to a classic 32-bit device.

**Boki** · Today, 07:49 PM

I will continue to focus on apps

What is most obvious and interesting - Avic, although it is intended for cars, has always had complete truck support. At least that was the case with the previous generation
What is interesting about the new generation is that there is no separate ux, but it is possible to select a truck in the settings and set its parameters. Only the question of available licenses and content coverage remains

World, on the other hand, was never intended for heavy truck use also, truck functions were obtained only with an adequate ux. With the previous generation, it was achieved with a lot of manipulation, with this one - I still don't have adequate feedback, but the ux is too generic

P.S:
I finally got the weather forecast working in Avic
[Only registered and activated users can see links. ]

Thread: iGO 64-bit for Trucks [discussion]

Thread Tools

Display

Advertissements

Bookmarks

Bookmarks

Posting Permissions