I saw someone post this link at work. Its a list of some game studios that choose not to use generative AI: https://aftermath.site/video-games-no-ai/
Remote
TomGwozdz
@TomGwozdz@oldbytes.space
mastodon 4.7.2+glitchGame dev by day. Work on retro-computing projects by night. Currently building the TG6502 single board computer. Also developing Blightmare!
237 Followers
705 Following
8 Posts
Joined October 04, 2022
Replying to
@vincentpants@social.treehouse.systems a couple months ago, a large company I work with force removed nodepad++ from all computers in the company without saying why. I guess this explains that.
I need some floppy imaging advice. I have a Greaseweazle connected to a 3.5" drive. But the floppies I have to image are a bit fragile. When I try to read a whole disk, the first few tracks read fine, but then it starts getting more and more scratchy as it goes, so much so that it starts destroying the disk surface. If I clean the heads, its fine again, for a little while. Is there a way I can read a few tracks at a time so that I can clean the heads in between? Or is there another approach I can use to read these disks?
Replying to
@mos_8502@studio8502.ca What if you focused on some kind of virtual architecture? Something like, for example WebAssembly (just using it as an example, not an endorsement), then your hardware platform could change and evolve as needed as different CPUs become available, or stop being available? Were this to be a reasonable option, the virtual architecture would have to be simple enough such that a VM for it could fairly trivially be implemented on this set of 8 bit CPUs
Replying to
@jope@mastodon.social I had read about that for tapes, I didn’t know if it would apply to floppies too. I might give it a try.
Replying to
@SuperDicq@minidisc.tokyo the drive works fine for known-good disks. But it’s possible there’s still an issue there. I noticed the track option for the tool, but how would I then combine all the pieces into one image?