Wow.
Hum, how does PAL differ? I recall these artifacts on PAL screens too (which is why it looks so awesome to me), but I have used too many badly-tuned TVs, ancient TVs (a ~210 scanline b&w TV for example), or pirate-nes-clones (which might actually output something resembling NTSC) to actually have something to say on PAL.
Nitsuja, is there a frame search feature in snes9x improvement v9? I looked around the menus and such but couldn't find anything resembling it.
If it isn't, do you think it would be too much trouble to add it to snes9x improvement?
I'm accually interested to see a PAL composite filter (I suspect that it'll be more clear than the NTSC one). Hopefully blargg makes a PAL composite filter. But yea, ZSNES and bsnes has it allready, and Snes9x dosen't.
I was just wondering if there was an option in Snes9x that will remove the on-screen text. Whenever I record an AVI movie, the text messages that appear on screen (such as "movie replay") are being recorded into the AVI which is kind of detracting. Is there anyway to get rid of that text?
Well I was able to dig around in the source files and found the right items to change so that 'Movie Replay' and 'Movie Ended' no longer display on-screen. Took me a LOT of time to figure out how to compile the source code, but good ol' ingenuity taught me how to compile it with MS Visual C++. (I had only compiled MAME previously which is pretty straightforward). :D
I hope this is the right place to ask...
Does anybody know if the format of the controller data in a SMV file still follows the description in the FAQ?
Eg. A and B seem to be swapped, haven't checked for the other keys yet.
The controller data's format as it appears in a hex editor is as follows:
0001 = Right
0002 = Left
0004 = Down
0008 = Up
0010 = Start
0020 = Select
0040 = Y
0080 = B
1000 = R
2000 = L
4000 = X
8000 = A
EDIT: Nevermind, I figured it out.
Bit0 = undefined?
Bit1 = undefined?
Bit2 = undefined?
Bit3 = undefined?
Bit4 = R
Bit5 = L
Bit6 = X
Bit7 = A
Bit8 = >
Bit9 = <
Bit10 = v
Bit11 = ^
Bit12 = S (Start)
Bit13 = s (Select)
Bit14 = Y
Bit15 = B
This new version is great, I love the instant display on load state. And Bisqwit+Angerfist showed the power of watching memory values, so I was pleasantly surprised to see this was already implemented in the latest improvement.
There is a slight bug/misfeature of watching memory locations though: setting the data type to signed is ignored in the watch, but works in the cheat search screen. This is a bit of a pain when monitoring things like velocity, where often the value is negative.
Overall though this watch stuff is really cool and I think will lead to high quality runs as well as saving everyone time, if only I found out about it before I got to the second to last level of Umihara Kawase ^^
I've bastardized a version 1.43+v7 snes9x. It compiles runs anything on the site, and can be used for AVI making, etc.
But since I'm often fiddling with it, and it's kinda messy and full of personal mods, I don't really have it up for permenant download. I'll tarball it on request though.
In the newest version there's a major bug when configuring input. It tends to configure many input at same time. It's pretty annoying.
Seriously, it happens when configuring joypad. I have 2 gamepad, one is Logitech Wingman and the other is Gravis Gamepad pro. Both have this problem, so it's snes9x that hates gamepad :P
Example of the problem:
If I configure Dn Left, for some "asshole" reasons, it also configures Dn Right.
So, who dares to defy Snes9x team by fixing this major bug? ;)
And here I thought it was my controller being a piece of crap.
It took me almost 20 minutes to configure the damned thing properly, because I had to constantly correct things. Half the time the button I wanted to map wouldn't even be changed, while another or two functions would be changed.
That definitely needs to be fixed, and since I've noticed a few other topics regarding it I won't make another, but it'd also be extremely helpful to be able to actually use the hotkeys mapped to the controller. As of now the emulator accepts the change, but the buttons still do nothing. I mainly want to use the L2 and R2 buttons for savestates.
A .cfg would be infinitely more useful for this stuff I would agree.
An unusual bug that just started happening to me today is this: any new movie I create isn't created in the same directory as snes9x if i specify no path, it's created on a completely different drive in a program folder (wtf?).
I wonder if it'd be possible to hack the snes9x source some more to make it use a config file vs registry, it'd be a ton easier to work with I'd imagine.
I just remembered a small bug in SNES9x improvement 9 regarding the memory watcher.
When using "Search For New Cheats" (under the Cheat menu), you can select the Data Type as Unsigned, Signed, or Hexadecimal, and in this menu, the changes work.
However, when using the "Watch" command on a variable (even when "signed" is selected), it will remain unsigned. For example, in Super Mario World, the variable for Mario's horizontal velocity is signed. However, when traveling left, the values will be in the high 200's (rather than the negative 40's and 50's), but only using the "Watch" command, not on the menu itself.
Not a huge deal, but I guess it should be at least pointed out for whenever a new version is done, as I'm guessing it wouldn't be a difficult fix.
<Swordless> Go hug a tree, you vegetarian (I bet you really are one)
By the way, it wouldn't be possible to like save what parts of the memory I was watching, because it's kinda tiring to re-enter 10 different codes everytime I'm working on a TAS. I havn't found a way to do so.
Hey all. I'm hoping someone can help with a compilation problem. Using MinGW/MSYS and the command "make -f makefile.mgw" I run into a problem. First, wsnes9x.cpp dies when ID_FILE_OPEN shows up(it doesn't seem to be declared anywhere). Adding it to resource.h fixes the error, but I don't know if it's the right solution or not.
Second, windres doesn't seem to like snes9x.rc. It complains about a syntax error on line 276. Unfortunately, I've never seen this type of code before, so I can't begin to find it.
Any ideas?
