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.