John Novak

Yeah I'll add this at some point, but it's relatively low on my priority list. Ideally, I'd like to do it after @GranMinigun's pipeline refactoring stuff; easier than fighting the...

> And, If you play Alley Cat, use the booter version or you won't get the awesome PCJr music. You seem to be a bit of an expert in all...

> The easiest way to show overscan colour would be to set clear colour for both texture and GL outputs. Of course, that will paint the whole area around actual...

> Not the case, because clearing backbuffer doesn't equal drawing to it with a shader. Yeah, so everything what I wrote in my long post above stands then.

> Personally, I suspect the _most accurate_ way to handle this is to have the VGA code just generate a larger image with the border included. The exact size of...

> I use the Hoxs Commodore 64 emulator and it allows you to set the border to just the right and left sides. This effectively makes your widescreen monitor the...

> I recommend ripping the band-aid off and doing this the right way. Well, I don't agree with any of that. What _practical benefits_ would this extremely hardware-accurate approach bring?...

> There's a lot of room for improvement, but there's a huge amount of risk for failure and regression. I appreciate the confidence, and yes - like @johnnovak said, if...

I'm honestly curious (no irony) where would the "correct" border implementation have any tangible benefits over the proposed simplified approach where you just pick any border width you like, basically?...

Note hardware accuracy and "emulation as documenting hardware accurately" is not among our goals, by far. It was never among the goals of the original DOSBox either. Have you ever...