Visit our Popular Forums

bdbcat · 10-04-2015, 17:21

Testers...

About raster chart performance:

OA uses compressed texture caching for raster charts, just like O desktop.

This means that the first access of a particular chart at a particular location will be slow, and the spin wheel will go round and round.... This effect will be most apparent at small scales, ie highly zoomed-out viewports.

Subsequent accesses to this chart will be faster, as the texture cache is populated and saved to sdcard.

Also, OA is intended to run only in OpenGL mode. This will be made a fixed, immutable setting in the next version.

Thanks
Dave

bdbcat · 10-04-2015, 17:27

Hi testers...

I am interested in subjective comments regarding performance of OA, especially with different chart types and use cases that you yourself might encounter on a daily basis.

Thanks
Dave

barnakiel · 10-04-2015, 17:29

Yes. Drag and drop (and loss) of folders when choosing the chart folders here too.

Ooooppps.

Things happen when testing. Good if can be fixed up in future code.

Love,
b.

RhythmDoctor · 10-04-2015, 17:30

Nexus 4 (phone) running Lollipop 5.0.1

Some quickies:

ENC charts are not working. Are they turned off in this version? (Yes, I rebuilt the chart database after loading them)

Routes display but have some issues. The connecting lines are so thin in places that they totally disappear. Arrow heads show. Haven't tried displaying tracks yet.

I am getting Wxwidgets error messages after exiting many dialogs.

ejs · 10-04-2015, 18:48

Dave,
On my Moto Xoom Android ver 4.1.2 Phys Screen on auto reports 203mm, measured with a ruler it is 215mm. In both cases the icons are 9mm square. I cannot measure any difference between the two phys screen sizes.

BTW, the bottom 100 (I think) pixels are reserved for the android back, home menu etc Icons. O tries to use this area and so the status bar and chart bar are hidden by this bar and are unusable. If I enable one I can't see it at all, If I enable both, I can see the top half of the chart bar.

Best, Eric

barnakiel · 10-04-2015, 19:31

Quote:

Originally Posted by ejs

BTW, the bottom 100 (I think) pixels are reserved for the android back, home menu etc Icons. O tries to use this area and so the status bar and chart bar are hidden by this bar and are unusable. If I enable one I can't see it at all, If I enable both, I can see the top half of the chart bar.

Best, Eric

Same finding here, hiding charts bar.

I think there is a way to use 100% screen. I believe I have seen 100% apps before.

Maybe the OCPN menu bar could be written so that it fades to near transparency?

This bar covers a large portion of our 7 incher.

b.

barnakiel · 10-04-2015, 19:35

Quote:

Originally Posted by bdbcat

Hi testers...

I am interested in subjective comments regarding performance of OA, especially with different chart types (...)
Thanks
Dave

Would it make chart redrawing / zooming / panning faster if I skin the charts folder?

I do not need all CMAP and all BSB charts at once. I could make skinned chart folders say with just the regions which I am actually using.

Would this affect speed in any way?

b.

RhythmDoctor · 10-04-2015, 19:37

Quote:

Originally Posted by ejs

BTW, the bottom 100 (I think) pixels are reserved for the android back, home menu etc Icons. O tries to use this area and so the status bar and chart bar are hidden by this bar and are unusable. If I enable one I can't see it at all, If I enable both, I can see the top half of the chart bar.

FWIW, my phone has the Android virtual keys at the bottom of the screen, but O does not interfere with them. O only uses the portion of the screen above the virtual keys. You can see the chart bar and the status bar (if both are activated). No interference between the Android keys and the bottom of the O window.

It's possible that the different behavior is due to different Android versions.

barnakiel · 10-04-2015, 19:47

Quote:

Originally Posted by bdbcat

Hello testers...

1. Does the OA default screen size calculation work for your device, resulting in 9 mm icons?
2. If the default calculation is wrong, and you override it in "options->display->advanced->Screen size", do the toolbar icons then show as 9 mm square?

Thanks
Dave

Acer Iconia B1:

Slightly off, 162 mm (calculated) vs. 152 mm (actual).

Icons 8 x 8 mm

b.

bdbcat · 10-04-2015, 20:55

Testers...

OK, talking about the lower 100 pixels of the screen, where android persistent control buttons live, e.g. back, home menu, etc......

If OCPN interferes with these buttons, please respond and tell me the version of android you are running. There is some special code processing necessary to identify the usable screen height based upon the android version. A well known android glitch. We may have the version definitions incorrect...

Thanks
Dave

Icnoships · 10-04-2015, 23:23

Great stuff.

This is a screenshot of OA installed on a google nexus 10. running version 4.4.4
The actual screen resolution is 2560x1504.
wxdisplaysize picked this up in the log.
Android auto display size is estimated at 203.2mm.
the actual size is 216mm.
OpenGL on.
No text apart from soundings.

Have pushed every button on/off to try an loose the two vertical repeated strips.
They do disappear when pinch zooming but immediately reappear on release.

Switching on the device only internal gps and starting oa causes a crash.
starting oa and then activating gps makes for a crash.

mo

bcn · 11-04-2015, 00:49

Playing with the display settings:

real display size is 170mm - results in 9mm icons with the exception of the AIS icon (all of them) rendered at 4.5mm

tweaking display size will scale the icon size accordingly - with 340mm everything is in 4.5mm.

Input > than 340 will not shrink the icons further.
The AIS icons are rendered always with 4.5mm

A screen size of 170150mm entered by accident did create interesting effects..

verkerkbr · 11-04-2015, 03:08

This Alpha version of O for Android works on my Lenova Thinkpad including the internal GPS receiver. Works very fast.

The (external) SD directory with the ENC charts is found and the database seems to work. Although the Window for rearranging the database is grayed out.

But no display on the screen. Message states Overzoom.

Charts are the Dutch ENC's.

Tried several display settings, but this does not help.

Thanks for all the work on the OpenCPN project.

Bram