OpenCPN Version 5.5.x Beta Test Starts

[Hakan]

Originally Posted by stevead

Current build as of today from Github.

OpenCPN renders chart incorrectly and crashes when switching between North-Up and Heading-Up Mode. Switching between North-Up and Course-UP seems OK, so possibly something related to World Magnet Model (WMM) plugin ?

For a comparison I tested your NMEA's by VDR with today's master code on Win10. - No crash or other obstacles detected here.
North up and heading up works fine. Course up wouldn't work but is acting as North up since COG is not available in the messages.
Now I've only CM93 to use in your area if that's a difference?

[stevead]

Well maybe its my build or my Windows 10 PC...

My initial observation was also using the CM93 charts.

Just for the hell of it, with no plugins enabled, using the NOAA ENC charts for Washington State and following sample data:

$IIMWV,155.17,R,11.88,N,A*0A
!AIVDM,1,1,,A,ENkb9TvP0000000000000000000;VoEg=jIg`00003vP0@,4*07
$IIDBT,18.93,f,5.77,M,3.16,F*13
$IIVHW,,T,,M,0.00,N,0.00,K*55
$IIVLW,,,,,899.03,N,899.03,N*4D
$IIMWV,155.05,R,11.82,N,A*03
$IIZDA,211107.00,29,09,2020,01,00*76
$IIGLL,4741.0069,N,12224.3379,W,094100.00,A,A*60
$IIVTG,311.71,T,,M,0.02,N,0.04,K,A*29
$IIMWV,154.99,R,11.74,N,A*0E
$IIGGA,211107,4741.0070,N,12224.3379,W,1,3,15.90,-0.0,M,638.0,M,,*65
$GPGSV,3,1,11*7B
$GPGSV,3,2,11,21,73,249,39,11,44,288,36,08,31,249,36*4D
$GPGSV,3,3,11*79
$IIMWV,155.00,R,11.68,N,A*02
$IIMWV,155.06,R,11.62,N,A*0E
$IIMWV,155.15,R,11.55,N,A*08
$IIMWV,155.24,R,11.49,N,A*07
!AIVDM,1,1,,A,ENkb9MNP0000000000000000000;Wma:=Tjv`00003vP0@,4*50
!AIVDM,1,1,,B,15NHkdg000G?lv6KAB7;ABPAR6`d,0*1D
$IIMWV,155.27,R,11.45,N,A*08
!AIVDM,1,1,,A,15NMe69P00G?jddKADbea?v@P84j,0*1E
$IIMWV,155.23,R,11.39,N,A*07
$IIMWV,155.15,R,11.33,N,A*08
!AIVDM,1,1,,B,ENkb9MNP0000000000000000000;Wma:=Tjv`00003vP0@,4*53
!AIVDM,1,1,,B,35Pm=CP001o?edDKAT8<NkF@011@,0*1D
$IIMWV,155.05,R,11.29,N,A*02
$IIDBT,18.93,f,5.77,M,3.16,F*13
$IIVLW,,,,,899.03,N,899.03,N*4D
!AIVDM,2,1,2,B,55Mi<nT2;K==L=WOW?QM<J11ET4hiE22222,0*4C
!AIVDM,2,2,2,B,2220t;Ph>>5mig>000000000000000000004,2*3C
$IIMWV,155.00,R,11.24,N,A*0A
$IIZDA,211108.00,29,09,2020,01,00*79
$IIGLL,4741.0070,N,12224.3377,W,094102.00,A,A*64
$IIVTG,158.86,T,,M,0.02,N,0.04,K,A*2E

still had weird behavior when switching between North Up and Course Up modes including a few crashes upon shutdown.

Perhaps it may be related to the fact that in my different data samples I don't have coherent heading or course data. If it's only me experiencing this, then so be it.

[JohnGC]

Windows 10 64-bit

Update from 5.2.4

AIS target trails issue.

I don't know if this is new but I have never noticed it in previous versions.

When using the mouse to pan the chart, I have found that some AIS target trails disappear. Panning again will restore them.

