OpenCPN Version 5.1.428 Beta Test

[cagney]

I think there was a slight hicup and the original beta file was overwritten.

The link below is to the latest win version and includes code contributed after the proper beta. Still worth testing. Next beta version probably due "soon".

https://cloudsmith.io/~david-registe...56a2_setupexe/

[P_Dub]

This site version 5.1.428+2170.71656a2_setup.exe works very nicely in Windows 10 pro. No problems with the icons and plugins. Great job.
Best Regards.

[Baikal]

Testing version opencpn-msvc_515112175a1f3b5e_setupexe
Icon - not displayed
Mbtiles - the behavior of working in a group suits me completely, Thanks Dave!
Notice overlay when the ENC and Mbtiles and switch back to Mbtiles group all the charts are turned off. Maybe when you switch to Mbtiles group include them automatically?
Marks of the depths - much better
Safe Isobath / Depth - Shows well for my 24` screen size

Gaps in DEPARE areas on ENC charts still not understood
In ENC viewers this is not observed

[Karanga]

Dave
Just a data point in the evolution of versions...
I still have black overlays of mbtiles, with latest version 5.1.511
I went through my graphics card software, trying to tweak settings. I haven't managed to achieve anything useful.
I also created a couple of new mbtiles, and they showed up black too.
I suppose I may have to re-download my satellite images as kap files instead of mbtiles, until I can get the situation sorted.
Tim

[Baikal]

Originally Posted by Karanga

Dave
Just a data point in the evolution of versions...
I still have black overlays of mbtiles, with latest version 5.1.511
I went through my graphics card software, trying to tweak settings. I haven't managed to achieve anything useful.
I also created a couple of new mbtiles, and they showed up black too.
I suppose I may have to re-download my satellite images as kap files instead of mbtiles, until I can get the situation sorted.
Tim

How do you create mbtiles?

There is a problem when creating mbtiles from one zoom layer, in some cases there were problems from two zoom layers.
Also, zoom layers over 18 do not work.

[yachtvalhalla]

Originally Posted by Baikal

Also, zoom layers over 18 do not work.

Actually using Sat2Chart you can create an Mbtiles down to the level that the source map will show.

Here's one from Google Earth at zoom level 20.


Terry

[yachtvalhalla]

Originally Posted by Baikal

There is a problem when creating mbtiles from one zoom layer, in some cases there were problems from two zoom layers.

And creating multi-level charts is also easy with Sat2Chart.

Here is a chart at zoom levels 17,18 & 19.

Terry

[Karanga]

I use Sat2chart, and SASPlanet.
I usually select 8x8, which produces zoom levels of about 16 to 18 (I think).
I don't know what effect the options in the SASPlanet page of Sat2chart have, so I leave them as default.
This is how it used to work for me in v5.0.
Now in v5.1 beta, those mbtiles appear as almost completely black (very feint image can be seen).

Originally Posted by Baikal

How do you create mbtiles?

There is a problem when creating mbtiles from one zoom layer, in some cases there were problems from two zoom layers.
Also, zoom layers over 18 do not work.

[phiggins]

Karganga,

Can you reproduce this problem? if so, send me the Sat2Chart.log as an attachment to an email. This log is the directory where Sat2Chart is installed, my email is in the help.

Paul

[RhythmDoctor]

Hi Dave and team,

I did a quick look at the 5.1.438 beta, and it looks like my two Flyspray complaints have both been successfully fixed:

https://opencpn.org/flyspray/index.p...s&task_id=2581

https://opencpn.org/flyspray/index.p...s&task_id=2638

Portable mode still appears to be working too!

I just noted that you are now up to 511 beta, but haven't had a chance to test that yet.

Thanks for all your efforts!

[spithost]

I entered a bug right after the release of 5.0.0 (FS#2541) and hoped it would have gotten a solution in this new beta or at least be "recognized" as valid.

But when I look at the bug, it still has the status of unconfirmed :-(
I entered some additional comments and some test-data for a developer to test and work with. I hope this is the right way to "bubble" the bug up under attention? ;-)

If not, please enlighten me in how I could get the bug to the state folowing unconfirmed ;-)

[rgleason]

Dear spithost, the crew tries to address bugs, but more skilled volunteer hands are needed to address these.



The "bug" is FS#2588 - Depth offset from transducer depth to sea level
This is not a bug but a "Feature Request". Additionally it does not apply to OpenCPN, but to the ancient and venerable LogbookKonni which has been maintained by a band of users of that plugin. I suggest you post your request under the Logbook thread to see if someone can add that, rather than here, where it is not pertinent.

Originally Posted by spithost

I entered a bug right after the release of 5.0.0 (FS#2541) and hoped it would have gotten a solution in this new beta or at least be "recognized" as valid.

But when I look at the bug, it still has the status of unconfirmed :-(
I entered some additional comments and some test-data for a developer to test and work with. I hope this is the right way to "bubble" the bug up under attention? ;-)

If not, please enlighten me in how I could get the bug to the state folowing unconfirmed ;-)

[Jon Hacking]

Good question, Klaus. As I understand it, it depends if it's a valid bug or a feature request. Real bugs should get fixed, but it helps to generate a bit of enthusiasm & visibility. In the Advanced section of creating your post is an easy way to post a link to FS2541 so folks can look at it with just a single click.

I helps to talk about it a bit on the forum, & give it some visibility & discussion, as there may be workarounds or valid reasons things were changed. The system is good, but it's not perfect & there are a LOT of issues in FlySpray. You want to make it as easy for the Devs as possible. They're all volunteers.

If it's really a feature request, then you really need to generate some enthusiasm, because those need to have several others want that feature as well, which is why there's a check-box to vote for the request. One way is to post a link to the FlySpray request in the Help/FAQ section & talk it up, so folks can vote for it easily.

In your case, it would help if you posted a full line of what you put in the Name field of a Waypoint, along with images of how that was rendered before (state the OpenCPN version & platform) & how it's rendered now. This would also provide the Devs with an easy test case, & you want to make it as easy as you can for 'em.

Hope this helps.

[spithost]

Hi Jon, It actually IS a bug (I think ;-)). There are examples of layers usable to explain what I mean on the page: https://opencpn.org/wiki/dokuwiki/do...layers_library
Here you can see a picture of a layer for UK Met Office forecast areas.
In this layer there's for example EAST NORTHERN SECTION which is devided over three lines.
I "dove" into that example in the pre-5.x days (OpenCPN 4.something) to adapt "my" layers (of which I have attached an example to one of the comments in the bug-report).
The "lines" in the example are seperated in the gpx-file by the combination: 
 (sort of a html-code with a hex-value of a newline I guess).
That used to work (most of the time I should say) in OpenCPN-versions previous to 5.x.
But after installing 5.0.0 this didn't work anymore. Everything after the first "newline-combo" is now cut of and not displayed anymore.
As I create layers with for example bridge and lock-info with the name of the bridge and the VHF-info on the first "line" and the rest of the info (width and height for the openings etc) on the following lines this is quite annoying ;-)
I now produce two variations of these layers. One with the "multi-line" and one with the info in one long line which clutters up the screen more then nessecary. If you would load the example gpx from the fore-mentioned page into OpenCPN 5.x you'd also see that only the first line of every waypoint is displayed and EAST NORTHERN SECTION is cut off after EAST.
As I know that the developers are volonteers (I support them on a monthly basis through Paypal and hope lots of others do the same) I don't want to put unneccesary pressure on them by trying to to put "my bug" on top of their list.
I'm only asking if I entered the bug in the right place to begin with, so that it will not "glide away" unnoticed in some way as it apparently only reached the "unconfirmed" status since entered more then a year ago ;-).

Originally Posted by Jon Hacking

Good question, Klaus. As I understand it, it depends if it's a valid bug or a feature request. Real bugs should get fixed, but it helps to generate a bit of enthusiasm & visibility. In the Advanced section of creating your post is an easy way to post a link to FS2541 so folks can look at it with just a single click.

[bdbcat]

spithost....
Your bug got missed because if was filed under the wrong project, as you have noted in the Task itself. We are not closely monitoring the "OpenCPN Version 5 Beta" tasklist at Flyspray.


I will move the Task, and take a look.


Sorry
Dave