OpenCPN Beta Version 4.8.10119

[rooiedirk]

Yes, works fine now.

[Gilletarom]

Hello,

Lenovo W 10, 64 bits, Intel core i5-5200U, CPU@ 2.20 Gh, RAM 4.0 Gb, Graphic card : Intel HD Graphics 5500

In preparing screenshots as you ask, I observed a strange phenomenon.
I have CM93 and oeSENC from Norway. The visible boat is that of Hakkan.

The first screenshot shows the CM93.

On this map area, there should not be a green rectangle in the map bar because the oeSENCs do not cover this area with this zoom level.
Yet there is a green rectangle.

If I click on it, the map displayed is normally a CM93. But we observe two things:
- The green rectangle disappears,
- We observe a gray artifact, which follows all along the coast (OCPN use some tool that it use when it display oeSENC ?)

...Strange.

[bcn]

Have you tried OpenGL ON/OFF? Differences?

[Gilletarom]

Originally Posted by bcn

Have you tried OpenGL ON/OFF? Differences?

My previous post : OpenGL ON

This post, OpenGL OFF

[verkerkbr]

Because the plugins have moved, oeSenc no longer works. Otherwise no problems here. All running well.

Just another question. I have looked at the printer option in OpenCPN. Installed Cups on my Raspberry Pi Linux Stretch. This works with my laser printer. However I also have an Epson color A3 injet printer. I used for printing some charts on A3 format. It is good to have some paper Charts.

With the right drivers the A3 printer also works from my Raspberry Pi to my surprise. But in OpenCPN I can print only in A4 format, but not in A3. It works in other applications in A3.

I think it is a good idea to print some charts also on paper.

Because it works, it is perhaps not so difficult to have the A3 format option also in OpenCPN.

Regards,


Bram

[rgleason]

Originally Posted by bdbcat

Dirk/Hakan/Rick...
Improved cm93 at high latitude. Now we skip the NoFind logic if the array becomes too big, as it will in areas where cm93 coverage is very sparse.
Used locally, as for "normal" navigation, the array stays small, so we still use it.
Thanks
Dave

Dave, It's much much better. Superb in fact! Thank you. No black screens, the twirling spinner is hardly apparent. Very nice smooth operation.

[bdbcat]

Ahoy translators...

The crowdin .pot sources have been updated. There are some new strings to translate in OCPN core. I will pull the new translations at 23:59 UTC today, and include in the next Beta.

Thanks
Dave

[Hakan]

On Win10
I still have the issue noted here: https://github.com/OpenCPN/OpenCPN/p...ment-358110575

When click on Options->Display->Advanced->Options: It takes 5-8 seconds without any response whatsoever. Then a full canvas white window is opened behind Options window and after ½ a second the OpenGl Options dialog is eventually shown. If I close the OpenGl Options dialog and reopen it's fast as usual. But next time the whole path from wrench it's the same delay again.

Anyone else seeing this or I'm the only one?
Håkan

[nohal]

Originally Posted by Hakan

On Win10
I still have the issue noted here: https://github.com/OpenCPN/OpenCPN/p...ment-358110575
Anyone else seeing this or I'm the only one?
Håkan

Hakan...
No, on none of my machines. Already in that pull request comment I told you where I think might be your problem. So as a quick test - what happens if you replace https://github.com/OpenCPN/OpenCPN/b...pp#L8783-L8795 with

return wxEmptyString;

?

Pavel

[Hakan]

Originally Posted by nohal

Hakan...
No, on none of my machines. Already in that pull request comment I told you where I think might be your problem. So as a quick test - what happens if you replace https://github.com/OpenCPN/OpenCPN/b...pp#L8783-L8795 with

return wxEmptyString;

?

Pavel

Pavel..
Sorry, I missed that test. Now done and Yes, if I replaced that part with "return wxEmptyString;" the problem is gone. The dialog box is opened very quick. And if put the original code back the opening delay is there again.
Håkan

[nohal]

Hakan...
Is it a problem only in Debug builds or in Release as well? - On Windows, some filesystem operations are painfully slow (that's why we have all the new "missing cell" logic in cm93 now, for example) and all we could probably do here is cache the result of GetTextureCacheSize() - But for how long?

Pavel

[rgleason]

Turning on/off

• Enable Touch Screen Interface
• Enable Chart Object Scale Factor

Tend to crash Opencpn. I tried it on an earlier version and that also happened.

[Hakan]

Originally Posted by nohal

Hakan...
Is it a problem only in Debug builds or in Release as well? - On Windows, some filesystem operations are painfully slow (that's why we have all the new "missing cell" logic in cm93 now, for example) and all we could probably do here is cache the result of GetTextureCacheSize() - But for how long?

Pavel

I've only tried released, that is running the .exe file.

So why a difference now after #970, before it wasn't any problem? Is that change introducing a new file system operation?
Håkan

[nohal]

Originally Posted by Hakan

I've only tried released, that is running the .exe file.

So why a difference now after #970, before it wasn't any problem? Is that change introducing a new file system operation?
Håkan

Hakan...
I honestly do not believe there can be any difference between "before #970" and "after #970". Other than "before", your raster chart cache was smaller. #970 has absolutely nothing to do with this, it simply adds 2 checkboxes to that form.

Pavel

[Moo]

Originally Posted by nohal

Hakan...
Is it a problem only in Debug builds or in Release as well? - On Windows, some filesystem operations are painfully slow (that's why we have all the new "missing cell" logic in cm93 now, for example) and all we could probably do here is cache the result of GetTextureCacheSize() - But for how long?

Pavel

I also see this in the Beta release. Brings my machine to its knees. An older but decently spec. i7 machine with 4G of memory. Load a long track and a couple of Kap charts and disk access sky rockets. I thought I had a hard drive problem but it checks out OK. Can't be more specific about what is actually reading and writing but something is.