Nextgen (Navgear) 9.19.2.543580 (Jun 1 2015)

**Mike Hunt** · 30th September 2015, 07:38 AM

Originally Posted by ypsmav

Hi,
Now I found that I can not set up the 3D car model.
Does someone knows which is the ux related to the selection of the car model?

In many cases, if you delete this:
vehicle_selection.zip
from the UX folder, the option to choose a car model in Navigation View/Map Appearance magically appears.

**1franka** · 30th September 2015, 08:37 AM

Originally Posted by ypsmav

...Now I found that I can not set up the 3D car model.
Does someone knows which is the ux related to the selection of the car model?

Hi
Can you put up a link to the "ux" folder that you are using.

Much appreciated

Thankyou.

**beer2beer** · 1st October 2015, 04:22 PM

Trying to figure a way to get larger roads on screen. I've read this entire thread but no solution so far. As mentioned previously by another member, which parameter(s) must be changed in default.vis to get larger roads on screen? Thanks in advance!

**fob2310** · 1st October 2015, 04:26 PM

Here you have default.vis with larger roads:

[Only registered and activated users can see links. ]

**1franka** · 3rd October 2015, 09:40 PM

Hi ypsmav

is it possible to post a copy of the "ux" folder that you obtained from a Brazillian forum.

Thankyou

**ypsmav** · 5th October 2015, 06:07 AM

Hi 1franka,
I'm not using the Brazilian UX anymore, it was the previous version (9.19.1...)
I managed to make the voice radar warnings in the version from this thread, but the warnings are not working as in the primo.

I've had to update the voice (I'm using Spanish) for the new guidance and remove any radar speech from the config.sys

Sent from my phone

For those having issues with the radar warnings (As I had), you need to modify the voices files as follows:
Edit the TTS voice files and look for the folder i18n/dictionary.voice

Add the following:
Speed camera ahead.="zzzz"
Speed camera.="zzzz"
Mobile speed camera ahead.="zzzz"
Mobile speed camera.="zzzz"
Average speed camera ahead.="zzzz"
Average speed camera.="zzzz"
Red light camera ahead.="zzzz"
Red light camera.="zzzz"
Railway crossing ahead.="zzzz"
Railway crossing.="zzzz"
Bus lane camera ahead.="zzzz"
Bus lane camera.="zzzz"
High accident zone ahead.="zzzz"
High accident zone.="zzzz"
School Zone Ahead.="zzzz"
School Zone.="zzzz"
Town entry point ahead.="zzzz"
Town entry point.="zzzz"
Red light and speed camera ahead.="zzzz"
Red light and speed camera.="zzzz"
Toll booth ahead.="zzzz"
Toll booth.="zzzz"
Congestion charge zone ahead.="zzzz"
Congestion charge zone.="zzzz"
Dangerous area ahead.="zzzz"
Dangerous area.="zzzz"

translate the right side ("zzzz") to your language, and it should work now.

**ypsmav** · 9th October 2015, 07:04 PM

Hey guys,
After tweaking this version, I'm happy with the results and happy to change from Primo to NextGen permanently.
I have 2 issues that still couldn't solve:
- starting time. When i launch the nextgen it takes about 10 secs to show the logo and about 20 secs to start. I've slim the nextgen add much as possible (removed ux and resolutions not used) but still slow start. Any idea?
- over speed warning. I can't get the overspeed warning by voice.

All the rest seems to be working fine.

Sent from my phone

**Mike Hunt** · 10th October 2015, 07:37 AM

Originally Posted by ypsmav

- starting time. When i launch the nextgen it takes about 10 secs to show the logo and about 20 secs to start. I've slim the nextgen add much as possible (removed ux and resolutions not used) but still slow start. Any idea?
- over speed warning. I can't get the overspeed warning by voice.

1) Start time for Nextgen is inherently slow. Much is due to the amount of customization that can be done compared to some other Nav Apps that are more locked down with their look and function. Every line in sys.txt, every UX module, every voice file, every map, etc is processed at start up. If you have already trimmed some things back, you may have saved fractions of seconds (it all add up), but probably nothing much more to do about that.
2) Assuming you are using a TTS voice, you may be missing a line (or more) in it's dictionary.voice file, Like this:

The speed limit is %s!="The speed limit is %s! Slow down."

If you know how to edit a voice file successfully, try adding this to dictionary.voice.

**osiris4isis** · 10th October 2015, 07:45 AM

I'm sure Nextgen is slower than Primo; but I don't think it would be very much. 20 secs to start is way too slow. Is Primo also took 20 secs? The only things that Nextgen gets you is better organization and more consistency in the buttons and layout of them via built-in skin. Compare to Amigo (which run on the slowest processor of WinCE 320x240), Nextgen is a dinosaur. Please someone work on making a skin with "Avg driving speed" for Nextgen, soon!