I've uploaded a screen capture video to Youtube, it's low res but you can see what is happening.
https://youtu.be/MCZY2C3oo0A

A VDR file recorded during the screen capture is attached.

Note: The AIS data is live using AISdeco2 which makes AIVDM sentences available via UDP. There is no Position (GPS) device on my PC, the boat location is set close to this screen view using "Move Boat Here". The charts are o-charts vector.

John

[P_Dub]

I am coming back with that, and did not get any reply:-
They only thing I would like is the possibility to have the course degree number on the course line for line longer than say 1/4 of a mile or so; or what ever one wants. This in order to avoid crowding the chart, if one does the roundings. I know that we can see them in the route manager, but maybe one can do that. Thanks for this version.

[bdbcat]

P_Dub....


"course degree number on the course line"


Sorry, too late for this new version.
Add to Flyspray for next Release, please.


Thanks
Dave

[P_Dub]

My access prevent me for doing so, could you add it for me please.
Thanks.

[yachtvalhalla]

Originally Posted by P_Dub

I am coming back with that, and did not get any reply:-
They only thing I would like is the possibility to have the course degree number on the course line for line longer than say 1/4 of a mile or so; or what ever one wants. This in order to avoid crowding the chart, if one does the roundings. I know that we can see them in the route manager, but maybe one can do that. Thanks for this version.

For clarity are you asking that the course bearing be added to the information in the yellow box that appears on legs of a route? See image.

[P_Dub]

No, but on the course itself. It could be in it aswell.

[JohnGC]

I've now tested this with a GPS fix. The problem persists.

My location is Plymouth UK.

Originally Posted by JohnGC

Windows 10 64-bit

Update from 5.2.4

AIS target trails issue.

I don't know if this is new but I have never noticed it in previous versions.

When using the mouse to pan the chart, I have found that some AIS target trails disappear. Panning again will restore them.

I've uploaded a screen capture video to Youtube, it's low res but you can see what is happening.
https://youtu.be/MCZY2C3oo0A

A VDR file recorded during the screen capture is attached.

Note: The AIS data is live using AISdeco2 which makes AIVDM sentences available via UDP. There is no Position (GPS) device on my PC, the boat location is set close to this screen view using "Move Boat Here". The charts are o-charts vector.

John

[bdbcat]

JohnGC...


The logic is this.
To display an AIS target's tracks..


1. The target must be visible on-screen,
.or.
2. The first recorded point of the track must be on-screen.


I find that this logic is working on my tests.
Will you confirm?


We use this logic to avoid excessive screen clutter in busy areas from targets that have left the screen, and so are no longer a safety factor, probably.


Thanks
Dave

[Moo]

https://dl.cloudsmith.io/public/davi...3571_setup.exe Gives me "File not found" error

[JohnGC]

Hi Dave,

It's not consistent. Some target tracks work exactly as you describe.

Other target tracks will remain on the screen even if only the first (oldest) point is visible.

Such tracks can be close to each other.

I've tried a few different zoom levels and the behaviour seems to be the same.

John

Originally Posted by bdbcat

JohnGC...


The logic is this.
To display an AIS target's tracks..


1. The target must be visible on-screen,
.or.
2. The first recorded point of the track must be on-screen.


I find that this logic is working on my tests.
Will you confirm?


We use this logic to avoid excessive screen clutter in busy areas from targets that have left the screen, and so are no longer a safety factor, probably.


Thanks
Dave

[bdbcat]

JohnGC..


The logic condition is "or".
A track will be shown if the oldest track point is on screen, even if the target itself is not on screen.


Dave

[bdbcat]

Moo...
Beta Test 5.5.928 is now active.


https://www.cruisersforum.com/forums...ed-256254.html


Thanks
Dave

[JohnGC]

There are very few vessels moving today, I'll check when there is more activity.

Originally Posted by bdbcat

JohnGC..


The logic condition is "or".
A track will be shown if the oldest track point is on screen, even if the target itself is not on screen.


Dave