OpenCPN Version 5.1.529 Beta Test

[bcn]

Originally Posted by bcn

Dave...


thanks for the soundings size slider.
However, it has no effect on macOS.....


Hubert

To be more precise: does work fine under macOS for plain S-57 and S-63 charts, but not for oeSENC.

[bcn]

Installing oeSENC 4.2.10 (managed update) and restarting OCPN brings the feature up for oeSENC charts as well.

[bdbcat]

bcn...


" and restarting OCPN"....
Theoretically, OCPN should not need a restart to reflect the new oeSENC plugin behaviour. I will double-check this.


Thanks
Dave

[bdbcat]

cagney....


re: "Better synchronizing is needed."


This is as intended.
In order to avoid enlarging the right-click context menu too much, we do the following:
1. If the current mode is "north-up", the context menu offers "course-up" option. If the system is receiving HDT info, "head-up" is also offered.
-later-

2. If the current mode is anything other than "north up", the context menu offers only the option to switch back to "north-up".



Maybe the menu entry should say "Switch to North-up", etc. ??


Hope this is not too confusing.


Thanks
Dave

[cagney]

Dave

re: "Better synchronizing is needed."

Thanks for the clarification. I fell into your "trap". I was to quick.
I'll document the intended behavior.

Thomas

[Hakan]

Originally Posted by bdbcat

bcn...


" and restarting OCPN"....
Theoretically, OCPN should not need a restart to reflect the new oeSENC plugin behaviour. I will double-check this.


Thanks
Dave

Works "on the fly" (wo restart) on Win10 using oeSENC v 4,2,10
Håkan

[Tolt]

Surface GO2 LTE (with GPS/GLONASS) m3 processor
8GB RAM
Windows 10 Pro 2004
Coast Guard ECN and Rastar Charts: All of California, Oregon, and Washington (excluding navigable rivers) on a 128GB SSD.

I'm currently on the last leg (8 hours south of Columbia River) of an Outbound 46 sailboat delivery: L.A. to Seattle.

5.1.529 Observations
With 5.0, I was getting chronic Crashes to Desktop (CTD) on 2 different PCs, just zooming and panning Coastguard ECN and Rastar Charts. Dave had me switch-off OpenGL and that solved my problem. Even better is that 5.1.529, WITH OpenGL, is Rock-Stable. No crashes. Love it. Happy to have OpenGL back.

With 5.1.529, when creating a route, when I get to the edge of the screen, instead of automatic, orderly panning, the chart goes wildly erratic, making it impossible to drop the next waypoint. This is with and without Chart Smooth Panning/Zooming selected.

Chart Selection, Piano Keys are not very responsive to touch (Double Tap) input. I assume the cause is a delay while loading the selected chart package, because, eventually, chart switching is instant. (I am fond of switching between the ECN and Rastar charts.) I could use an hour-glass, or some kind of message to let me know the computer wheels are churning. That would stop me from double-tapping 7 or 8 times, trying to get the chart to switch. I have seen something like "Preparing Rastar Charts", but that is rare.

Lastly, I'm having a little trouble with Geolocation TCP reliability. (It's the App that creates a NMEA stream from my onboard GPS and OpenCPN.) Totally off topic, I know, but it's just one of the little problems I'm having with my enjoyable OpenCPN setup. Also, I swear there was a couple of times where OpenCPN connected with my Surface GO GPS without Geolocation TCP.

[Jon Hacking]

Originally Posted by Tolt

... Chart Selection, Piano Keys are not very responsive to touch (Double Tap) input. I assume the cause is a delay while loading the selected chart package, because, eventually, chart switching is instant. (I am fond of switching between the ECN and Rastar charts.) I could use an hour-glass, or some kind of message to let me know the computer wheels are churning. That would stop me from double-tapping 7 or 8 times, trying to get the chart to switch. I have seen something like "Preparing Rastar Charts", but that is rare...

I'm having a similar issue with my mbTiles the FIRST time they're accessed. I've now created chart groups for my ArcGIS, Bing, GE, CMap, & Navionics mbTiles, so I can switch between them easily. But the first time I try to switch to a new chart group (& therefore, a new multi-GB mbTile) it appears that nothing happens.

Tolt, one possible work around for you is to try to move the chart slightly after tapping your piano key. For me, this seems to kick OpenCPN & it then displays the Win10 rotating circle, so at least I know it's taken my keystroke & is now digesting my huge mbTile so it can display it.

Note that this only happens the first time I try to access a new mbTile. After that, switching between chart groups (mbTiles) is virtually instantaneous. I take this first-time delay as the price for OpenCPN waking up faster initially, which is a good trade-off. An indication that it's taken my keystroke & is thinking about it would be nice, but for now I'm OK with the above work-around. This is SOOO much better/faster than 5.0, so thank you for that!

[Schnapsy]

Hi,

I compiled and then installed the latest available version of OpenCPN on github.

