OpenCPN Beta Version 3.3.2330 Released

[Hakan]

Originally Posted by Hakan

Dave.. A crash report.
In WinXP I had a couple of long time run crashes. A crash report is sent..............Håkan

Some more crash info:

My own build can run for say 3.5 hours.
The memory usage is growing from ~55 MB to ~80, that is ~130 kB/min
I've used the GDIView but I'm not sure what to look for here, please advice. For the ungoing run I collected the following where the update period is 5 sek:

Process ID        : 1516
Process Name      : opencpn.exe
Pen               : 17  [0]
ExtPen            : 4  [0]
Brush             : 23  [0]
Bitmap            : 280  [+1]
Font              : 45  [0]
Palette           : 2  [0]
Region            : 48  [0]
DC                : 24  [0]
Metafile DC       : 0  [0]
Enhanced metafile DC: 0  [0]
Other GDI         : 1  [0]
GDI Total         : 444  [+1]
All GDI           : 471  [+1]

There is a constant enumeration in the extended info, see attached picture, but please advice what more I can collect.

Håkan

[Gilletarom]

Hello everyone,

I think I was the first to react against the fog in case of "overzoom." Dave was also made a point of explain and had replied to the forum.

It happens that I have read since my surgery, two reports of accidents, recent, French Survey Bureau of sea Accident (BEA mer):
- A boat, French customs, threw himself on the coral reef in front of the Tuamotu Islands
- A boat taking part in the supply of scientists on a deserted island in the South Pacific hit a rock.

In both cases, the authors of the accident report had said that the crews were not sufficiently trained in relation to the employment of ECS zoom capabilities that equipped these boats.
In one case, the "BEA mer" forced the French software manufacturer to introduce a limitation to the use of overzoom.

The overzoom was limited even with OpenCPN. And this from the beginning with version 1.36. The new method proposed by fog Dave, I am puzzled. Personally, this method bother me. Dave said he will put an option. But it will still restricted overzoom.

One of the forum participants reminds us of the existence of the "splash screen warning about using the program for navigation."

Maybe it would, at first, or more regularly, educational messages to remind users of the risks of overzoom.

Best regards. Gilletarom.

[Hakan]

With other words, leave it as it is, them understanding the risks and what's all about can manipulate the software in terms of changing the config file.
Håkan

[bdbcat]

Håkan...

On the long term XP crash:

What type of chart is displayed? GPS input active? AIS? Any other special conditions?

Thanks
Dave

[NahanniV]

Originally Posted by Hakan

Dave..
Many thanks for your investigation.
I've tested it on Win7 and got the same display there as well.

I'll try your suggestions in my copy and test. Hopefully it works nice and I push that to Kees original source.

Håkan

I'm running:

OpenCPN Version 3.3.2330 Build 2014-11-30

br24radar_pi.dll 237 KB (242,688 bytes) Saturday, ‎November ‎15, ‎2014, ‏‎6:12:50 PM

Win7 Ultimate 64

All the buttons appear as they should ?

Also with the latest sources built on ARM yesterday.

[Hakan]

Originally Posted by Hakan

Some more crash info:

I've using GDIView collected 3 hours run for 3.3.2330 beside a portable 3.3.1419. The two instances are UDP connected and consequently used the same NMEA data. There is a significant difference. See attached docs enclosed in a zip file, please discard the .pdf extension.
Håkan

[Hakan]

Originally Posted by bdbcat

Håkan...

On the long term XP crash:

What type of chart is displayed? GPS input active? AIS? Any other special conditions?

Thanks
Dave

