djyt/cannonball

Non interlaced resolution compatibility

baritonomarchetto opened this issue · 5 comments

Hi Chris, I have noticed that the new engine (v032) only runs with interlaced resolutions. Could a resolution of 320x240 (or even better the original resolution) be supported in future releases?

Thanks for resuming the development of this great project!

djyt commented

It runs at 320x224. I have it running here on a CRT via the Pi4.

What video settings are you using?

scale = 1, hires = 0, full-screen will ensure you're running in the original resolution.

Those are exactly the settings I have, but probably it's a groovymame fault ( or better, my fault in setting resolutions up) even if mame's outrun runs at native resolution without issue here

djyt commented

How do you mean a GroovyMAME fault? I don't understand the connection between CannonBall and GroovyMAME.

No sorry: I meant CRT emudrivers. I should stop working and writing posts at the same time :D

Thinking at this, I had no problems running cannonball (2.2 IIRW) on my old pc with CRT emudrivers 1.2. Now I use super resolutions with v2 emudrivers and I am starting to think that this could be the culript. Would it be possible to add an option to set a user/custom resolution so that one can toy with that option? :D