/vr/ - Retro Games

>>8279536
historically it was actually the opposite. the Z80 was built to have compatibility with the 8086. intel of course improved their chip and eventually took over the entire planet. the rest is history.

>>8121183
You want to keep the game in the stable part and switch out your resources. Plan your game accordingly. It takes skill and care.

>>8005762
something something NTSC colorburst with non-standard voltages
https://wiki.nesdev.com/w/index.php?title=NTSC_video

>>7999250
i couldn't agree more =)
it's nice to remind myself that i'm actually a Mother Fucking Programmer instead of a glue monkey scotch taping the internet together with regurgitated workarounds from stackoverflow posts.
> doing a sound driver for the system is its own world by itself.
indeed it fucking is. it's the most frustrating amount of fun i've had in a long time =)
> without hardly any constraints
i think he means that you are free to write the code however you want, as opposed to sucking satans dick in a cubicle with an Agile PM's gun to your head.

>>7933969
> there's no difference in X or Y scrolling on the NES
Ohhhhhh yes there is. You can just write to the scroll registers in vBlank to denote a new position, but, if you change values mid-frame it gets a whole lot messier.
Changing the X value mid frame is pretty easy: you just write a new X value to the scroll register ($2005), and it just werks. Plenty of time to do it. Changing Y or both X/Y is much more complicated.
The PPU uses the ADDR ($2006) values to render the nametable, and keeps / increments the nametable value there. so, in order to change the Y value, you have to write the "top left of the nametable" value into $2006 and it will start rendering from the scanline you're at. You can't just write to the scroll register mid-frame: it doesn't compensate for the new nametable value, unlike in vBlank.
However: you can't just write in the new nametable value either. There are fine X and fine Y registers that actually exist in the PPU, each denoting 0-7 pixels from the offset of the nametable values. You end up with a combination of $2006, $2005, $2005, $2006 writes in this specific order so you get the X/Y scroll values you want where you want them. It's messy and extremely time sensitive. This isn't even getting into the various (sometimes documented) hardware bugs that fuck up your sprites / palettes when you fuck with the PPU mid-frame. That is a whole 'nother bucket of fun =)
https://wiki.nesdev.com/w/index.php/PPU_scrolling#Summary

>>7413534
whoa! i've never seen a gamecube hack before besides melee of course

what is your toolchain like to accomplish this? did you just hex edit or somehow rebuild it back into C with ghidra or something? did you use debugging features in dolphin? very curious. nice job!

>>7349529
> I'm basically on rewrite three now with no gameplay in sight.
based
https://www.youtube.com/watch?v=KcOneF-dLfc

>>7285374
I started with these:
https://skilldrick.github.io/easy6502/
https://taywee.github.io/NerdyNights/
And i still use this reference:
https://www.masswerk.at/6502/6502_instruction_set.html
It helps if you have other programming experience, but bare metal is a trip man. A bit different than higher level languages for sure.

>>7125497
> Krystal = 2003
> Star Fox = 1993
> Tails = 1992
Brilliant work OP

>>6949826
>Jeremy Parish
Hey guise this one yootoober has an opinion and i base my entire argument around what he said because my Zoomer brain is incapable of independent thought