View Full Version : Jnes Known Glitches

April 11th, 2002, 18:32
Ok, there are many i know.. the ones that really annoy me are

Rad Racer [All versions] (Gfx Prob)
Rad Racer 2 [All versions] (Gfx Prob)
Cobra Triangle [All versions] (Gfx Prob)

Just thought i'd let you know.

Thanks for continuing this Great Nes Emu!

April 11th, 2002, 21:27
Alrighty, sounds good, didn't know there were that many in RadRacer, last time I checked it worked rather well with the exception of a few glitches <?> on the track ...

If you have any others let me know

April 12th, 2002, 06:33
Glad To Help, Ill let you know :)

April 17th, 2002, 06:48
umm.. some mappers like the ones to play Dragonball Z games and some other (j) games aren't supported. They tend to crash the emulator..

April 18th, 2002, 01:55
That's actually a known issue, I simply just don't really care much about those games truth be told. Perhaps in the future I should look into again, I know there are tons of people who like DBZ stuff. It should just setup an unsupported error text message, shouldn't crash perse

April 18th, 2002, 15:15
yeah , guess so lol

May 16th, 2002, 20:40

i have just recently downloaded jnes and i went to use it and all it did was bring up a giant black screen when i tried loading a game???

help please


May 20th, 2002, 00:53
Check the default video setting. It's probably on fullscreen mode.
Options | Video | (choose anything in Window).
I usually use the second option here.

On an unrelated note to Jabo:
I'm having some odd glitch with any rom I load. Whenever I open a rom, the following error happens:

JNES caused an invalid page fault in module JNES.EXE at 015f:00401239. Registers:
EAX=00000000 CS=015f EIP=00401239 EFLGS=00010297
EBX=00000000 SS=0167 ESP=006ef5b8 EBP=006ef854
ECX=004b2994 DS=0167 ESI=00000000 FS=3aaf
EDX=00000000 ES=0167 EDI=0042c140 GS=0000
Bytes at CS:EIP:
88 1c 30 89 51 a4 88 91 4c ff ff ff 7c cb 5e 5b
Stack dump:
006ef601 00000000 00404577 0042c140 006ef601 004048cd 00000111 0040ec78 0040b8d7 00000001 00009e35 006efb28 70014022 1a53454e 00420020 00000000

While this may look like gibberish, is there any way I can work around the page fault?

May 20th, 2002, 06:20
There is no mapper for it, read above