Gigatron Hackers

lb3361 wrote: ↑06 Jul 2023, 01:56 Then it seems logical to update GLCC in place ?

Yes.

[*] GLCC update: I see no problems maintaining a version of glcc inside my Contrib dir. But this means that one should also revert the commit that creates the subdirectory Compilers, which currently contains only glcc (outdated). The Compilers folder was mutually agreed to be beneficial to multiple...

Pull request won't be accepted as per https://forum.gigatron.io/viewtopic.php?t=19, I don't have the hours required to review the amount of changes you have made to the root/core. The simple solution is to refactor it all so that it sits in your Contrib area, as everyone else, (including myself has ...

I performed some visual comparisons between your generated images and the best I could produce, using ImageMagick commands such as: magick 21.jpg -ordered-dither checks,4,4,4 "D:\Projects\Gigatron TTL\buildx64\res\image\21.tga" magick 21.jpg -ordered-dither o2x2,4,4,4 "D:\Projects\Gig...

Console log says: ich@iMac-von-ich Gigatron % Loader::initialise() : INI file 'loader_config.ini' has bad Sections : reverting to default values. Cpu::addROMS() : unknown ROM type : roms/racer.rom (That is your loader_config.ini from your url - not any old one) Delete the ROMS section in loader_con...

You're not using the latest version of gtemuAT67, the latest version is always here:
https://github.com/at67/gigatron-rom/tr ... ntrib/at67

P.S. That's not a crash, it's a clean exit handling an unknown ROM

That INI file section is no longer needed, create a 'roms' folder wherever your executable is, (case sensitive for Linux and MacOS), and copy your ROM's into the folder.

Aaaah very nice, you're simulating more bits per colour component, (I assume by flicking between different combinations of black scanlines), reminds me of interlaced HAM on the Amiga.

Now fess up and tell us exactly how you did it, if I was wrong

P.S. Very cool!

I see a strobing anime character.