Search results

These are probably things worth posting in the NESemDev forum at NESdev :)

If it's out of warranty anyway you can open it up and see if one of the heatsinks is not properly on. If that is the case you should go buy some heat sink paste and put the heatsink back on properly.

That's odd... in my brief usage of 3.0.0 I never had the black lines.

FCEU does not autodetect PAL or NTSC roms, in fact I'm not sure there is a way to do that at all since the iNES format does not have a flag indicating 50/60hz operation. So, uh, I guess there needs to be a per-game option for that.

Quoted for fail.

It's a bug in certain versions of hardware SDL as far as I can tell.

2.0 to 2.1.1 direct works fine, and the version in the archive is what you want.

Right now, the fact that avatars are tall but not very wide means more chance of wasted space... the avatars can be tall enough that there is wasted vertical space on short posts, but currently avatars could be nearly doubled in width and still not affect the amount of available space.

Why are you guys so concerned about bandwidth? The size of each avatar is already limited to 10kb, and it's fine with me if that goes all the way down to 5kb so long as the pixel size is upped. The full original size of my current avatar was 5.22 KB and that's at a resolution way higher than...

No, it has about the same support as Linux does.

You forced me to destroy the artistry of my probably-originally-from-4chan avatar! Graaah! :D I could handle some cropping, but the amount of shrinking needed simply crushed my spirit or something.

Nah, actually I saw this in some other forum and found it awesome. Except the full version is awesome-er.

Why are avatars limited to 80px wide? That's stupidly small.

<-- House avatar demands tribute.

The Sega Saturn VDP1 :) It was a weird hack of a 2D sprite engine yes, but it had true texture mapping unlike the Playstation.

Yes the Saturn does have 3D hardware, and it's weird hardware that generates quads instead of triangles. :P

Palette file loading should be very easy, since those files are just a bunch of raw RGB values you load into whatever palette table the emulator is using. As an additional possibility, I found some code that dynamically generates the palette based on NTSC hue/tint/brightness... the code is in...

^^ Duke Nukem Forever screenshots and vids have been released too :)

Your example of "Normal" werty is this: QUOTE Modules loaded or compiled after the image is running , is poison . Make files and includes and etc etc are poison .. They do not work . They cause flood and bloat and doc's of 100's of pages . Forth has no docs nor manuals . You cant port s/w by...

Post it on the archive under programming utilities... I'm sure lots of people would enjoy having it available :)