nesdev.org

Yeah would have to be not CPU intensive (and not sprite loading intensive either) because Overdrive does a CPU spin instead of relying on hblank interrupts (i.e. CPU is busy looping through the entire active scan in order to get the right timing). Maybe it's more doable when the palette changes onl...

There are a few cases where there are too many faces in a line and it glitches up, luckily those areas are small enough to be overlooked. Ah ok, so there is this limitation, still pretty impressive to see it running at 60 FPS and that big :) I made my own 3D flat rendering engine and of course it j...

The cube relies on the scroll planes actually =/ (and the cube is bigger in PAL too, 1.1 isn't NTSC-only in case you wonder) Pretty sure there was an explanation of how it works in some site... if not huh just look at it while disabling individual layers and it becomes obvious, honestly. It was the...

Nope, that was just a coincidence, although when Titan was struggling in Revision to get it working (since timing wasn't fast enough) and I was brought in at last minute I did point out that Puggsy did something similar... sadly there wasn't enough time to disassemble the game and find the relevant...

Mickey Mania does it as well (disabling VDP during hblank) during the moose hunter run sequence and it still does display sprites (some are clipped for that specific reason hopefully that is a wanted effect in the situation). I didn't know about the effect in the puggsy credits, this game is awesome...

The timing matters because you can't make 7~8 palette writes in a single line and not have garbage pixels, you were arguing that because the FIFO ate them that it was safe =| What i meant by *safe* is that your writes aren't lost whatever happen which is already a good point... and the FIFO is defi...

Can you please stop talking about "fast slots"? There isn't any such thing, you're just going to cause even more confusion and I think you don't even know what "slot" means (again: it's the dot clocks where a write can go to VRAM/CRAM/VSRAM, nothing else - vblank also has slots ...

Yeah but the hblank time is almost identical from what i remember (maybe 46 cycles actually). But that is just the hblank flag timing, not representing the real hblank i guess. And if the hblank does not provide extra slots (i mean fast slots) then it doesn't really mind... It's then just timing rel...

That actually explain... HBlank accesses are not any faster than active period accesses (it's what i meant by "slow" slots). Strangely i was still able to fed about 8 words without any wait state on the 68000 in a code i made a long time ago, maybe the code was slow enough to allow 3 slots...

I know what a slot is, but normally during hblank the vdp access should be fast, by slow I meant as slow than during active period (which is slower than the 68k can write). From my calculation hblank is about 44 68k cycles and so you should have more than 3 full speed slots but I guess the vdp uses ...

I've never touched the PCE. So i hardly see how you can find it that limiting, of course vram accesses are tricky during active period, the vdp is hell busy and I think it's already quite nice to have (even limited) access (snes is not that permissive here). Point stands though that you simply can'...

If you're going to compare SNES in different modes you should also compare Mega Drive in different modes as well, since the bitrate is completely different in H32 and H40 (as I said, on the Mega Drive you only get 800 pixels in H32 mode, meaning the SNES actually has more pixelrate for the same res...

The MD had 2 BGs and sprites all across the screen for 960 pixels. 976 actually, since it always fetches an extra column for each tilemap (i.e. 336 pixels instead of 320). Sounds wasteful but don't forget that horizontal scrolling causes an extra partial column to show up. Just thinking, what do yo...

lda {x_velocity} bpl + clc adc {x_position_lo} sta {x_position_lo} bcs ++ dec {x_position_hi} bra ++ +; clc adc {x_position_lo} sta {x_position_lo} bcc + inc {x_position_hi} +; It's about 28 cycles max. It's not too much faster than doing 16.16 format, but the benefit is that it makes it easier to ...

Also can you explain me why my collision code have no use in a game ? could you make it faster by the way ? i spoke to have so much velocity in a game, i took this example on sega-16, when you comparing with tomaitheous the efficiency of 65xxx (as you described crappy) and 68k, strangely it was 32b...