Emulator Coder, Experienced Forum User, Published Author, Skilled player
(1301)
Joined: 12/21/2004
Posts: 2687
For game versions, NTSC generally means "USA or Japan", so either USA or Japan would be better, as it's more specific than NTSC, unless the game in question is actually a combined "(JU)" type ROM.
Emulator Coder, Experienced Forum User, Published Author, Skilled player
(1301)
Joined: 12/21/2004
Posts: 2687
VBAlink made tons of changes, so don't expect a small update to integrate link support into re-recording VBA. It might be easier to apply it the other way around, actually, but either way it won't be simple to do or likely to happen soon.
Emulator Coder, Experienced Forum User, Published Author, Skilled player
(1301)
Joined: 12/21/2004
Posts: 2687
Look a few posts above... Somebody just said that the Pokémon will start to evolve after you get to the end credits (which apparently is only halfway through the game).
Emulator Coder, Experienced Forum User, Published Author, Skilled player
(1301)
Joined: 12/21/2004
Posts: 2687
Now that is odd, because www. is not part of the domain name, and I get a 404 if (and only if) I add that.
BoltR: Your Mario Paint movie seems to have been taken down, and I haven't seen it, and wonder if my movie is faster... probably not, because I wasn't actually aiming for fastest time, just a "pretty fast" playthrough of the first level without luck manipulation.
(I would be more concerned about filling this thread with off-topic posts, but I don't see what other good could come of a thread about pointless things to do.)
Emulator Coder, Experienced Forum User, Published Author, Skilled player
(1301)
Joined: 12/21/2004
Posts: 2687
Not to belabor this too much, but... Something must have been wrong with that spindash, it doesn't lose speed anywhere near that quickly. There was enough speed left to jump up and slam into the ceiling, which is more than enough height to continue onto that ledge. Definitely no need to do 2 spindashes there.
Emulator Coder, Experienced Forum User, Published Author, Skilled player
(1301)
Joined: 12/21/2004
Posts: 2687
Because the update to 1.5 emulation-wise was major and didn't receive enough testing, so while it fixed a lot of bugs, a lot of other games broke or became very screwed up (Mortal Kombat II, Wild Guns, Super Star Wars, Pilotwings, Super Off-Road The Baja, among others). Also a few things like cheat codes and multiple-joystick controls broke in the port. So I recommend not using version 1.5 for making movies and don't think it's worth supporting that version at this site.
However, all of the above problems have since been fixed, so whenever 1.51 is released, I think we should begin using that as the preferred snes9x version for making new movies.
Pro: Emulates more games and emulates existing games better
Pro: Can record SuperScope, Mouse, and Justifier input, and can record resets
Pro: More features (better cheat search and RAM watch, more graphics filters, less AVI problems, etc.)
Pro: Is being tested for all platforms (at least Windows, Mac, Linux; movies should be compatible between the three, except in cases of unreliable-playback movies)
Con: Can't play any movies made in previous versions of Snes9x (way too many core emulation changes for that to be remotely possible; just use an older version to play existing movies)
Con: While it's more accurate, it's also slower due to less shortcuts being taken and abandonment of some old but fast parts of the emulation code. Won't matter much unless your CPU is really outdated.
EDIT: I'm now having doubts that people here would choose to use this newer version, because the more accurate emulation causes games to load significantly slower, in actual frames. Nevertheless, for games that use peripherals or don't have an existing run to compare with, it would still make sense to use this version.
Emulator Coder, Experienced Forum User, Published Author, Skilled player
(1301)
Joined: 12/21/2004
Posts: 2687
It is "spiffied up". Moreso than the current TAS version, in fact (it's an upgrade of that). And it does play Doomsday Warrior; I checked.
If you really can't stand to download more than one thing, then OK, just wait...
Emulator Coder, Experienced Forum User, Published Author, Skilled player
(1301)
Joined: 12/21/2004
Posts: 2687
It wouldn't work too well to get the description from the posts this time. Well, someone could pick any bunch of posts in this thread and string them together to get an awfully funny description...
I liked the "Totally rad? More like totally unfair!" part.
Emulator Coder, Experienced Forum User, Published Author, Skilled player
(1301)
Joined: 12/21/2004
Posts: 2687
I was only warning you not to do that rhino glitch. I found a way to get much further up the castle with it than in that video, and at some point transform into a zombified Dixie, but if the whole thing relies on an emulator bug then it should not go into the run. Until a later version of the emulator has been released that has the bug fixed, at which point you can see if it's really possible to do without crashing the game.
Emulator Coder, Experienced Forum User, Published Author, Skilled player
(1301)
Joined: 12/21/2004
Posts: 2687
Are you watching your versions together when making the movie? If you leave the previous one paused in another window and periodically advance it to sync up with your new one being recorded, you can check that you're never losing any frames to it. (And I would keep another window open for comparing with the Any% run wherever it's applicable.)
Emulator Coder, Experienced Forum User, Published Author, Skilled player
(1301)
Joined: 12/21/2004
Posts: 2687
I was tempted to (but didn't) vote No just because of the humor factor of those last two posts, but... what's going on with these votes? Is someone picking random votes on random submissions?
Emulator Coder, Experienced Forum User, Published Author, Skilled player
(1301)
Joined: 12/21/2004
Posts: 2687
There seems to be a problem with the video scaling.... Here is the sort of output I get for 640x480 -> 320x240 (Mario 64 title screen):
The smaller the scaling should be, the more pieces of a smaller segment of the screen are repeated, and (because the height is less) the closer it is to the bottom.
Emulator Coder, Experienced Forum User, Published Author, Skilled player
(1301)
Joined: 12/21/2004
Posts: 2687
There were some other warnings that were disabled because they would happen almost all the time in some games... Probably should add some options to enable them, if not fix the issues behind them.
One bug that hasn't been tracked down is that sometimes when you load a savestate, it will think a different button is being pressed than what you were pressing when you made the savestate (it won't show it in the input display or record it in the movie, but the game will act like you pressed it). So keep that in mind when loading a savestate. If the cursor starts moving before you thought you told it to, or something like that, it could be that bug happening.
3 buttons vs. 6 buttons: I don't think it matters at all.
Emulator Coder, Experienced Forum User, Published Author, Skilled player
(1301)
Joined: 12/21/2004
Posts: 2687
I forgot to post about this before:
When I played back that movie with debugging on, Snes9x actually crashed. It's an emulator bug; the game is supposed to freeze and stop instead of letting you zoom straight up the castle. It might be possible to do it a certain way to get similar results, but on the current version of Snes9x you cannot be sure that what you are seeing is really what the emulation is supposed to be doing. In case anyone is thinking about trying that trick... [I am saying, don't even try it yet because it probably shouldn't happen.]
Emulator Coder, Experienced Forum User, Published Author, Skilled player
(1301)
Joined: 12/21/2004
Posts: 2687
For SMB3 it is probably possible to "port" a NES run to SNES if all you want is prettier graphics. It would take some effort though, editing in a delay at every transition sequence and deleting a frame wherever the NES version lags (which normally only happens every 9 minutes or so, but not always).