I have an honest question: Why did you use FBA-RR 0.0.2 in the first place when a newer version is available (where you don't have to use an older version of the Neo-Geo BIOS)?
Easy, by two reasons, first because I like playing in simple emulators, second because the successor versions don't have slow-motion enabled to TASing.
Why mz decided to disable slow-mo (and speed-up, for that matter) in later versions of FBA-RR, I have no idea.
Thanks for your answer, anyway.
EDIT: Except that FBA-RR 0.0.3.03 also supports slow-mo/speed-up, but uses the new(?) Neo-Geo BIOS.
If someone try to run by another fba version it don't sync, fba v0.2 probably is the only emulator which uses old bios.
I have an honest question: Why did you use FBA-RR 0.0.2 in the first place when a newer version is available (where you don't have to use an older version of the Neo-Geo BIOS)?
Oh, it appears you actually used Snes9X 1.51. Nevermind me for assuming you did it on 1.43 (I actually was confused about the bizarre emulator version, so I assumed it was 1.43).
So....apologies for that.
Just change the movie status (just below "Extra edit privileges") to "decision: cancelled".
Furthermore, if you wish to upload WIPs or ILs or whatever, have a nice link to the userfiles (the upload form is at the very bottom of the page).
(pardon the harsh tone in my posts, by the way, it's just that I very much favour emulation accuracy)
By the way, if you run this game on console, you probably know that Snes9X 1.43 is a very inaccurate emulator (nevermind the fact it's 12 years old) and that you should've probably used either lsnes or BizHawk instead.
(as a side note, Snes9X 1.43 is banned from SpeedRunsLive)
"Emulator used: Snes9X 1.4.0.0"
1) Snes9X 1.4.0.0 doesn't exist.
2) You probably used Snes9X 1.43, which isn't accepted at all.
3) You just played one level, which also isn't acceptable.
Dumping it, as we speak....and praying that:
1) The run doesn't actually desync now.
2) I don't run out of HDD space.
EDIT: Status update:
I'm past the Boolossus fight.
EDIT 2: Another status update:
I'm at Bowser/King Boo. Time to pray for real.
EDIT 3: Last status update:
It synced....and now I need sleep (it was 12:18 AM my time when I wrote this... and I went to bed at 12:50 AM, since the dump wasn't done at the time).
Let the fun begin.
Short answer: No.
Long answer: I don't see the need for such an area. Encodes are done when the encoder has the spare time to do one. Not to mention that constantly asking for encodes (be it in such an area (which, as I mentioned, I don't see the need for) on in the game/submission thread) isn't exactly the best idea (there has been at least one precedent). Just be patient, someone will eventually make one.
The Return of Ishtar is the sequel to The Tower of Druaga. It is an action game with light puzzle-solving elements that requires two players. One person is in control of the maiden Ki who fights with magic and the other controls Gil, the sword-wielding knight. Search for keys and special items. The tower has a few different ways to exit, and the aggregate total of levels is 128.
Game overs are pretty much a no-go in my book (as it would be similar to feed fictive coins ad infinitum (there's a precedent, also stated in the Movie Rules)), and since both Ki and Gil only have one shared life (if either dies, it's game over)...this rules out deaths at all.Disregard this for now.
As of now, this is purely in idea phase. In the meantime, check out the StrategyWiki walkthrough of the game, with detailed comments on the rooms and maps. Routing is going to be the key to the fastest route.
This used to be in the PSX games sub-forum, as back then, MAME-rr TASes were not allowed on the site (and FBA-rr does not support the game at all), and thus the only possible way was to TAS on the Namco Museum Volume 4 compilation release on PS1, which contains a reprogrammed a version of the Arcade original. However, things have since changed and not only is MAME-rr accepted now, but MAMEhawk is also a thing now alongside MAME via libTAS.
You should just use Jabo 1.6.1 (or jabo overall) this is the best video plugin
Jabo is objectively one of the worst graphics plugins, with many graphics issues (not only in this game, but in many other games).
Anyway, Weegeechan, try the regular Glide64 (I'm going to test in the meantime which setting fixes the issue you're having).
EDIT: Try setting the buffer swapping method to "New" in the Glide64mk2 settings. That fixed it for me. (uncheck "Use defaults for current game" first)
I'm only able to publish 384x224 screenshots, since the site expects Arcade screenshots to be 384x224. Therefore, I added transparent borders left and right, since it'd look really ugly when stretched to 384x224.
Only the admins and the senior publisher can override this limitation.
If anyone wonders why the sound effect when selecting characters is higher pitched, blame FBA. It was caused by the savestate mamuuuut provided to me that I used. (mamuuuut's savestate was done at a sample rate of 22050 Hz, while I was at 48000 Hz).
It was also a notorious bitch to get to sync, even with the savestate he provided to me. Not to mention the emulator crashed at least 50 times (and that's probably not even an exaggeration) while trying to dump the movie to AVI (or even loading the savestate).
According to the Touhou TASer kopiapoa, this TAS isn't great.
He commented on the TAS just now, basically saying that you shouldn't bother watching it (note: I used Google Translate).
Some things I'm already iffy about:
1) You did the TAS in 6 hours, which is horrifically short.
2) "Re-record count: (unknown)", basically meaning you didn't use savestates and only used slowdown and/or frame advance, which just isn't enough.
3) I personally don't think speedrunning these kinds of games is interesting. You should aim for score runs instead, like this run (by kopiapoa, incidentally):
Link to video
EDIT: Also, you TASed on the unofficial English translation.
EDIT 2: Did you seriously try to load your replay? That's never going to work, unless you provide it.
For the record, to anyone else, this is what happens as of now:
Game loads -> goes to Replay -> selects Replay #13 -> let time pass -> closes game.
