OpenCPN Beta Version 3.3.2118 Released

[Gilletarom]

Hello Dave,

Yesterday, with O 332118, making updates information and icons associated with my own marks, I found that
- The layers were not visible in the layers.
- The marks associated with these layers were invisible on the screen

Today, with 322 O, I see:
- The layers are clearly visible in the layers
- Icons of my layers appear well on screen.

Restarting 332118 O, I see that the situation remains the same as yesterday. No visible layers and marks.

issue:
Have you changed the folder location of the permanent layers?
I do not remember ever seeing a check box to display or hide all layers. Am I wrong?
Best regards Gilletarom

[Gilletarom]

Dave, Pavel

He came to me an idea.
I disabled the plugin sQuiddio .... And the layers are visible again in O 332118.

So, this plugin is at stake.

Gilletarom

[CarCode]

Gilletarom,

in my compiled version for Mac OS X squiddio has nothing to do with layers.
All marks of squiddio sits in waypoints and not in layers.
Switching on/off the squiddio marks with right-click context menu has no other effects.
However I have changed the squiddio sources so the gpx file of squiddio is saved in ~/Library/Preferences/opencpn/plugins/squiddio/

Possible the gpx file is saved at other places with other operating systems and therefore makes problems.

Gerhard

[Gilletarom]

Hello,

Originally Posted by CarCode

Gilletarom,

..version for Mac OS X squiddio has nothing to do with layers.
All marks of squiddio sits in waypoints and not in layers.
Switching on/off the squiddio marks with right-click context menu has no other effects.
However I have changed the squiddio sources so the gpx file of squiddio is saved in ~/Library/Preferences/opencpn/plugins/squiddio/

....
Gerhard

I recall that my PC is an ASUS EeePC 1015H under W 7 starter.

I added that if I mask or if I keep showing the marks added by sQuiddio, the problem is the same: My layers are invisible in the managers of layers and on the screen.

I also point out that the marks added by sQuiddio are visible in the waypoint manager (not in the layers manager).

You still have to remember that O was not able to handle a very large number of objects to display. This was the subject of a debate there a long time now. I do not know if the latest beta are able to do so. At the time, I had also cut the layers, proposed on the site of O, to help partially solve this problem.

I think sQuiddio adds too many additional marks. And it should get worse with time.

[bdbcat]

Gilletarom...

Regarding the instant problem with Layers display and squiddio PlugIn:

I can recreate easily.

I think this is related to:
http://www.cruisersforum.com/forums/...ml#post1622349

squiddio inadvertently causes OCPN to lose the location of the layers files, and all other private data files, after it searches for and loads one of its own set of waypoints.

The solution lies in a new Version of squiddio, incorporating all the recently merged activity therein. Special mention to Pavel. Schedule? I dunno about squiddio...

Also, it may be that O will stumble with large amounts of waypoints imported by squddio. How many waypoints are you importing, and how is the performance, considering only the squiddio POIs visible?

We did some major work on layer and waypoint display performance in early 3.3 days, and I expect it will be ok with "reasonable" waypoint count.

Gerhard is correct. As far as I can see, squiddio imports only waypoints, not layers. Despite its confusing log entry....

Thanks
Dave

[Gilletarom]

Hello Dave, Hello Pavel,

Originally Posted by bdbcat

Gilletarom...
....

Also, it may be that O will stumble with large amounts of waypoints imported by squddio. How many waypoints are you importing, and how is the performance, considering only the squiddio POIs visible?
.....
Dave

Currently, we do not choose the number of imported sQuiddio waypoint. We can only show or hide some of the waypoint by geographical area desired. But I guess all waypoints from squiddio are loaded anyway.

B.R. Gilletarom

[CarCode]

Originally Posted by Gilletarom

Hello Dave, Hello Pavel,

Currently, we do not choose the number of imported sQuiddio waypoint. We can only show or hide some of the waypoint by geographical area desired. But I guess all waypoints from squiddio are loaded anyway.

B.R. Gilletarom

In your local database are only the waypoints of the area you have been interested in. You may check your opencpn logfile to see details:

11:04:21 CEST: /Volumes/MacBookHD/Users/heidi/devel/Cocoa-OCPN/buildXcode/Debug/OpenCPN.app/Contents/PlugIns/libsquiddio_pi.dylib
API Version detected: 110
PlugIn Version detected: 2
11:04:21 CEST: squiddio_pi: Init()
11:04:21 CEST: squiddio_pi: getting .gpx layer files from: /Volumes/MacBookHD/Users/heidi/Library/Preferences/opencpn/plugins/squiddio
11:04:21 CEST: squiddio_pi: new layer 2018576753: SQ_N07E02
11:04:21 CEST: squiddio_pi: loaded GPX file /Volumes/MacBookHD/Users/heidi/Library/Preferences/opencpn/plugins/squiddio/SQ_N07E02.gpx with 89 items.

Compared to Active Captain there are much less points in squiddio. Perhaps this might become better when more people are using squiddio.

Gerhard

[Gilletarom]

Hello Gerhard,

Originally Posted by CarCode

In your local database are only the waypoints of the area you have been interested in. You may check your opencpn logfile to see details:
.........
Gerhard

