Skin iGO nextgen by pongo (DISCUSSION)

1. button size - Settings > Skin Settings > Cockpit > Number vertical of menu buttons
Select from 4 to 7 and all buttons are affected

Spoiler: image

[Only registered and activated users can see links. Click Here To Register...]

2. bmp -> jpg - try removing the ; from the screenshotfilename="\android_linked_root\captures\capture_%02d.jpg" line in your sys.txt file.

3. Alert Points - update your Pongo skin [Only registered and activated users can see links. Click Here To Register...]


EDIT:

2. bmp -> jpg - Only the Avic apk save the image in the .jpg format, the other apk regardless of the sys.txt configuration save in the .bmp format.

TNX again jorgeultra for yr help
1. button size : yr answer concern Number vertical of menu buttons. My question the size of the button itself small/big size.

2. 2. bmp -> jpg - try removing the ; from the screenshotfilename="\android_linked_root\captures\capture_%02d.jpg" line in your sys.txt file.
already done without success. That line works for Primo not for Nextgen. Here bellow the sys.txt commands for Primo

[interface]
capture_to_jpeg=1

[debug]
screenshotsavecameraini=0
screenshotfilename="\android_linked_root\captures\capture_%02d.jpg"

for some Primo (WinCE?) you may add
[folders]
app="\SDCard\iGO"
sdcardpath="\SDCard"
screenshot_dir="%app%/captures/"

3. I'll install the latest version skin later

Regards

Repeating:

1. My answer is exactly for your question: the size of the button itself
The amount selected will influence the size of all buttons. There is no option to choose the button size individually.

2. As I wrote with Nextegn, only the Avic apk saves images in .jpg format, not depending on any configuration in the sys.txt file.

TNX again for all these infos ;)
BTW, Is there a tool to view the cars in my computer before copying in the smartphone? I've more than 2000

Regards

Please ask this question in this Forum [Only registered and activated users can see links. Click Here To Register...] maybe someone can help.

I'm using Igo 9.18.27.736653 with Pongo skin.
The default TRACK (ROUTE)is very thin.
What setting to change that will widen the size of track.
I have already tried in sys.txt

planned_route_contour_width=1
planned_route_track_width=12 < tried different seetings

Thks
AslBal

@aslbal

It has already been discussed here [Only registered and activated users can see links. Click Here To Register...]

Quote:

---

Originally Posted by aslbal [Only registered and activated users can see links. Click Here To Register...]

I'm using Igo 9.18.27.736653 with Pongo skin.
The default TRACK (ROUTE)is very thin.
What setting to change that will widen the size of track.
I have already tried in sys.txt

planned_route_contour_width=1
planned_route_track_width=12 < tried different seetings

---

Not in sys.txt

data.zip > project_config > igo_nextgen

In my file:

Code:

---

[3d]
guidancearrow_first_size=1.1
guidancearrow_first_alpha=24
guidancearrow_second_size=0.8
guidancearrow_second_alpha=12
show_guidance_arrows=0
show_guidance_strip=1
guidancestrip_stretch=15
guidance_arrow_head_width=5.0
guidance_arrow_head_length=4.0
guidancestrip_stretch=25
guidancestrip_stretch_forward=20
planned_route_contour_width=2
planned_route_track_contour_width=2
planned_route_track_width=5
building_camera_distance_medium=6000
building_camera_distance_medium_back=5000
fade_overlap_tolerance=32
subpixelpois=1
modelviewer_scale=58982
modelviewer_pos=-135

---

Check the file you have.

Quote:

---

Originally Posted by kwbs [Only registered and activated users can see links. Click Here To Register...]

Not in sys.txt

data.zip > project_config > igo_nextgen

In my file:

---

These sys.txt entries do not work! This is the tragedy of NNG. It remained as a memory. The changes in question can be resolved in the default.vis file.

[ROADSTYLEPARAMS]
All values from 0 to 28 must be recalculated (cannot be remedied with 3 sys.txt commands)

Need to add width_road_....zip Many such files have been made. Same in Pongo skin map_visual_config.zip

OK @Tajfun

[ROADSTYLEPARAMS] record does not exist at all in default.vis file.
Do you want to be more precise and offer an absolute solution?