Thread: iGO Nextgen Avicsync 64bit, Pongo skin [mod FotiL]

Hi Boki,

Colleague, let's look at the raw facts instead of old habits. When a user completely deletes the [rawdisplay] section from the sys.txt, the engine doesn't go blind. It instantly falls back to the default rules inside the data.zip (project_config/igo_nextgen.ini).

Since AnthonyGreek mods the Pongo skin, he uses the data.zip from the Pongo package. If we open that file, we can see exactly what is coded in the native [rawdisplay] section:

[rawdisplay]
;force_renderer="RENDER_MOYA"
always_use_high_precison_in_vs=1
always_use_high_precison_in_fs=1
early_high_dpiclass_round=1

As you can see, the rendering is completely left to iGO and Android to handle automatically. There are no rigid screen restrictions forced here.

This is exactly why Anthony's test in post #84 ended up the way it did. When he left sys.txt blank, the native auto-scaling took over. The 9.35 engine and Android communicated perfectly, and the interface scaled beautifully on its own, providing larger icons and text. It worked so well that his custom, manually enlarged fonts became unrealistically huge on the screen, forcing him to go into his AvSpeed UX and actually decrease the sizes!

I am no programmer, just a truck driver, and I am at the age where I also need +1.5 reading glasses, so I completely understand the need for large, readable layouts while driving. But the reality is: any testing here will only yield as many different results as there are different, customized data.zip files being used by our members. Forcing rigid values in sys.txt usually just chokes the native engine's ability to scale properly.

On any device that is 10 inches or smaller, iGO's native auto-scaling handles the proportions perfectly out of the box. Trying to use monster tablets over 10 inches for navigation is not recommended anyway—mounting them on the windshield is legally forbidden in most countries due to blocking the driver's view, and the software was never tailored for that size. Now, if someone runs it on a regular device and still finds the icons or fonts too small after clearing sys.txt, the correct way is this:

[rawdisplay]
base_dpi=
dpi=

Look, I don't own every single navigation-ready device on the global market. But the 4 different devices I currently run and test all display perfectly sharp and big using this exact method. This forum is weaponized with hundreds of members running all kinds of different hardware. If the community starts testing builds with a blank sys.txt [rawdisplay], we can verify this across dozens of hardwares. Maybe a new direction for the forum?