Scanline opactity/level and Scanlines vs Doubled modes

[mark_k]

Using null filter, graphics API Direct3D, I set Line Mode to Scanlines. I can adjust Scanline opacity and level (under Extra Settings in Filter page) and the result is shown in realtime. However instead of mixing the Amiga output colour with a variable proportion of black, WinUAE always shows a shade of grey (so no relation to the Amiga output image). The intermediate lines are created as a blend between black and the shade of grey specified by scanline level. Where in the blend is determined by the scanline opacity setting.

The reason for that seems to be, scanline transparency and level settings only apply in the way you would expect when Line Mode is set to Doubled. When Line Mode is set to Scanlines, the intermediate lines are all black and the opacity/level settings affect those black lines.

So I'm just wondering, what is the point of the Scanlines setting when the scanline opacity/transparency settings only do something reasonable when Line Mode is Doubled? And the Scanlines mode is visually equivalent to setting scanline opactity = 100, scanline level = 0. I think it would be less confusing if Doubled mode would always double lines (ignoring scanline opacity and level settings), and the Scanlines setting would behave as Doubled does now (i.e. scanline opacity and level settings active).

[Toni Wilen]

Display Panel Scanlines option is oldest option. It is there just because it has always been there (It is hardwired to custom chipset emulation). I never use it.

D3D scanline option is second option. It always has 1:1 pixel mapping, totally independent of Amiga resolution and chipset processing. (Does not look like a crap if you have any scaling options enabled) EDIT: this is simple alpha channel transparency.

Best option is RGB masks.