OpenCPN Beta Version 3.3.2330 Released

[Hakan]

Originally Posted by HotRod

Two issues..................
When in overzoom scale 3200 every thing looks fine, but next zoom stage at scale 1600 every chartdetail turn blurry and unreadable... This is both in GL and standard. See enclosed pictures...
Also added comment to FS#1591

HotRod... Please read back in this thread and the one for last beta 3.3.2316. There's a massive discussion about the fogging and blurring feature.
Ha de
Håkan

[Gilletarom]

Bonjour dave, Bonjour Pavel,

Originally Posted by bdbcat

Gilletarom...
Sorry to bother you.
Could you include a similar screenshot of the US Coast "Eatons Neck" with full screen, to show the chart selector bar at the bottom, like this:
Dave

I can not make the screenshot Dave asks me.
Just because we do not use the same raster charts game!
And yet, I proceeded to download this morning on the NOAA website. I went on this page:
Chart Downloader for NOAA RNC&#174
And I clicked on this link:
http://www.charts.noaa.gov/RNCs/05CGD_RNCs.zip (3OOGB)

To arrive at this conclusion, I copied the folder that contains the charts there. Then I opened the new folder with PolarWiew (Sorry, but that was my only means of comparison).

I get exactly the same views with PolarWiew as with OpenCPN. Here is a screenshot of PolarWiew. There is a list of all the charts of the set charts for the area requested by Dave.

Please Pavel, what is your chart ?

Gilletarom.

[HappySeagull]

Originally Posted by HappySeagull
I really don't like it. Perhaps there could be an option for it.

Originally Posted by Hakan

There is, in config file set "FogOnOverzoom=0"
Håkan

No, I was thinking it could be in: Tools\Display\Advanced
Perhaps disabling blur would enable "Overzoom" on the screen. Having Both is maybe not needed.

[HappySeagull]

Originally Posted by bdbcat

Caesar....

Actually, I go the other way. I think the menubar and the options dialogs should track absolutely. The F9 shortcut to temporary single-chart is a whole different animal. Indeed, F9 should have no effect if you are already in persistent single-chart-mode, for whatever reason,although this is presently incorrectly implemented, IMHO.

So, to say again, for the docs:

F9 is temporary toggle.
"Q" is persistent toggle.

Or, if this is too confusing for punters, we should drop the F9 temporary toggle altogether.

Dave

Ok with me! [q] is easier to find at night and generally is a larger key ( I never use F9 except by accident)

Incidentally, I have some freezeups (on Win7 and XP) if the Quilting is off on CM93 charts. I know quilting toggle is not for them but stuff happens...especially playing with blur function, this pimple has arisen

[Hakan]

Dave.. A crash report.
In WinXP I had a couple of long time run crashes. A crash report is sent.
First.
I used my own build after your commit; "Correct pen resource leak on DC mode rendering." It was running with a VDR play and BR24Radar_pi simulation, so OpenGL is on. After say four hours it crashed.
Second
To be able to give you a usable crash report I now used the official beta download for a similar test. Now I got a crash after 1.5 hours and this is the report you've got. Your last commit is then not included but in other hand I am using OpenGL

Håkan

[bcn]

Håkan,

what I found interesting in this cases is to open the Windows resource manager observing the memory usage of OCPN.
With previous drivers we saw the memory used creeping up until it consumed all available and crashed.

Hubert

[Hakan]

Hubert..
Ok thanks. I've it running again so I'll have look.
Håkan

[MarkJ]

I thought I better get the update...

And I am staggered and amazed at the 'fogging'. What earthly use could it be to degrade the vision of the previous versions of the program?



I sail 2 bridges often both with a canal and the new offering must surely be some kind of joke.

My screen shows 1.25NM side to side. In a 100m wide channel I dont want 1.25nm.

I just looked back over my track down the ICW and OpenCpn crashed...

Fortunately I keep the old versions of the program.

Someone wake me up when overzoom is brought back.