All NMEA data are from a VDR playing one Garmin navigator, one AIS transceiver and Simrad IS15 data for wind, depth, heading etc;
(The file is here: https://dl.dropboxusercontent.com/u/...st_VDR_rec.txt)

All NMEA is also sent to a Portable OCPN via UDP.

Also BR24 radar is shown but I did also run without it, without any visible difference in GDIView.

Charts viewed are CM93 and I haven't touched it during the whole session, e.g. no zooming or moving more then "boat follow" of the small anchorage movements. There are also some raster charts loaded but not viewed in this session.

Håkan

[Mollymawk]

Everyone,

Good to see some discussion on the chart blurring overzoom emphasis feature.

I would like to clarify what I said earlier, in case it came across as if I was opposed to this feature... In fact, I support this method of emphasizing the limitations of overzoom. I think it is great.
BUT, I think the soundings and texts must be enlarged (like when overzooming a raster chart) so that they remain at least legible.

In general, as dacust suggested, it should just appear that the chart has been drawn at its true scale and then the image has been zoomed like a raster.

Dave, what do you think about this, is there any reason not to do it this way?
I think it would have the benefits of the current blurring but without most of the drawbacks, and the new users you worry about would be more likely to leave it enabled.

Caesar

(PS - I would support the idea of a checkbox in the advanced options for this, as it seems a lot of people would want to disable it. But I think when disabling it, a notice should pop up warning users about the limitations of overzoomed vector charts and asking them if they are sure they want to continue. The user must then click a button saying they understand the limitations and want to continue anyway. Additionally, when blurring is disabled, the screen could flash a couple of times when a certain overzoom level is passed, just as a reminder.)

[Hakan]

Originally Posted by NahanniV

I'm running:

OpenCPN Version 3.3.2330 Build 2014-11-30

br24radar_pi.dll 237 KB (242,688 bytes) Saturday, ‎November ‎15, ‎2014, ‏‎6:12:50 PM

Win7 Ultimate 64

All the buttons appear as they should ?

Also with the latest sources built on ARM yesterday.

Nahan...
Excuse me but are you sure? I've just tested on a Win7 and the BR24 buttons where not correct. Ok, there where no "squares" but where it should be two rows it was only one.
The correct appearance should be as the picture:

Thanks
Håkan

[Gilletarom]

Hello Anyone,

Originally Posted by Mollymawk

Everyone,

Good to see some discussion on the chart blurring overzoom emphasis feature.
...

(PS - I would support the idea of a checkbox in the advanced options for this, as it seems a lot of people would want to disable it. But I think when disabling it, a notice should pop up warning users about the limitations of overzoomed vector charts and asking them if they are sure they want to continue. The user must then click a button saying they understand the limitations and want to continue anyway. Additionally, when blurring is disabled, the screen could flash a couple of times when a certain overzoom level is passed, just as a reminder.)

I resume, by the way, the idea of Mollymawk which is in its postscript.
Let users use overzoom. But the alert with a message on the danger of Overzoom, when we reached the overzoom, or at least when we really exaggerating, is a good idea. But if the message could be educational, it would be better. Or at least, if access to educational explanations could exist in an ad-hoc window.
But, hey, it can become too "heavy" to manage. This must remain pleasant.

Best regards, Gilletarom.

[HappySeagull]

Bad things happening here....
Make a new wpt (special icon-does it matter?)
Hide a chart.
view CM93
Pan and zoom (using mouse scroll wheel)
The new wpt moves, the Hidden Charts disappear from chart bar
things screw up, O freezes
.....see the junksail? at one point Ownship moved onto this rock from 20 miles away .


Repeatable as a process but I haven't tracked it down to which setting of these (or my particular computer)is a possible cause.
GL OFF ,No GPS connected

These are ON:
Quilting,Preserve Scale,
Smooth Pan,
Zoom to Cursor,
Lock Wpts,
Skewed Charts North Up

ChartZoomScale Bias = -4

Computer: HP G60 Win 7

[bdbcat]

Happy...

Read back a ways, you will see that this is a known bug in 2330.

Vector charts, Windows, and no-GL mode, known unstable.

Sorry
Dave

[HappySeagull]

Re Mollhawk post 128

I think when disabling it, a notice should pop up warning users about the limitations of overzoomed vector charts and asking them if they are sure they want to continue. The user must then click a button saying they understand the limitations and want to continue anyway. Additionally, when blurring is disabled, the screen could flash a couple of times when a certain overzoom level is passed, just as a reminder.

Please, no. Just include the Warning in text beside the box. As in:
"Overzoom Blur Off: This Can Be Dangerous!"

I am not seeing why we need to be punished with a stream of turnstile dialogues and blinking lights.

People hit rocks with paper charts in hand. As far as I know, they were not wearing jewellers' loupes at the time.

[HappySeagull]

Originally Posted by bdbcat

Happy...

Read back a ways, you will see that this is a known bug in 2330.

Vector charts, Windows, and no-GL mode, known unstable.

Sorry
Dave

My Bad,Dave recall reading it but couldn't refind find it in the flurries. so tossed this in Anyways I get panicky when O stumbles.

[NahanniV]

Originally Posted by Hakan

Nahan...
Excuse me but are you sure? I've just tested on a Win7 and the BR24 buttons where not correct. Ok, there where no "squares" but where it should be two rows it was only one.
The correct appearance should be as the picture:

Thanks
Håkan

OK, sorry, I see what you are saying now.

In English on Win7 there are no extra characters (squares) everything is readable, looks OK except for lack of space or newline in some instances.

See my screen image: