nesdev.com

NTSC - Never The Same Color :roll: It truly varies from screen to screen unfortunately. NTSC color burst interpretation seems to be more of a suggestion than an exact science. Ah, the good 'ol days. I have a TV where some of the purples ($03 / $13 / $23) are clearly blue. Except composite video isn...

Jacobson wrote: ↑

Tue Sep 01, 2020 7:52 pm

Then do you want to ban me from logging in?

Potentially.

Señor Ventura wrote: ↑

Tue Sep 01, 2020 9:57 am

although it seems to be due an error in the source code, or something like that.

Or potentially their destination code.

Literal values does not mean immediate values. It's telling you the format of using direct numbers vs something like labels - not the addressing mode.

You can detect changes and silently alter the gameplay, like Earthbound did . To make it harder to modify the code you could store it encrypted and only decrypt it in small blocks at runtime, while also using the encrypted code as data. ( related ) This. While it's kind of a pain to setup, it needs...

However like the VICII, are the PPUs the clock masters. So if you switch the PPU to "50hz", does this also modify the clock speeds to be PAL or does the PPU run "50hz" timings, for vblank, hblank, active display etc off the NTSC Master clock? Or does it drop to PAL Master Clock. In typical hardware...

DRW wrote: ↑

Sat Aug 22, 2020 8:49 am

And that's all I have to say about it.

You still completely miss the point. Wow. hahah.

The issue is the VBlank time. NTSC has this tiny small useless VBlank period. While PAL has basically double the VBlank this means we can DMA an entire frame to VRAM in 1 Vblank, so we don't have to double buffer VRAM. So while we could run it on NTSC and say its 3 frames on pal, it would drop to 4...

Assigning an INT to a CHAR should always be a warning (enums are INTs). Just because you can, doesn't mean you should. If we're talking about variables, then yes, you're right: Always use an explicit cast when converting from larger to smaller. But we're talking about constants here. Compile-time v...

Not only is that bad form (and that should generate a warning) Why should it be bad form? And which compiler ever created a warning here? Having auto-incrementing values can be quite useful, even if you don't have a dedicated type for the enums. Assigning an INT to a CHAR should always be a warning...

But it won't hurt your performance if you do this: enum { A, B, C }; unsigned char MyVariable = A; Not only is that bad form (and that should generate a warning), but It will technically hurt performance if you do something like if (myVariable == A) as CC65 like most compilers auto promotes to INT ...

https://github.com/ilmenit/CC65-Advanced-Optimizations Can anybody tell those authors that even if you don't want to use enum types, there's still no reason to replace the comfortable, automatically-incrementing enum constants with manual defines? What exactly are you going to use instead then? If ...

Why not "CHR MEM" and "PRG MEM" and then have a side note saying what's available as options for those.

If I may, I want to use this opportunity to complain about PCEAS non-standard syntax. I was bothered so much by its use of brackets for [indirect] addressing, that I started working on a PCE-specific fork of ASM6 just so that I could stick to what I'm used to. I should get back to that at some poin...

The MD version got lucky for the simple fact that the MD uses linear pixels instead of planar. Interesting, Where can i read about this and its differences?. I know about the chunky tiles although i don't know how it works exactly. Do linear pixels are related to chunky tiles?. I'm sure you'll find...