OpenCPN Beta Version 3.3.2222 Released

[PjotrC]

On Windows Vista the selection of alternative tides database is forgotten after a restart. I am not sure if this is intentional - the manual does not indicate if the selection is temporary, so a natural expectation would be to have it preserved.

This was also the case in previous 3.3.x beta(s), but stable 3.2.2 is OK in this respect.

[P_Dub]

Can not send a message to Saildocs for obtaining the weather grib file!
Windows 7; the pup-up ask for making Outlook as my mail, which it already is. Ed 3.3.2222
Bye

[Ptizef]

Originally Posted by P_Dub

Can not send a message to Saildocs for obtaining the weather grib file!
Windows 7; the pup-up ask for making Outlook as my mail, which it already is. Ed 3.3.2222
Bye

P_Dub

Sorry but I didn't understand well..
which pop-up are you speaking of ?
What exactly happens when you click the "send" button ?
thanks
JP

[P_Dub]

Here is a print screen of the pop-up.
Bye

[jongough]

HI, just installed 3.3.2222 and been for a quick checkout run with it. All is fine except for the autopilot output, APB (TMQ AP4 only recognises APB, not RMC). In this version the output to the autopilot gets more and more unstable the longer it is run. The APB messages seem to vary each side of the true course required by more and more, and in fact you end up going somewhere completely different from the route that is supposed to be followed.

I went back to 3.3.2118 and the autopilot was as it used to be. I have a feature request in to enable true filtering of input messages to solve a slight problem. But in this version I am not really sure what is going on. The NMEA output window does no seem to show the amount of erroneous messages being sent to my autopilot. Looking at the autopilot front panel which shows the magnetic course it is trying to steer there appears to be a new course every second with differences as big as 30degrees.

I have attached a PDF showing two screen shots of the NMEA output and part of the track followed. You will notice the complete overshoot of the waypoint. The log from the time I was doing the test and a screen shot showing the track that was actually followed.

Regards
Jon

[George64]

Originally Posted by bdbcat

Rick, et al...

In 3.3.2222
"He asks what the difference between
Default Tracking and Always Track is..."

The MMSI Properties dialog allows one to preset the tracking behaviour of a particular MMSI target, even if the target is not presently visible.

For instance, a particular ferry comes to your area 5 times daily. We don't want his track cluttering the screen. So, catch and write down his MMSI once. Then set that MMSI to either "ignore" or "never track". O will forever-after not track this target. There you have it...

Or, for whatever reason, you always want to track the "Queen Mary", even if you have no idea where she is, or even if you will see her at all. Preset it as you like.

Default tracking is what you get as in previous versions. Controlled by options->ships global setting, and individually in the AIS target list.

"Always" and "Never" override the setting in options->ships, and the per-target eye icon in the AIS target list

Hope this helps
Dave

Can this also be used to not display your own mmsi? Using AIS still shows a collision situation with myself

[cagney]

Dave

When preparing to update the wiki with the new MMSI properties, I had a crash. I'm sure I have tested this earlier without problems......

Pressing "Edit" below


Generates this repeatable (most of the times) crash


Thomas

[CarCode]

I have checked the Mac OS X version from opencpn.org.
It is coming without any plugin now? Not even grib_pi and dashboard_pi anymore?
Strange.

Gerhard

[AISEAG]

Hi,

First of all, thanks for this brilliant new beta version.

What is the logic to prevent particles running when they have been selected in both wind and currents ?
specially if, just like now, in the Grib window, options are exclusive ?

Thanks
Serge

[sailorF54]

Including the 'Timezones.gpx' layer in the Layers folder slows down O opening by about 30 seconds, whether hidden or not...
Layers Library | Official OpenCPN Homepage
Did not occur in 3.3.2118

[nohal]

Uwe, Francois & all...
There is a regression in 3.3.2222 causing an extensive (and unnecessary) calculation every time a point is appended to a track during the load, resulting in the slow loading times with big navobj file or layers like the timezones.
Problem well understood now and fix trivial.
Pavel

[P_Dub]

Is there a way to remove or not showing time zones when not necessary?
Regards

[nohal]

P_Dub...
I'm not sure I understand what you are asking about. But you can hide it as any other layer.
For source builders: The master performance is now back to normal.

Pavel

[P_Dub]

I don't see them in the layers but they are visible on the charts. So what am I missing?
Bye

[Ptizef]

Originally Posted by AISEAG

Hi,

First of all, thanks for this brilliant new beta version.

What is the logic to prevent particles running when they have been selected in both wind and currents ?
specially if, just like now, in the Grib window, options are exclusive ?

Thanks
Serge

assuming you have set particles for both :
If you want current particles you select "current" on the main grib window
I you want wind particles, select wind
Just one data type at a time is displayed with all his parameters
The only exception is for wind arrows and pressure isobars which can be displayed in any case

This is in the current 3.3.2222

A patch is proposed to allow multi selection.
that means you will be able to select wind + pressure + ...
but of course superposition of the same parameter for several data types will stay impossible
For example, in the case above the multi -selection will not work to ovoid superposition of two particles at the same time
but if you set wind with barbed arrows + particles, current with direction arrows + colored overlay, the multi selection will work
Jean Pierre