I understood that. but:
1) First, the definition of areas in which we upload the waypoint sQuiddio is not practical. At least for now. My attempts to understand the operation did not allow me to understand whether the downloaded areas depended on O or site squiddio.com

2) On the other hand, I feel, now, to be a prisoner of this mass of waypoint. I wish I could choose more freely and get rid of all that clutter up my PC.

I guess Pavel develops sQuiddio plugin will think.

But here we are in a conversation that does not belong in this thread. Should be put in the specific sQuiddio thread.

B.R. Gilletarom

[Hakan]

A positive report using 3.3.2118 on a Win32 system.
I use primarily CM93 and some Swedish raster charts but also ENC inland channel charts were used. The plugins I use are Dashboard, Grib, WMM, Launcher and BR24_Radar.
I use OpenGL:

21:44:39: OpenGL-> Renderer String: Intel 965/963 Graphics Media Accellerator

21:44:39: OpenGL-> Detected Intel renderer, disabling stencil buffer
21:44:39: OpenGL-> Texture rectangle format: de1
21:44:39: OpenGL-> Framebuffer Objects unavailable
21:44:39: OpenGL-> Using Depth buffer clipping
21:44:39: OpenGL-> Using s3tc dxt1 compression
21:44:39: OpenGL-> Compressed tile size: 128kb (6:1)

The used connections are three NMEA ports, GPS/AIS/Simrad IS15, and one internal UDP “broadcast” to a parallel portable instance of OCPN.

The base for this report is a two month cruising from Sweden, through Scotland around England, passing inland of the Netherlands and back.

Talking crashes the 2118 beta is the best version for me since 1912. Apart from crashes discussed here;http://www.cruisersforum.com/forums/...ml#post1600917, no version but 1912 survived more then 24 hours, basically much less, until 2118. I’ve tried every version in between but quickly returned to 1912 when it crashed. Since the tests were on my primary navigation tool while sailing I didn’t had time to neither investigate nor save a crash report. The latter since I use my own build and those crash reports are obviously useless for Dave. The 2118 did survive for several days until one crash probably related to a CM93 E-section occurred, but I couldn’t repeat it so I’ve no details.
I’ve two repeated log notes:

-warning: found incorrect chart db version: V017
-Scheduling db upgrade to correct db version on options->charts page visit…. 

I can’t judge whether these notes are connected to the crashes, please advice.

Anyhow is this report an appreciation of the ongoing development. The outmost benefit is that I can now use OpenGL also on my dated machines and thus be able to use the radar plugin. I’ve seen discussions about CM93 related crashes so the single 2118 crash I experienced may be solved in next beta?

With great gratitude / Håkan

[Gilletarom]

Hello Dave,

I know that there are more important now that the language file things. But can I afford to point out a few words that are not part of the item file language OpenCPN.

When you click on the icons Tides and Current, two windows open. See image below.


In the "Tides" window, the following words are not translated:
- Tide
- Reference station
- Data source
- HW
- LW
- Today
- Prev

In the "Current" window, the following words are not translated:
- Reference station
- Data source
- Today
- Prev

I see in Crowdin website. They are not present.

Can you add theses items.

Thank by advance.

Gilletarom

[nohal]

Gilletarom...
Good catch, fixed now. The strings are also available on Crowdin already.

Thanks

Pavel

[Gilletarom]

Hello Pavel,

Originally Posted by nohal

Gilletarom...
Good catch, fixed now. The strings are also available on Crowdin already.
Thanks
Pavel

Wouahhh ... Thank.

Additional translation made

Gilletarom.

[Gilletarom]

Hello Dave,

By "clean" and proper installation problems, I have, this afternoon, uninstalled all parallel versions of O, and version 3.2.2. CCleaner then ... as usual. After that, I reinstalled O 322 and in parallel, O 332118.

Then I tested my traditional plugins (Grib, Dasboard, WMM, VDR). No problem unless I open the properties window of a waypoint. In this case, I have to close the process if I want to revive O after closing. We have already spoken.

Remember. This summer or more likely in the spring, I met a curious window by testing the beta versions of O. See attachment.

But there is a difference.
- I observe with O322, the window opens with O 322 at launch, just after the initial warning window.
- I observe with O332118, the window only opens when I click on the "Options" icon in the toolbar of O.

Just a little difference with the same window in the spring. Now the mouse pointer automatically moves to "No" so that memory, he put "Yes" before (not sure).

Furthermore, I confirm the bug reported, in the other thread, about the S63 used with S63 V 1.0. Many objects are not displayed with O 332118 while they are displayed with the CM93. By example, the tower, the wrecks but not only these objects.

Hoping that my information will be used for something, best regards.

Gilletarom.

[Gilletarom]

hello dave,

Then after the previous post, I test the plugin watchdog. Crash.

A crash report was send but, is it really sent ?

See screen copy.

B.R. Gilletarom.

[CarCode]

Gilletarom,

the error message you see might not come from OpenCPN. Regard the icon next "Error" in the message titel bar.
The event handling is a weak point of OpenCPN and often results in problems.

Furthermore I don't know what for is the new MMSI Properties introduced right now in the code at Ship Options.

Gerhard