v0.56.0

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

JetSetIlly

https://github.com/JetSetIlly/Gopher2600/releases/tag/v0.56.0

Improved rendering for monitors with refresh rates higher then 60Hz. Games with flicker kernels should render more cleanly on a 75Hz monitor, for example (without relying on phosphor)

Also added support for DevCard. This is a cartridge type but one that requires a 2600 where all cartridge addresses are visible at once. In other words, a cartridge that requires a complete cartridge bus. In practical terms this really means a 7800 in 2600 mode.

There are prototypes that require this special cartridge that will be released in the future (out of my hands currently).

Full list of bug fixes and new features at the link above.
https://github.com/JetSetIlly/Gopher2600
@JetSetIlly@mastodon.gamedev.place
@jetsetilly.bsky.social

Thomas Jentzsch

Quote from: JetSetIlly on 01 Jun 2026, 07:00 AMImproved rendering for monitors with refresh rates higher then 60Hz. Games with flicker kernels should render more cleanly on a 75Hz monitor, for example (without relying on phosphor)
I don't think so. E.g. 30 Hz flicker at 60 Hz is very even on/off. While at 75 Hz it becomes something like on, on, off, on, off, off, on ...

JetSetIlly

Quote from: Thomas Jentzsch on 01 Jun 2026, 07:53 PM
Quote from: JetSetIlly on 01 Jun 2026, 07:00 AMImproved rendering for monitors with refresh rates higher then 60Hz. Games with flicker kernels should render more cleanly on a 75Hz monitor, for example (without relying on phosphor)
I don't think so. E.g. 30 Hz flicker at 60 Hz is very even on/off. While at 75 Hz it becomes something like on, on, off, on, off, off, on ...

It works well here. There maybe some monitor refresh rates it doesn't work well with though - I don't have the ability to test them all.
https://github.com/JetSetIlly/Gopher2600
@JetSetIlly@mastodon.gamedev.place
@jetsetilly.bsky.social

JetSetIlly

To be clear, it's still a compromise but it's a different compromise to having high phosphor. And I think it produces better results than high phosphor.
https://github.com/JetSetIlly/Gopher2600
@JetSetIlly@mastodon.gamedev.place
@jetsetilly.bsky.social

JetSetIlly

v0.56.1 fixes a serious disassembly bug

https://github.com/JetSetIlly/Gopher2600/releases/tag/v0.56.1

The disassembly process needed to be changed to support DevCard, which supports a bank size greater than 4k. The way I did it introduced a bug for cartridges with bank size less than 4k.
https://github.com/JetSetIlly/Gopher2600
@JetSetIlly@mastodon.gamedev.place
@jetsetilly.bsky.social

alex_79

#5
Quote from: JetSetIlly on 01 Jun 2026, 07:00 AMAlso added support for DevCard. This is a cartridge type but one that requires a 2600 where all cartridge addresses are visible at once. In other words, a cartridge that requires a complete cartridge bus. In practical terms this really means a 7800 in 2600 mode.
Eckhard Stolberg's DevOS for the 7800 allowed to do the same thing: you could load 2600 code into a 32k or 48k linear RAM cartridge and run it in 2600 mode (no need for locking code: the DevOs booted to a menu where you could choose which mode to start the cartridge in, and it automaically locked before jumping to the cart reset vector). Addresses with A12 low in cart space had to be avoided as, in 2600 mode, they were mapped to both the cart and TIA/RIOT, causing bus contention (this is true for the DevCard as well), so you had 16k or 24k avilable in 2600 mode with a 32k or 48k cart respectively.

This same trick (a 2600 game in a 7800 cartridge board), was used in the early 2000s for a reproduction of the 2600 "Save Mary" prototype released by "Video 61". While bankswitching was easy to achieve with off-the-shelf parts at the time, replicating "Sara" ram was not, and early 2600 homebrews or reproductions that needed Sara had to rely on old original chips (either old-stock or scavenged from existing games).
The use of a 7800 board solved the problem as the control signals for RAM are available and allowed to use any standard SRAM chip. The ability to avoid bankswitching was a bonus (Save Mary uses different addresses for the various banks, so requires no change to the code for that).


Thomas Jentzsch

Eckhard was the first person I asked when I realized that the Crack'ed prototypes were meant for such a hardware. And I only remembered him and the DevCart, because I had to make small modifications for my Thrust game back in 2000. So that Eckhard was able to test it on real hardware. 

Good old times... :)