Joypad.get()
Snes9x.frameadvance()
Joypad.set()
snes9x.frameadvance()
Snes9x.frameadvance
Joypad.get
Joypad.set
Snes9x.frameadvance
DarkKobold: If you look at the pseudocode I posted above, you will probably see the cause of your problem. The lua main loop is called after the screen has been updated, but before the next frame has been emulated. So at this point, your script has access to the previous frame's state, but anything you draw will appear the next frame, and thus effectively lag one frame. To avoid this problem, you can use the other lua hooks. Afteremulation, for example.
Yeah, please don't be like symbolic pixel go rain. No need to change it just to match irc... you'll still be the loudmouth with a nick starting Fl on both :D
a little bad design in the game that it allows you to outrun the screen. it would be nice to see what's going on. must have been harder to TAS too because you can't see what you're doing. funny how you can beat this in two minutes, i remember it took me hours to beat 16 years ago. i'd like to see someone make a TAS with grant instead of the raptor, that would be a little longer.
BackTrack = savestate.create();
while true do
savestate.save(BackTrack);
x = memory.readword(0x7e0b1d)
y = memory.readword(0x7e0ff9)
memory.writeword(0x7e1a62,x-0x80)
memory.writeword(0x7e1a4c,0-y+0x6f87)
gui.text(10,10,"" .. x)
gui.text(10,20,"" .. y)
snes9x.frameadvance()
keys = joypad.get(1);
savestate.load(BackTrack);
joypad.set(1,keys);
gui.text(10,50,"Don't Touch Joypad!");
snes9x.frameadvance(); --replace with snes9x.emulateframeinvisible() if it becomes available
endI think most of your confusion and questions would be cured by picking any of our rerecording emulators and spending 5 minutes messing with a lua script.
I never meant for this to be grounds for preventing publication; the run should definitely be published. However, it should not be published with "plays on hardest difficulty" as one of the criteria. A super run which beats the game in a similar amount of time should be able to obsolete this.
Another problem that I believe has cropped up is lack of accessibility for a method to quickly and easily share WIPs. For years, DeHackEd's microstorage was the default for showing off tricks and progress, however as new emulators have cropped up, so have new file formats, some of which aren't supported, and some are supported with limited functionality (i.e. lack of .m64 embedded savestates). One possible way to increase sharing of files and WIPs is to make an official script for use on the site, where a user has X amount of hard drive space to upload files, and they are stored in an accessible manner for others to view. I don't know how much allotted hard drive space comes with the current site hosting contract that we have, but even if it's 20 GB, that allows for nearly 7 MB of space per user to utilize to share their collection of files. Or, limit uploading to those users who have posted within the past year, and the allotted amount would grow greatly.
I'm having a bit of problems with LUA feature. One is, what happen to LUA? I liked old way when I could click "run script", browse for script, then click ok, and click "stop script" when done from FILE dropdown. This new one, have to click "new lua window" then some giant window box blocking fceu game screen, click browse, choose script, click ok, then click "run", click minimize, more clicking here. Oh boy it look like I'm complaining here, I'm not, LUA works just fine, I'm just asking for those feature return. Put "run script", "reset script", and "stop script" below the "Close All Script Windows". Second is, are those on-screen lua aligned correctly? It look like stuff on screen shifted down by 8 pixel or so (or are those script outdated?)
Heck, if adelikat and Tompa weren't so crazy, we'd probably have done the same with Bubble Bobble. Old movie, relatively boring, painfully unoptimized... yeah. We'd have found an excuse. Publishing the new Bubble Bobble run felt awesome because of these reasons. I think everyone else who worked on that run can agree that the motivation to finish that huge project just wouldn't have been the same if we could have instead just taken down the old run and said that it "doesn't count anymore"