Thread: Truck support in NG versions

@The Bookworm,

I do agree it is not always 100% accurat, and i do think there are some things missing or incomplete in the FTR or Map files for the Netherlands, i don't think it has something to do with Nextgen of any version, i tried the same route with different ones and i get no other route planned or warnings.

For the Scania radio they don't give any information, Ive got the Premium Scania Radio, it's is a Bosch 7 620 000 063 unit, i think it's Windows os, and i can't get in the menu for update anything, only thing you do can is buy a micro-sd card with map updates.
It doesn't have a internet connection, it get TMC from radio signals, no cellular either, just a Radio/CD/ combi with USB, Bluetooth and touchscreen for navigation.
Thing is, i don't wanna loose the radio, because i have a integrated telephone system, and full steering wheel control, if i change it for by example a Pioneer, than i loose most of the steering wheel control functions and telephone, they do sell a interface for it, but not all functions work, the microphone is integrated in my seat for example.

If you can help me out, please let me know.

Spoiler: Scania Premium Radio

[Only registered and activated users can see links. ]

[Only registered and activated users can see links. ]

[Only registered and activated users can see links. ]

[Only registered and activated users can see links. ]

Grtz. Ludo.

Hello All, i tested today the program iGO NextGen 9.18.27.687519 from Jan 26 2017 without a skin and only added the Truck(World) Ux zip.

I only can tell right now, i don't see any differences in route calculation, warnings or others, it's all the same as descriped in my post 111.

If you wan't to change or try something, just let me know, for now i leave the program the way it is, all original and do some more testing.

Grtz. Ludo.

Originally Posted by the_bookworm

So, it seems (at least for me) that WORLD versions are not capable of handling extended settings.

Yes, this is what I found for NextGen9.18.27.693527-World(14Mar2017) as well and had posted early in this thread. The reason is the truck "license flag" is never true; this led me to believe either it's not "fully" cracked or not fully implemented (map engine can't handle truck data)

Truck support is implemented in software code. Not in extra plug in.
UX is just an interface for software possibilities.
For now - NOT implemented in latest World & Basar.

Cr@cking the program to work with licenses or without, is another story.

You are wrong. "Truck restrictions" are done in many places. In core/base codes such as: mapping engine and routing engine; and in presentation layer codes such as: UX's and skin. They ALL have to work to get "full" capability. I already posted proof of that. Please do NOT say things you do not know.
A "good" cracked program will fixed/replaced libraries with those capabilities. Cracking isn't just for fixing licenses. If it can't do it (especially when World release note said "truck restriction" was added) then it's not "fully" cracked. And as I already said, the license flag was false.

News flash: UX's are "software code"

Truck data for restrictions are written in fbl and ftr files. I didn't say anything about that.
Truck support depends only of software version/edition, I said.
Truck ux for World is 48kB.
There is no truck ux in AVIC/Basar/Gift/Israel/T4A/Szulin
Vehicle Selection ux is arround ~70kB for all versions, approximately the same content is in each.

If you interchange files, happens...nothing.
Payed versions of world for example still do not have extended settings for truck. That have nothing to do with patching software. Stop guessing.

We could guess what could or should be if something would or not be done one or another way.
It does not matter where or how (internally) is some function supported in some program.
It is, but not for this discussion.

Important are real useful functions of navigation.

Only "upgrade" of functionality is available by adding truck.zip from World to them, and we could discuss about their truck support as they are with or without it.

So all this theoretic (what if) discussions are pointless (off topic).

Hello,

Remember my earlier post's about Height Limit signaling?
Some have claimed that they are incomplete and that there are no warning icons on the map during real drive.
Hocus Pocus - they are?

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

PS.Special thanks to Boki_Srb and Midnight Blues!Many thanks for your recent comments and remarks.
regards wojpen

Originally Posted by Boki_Srb

Truck data for restrictions are written in fbl and ftr files. I didn't say anything about that.
Truck support depends only of software version/edition, I said.
Truck ux for World is 48kB.
There is no truck ux in AVIC/Basar/Gift/Israel/T4A/Szulin
Vehicle Selection ux is arround ~70kB for all versions, approximately the same content is in each.

If you interchange files, happens...nothing.
Payed versions of world for example still do not have extended settings for truck. That have nothing to do with patching software. Stop guessing.

Really? If truck restriction data is in .fbl then why have .ftr? And what happen when you don't use .ftr, you still get truck restriction? Who is guessing now?

No, you said "Truck support is implemented in software code. Not in extra plug in." Which is WRONG! So stop trying to rewrite what you said.

You can look at size all you want, it really doesn't tell you much. You must examine the codes. Fact is fact, code don't lie. There must be some change in core codes between World and Gift (at least in regard to truck restriction). Gift allow truck restriction and World doesn't. Why? Simple, World doesn't have truck restriction license enabled. Period! License is ONE of many criteria that must be met before you get truck restriction functionality.
Yeah, more "guessing"

Spoiler: .

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

If you do not use (or can't use) truck.zip UX, you won't get certain functionality. If you are happy without it, good for you. Just because some proggy doesn't have (or can't use) truck.zip UX, doesn't mean you have full truck restriction. So the requirement of needing/using truck.zip UX said nothing about how truck restriction are implemented. Look at World, no need to use the bogus truck.zip UX that comes with it, you still can't access extended settings.

Nuff said!

Originally Posted by Midnight Blues

We could guess what could or should be if something would or not be done one or another way.
It does not matter where or how (internally) is some function supported in some program.
It is, but not for this discussion.

Important are real useful functions of navigation.

Only "upgrade" of functionality is available by adding truck.zip from World to them, and we could discuss about their truck support as they are with or without it.

So all this theoretic (what if) discussions are pointless (off topic).

OP asked a question and as far as I'm concerned it has been answered. There is no "guess" in what I say, just look at the codes. You can take truck.zip from Avic (if you change Arimi's mod) not just World and it will work. They have similar code base. Compare them and you shall see. And as I said before, if you are comfortable with just the "basic" truck restriction, good for you.

Originally Posted by wojpen

Hello,

Remember my earlier post's about Height Limit signaling?
Some have claimed that they are incomplete and that there are no warning icons on the map during real drive.
Hocus Pocus - they are?

-= Hidden Content =-

PS.Special thanks to Boki_Srb and Midnight Blues!Many thanks for your recent comments and remarks.
regards wojpen

Quite incredible that you keep insisting on speedcam being part of the truck restriction subsystem. Your "properly prepared speedcam.zip file" was to show a single class (Max Height) as a speedcam alert (NOT TRUCK ALERT) Why don't you "properly prepare" a "Max Weight" alerts for use by speedcam.zip as well. While at it, also hazard transport. So users have to collect all truck related "speedcam data" to use for truck alerts? Nonsense, truck restriction data comes from .ftr ONLY!