OpenCPN Beta Version 3.3.814 Released

[bdbcat]

Ahoy, OpenCPN'ers...

OpenCPN Version 3.3 Beta Build 814 will soon be available for download from opencpn.org.

Monitor the opencpn.org Downloads page to find and download the latest Beta version binaries.....

Source is available now on github at:
https://github.com/OpenCPN/OpenCPN
Branch: master

Changelog:


74. Improve S52 symbolization of some features (SLCONS, VEGATN)
75. Correct fault on some ENC National text strings.
76. Modify GPX Waypoint output format to conform to GPX1.1 Schema. Thanks, ChuckSK
77. Correct AIS target rollover SOG units to conform with globally selected speed units (FS#1047)
78. Correct georeferencing on BSB charts during zoom-to-cursor actions in single-chart-mode.
79. Correct behavior on Windows when AIS alert occurs and OCPN is iconized to taskbar (FS#968/998)
80. Correct midnight track restart logic to avoid occasional crash.
81. Correct occasional cm93 loss of Features on display properties change.(FS#1050)
82. Correct reset of route total length on reverse. (FS#1053)
83. Correct linux serial port baud rate setup.
84. Improve position and visibility of MOB tool on toolbar (FS#992)
85. Improve Rollover popup window dynamics (FS#1054)
86. Correct file type specifier mask in GRIB File Dialog.
87. Improve S57 extended light sector rollover algorithm. (FS#1057)
88. Correct cm93 floating detail level slider on Mac OSx.
89. Correct RouteManager Dialog to "stay-on-top" for OSx.
90. Implement Alert Dialog for DSC Distress calls. (FS#1051)
91. Change vector display category "Other" to "All".(FS#1048)
92. Correct Chart Info Widow and Chart Thumbnail on Mac, OpenGL mode.
93. Improve "Busy/Hourglass" cursor dynamics on cm93.
94. Complete implementation of CrashReporting scheme on Windows.

Release 3.3.814

Notes:
90. Here is a string for testing DSC distress Alert Popup.
!CDDSC,12,3081234000,,07,00,0354013946,0657,,,S,E* 6D

94. If you crash on Windows, and have an internet connection, you may select the option to "Send Report" I will receive the report automatically, and be thus able to quickly identify crash causes. This is an improvement over the previous requirement to "Export" the Crash Report and email separately. You may still use this "Export/email" process if you have no internet at the time of the crash.
Please do not overwhelm my server with ALT-F12 crash testing

Thanks, and happy testing
Dave

[MarkJ]

Originally Posted by bdbcat

90. Here is a string for testing DSC distress Alert Popup.
!CDDSC,12,3081234000,,07,00,0354013946,0657,,,S,E* 6D

Hi Dave,

How does one put this test string into Opencpn?

(In laypersons terms please )


Mark

[cagney]

Originally Posted by MarkJ

Hi Dave,

How does one put this test string into Opencpn?

(In laypersons terms please )


Mark

Copy the sentence to a new text file. Then, point the VDR plugin to this file for playing. The VDR is available on the plugin download page.

Thomas

[nohal]

Ubuntu/Debian testers...
The beta PPA packages are in the process of baking, should be ready shortly.

Happy testing

Pavel

[MarkJ]

Righto. I did that and nothing happens. I get a box with a green line in it.

What is meant to happen?

See screen shot attached.

I dont know why I always feel like a fool when I am talking to you guys.


Mark

[bdbcat]

MarkJ...

No fools here. This stuff is complex, and often not intuitive. We try hard to simplify as much as possible the normal operation of OpenCPN. Someone famously said (paraphrased) "Make things as simple as possible, and no simpler"

So, back to the test.

Start OpenCPN from scratch.
Click Options->Connections->Show NMEA debug window.
Close the Options dialog.
Then play the VDR file containing the DSC message.. You should see the DSC sentence in the NMEA debug window.

Good Luck
Dave

[MarkJ]

Originally Posted by bdbcat

You should see the DSC sentence in the NMEA debug window.

Good Luck
Dave

OK, Thanks Dave. I followed you instructions and saw it in the NMEA window. Thanks.

I thought it might put a nice bright message on the screen or sommit. LOL


But very nice.


Mark

[bdbcat]

Mark...

You should see something like this attachment. If you don't see the Alert Dialog ("DISTRESS", etc), then something is not working right.



Dave

[Icnoships]

Dave thanks for the updated beta,
had a quick play with the osx updates

all good apart from a bit o hair splitting...the thumbnails of charts are working well, the detail slider / route manager are now on top only problem is they are now on top of all other apps as well.
Also a small issue with the slider now its visible...when set to 0 at 57300 scale there is a small cell misalignment, moving the slider to full detail at the same scale realigns the cells, not the same behaviour for scales.
see screen shots

good stuff

mo

[bdbcat]

mo...

The cm93 detail slider "on-top-ness" behavior is a bug. I will get it on the list.

The misalignment of cm93 cells is probably in the data, I'm afraid. The two cells are of very different compilation scales, and they just do not match up cartographically. Lots of places in the world where cm93 is like that.

Thanks for the report

Dave

[cagney]

Originally Posted by MarkJ

Righto. I did that and nothing happens. I get a box with a green line in it.

What is meant to happen?

See screen shot attached.

I dont know why I always feel like a fool when I am talking to you guys.


Mark

Mark

The reason you don't get the view Dave is talking about, is probably that the sentence you put in the text file has extra spaces in the start or end. I'm attaching a correct version for testing.

dsc_test.txt

Thomas

[cagney]

More details about a couple of issues in Dave's list above.

87. Improve S57 extended light sector rollover algorithm. (FS#1057)

On a raster chart the presentation is of course exactly what the Hydrographer intended. Leading light sectors are presented as such. Things are not that clearcut when it comes to vector charts. There are different standards in different countries, and there is no clear standard attribute, that is mandatory, for leading sectors.
Leading sectors, by the way are intended to be extended by O if the proper box is ticked.
A review of how this is handled was triggered by a few odd sectors in a couple of Danish lights. This is what is going on in 3.3.814.

A light sector is extended if:
0. The words "Leading" or "Directional" can be found in the Object Query.

Otherwise, the rules are

1. The sector is < 15 degrees wide.
2. It is White.
3. The light also has red and/or green sectors.

These rules works quite well, but there are exceptions that are difficult to catch. The number "15" may be increased in the future......
As always, it's the responsibility of the navigator, how a light and its sectors are used for practical navigation.

90. Implement Alert Dialog for DSC Distress calls. (FS#1051)

A VHF/DSC emergency is now displayed the same way as an AIS/SART emergency. A small dialog pops up and the audio alarm is set off.
An audio alarm can now mean three different things. Apart from DSC and SART it could also be an AIS warning about a target coming to close.
If all these alarms are set of at the same time, what will happen?
The alarms will show according to their priorities.
The priorities are
*SART
*DSC
*AIS
If two alarms of the same priority are triggered at the same time, the nearest will be shown.

So... for your own safety if an alarm is triggered, evaluate the full situation near your boat.

There is already a feature request for different alarm sounds for the three cases above.

Thomas

[bdbcat]

Good morning....

The crash reporting scheme works, although we could use some better management tools at our end. But this will come soon.

Got two already. (This is like fishing...)

One feature of our scheme is that it is anonymous. So, I don't know who sends them unless the user enters "Provide additional info" fields. So, as now, I will be asking for more info on the Forum in-the-blind, so to speak. I suppose that the crashers will recognise their own events.


1. Central Russia S57 ENC, looks like fault on ENC processing. More info needed, especially the ENC cell ...405039.000

2. Crash on initial load, caused by mouse wheel zoom event before the PlugIn stack was fully loaded. Never seen this before. Easy fix.

This is fun....

Thanks
Dave

[MarkJ]

Originally Posted by cagney

Mark

The reason you don't get the view Dave is talking about, is probably that the sentence you put in the text file has extra spaces in the start or end. I'm attaching a correct version for testing.

Attachment 65532

Thomas

LOL Thanks for sending that file I was just pulling my teeth out!

OK I got the Distress box and point on the map

However you will note on my screen capture my NMEA box is not multi coloured like the ledgend indicates or like in Dave's post. I can live without the colour if its not important.

Mark

[redog]

A question about the VDR.

I save a recording as a plain text file and ubuntu doesn't add a file extension.
(I just follow the steps as I see them in O)
(Do I need to need to specify the type of file here?)

I can view these files by just clicking on them in file manager.

But I can only replay in O if I add the .pfd extension to the file.

Same with Dave's distress file.

Still on 3.3.604 so not expecting to see the alert.

What am I Missing?

One screen shot shows all files in folder.
Other shot show what O gives me as a selection.

redog