Mark

[Opie91]

Originally Posted by bdbcat

Opie... Very strange. So you never see the Rebuild dialog box, with a progress indicator and "Skip" button? Yet it appears the cache rebuild is actually happening in the background? If you activate Windows task manager, what is the CPU Usage factor during this time? Dave

Dave,
No dialogue box shows up at all. CPU usage remains unchanged from before. The only thing that seems to happen is O cannot be closed. The cache rebuild does not appear to be happening.
Carl

[cagney]

Originally Posted by MarkJ

I thought I better get the update...

And I am staggered and amazed at the 'fogging'. What earthly use could it be to degrade the vision of the previous versions of the program?



I sail 2 bridges often both with a canal and the new offering must surely be some kind of joke.

My screen shows 1.25NM side to side. In a 100m wide channel I dont want 1.25nm.

I just looked back over my track down the ICW and OpenCpn crashed...

Fortunately I keep the old versions of the program.

Someone wake me up when overzoom is brought back.


Mark

Talking about jokes.......
Why would you even think about using a navigator/OpenCPN to pass those two bridges?

Thomas

[CarCode]

Originally Posted by MarkJ

I thought I better get the update...

And I am staggered and amazed at the 'fogging'. What earthly use could it be to degrade the vision of the previous versions of the program?



I sail 2 bridges often both with a canal and the new offering must surely be some kind of joke.

My screen shows 1.25NM side to side. In a 100m wide channel I dont want 1.25nm.

I just looked back over my track down the ICW and OpenCpn crashed...

Fortunately I keep the old versions of the program.

Someone wake me up when overzoom is brought back.


Mark

I don't know why "FogOnOverzoom=0" in opencpn.ini is a hidden feature for experts only...
Gerhard

[MarkJ]

Originally Posted by cagney

Talking about jokes.......
Why would you even think about using a navigator/OpenCPN to pass those two bridges?

Thomas

I sail in pretty busy parts of the world... Currently where a "yacht" squeezing through a bridge may be worth more that $100 Million. I wonder if he would use degraded nav systems? Or be expecting me to?

You navigate the way you like. I likeColRegs that says navigate with ALL available methods. But as a reminder here is Section 7:

. 7. Risk of Collision
Vessels must use all available means to determine the risk of a collision, including the use of radar (if available) to get early warning of the risk of collision by radar plotting or equivalent systematic observation of detected objects. (e.g. ARPA, AIS).
If the distance of any vessel is reducing and her compass bearing is not changing much or it is a large vessel or towing vessel at close distance, or if there is any doubt, then a risk of collision shall be deemed to exist.[6]

[P_Dub]

Originally Posted by MarkJ

I sail in pretty busy parts of the world... Currently where a "yacht" squeezing through a bridge may be worth more that $100 Million. I wonder if he would use degraded nav systems? Or be expecting me to?

You navigate the way you like. I likeColRegs that says navigate with ALL available methods. But as a reminder here is Section 7:

I agree with you 100%, that should never exit. I hope that many will answer the same way.
Best of luck.

[nohal]

Guys...
You don't like it, you turn it off. Done. I really don't understand what you keep talking about. The "Don't touch our mojo message" received, I supposed.

Pavel

[sailorF54]

.......

Originally Posted by colemj

I made that point. I also asked you where you suggest a charting program stops protecting people from themselves - not whether you think a certain use is valid.
This feature just echoes official statements on the risks of overzooming,

Here is an example where using a chart at overzoom is valid: We are often in poorly charted, but very clear, waters. I use overzoom to carefully mark reefs and shoals on the chart as we nudge the boat to and around them so that they have more accurate positions for the next time we are going through. Having the chart and soundings blurry is not very helpful for doing this. Particularly when the only chart of the area is a large-scale soundings and the fogging happens quickly.
You're welcome to create your own personal chart. You can do it on a blurred chart. The point is: how accurate are PRINTED features when you overzoom.

Mark