OpenCPN Beta Version 3.3.2316 Released

[bdbcat]

Håkan...

This is a bug in ATI OpenGL drivers. glGenerateMipmaps for ATI drivers is a chronic problem.

To continue testing, disable the entire fog_it clause:

if(0){ //if(fog_it){
.
.
.
}

Dave

[bcn]

Dave,

noticed that the color for MMSI backed-up AIS targets has gotten a bit more yellowish now (latest build).
Any special reason?

[Hakan]

Originally Posted by bdbcat

Håkan...

This is a bug in ATI OpenGL drivers. glGenerateMipmaps for ATI drivers is a chronic problem.

To continue testing, disable the entire fog_it clause:...
Dave

Ok, thanks. But strange that the fogging was working a week ago?

Thanks for the tip, but disabling is not a problem, it's just to set FogOnOverzoom=0 in config.
Håkan

[bdbcat]

Hubert...

We shifted to 0xAAFF00 for the name-cached target color, on someones recommendation.

Is this color OK?

Dave

[bcn]

Dave...

different and one has to got used to it.

When there are targets with different status one next to other it's obvious (as before) - but I have yet to see the situation of an isolated target (backed-up) in order to have a look if it is intuitive...
In the day/dusk/night setting one can distinguish the three colors.

Looks ok.

Hubert

[bdbcat]

Håkan

I have pushed to github a workaround for ATI/Radeon graphics cards on the overzoom fog/blur crash.

Will you please test with your card, setting FogOnOverzoom=1 in config?
I wonder about performance in the overzoom situation....

Thanks
Dave

[Hakan]

Originally Posted by bdbcat

Håkan

I have pushed to github a workaround for ATI/Radeon graphics cards on the overzoom fog/blur crash.

Will you please test with your card, setting FogOnOverzoom=1 in config?
I wonder about performance in the overzoom situation....

Thanks
Dave

Dave..
Well, in debug it was again a break although not the same:
First: See attached pic.

End then upon "Retry"

In dbgheap.c : 1376
else
                {
                    _RPT3(_CRT_ERROR, "HEAP CORRUPTION DETECTED: after %hs block (#%d) at 0x%p.\n"
                        "CRT detected that the application wrote to memory after end of heap buffer.\n",
                        szBlockUseName[_BLOCK_TYPE(pHead->nBlockUse)],
                        pHead->lRequest,
                        (BYTE *) pbData(pHead));
                }

More ideas I can test? It's my pleasure.
Håkan

[bcn]

The AIS targets side by side day/dawn/night

[bdbcat]

Håkan ...

OK, I adjusted the overzoom effect again for cases where the OpenGL driver has trouble blurring.

I reverted to "fogging" instead of "blurring" for ATI graphics cards.
"Blurring" for ATI cards is just too slow...

Try the latest commit, please.

Thanks
Dave

[Hakan]

Originally Posted by bdbcat

Håkan ...
.......Try the latest commit, please.
Thanks
Dave

Dave..
Now we're talking!
It works fine in Debug and in Release build. Run time function is great both with and without fogging. Very good!

And I also like the "fat" shore line at great zoom levels introduced some commits ago. (Hopefully intended?)

Thanks
Håkan

[bdbcat]

Folks...

In preparation for a new Beta Sunday PM, there are new .po files available for translation in crowdin. There are some new and revised terms....

We will cut off crowdin input at 2300 GMT, 30 November.

Thanks
Dave

[Gilletarom]

Dave,

Originally Posted by bdbcat

Folks...

In preparation for a new Beta Sunday PM, ...
We will cut off crowdin input at 2300 GMT, 30 November.

Dave

I visited the crowdin just before 24h French time. It must be good.

Gilletarom.

[rgleason]

Yesterday compiled v3.3.2316 and started using it. My reactions.

1. Options interface is very much improved. Thank you Caesar & Bdcat.

2. When in non-opengl and Options is stretched, resize causes double boxes to appear. See attached.

3. When in opengl this does not happen.

4. Overzoom blur - It takes about 5 scale steps beyond initial Overzoom before blur is actually seen or effective. I find this to be a very reasonable reminder that you are really overzoomed! I really like the feature and cannot understand why it is such an issue. Being able to turn it off in config is a bonus, but I am not going to do that. If I could, I might even adjust it to be a little earlier, at 3 or 4 steps in.

5. Somehow OTcurrents was installed with the new install. I really like this plugin for planning because it allows us to select a date and time for tides and currents.

6. It would be very nice if this same plugin interface for adjusting Date and Time would be selectable when an individual station is brought up (Right click) because we only have "Next" and "Previous" controls rather than "Date" and "Time" as in OTcurrent as Mike has done. See screen shots attached. How hard would this be to do? --Would be a Big planning improvement. In many respects OTcurrent is far more useful....as it changes all of the stations. However similar control of each station would be appreciated. ...Actually I think these functions could be merged somehow as they are similar. Many thanks to Mike [Rasbats] for an excellent plugin.

I remain incredulous at the energy and productivity in this group and the many valuable contributions. Thank you all.

[rgleason]

When did 3.3.2330 get released? Coming fast and furious now.

[rgleason]

One other small thing I noticed was an unusual difference in text size for Options > Charts > Groups. See attached. The text is greyed and italic which is fine, but I think it is scaled a little large on this Win7 machine. Is it the same way on Mac and Linux? If so perhaps it can be adjusted? ---But don't go through lots of hoops, just a suggestion, we can all live it.