nesdev.org

Hey all - we started a YouTube show in an attempt to highlight the awesome stuff you guys are doing. Here is the first episode, looking at Batlab's Super Russian Roulette. https://m.youtube.com/watch?v=BhC1k5VxDR8 If you'd like us to check out what you're working on, hit me up at Joe@TheNew8bitHeroe...

It's funny, I feel this odd sense of deja vu like I've had this exactly problem before, and there is some weird lingering code right here that i found that is never referenced in my entire program. I wonder if I dropped this for the other method. I'll give this a try. Speed is not a problem with thi...

I have a few instances of this - it is very very very old code, so it's been a while since I dug in, and there are a few quirks I'm not sure the reasoning behind. That being one. Now as I go back through and optimize with greater understanding, I'm attempting to fix all those sorts of things (in any...

Alright - so I'm attempting to do some optimization. Using ASM6, and using CHR ram. Essentially, I have different *types* of tiles that can be loaded (background, screen object, paths), and the loading of each treated slightly differently...and indexes to each are buried in their own tables. It gets...

Annnnnd first step = a failure. You are correct. On hardware, I had the glitch that tells me timing was, indeed, off. Drat. Curses. Foiled. IMG_2910.JPG I'd imagine this would be a fairly obnoxious series of trial and erroring to get exactly right (changing values, flashing, testing...rinse, repeat)...

Yeah, my order of operations for tomorrow is: 1) flash this to cart, test it on my top loader. If it works... 2) Iterate the actual game in its current form and spend likely the whole day moving some memory around, cleaning up my NMI to make it a bit more economical, tracking down places that would ...

Ha. That's funny. I didn't realize NOP was actually an instruction. I just thought it was an abbreviation for a family of potential operations that acted as null. This is where having studied computer science probably would've paid off! haha And...whoa! After counting cycles (and understanding how t...

Thanks for posting that - I think, due to the fact that other things will be going on (and I'm perfectly ok with a single black line...even two wouldn't be so horrible, since it bottoms out with a black line for separation as it is) separating the menu from the action, the looser i could be with the...

Cool. For single cycle increments, just load dummy values into the accumulator or something? Never really done cycle counting like this, not sure what opcodes = how many cycles, etc. Best practice? Is there a source with this so I could evaluate how many cycles each part of this is taking? I'd imagi...

Yeah, I figured I'm was cramming too much in there. I had a feeling that was one of the problems... So then the solution would (or could) be something like... ;;;;;; HBLANK WAIT 1 LDX #$08 ;; i know this value will have to be played with to get it right WaitScanLine: DEX BNE WaitScanLine ;;;;;;TURN ...

Ok - now I'm not *that far* away from implementing this. I'm circling the drain and generally am able to substitute values for the bottom half to get different palettes from the menu bar. I'm having trouble (presumably) with getting the hblank timing right, and still having slight issues getting the...

So...I've gone back to a much earlier (read: simple) version of the code. After a lot of trial and error, I found that putting in some flags to make sure that the nametable AND zero sprite are drawn prior to checking for the hit got me past the *freezing* in that version. It's possible that a sprite...

Yeah, I looked at that for a lot of reference. Everything seems fine, except for the sprite 0 hit. If I take the sprite zero hit out, i can change the palettes no problem. But as soon as i do the sprite 0 hit stuff, I crash and get all sorts of funky things happening with scroll. Hm.

Sorry - that was a misplaced note to myself. Yes, rendering is on for the eval. Essentially, I load the palettes (all) then turn back on rendering, do the checks for sprite 0 hit, turn rendering back off, and then load the *other* palette* once the hit fires. I have tried zeroing out $2005 afterward...

I'm making a bit of progress...right now, in just trying to successfully read a hit without glitching or locking up. I can visibly see where I'm getting a split (right now, ugly horizontal line that flickers...i'm sure that's a timing issue) but unfortunately, the bigger problem is that: a) I get a ...