Beta Test / Technical

[rgleason]

Thanks for posting this.

I just want to make it clear here, that both my integrated Intek HD Graphics 3000 board and Nvidia Geforce 540m board run hardware opengl when using OpenCPN. What I cannot seem to do with this rig is disable all hardware opengl and enable did-g's suggested software opengl, so that I can run some tests on speed and fps, etc.

[travellerw]

Originally Posted by travellerw

I will source that exact driver and try it out. At this point I have tried about 4 versions of the driver and they all have the same result. My frame rate is about 1 frame every 5 seconds (no not kidding). The only way I have been able to get OpenGL to work is with the dll I listed above..

However.. I will source this driver version and test it out. I will report back..

Alright back already...

Unfortunately that driver had the exact same result for me. Scrolling and zooming is so slow that OpenCPN is unusable. In fact even loading OpenCPN is very slow. Once OpenCPN loads, it takes 15 seconds before the toolbar shows up.

I'm only using OpenCPN with CM93 charts and just the Dashboard plugin. I run 1600 X 900 resolution.

At this point, back to using the dll I posted..

[rgleason]

When are we changing to wxWidgets 3.0.3?

Jon reports that wxWidgets has that as the stable version. I understand from the previous wxWidgets change that all plugins will need an update and will not be backward compatible with previous versions of opencpn, but will be going forward.

Is there a plan for these upcoming changes?

Thanks.

[rgleason]

Forgot the post
http://www.cruisersforum.com/forums/....php?p=2523265

[bdbcat]

Rick...

Any good reason to change to wxWidgets 3.0.3?
Do any of the fixes there relate to us?

Thanks
Dave

[rgleason]

Sorry Dave, Tdan and Jon will have to advise, I know they've been using it.

[transmitterdan]

Originally Posted by bdbcat

Rick...

Any good reason to change to wxWidgets 3.0.3?
Do any of the fixes there relate to us?

Thanks
Dave

I don't think there is anything in 3.0.3 that affects O.

Eventually we will want to move to 3.1. I have been testing with Win10 against latest git of wx and no issues so far. Next I will try on Rpi. But there is no rush I think.

[rgleason]

Thanks Dan,
So I guess we can wait until 3.1 anyway, but

"I don't think there is anything in 3.0.3 that affects O."

Makes me think using wxWidgets 3.0.3 would not affect other PI anyway. So I'm going to find out with Jon's O4.8.0 w/wxW 3.0.3 version.

[bdbcat]

Rick...

I doubt there is any change in the wxWIdgets API for 3.0.3, so I suspect the Plugins, etc. will all work fine without modification.

Dave

[rgleason]

Dirk's new plugin deviation_pi has about nine errors when I compile as standalone, related to tinyxml.h which is missing from the src folder.

I know that opencpn now includes those tinxml files somehow, but would we need to include a tinyxml.lib file somewhere to eliminate the errors I am getting when compiling as standalone?

A brief explanation would be helpful.

Thankyou.

[bdbcat]

Rick....

First thing to do is copy tinyxml.h from the OCPN source tree into the plugin source tree. Then try the build again, to correct compile errors.

Then try to load the plugin, and check the log for errors....

Good luck
Dave

[rgleason]

Thanks Dave, That has helped. Also Dirk now has a tinyxml directory under src, which I copied tinystr.h into. Just one more error like that to fix now.

[jongough]

Hi Dave,
If I try and run my plugin which has been compiled with wxWidget 3.0.3 against the standard released version of OCPN I the following error. There appears to have been a change in one of the colour routines. I get around this for my testing purposes by using the current widget DLL's in my build of OCPN exe's as I don't have wxWidgets 3.0.2 as 3.0.3 is the only downloadable version.

It should not be a problem when a new release version of OD is made as the build system should have the compatible version of widgets.

Regards
Jon

Originally Posted by bdbcat

Rick...

I doubt there is any change in the wxWIdgets API for 3.0.3, so I suspect the Plugins, etc. will all work fine without modification.

Dave

[rgleason]

Dave, this might be an OpenCPN bug.

http://www.cruisersforum.com/forums/...ml#post2535382

The symptom is GPS JUMPING.
It appears to be a malformed AIS sentence that is not rejected, so that it apparently is interpreted as a new position for own ship, which should not happen!

I'd be interested in what you think.

[rgleason]

Bad AIVDO checksum, causes OpenCPN OWN SHIP GPS JUMPING!

http://www.cruisersforum.com/forums/f134/opencpn-jumping-map-194531.html#post2535407

This is a little bizzare.

Shouldn't Opencpn have a checksum calculator built in and reject bad sentences that cause this kind of problem?

Or at the very least, a bad checksum on an AIVDO should not cause a GPS Location JUMP for Own Ship!!!