MacroSystem DraCo emulation

[BastyCDGS]

Heyho!

I just compiled a LHA-Archive containing (hopefully) all DraCo tools from C and DracoTools.

The LHA archive contains:
C/DraCo060Emu
C/DraCoAlert
C/DraCoCache
C/Dracodebug
C/DraCoLook
C/DraCoSetpatch
C/LoadMonDrvs

DraCoTools/DraCoFloppy
DraCoTools/DraCoMouse
DraCoTools/DraCoSCSI
DraCoTools/DraCoSerNum
DraCoTools/DraCoSystem
DraCoTools/DraCoZ2Control

Hope this helps debugging...please note I didn't mention the corresponding .info files.

[Toni Wilen]

Originally Posted by LanceT

Also occurs with CybergraphX V2.1 + 3.1 in Palette Preferences it seems in 24-bit the colours shifts to the right.

It sets graphics start pointer to end of VRAM - 4 bytes and assumes wrap around not working like it would normally work. Not yet sure what the NCR chip does in this situation.

EDIT: Temp fix adjust RGB - BRG in Reshade/ColorMatrix

This is not a fix, image is still "blurry". It is not R<>B swap but shift (Two RGB color components are located in first pixel, one RGB component in next pixel)

In 24-bit modes (and also in 16-bit) some SVGA chips, when panning, shifts color components one by one, not complete pixels.

[Thomas Richter]

Originally Posted by Toni Wilen

It sets graphics start pointer to end of VRAM - 4 bytes and assumes wrap around not working like it would normally work. Not yet sure what the NCR chip does in this situation.

At least the smaller NCR chip (on the RetinaZ2) has a "glitch" in true color mode and I added a workaround in the NCR driver for exactly that. I am currently not able check what exactly I did there unfortunately... I believe the glitch is that the first pixels are lost unless you pre-fetch the data.

[ShK]

For some reason WinUAE seems not use my saved configurations on the next time when I run WinUAE again. Next time after emulation is started it's in 1x size. It will go back to 2x if you change "No Scaling" to "Default" via F12 button.

[Toni Wilen]

Originally Posted by ShK

For some reason WinUAE seems not use my saved configurations on the next time when I run WinUAE again. Next time after emulation is started it's in 1x size. It will go back to 2x if you change "No Scaling" to "Default" via F12 button.

Lots of problems with this report.. (Like this does not have anything to do with DraCo..)

But untick RTG panel "scale if smaller than display size setting". You can't have both manual scaling and window size based scaling active at the same time.

[ShK]

Hmm... That was unticked. I'm using same 2x setting with all other configurations, but DraCo is only which goes to 1x size even 2x is selected and saved.

Edit. ah, I can see that when selecting "No Scaling" to "Default" it seems to also tick "Scale if smaller than display size setting" by itself. New log file is attached without changing "No Scaling" to "Default". In this log it did open into size 1x even 2x was saved and selected.

[Toni Wilen]

Originally Posted by ShK

Hmm... That was unticked. I'm using same 2x setting with all other configurations, but DraCo is only which goes to 1x size even 2x is selected and saved.

It was ticked in attached config file.

EDIT: right, it should be unticked automatically in that case. Apparently not..

[Toni Wilen]

Originally Posted by ShK

Edit. ah, I can see that when selecting "No Scaling" to "Default" it seems to also tick "Scale if smaller than display size setting" by itself. New log file is attached without changing "No Scaling" to "Default". In this log it did open into size 1x even 2x was saved and selected.

If I load it, it shows both hor and vert = 2x. Attach the "real" config file (logs zip contains "raw" version which also includes config lines that are only written to config file when they contain non-default value)

[Toni Wilen]

Originally Posted by Thomas Richter

At least the smaller NCR chip (on the RetinaZ2) has a "glitch" in true color mode and I added a workaround in the NCR driver for exactly that. I am currently not able check what exactly I did there unfortunately... I believe the glitch is that the first pixels are lost unless you pre-fetch the data.

It looks like first byte is skipped. Graphics data in VRAM seems to be like this:

XBGRBGRBGR...
XBGRBGRBGR...

X = byte that does not appear on screen. Even when panning, line's first visible byte is always skipped.

Colors are correct if I add +1 to emulated VRAM pointer.

But this only happens when using CGX. Picasso96 or "native" DraCo 24-bit mode works normally

BGRBGRBGR...
BGRBGRBGR...

Maybe some config register difference?

[ShK]

Originally Posted by Toni Wilen

If I load it, it shows both hor and vert = 2x. Attach the "real" config file (logs zip contains "raw" version which also includes config lines that are only written to config file when they contain non-default value)

Sure. With this filter setting my other configurations will boot to 2x size, but not DraCo.

[Toni Wilen]

Originally Posted by ShK

Sure. With this filter setting my other configurations will boot to 2x size, but not DraCo.

Do you mean RTG filter panel still shows 2x but it still uses 1x? Or if filter panel shows 1x?

[ShK]

RTG filter panel shows 2x, but it uses 1x.

[Toni Wilen]

Try this: RTG panel -> aspect ratio -> Disabled. Seems to work strangely in some modes.

[ShK]

It still stays 1x.

It's kinda funny. After WinUAE has started emulation and if I change aspect ratio to anything via F12, it will immediately take use 2x size.

Just like if I change "No Scaling" to "Default" from filter, it will take use 2x size.

It's like changing something makes it first time to read that there is actually 2x value in the settings.

[ShK]

This RTG filter panel 2x has always been working and using 2x, and still does, except when Altais [DracoBus] (MacroSystem) board is selected.

With Draco it uses 1x as long as you change something RTG related via F12 and then it immediately takes use 2x size (which already was selected in there).

[Toni Wilen]

I think I understand what is happening. There are multiple "RTG" to another RTG mode switches which confuses some filter modes (Normal Amiga switches work slightly differently).

Not sure if I'll fix this is before 5.2 or later. It might not be simple fix.

Use of integer scaling might work around it.

[Toni Wilen]

Possible fix implemented (RTG window resize/aspect/etc). winuae.7z updated.

[ShK]

Starting WinUAE with a saved 2x size from the RTG filter panel. It still uses 1x size, but the image is now also shifted into the bottom right corner (see 1st picture).

Changing any random RTG-related setting via F12, such as enabling "Main window always on top" from the Miscellaneous section, makes it immediately take use of 2x size (2nd picture).

[Toni Wilen]

Second attempt. winuae.7z updated few moments ago.

[ShK]

That works now as expected!