I then installed the VDR plugin which is available in the catalog but the two icons does not appear, even after uninstalling / reinstalling the plugin, restarting OCN, etc.

[SCarns]

Originally Posted by Schnapsy

Hi,

I compiled and then installed the latest available version of OpenCPN on github.

I then installed the VDR plugin which is available in the catalog but the two icons does not appear, even after uninstalling / reinstalling the plugin, restarting OCN, etc.

Same here. Work around was to install the previous version the old fashioned way, then upgrade using the PIManager. It works then.

[Tolt]

Thank you, Jon, I will try that workaround. So far today, chart switching is working fine. Maybe I just need to be more patient.

[Schnapsy]

Originally Posted by SCarns

Same here. Work around was to install the previous version the old fashioned way, then upgrade using the PIManager. It works then.

Thank you.
Indeed, it works this way.
However, this is indeed an error that will have to be corrected ...

[stelian]

Hi,

This is with git head at 4f9c9c4 (aka v5.1.612).

Still on my Dell XPS 13 (HIDPI screen, screen factor 2), running Ubuntu 20.04.

The OpenGL bug (screen cut in 4) reported a while ago, which is still present.

Sometimes the option dialog pane contents are garbled (resizing the dialog fixes it), already reported as well.

A new one: when right clicking on a tide icon (supposed to show the tide graphic dialog), OpenCPN crashes with:

(opencpn:72559): Gtk-CRITICAL **: 08:53:33.613: gtk_box_gadget_distribute: assertion 'size >= 0' failed in GtkScrollbar

(opencpn:72559): Gtk-CRITICAL **: 08:53:33.648: gtk_box_gadget_distribute: assertion 'size >= 0' failed in GtkScrollbar
opencpn: ../../../../src/cairo-arc.c*:189*:*_cairo_arc_in_direction:  l'assertion «*angle_max >= angle_min*» a échoué.

Thread 1 "opencpn" received signal SIGABRT, Aborted.
__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
50	../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) bt
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#1  0x00007ffff656c859 in __GI_abort () at abort.c:79
#2  0x00007ffff656c729 in __assert_fail_base
    (fmt=0x7fffe479b777 "%s%s%s\302\240:%u\302\240:\302\240%s%s l'assertion \302\253\302\240%s\302\240\302\273 a \303\251chou\303\251.\n%n", assertion=0x7ffff6d0320c "angle_max >= angle_min", file=0x7ffff6d031f0 "../../../../src/cairo-arc.c", line=189, function=<optimized out>) at assert.c:92
#3  0x00007ffff657df36 in __GI___assert_fail
    (assertion=0x7ffff6d0320c "angle_max >= angle_min", file=0x7ffff6d031f0 "../../../../src/cairo-arc.c", line=189, function=0x7ffff6d03230 "_cairo_arc_in_direction") at assert.c:101
#4  0x00007ffff6c38b72 in  () at /usr/lib/x86_64-linux-gnu/libcairo.so.2
#5  0x00007ffff6c4bf77 in  () at /usr/lib/x86_64-linux-gnu/libcairo.so.2
#6  0x00007ffff6ca795f in cairo_arc () at /usr/lib/x86_64-linux-gnu/libcairo.so.2
#7  0x00007ffff765609e in wxGraphicsPathData::AddArcToPoint(double, double, double, double, double) () at /usr/lib/x86_64-linux-gnu/libwx_gtk3u_core-3.0.so.0
#8  0x00007ffff7655cef in wxGraphicsPathData::AddRoundedRectangle(double, double, double, double, double) ()
    at /usr/lib/x86_64-linux-gnu/libwx_gtk3u_core-3.0.so.0
#9  0x00007ffff7657b32 in wxGraphicsContext::DrawRoundedRectangle(double, double, double, double, double) ()
    at /usr/lib/x86_64-linux-gnu/libwx_gtk3u_core-3.0.so.0
#10 0x0000555555bb76bf in wxDC::DrawRoundedRectangle(int, int, int, int, double)
    (this=0x7fffffffc9a0, radius=0.75571955719557193, height=1, width=1, y=<optimized out>, x=<optimized out>) at /usr/include/wx-3.0/wx/dc.h:1186
#11 TCWin::OnPaint(wxPaintEvent&) (this=0x555559fdd230, event=...) at /home/stelian/TMP/OpenCPN_stelian.git/src/TCWin.cpp:770
...

Stelian.

[bdbcat]

Stelian...
re:
"The OpenGL bug (screen cut in 4) reported a while ago, which is still present."
Link please?

Also, what linux distribution are you running?


Thanks
Dave

[stelian]

Originally Posted by bdbcat

Stelian...
re:
"The OpenGL bug (screen cut in 4) reported a while ago, which is still present."
Link please?

Also, what linux distribution are you running?


Thanks
Dave

Here: https://www.cruisersforum.com/forums...ml#post3153474

I'm on Ubuntu 20.04.