Stop Interlace in AGA mode

[TCD]

^ Wut Anubis said
Set the cpu to 68020 or 68040. First will match the A1200, so choose that

For anime freaks you should visit OT and ask there. But beware once you enter your life will change forever

[andy_blah]

OT? I was just curious tho. 4th page! This thread is going to be quite long

[TCD]

You have been warned, but if you dare click here

[andy_blah]

I dared, but...

Originally Posted by Forums

Sorry - no matches. Please try some different terms.

[TCD]

Originally Posted by andy_blah

I dared, but...

Sorry, then click on 'OT' on the right side of 'Today's Posts' at the top this page

[Graham Humphrey]

Try this.

Now get back on-topic please

[andy_blah]

Yes, now to be on topic, I changed the configuration to what everyone from here suggested, but still I see those interlaces

[Toni Wilen]

This is getting too confusing. Artifacts are ALWAYS THERE, there is no config that can remove them.

[andy_blah]

As I said numerous times in this topic, I know that the mouse should have those artifacts, but I was talking about those:

[andy_blah]

Hmmm, no solution by now, then I suppose that I will stay with the PC or low-res versions, still the MT-32 does not sound that bad

[Toni Wilen]

Originally Posted by andy_blah

As I said numerous times in this topic, I know that the mouse should have those artifacts, but I was talking about those:

It is exact same problem. I originally thought it wasn't because you never mentioned bottom part was moving...

Any non-static object + interlace = interlace artifacts.

[Toni Wilen]

It may be possible to "fix" this (not in every case) by updating both fields 50fps but I don't want to modify display updating code until 1.5.2 is done.

[andy_blah]

It did not fix it unfortunately, at least not in this version.

[NoX1911]

Originally Posted by Toni Wilen

It may be possible to "fix" this (not in every case) by updating both fields 50fps

Wouldn't you need motion detection for that to duplicate fields only on parts that are moving? Otherwise the whole screen would only show one field at all reducing vertical resolution by 50% per frame.

On the other hand showing one field only (maybe with alternating scanlines 0%, 25%, 50%) would result in a permanent flickering even on static parts simulating real interlace behavior of a 50Hz crt tube. A cool retro feature maybe.

[Toni Wilen]

Originally Posted by NoX1911

Wouldn't you need motion detection for that to duplicate fields only on parts that are moving? Otherwise the whole screen would only show one field at all reducing vertical resolution by 50% per frame.

I meant updating both current and previous (*) field simultaneously instead of normal update odd field, update even field etc..

This can't fix programs that only update single field (not full frame) to save raster time etc (I don't think many games do this, demos surely do)

*) previous field = while updating "current" field, store bitplane pointers and all other important display parameters PER line and then playback it during next field. Not simple.

[Angus]

Originally Posted by TheCyberDruid

There is no AGA version. It's just an HiRes option I wonder why the WHDLoad version is LoRes. Maybe there were the same problems as here.

I was messing about in this sort of territory trying to get Mech Force 3.77 to work on my 1200 060 Mediator Voodoo set up. The game is in interlace and is not very 1200 friendly at the best of times.

I got a bit of a result with using a WHDLoad workbench and changing the screen resolution within that, but it was oversized and pretty much unplayable.

Shame, it was a great little game that one.