OpenCPN Beta Build 2.6.1210

[stensmo]

Tested on Vista laptop:


If you pan when "course UP mode" and "Use OpenGL" are selected, there will be artifacts on the screen

[stensmo]

Originally Posted by stensmo

Tested on Vista laptop:


If you pan when "course UP mode" and "Use OpenGL" are selected, there will be artifacts on the screen

I forgot to say I used CM93-charts.

[bdbcat]

ktcanuck...

This is odd...

Will you please delete and recreate the route you show?

I know this seems highly unlikely, but it may be that the route is "wrong", and 2.5.0 georef is "wrong", and two wrongs are making a right on 2.5.0. Later, on 2.6.1210, we only have one "wrong" (the route), hence the error.

Does the route look OK with ENC for this region?

I cannot reproduce your error so far. With a fresh route created under 2.6.1210, all works well in all combinations of quilting and NorthUp modes for me.

Anyone else?

Thanks
Dave

[cagney]

Originally Posted by bdbcat

ktcanuck...

This is odd...

Will you please delete and recreate the route you show?

I know this seems highly unlikely, but it may be that the route is "wrong", and 2.5.0 georef is "wrong", and two wrongs are making a right on 2.5.0. Later, on 2.6.1210, we only have one "wrong" (the route), hence the error.

Does the route look OK with ENC for this region?

I cannot reproduce your error so far. With a fresh route created under 2.6.1210, all works well in all combinations of quilting and NorthUp modes for me.

Anyone else?

Thanks
Dave

Dave, just a quickie!
I have similar results as ktcanuck


Creating a route,

then hitting F9

Activating Skewed as North Up no Guilt
Hitting F9 just makes the chart follow the poly lines , similar to the second pic.
Chart always stay "chart up" no matter what. In the last pic the polygon and the route moves with the cursor.

Thomas

[cagney]

Originally Posted by PjotrC

Carryover from previous thread...

Thomas...

I do not think that the Anchor Watch deserves coding / testing / documenting / remembering another keyboard shortcut.

As much as I would always like to drop a mark the instant the anchor goes down, in practice (unless seriously overcrewed) it never happens. There's simply too much to do up on deck - test the holding, watch the transits, watch the neighbouring boats... the need to reanchor is always a possibility... so the Anchor Alarm is only set after all this is done, and the sundowner / nightcap (or whatever the time of day happens to be) drinks are served.

No need to have a quick mode of doing that.

In practice, alas, I always estimate the anchor position from the track plot and some guessing (more if using OpenCPN, less if using MaxSea).

Having said that, 2.6.x brings in some new issues...

1. The 2.6.1012 Anchor Alarm circle seems to be blank filled now, obscuring the anchor watch mark (should be transparent, as in 2.5.0 example - last attachement).

2. The 2.6.x track display at medium scale cleverly shows the history of path crossings (the later one comes on top), but at large scale is hardly useful at all...

I consider a detailed track plot to be much more effective tool for safe anchoring than the Anchorwatch, which is the last-resort safeguard. I attach again a plot from MaxSea, where one can at a glance see how the anchor did hold over past hours - every gust of wind, tensioning of the chain, turn of the tide is clearly visible. All what is needed is the ability to change the plot colour now and then...

Piotr

Piotr

You have to read my suggestion in connection with my comment on FS#634. Updating the anchor watch documentation, I found that there are 3 ways to drop a mark. Only one sets a default watch circle when an anchor watch is set. "Enter" and "Ctrl + M" does not. My idea was to use one of these as a dedicated anchor mark that sets the default circle and creates an anchor watch in one go. This was, however, before I was made aware of the fact that "Enter" and "Ctrl + M" produces the same (ascii) code.
As to what is necessary and useful in the real world, for anchoring, we ca take that discussion some other time. I lived "on the hook" for ten years before I even put my hands on a gps.......

Thomas

[bdbcat]

ktkanuck/cagney....

There seems to be some chart differential here...
For 14772_1.KAP, my chart info window shows Edition 18, 2005-12-01, and the icon indicates "Skewed Chart"

I see on your images, that the icon indicates "Polyconic Chart". Cannot quite read the window on ktKanuck images.

Here is the KAP header for my chart....

VER/3.0
BSB/NA=ST LAWRENCE RIVER IRONSIDES I NY TO BINGHAM I ONT,NU=1020
    RA=9410,7739,DU=254
KNP/SC=15000,GD=NAD83,PR=POLYCONIC,PP=-75.925,PI=1.000,SP=,SK=45.1476502
    TA=135.1476502,UN=FEET,SD=GREAT LAKES LOW WATER,DX=1.50,DY=1.50
