OpenCPN Beta Version 3.3.2330 Released

[nohal]

Originally Posted by fgd3

Thanks. That part I remembered. I was afraid I wouldn't remember the commands in vi to exit the program with the file saved in the right place.

:wq

The image you attached was slightly blurred. Is that part of the FogOnOverzoom effect or just an artifact of OpenGL?

Fabbian

Fogging. You can set both - after the beta gets released in a few moments, head to the Advanced display tab in the toolbox and play with the 2 "Suppress" checkboxes. I can hardly imagine you wouldn't find a setting you like...

Pavel

[fgd3]

Originally Posted by nohal

Fogging. You can set both - after the beta gets released in a few moments, head to the Advanced display tab in the toolbox and play with the 2 "Suppress" checkboxes. I can hardly imagine you wouldn't find a setting you like...

Pavel

Thanks. I'm looking forward to trying it out. It already looks a lot better. Checkboxes in the program will certainly be a lot easier than editing the config file.

Fabbian

[Gilletarom]

Hello Anyone, Hello dave,

On the scale:

1 I notice that nobody has raised the question about Carcode deformation distance due to the Mercator projection. This means that in the collective mind it does not matter?

2. We used a small PC in a public demonstration of O. We used the HDMI output for display on the screen on a TV, four sizes larger than the PC screen.

Obviously, the scale marked on the bottom of the screen on the PC and the television was the same. This is normal with these operating instructions. Someone pointed out that what is important is the size of the screen.
A track may be exploitable: Measure the screen length and width, and provide this information to O.
O knows the coordinates of the points displayed in the 4 corners of the screen. With these coordinates O is able to calculate the actual distances between the extreme points displayed.
With the actual distances and size of the screen, it must be a way to deduce the scale of the display. And therefore to deduce the actual zoom ratio compared to the official scale used chart.

This idea is it absurd?

B.R. Gilletarom

[Gilletarom]

Hello dave,

You received, some minutes ago, a crash report.

I try to change group of chart from NV-Verlag to VMH. I add that I forgot to unlock the VMH stick before to use O.

[Hakan]

Originally Posted by Gilletarom

Hello Anyone, Hello dave,

On the scale:

1 I notice that nobody has raised the question about Carcode deformation distance due to the Mercator projection. This means that in the collective mind it does not matter?
........................
This idea is it absurd?

B.R. Gilletarom

Gille.......
I can't say I understand your purpose.
Do you actually intend to take a hand held ruler and measure a distance on the screen, instead of using the pencil tool, F4, or read the distance from boat to pointer in the bottom list?
Or did I misunderstood all of it?
Håkan

[NahanniV]

OpenCPN Beta Version 3.3.2410 Released

http://www.cruisersforum.com/forums/...ed-137911.html

[bdbcat]

Gilletarom...

1. Mercator projection: On paper charts, distances measured manually with dividers are converted to actual distances using the latitude scale. This is normal navigation practice. Of course, at high latitude, there will be distortion, horizontal vs vertical. This is the nature of mercator. The scale bar we show on screen is calculated with respect to latitude scale, as recommended by IHO.

2. Your idea is not absurd. It is the key point.

If we know the physical size of the display, we can accurately calculate the scale.

It just remains to determine how we ask for this information from the user. Dialog box entry of dimensions in mm? Or should we ask for monitor DPI specification, which is really the same thing?

And what is default?

These are good questions, and input is good.

Dave

[colemj]

Originally Posted by bdbcat

Mark...

re Mac color temp changes...

We have done nothing on purpose to change this in months.
If you have saved the older Beta DMGs, maybe you could discover when it changed, to give us a clue?

Thanks
Dave

I just went back to the stable release and it does the same thing. I either never noticed it before, or it is only my computer. The only thing I have done related to this in the in-between was calibrate my colorsync profile. Maybe it is something there.

Again, it is not a problem at all - just something I noticed.

Mark

[bdbcat]

Mark...

Does the color temp revert to your settings when OCPN exits?
It should....

Dave

[colemj]

Yes, everything goes back to how it was when I exit OCPN. If I just minimize OCPN and make another program be in the forefront, the color stays changed as by OCPN.

Mark

[CarCode]

Mark,
do you see a line like this in your OCPN log file?

14:42:04 CET: Warning: iCCP: known incorrect sRGB profile

This comes from newer png libraries which doesn't wants the old iCCP profile embedded in png pics.
Gerhard

[colemj]

Originally Posted by CarCode

Mark,
do you see a line like this in your OCPN log file?

14:42:04 CET: Warning: iCCP: known incorrect sRGB profile

This comes from newer png libraries which doesn't wants the old iCCP profile embedded in png pics.
Gerhard

Yes, I have this warning in the log file. Are you saying that my calibrated profile is causing the problem?

Mark

[rgleason]

Hakan:

Do you actually intend to take a hand held ruler and measure a distance on the screen, instead of using the pencil tool, F4, or read the distance from boat to pointer in the bottom list?

Yes!! We do it whenever setting up our CAD program on a different screen. It must be done to get the drawing image scaled correctly, otherwise the plan and proportions are all screwy!

I encourage this improvement in settings for greater proportional accuracy.

[rgleason]

It just remains to determine how we ask for this information from the user. Dialog box entry of dimensions in mm? Or should we ask for monitor DPI specification, which is really the same thing?

Priority in this order:
Monitor DPI: pixels/inch
Screen Resolution: width and height in pixels
Screen Dimensions: width and height in decimal inches or mm.

We enter in decimal inches for our CAD program.

[CarCode]

Originally Posted by colemj

Yes, I have this warning in the log file. Are you saying that my calibrated profile is causing the problem?

Mark

No, the reason of this line in the log might be that the Mac version of OCPN is compiled with a newer version of wxWidgets and this uses a newer png library also.
Gerhard