KNQ/EC=RF,GD=NARC,VC=UNKNOWN,SC=GLLW,PC=PH,P1=-75.925,P2=UNKNOWN
    P3=NOT_APPLICABLE,P4=NOT_APPLICABLE,GC=NOT_APPLICABLE,RM=POLYNOMIAL
CED/SE=18,RE=01,ED=12/01/2005
NTM/NE=18.188,ND=06/05/2010,BF=OFF,BD=12/01/2005

How does this compare with your chart?

Dave

[HappySeagull]

Ktcanuck,Dave...Deja vu?(this is halfway through the thread)
http://www.cruisersforum.com/forums/...tml#post652511
do I remember this right?The new chart had no skew in the header?

[bdbcat]

Happy...

Deja Vu all over again....

And the same conclusion holds: This chart is skewed, and NOAA's cartographers don't seem to have noticed it yet.

When I get a little more bandwidth, I'll check the current state of NOAA's chart repo.

I wonder if we should make a check of plypoints at runtime, and sing out a warning if something does not look right....NOAA may never fix this....

Thanks
Dave

[ktcanuck]

Happy has a mean memory! That was it. I know someone else notified NOAA but it would appear nothing has been done so far.

There is, nevertheless, a difference in effect of the two options between versions.

Clearly the route is being transposed to North-Up but the chart is not because of the header error.

Oh, and I updated all my charts from NOAA's website last week. My header indicates updated:

VER/3.0
BSB/NA=ST LAWRENCE RIVER IRONSIDES I NY TO BINGHAM I ONT,NU=1020,RA=9410,7239
DU=254
KNP/SC=15000,GD=NAD83,PR=POLYCONIC,PP=-75.925,PI=1.000,SP=,SK=0.0000000
TA=90.0000000,UN=FEET,SD=GREAT LAKES LOW WATER,DX=1.50,DY=1.50
KNQ/EC=RF,GD=NARC,VC=UNKNOWN,SC=GLLW,PC=PH,P1=-75.925,P2=UNKNOWN
P3=NOT_APPLICABLE,P4=NOT_APPLICABLE,GC=NOT_APPLICA BLE,RM=POLYNOMIAL
CED/SE=18,RE=01,ED=12/01/2005
NTM/NE=18.217,ND=10/29/2011

Is SK the skew? Your header has one!

[PjotrC]

Originally Posted by bdbcat

Maybe it would be better to eliminate the yellow highlighting. This was/is meant to show a 20m width, arbitrarily chosen and fixed in the code. The idea of the highlighting was to remind us that following a previous track exposes us to the inherent inaccuracy of GPS, and that the real track followed is most likely within the highlight region, but not necessarily in the middle.

Comments?

Dave...

I just wanted to show that a sequence of useful improvements eliminates an important function...

- the tracksize optimization (minimum distance), useful in itself, takes away the detail even on the tightest settings
- the track highlighting (nice idea, certainly should be tried in action) hides the rest of detail on the anchorage
- quick-marking introduces more complexity (FS#634 asumes the working waypoint has empty name, since this is what rightclick does, ctrl-M drops a "New Mark"...)

No bugs in there...

I think that perhaps with time-based tracking there should be no minimum distance between trackpoints (as was in 2.1.0?), or it should be settable (down to a very small number).

If possible, it would be nice to have optional or settable width of track highlighting (down to 0?).

Some improvements to track handling (both efficiency and functionality) are still possible, but this is more for Feature Requests...

Piotr

[HappySeagull]

Originally Posted by ktcanuck

etc..

Is SK the skew? Your header has one!

Yes it is,KTcanuck.I'll post directions how to fix it over on that thread...

[ktcanuck]

I'll be there shortly! Thanks.

[Ptizef]

Need Help

Impossible to build project 2.6.1210 get an error cmake
(see shot attached)
This is new , till now every thing worked
Thanks
Jean Pierre

[nohal]

JP...
Never seen one like this.
It complains about not being able to find Visual Studio 2008, but from the paths it looks like your environment should be VS 2010.
Could you delete everything in your build directory, especially CmakeCache.txt, start the VS command prompt (Visual Studio Command Prompt (2010) - should be in Start Menu\All Programs\Microsoft Visual Studio 2010 Express - in your case some of it in french of course), cd to the build directory and issue

cmake -G "Visual Studio 10" ..

?
If it fails, check that visual studio itself actually is OK and compiles stuff and perhaps try to reinstall cmake.

Pavel

[Ptizef]

Many thanks Pavel ...
and sorry for my ignorance .
I migrated from VS2008 to Vs2010 recently
Certainly there was a 'mikmak' between them
Every things OK now and 2.6.1210 compiled successfully
Thanks again
Jean Pierre