Hello again klmz. I would like to report a bug in VBA-v24-alpha. Apparrently, games that require motion sensing like Kirby Tilt 'n' Tumble don't work because motion sensing doesn't work.
Not surprised... motion sensing has been broken for a very long time AFAIK. It is planned to be fixed in v25.
EDIT: Other broken stuff:
* Frame Search.
* V-Sync (it has never worked right anyway, though).
* Full-screen with OpenGL and maybe D3D.
<klmz> it reminds me of that people used to keep quoting adelikat's IRC statements in the old good days
<adelikat> no doubt
<adelikat> klmz, they still do
<klmz> it reminds me of that people used to keep quoting adelikat's IRC statements in the old good days
<adelikat> no doubt
<adelikat> klmz, they still do
I think it would be more convenient if a publication entry could tells whether the movie file could be watched with the latest and/or most used versions of the emulator, though that would definitely increase the workload of our Movie Editors.
<klmz> it reminds me of that people used to keep quoting adelikat's IRC statements in the old good days
<adelikat> no doubt
<adelikat> klmz, they still do
Is all this means that... we may skip Snes9x 1.52 at all?
<klmz> it reminds me of that people used to keep quoting adelikat's IRC statements in the old good days
<adelikat> no doubt
<adelikat> klmz, they still do
I found it annoying to figure out which version of an emulator to use for watching a published movie from the input file at times. There have been some GBx movies with notes about the emulator versions, but wouldn't it be better to add a specific category/tag row noting the compatible emulator versions into the publication header?
<klmz> it reminds me of that people used to keep quoting adelikat's IRC statements in the old good days
<adelikat> no doubt
<adelikat> klmz, they still do
Help these members understand TASing, and how to submit videos to our site. Or how to submit WIPs. Perhaps offer to clarify feedback to them, or explain TASing terms which isn't covered by your standard English courses in school.
I surpose that the cultural problem is bigger than the language problem. That suggests that those people would be more likely to seek help from their native sources.
<klmz> it reminds me of that people used to keep quoting adelikat's IRC statements in the old good days
<adelikat> no doubt
<adelikat> klmz, they still do
...is not a proper name for branding, as it is the abbreviation of a popular vulgar phrase.
after the Neo Geo Pocket emulator named Rather Another Pokemon Emulator, no other branding seems innapropriate to me.
The fact that the ~3-year-old emulator is extremely obscure (only two results with Google for me) counters your opinion.
<klmz> it reminds me of that people used to keep quoting adelikat's IRC statements in the old good days
<adelikat> no doubt
<adelikat> klmz, they still do
<klmz> it reminds me of that people used to keep quoting adelikat's IRC statements in the old good days
<adelikat> no doubt
<adelikat> klmz, they still do
changes that came up:
1. JP ROM seems to be much faster at starting the game and has less lag in general, making me have to add in a lot of blank frames
2. JP's Grit's COP takes more time, probably due to the longer name, this doesn't affect the final in-game time because the game is smart enough not to count this screen
3. for some weird reason, JP ROM has 1 frame of lag less compared to US's right after attacking the first Neo
I might do the Campaign TAS using JP ROM, seeing as it apparently has less lag
The judge in charge then would tell that you chose the wrong version of the game and might try to reject the submission for that reason. You should instead tell everyone that the JP ROM has superior music/graphics, higher difficulty and/or tricks only available in this version.
<klmz> it reminds me of that people used to keep quoting adelikat's IRC statements in the old good days
<adelikat> no doubt
<adelikat> klmz, they still do
...is not a proper name for branding, as it is the abbreviation of a popular vulgar phrase.
<klmz> it reminds me of that people used to keep quoting adelikat's IRC statements in the old good days
<adelikat> no doubt
<adelikat> klmz, they still do
I prefer WowerGlass, seriously.
EDIT: logo idea (the rightmost one):
Yeah, I knew this could be drawn better :p
<klmz> it reminds me of that people used to keep quoting adelikat's IRC statements in the old good days
<adelikat> no doubt
<adelikat> klmz, they still do
030 4-byte unsigned long: string length of author name
Are you sure about this? Why did I get 512 with short strings?
That has been changed, all strings are now 512 to avoid having to mess with the entire header if you change author name. I will update the spec.
The problem (A.K.A. bug) is that the actual space allocated for the author string before the CD ids is smaller than 512 bytes.
<klmz> it reminds me of that people used to keep quoting adelikat's IRC statements in the old good days
<adelikat> no doubt
<adelikat> klmz, they still do
030 4-byte unsigned long: string length of author name
Are you sure about this? Why did I get 512 with short strings?
<klmz> it reminds me of that people used to keep quoting adelikat's IRC statements in the old good days
<adelikat> no doubt
<adelikat> klmz, they still do
Hi klmz! I'm not sure if you did this, but thanks for fixing a glitch that slowed down the game for no reason!
Yes, I did that.
jlun2 wrote:
Anyway, while using the revision linked above, it seems that it is hard to read the lag counter; when the movie is plagued with lag, the counter for gbx games becomes halfway offscreen. It would be nice if the lag counter could be made so that it would be displayed beneath/above the frame counter, like what DeSmuME does. It would be very nice this could be fixed.
MUGG wrote:
Okay, wanted to check something so I dug my VBA 24 out. Now half an hour later I feel like making a small rant post because the way the dropdown menu is looks inconvenient. All the menu elements being thrown around and re-arranged is also the main reason I refrained from getting newer VBA versions for a long time, and I still prefer using VBA 21 over 23.
It took me a while to find the hotkey config (in 'options>input'). Why is screenshot capture in tools and not in 'File'? What's auto convert? What's associate with savestates? I just think there's so much stuff I have no idea about and looks unnecessary.
It has been over one year since the last time I re-arrange old menu items (screenshot capture and hotkey config) IIRC. I made some that probably few people have been aware of e.g. while other contributors added some new features that also took some time for me to undestand their points. Perhaps a complete readme.txt or even a compiled/online help file is needed, but I'll explain to you those checkable options you mentioned (and one that probably nobody except a few was aware of):
* Tools->Movie->Auto Convert: Automatically upgrades the loaded movie from VBM ver 1.0 to 1.1 (VBA-RR v23+), according to the VBM hearder. A converted movie is back-compatible.
* Tools->Movie->Associate With Savestates: Stores on and loads from disk savestates with filenames like ROM_NAME-MOVIE_NAME-SLOT_ID.sgm instead of ROM_NAME-SLOT_ID.sgm. Perhaps this should be renamed and moved under Options->something.
* File->Current Slot->Show Timestamps: Shows when the existing savestates 1-10 was modified last time on all three submenus of loading/saving/selecting savestates. Perhaps this should be moved under Options->something.
MUGG wrote:
Next is a small bug report. I was playing playing Soulriver's TAS of Kirby's Dream Land 2 on VBA 21, then continued from it and noticed that autofire A doesn't press A every other frame but it basicly is like hold A... I checked on VBA 24 and it's still there...
Also, how have you been klmz? You seem to have become inactive. I'd wish to say there's no hurry to address the above problems immediately... just saying.
I haven't got much time recently since I've got busy in real life. There have been some major issues to resolve first. I'll take the proper time when I look into this bug.
And lastly, the status of v24:
* Problems that still exist in the latest SVN revision, if affecting GBx emulation timing, won't be fixed until v25 (expected to come in 2012).
EDIT: unless it's a very dumb mistake that must be corrected.
* It is still not decided whether to integrate/merge the GBA core from VBA-M (which was a fixed 1.8.x core) into/with v24. The BIOS part and GFX part have been done as they don't seem to affect old timing.... Well, the BIOS emulation does affect GBA timing, but the change seems to be either a matter of turning a frozen game (meaning no finished old movie showing this) into a playable game or just a matter of minor differences in timing that are neglectible (meaning old movies staying in sync).
* The format of savestates in the formal release might change and be made incompatible with any old version/revision! Proper diagnostic information would be given, though. (rationale: for TASers, safety > convenience, and not having done that was also why I had made a merged version but not made it public.)
Yes, I feel like hating to keep 3 branches of VBA-RR that have different timings.
<klmz> it reminds me of that people used to keep quoting adelikat's IRC statements in the old good days
<adelikat> no doubt
<adelikat> klmz, they still do
<klmz> it reminds me of that people used to keep quoting adelikat's IRC statements in the old good days
<adelikat> no doubt
<adelikat> klmz, they still do
Wow, I didn't expect anyone to be using the experimental versions of VBA for works aiming for publishing. Fortunately, the GBx emulation has been quite finalized in Rev 344. That is to say, this movie is supposed to sync with v24.
<klmz> it reminds me of that people used to keep quoting adelikat's IRC statements in the old good days
<adelikat> no doubt
<adelikat> klmz, they still do
<klmz> it reminds me of that people used to keep quoting adelikat's IRC statements in the old good days
<adelikat> no doubt
<adelikat> klmz, they still do
Why "XXX, The" instead of "The XXX"? No way to workaround the sorting problem?
<klmz> it reminds me of that people used to keep quoting adelikat's IRC statements in the old good days
<adelikat> no doubt
<adelikat> klmz, they still do
This somewhat resembles the case of the rejected Ninja Gaiden 2 submission by xipo. However there are some differences as mentioned in the preious posts.
The bigggest problem:
Not only was the camera work less entertainin but also was it more offending to those who had known what could have been expected to see.
<klmz> it reminds me of that people used to keep quoting adelikat's IRC statements in the old good days
<adelikat> no doubt
<adelikat> klmz, they still do
The freeze glitch in Drill Dozer has been fixed in the latest working copy of mine thanks to the fixed BIOS emulation code from VBA-M. I am unsure about if this fix could cause desync to any old GBA movie if I transplant this fix onto the v23 branch.
<klmz> it reminds me of that people used to keep quoting adelikat's IRC statements in the old good days
<adelikat> no doubt
<adelikat> klmz, they still do
This movie features the second worst camera control in all Super Mario 64 submissions. It appears as if the authors intended to prevent the watcher from seeing what was going on in the movie.
<klmz> it reminds me of that people used to keep quoting adelikat's IRC statements in the old good days
<adelikat> no doubt
<adelikat> klmz, they still do
Well, I can relate to that. There are times that I made simple mistakes that set me back by alot if I had to fix them, but I still went back to fix it. I suggest that you do, but its your choice.
It's not worth doing, as 1 second would be about 1/2700 of the length of the whole complete run.
EDIT: Still, I think I should finish the current WIP first.
<klmz> it reminds me of that people used to keep quoting adelikat's IRC statements in the old good days
<adelikat> no doubt
<adelikat> klmz, they still do
Basement done:
http://dehacked.2y.net/microstorage.php/info/795780881/sweethome-klmz-wip5.fm2
Unfortunately, I didn't realize until now that about 1 second should have been be saved if I had taken the Board in the main room on the second floor, and swapped the Blue (Flash-)Light with the Board in the dining room so that I could repick the BFL after the flying-away by Mistress Mamiya cutting off the detour at the beginning of the run in order to erase the Shadow on the first floor. Should I start this over again?
<klmz> it reminds me of that people used to keep quoting adelikat's IRC statements in the old good days
<adelikat> no doubt
<adelikat> klmz, they still do
I got a question. Why did you pick up the pickaxe, then without using it, swapped it with the FireX (Fire extinguisher)?
That was to place the Hammer there for later repicking it up and cracking down a wall in the long corridor with many bounders in it to reveal a secret passage. I didn't see you take it in your test run. Maybe you were unaware of it. Do you remember when you got next to the second bounder in that room, a "mysterious" dialog showed up? That was a hint by the game.
jlun2 wrote:
Otherwise, great run. Your "grind" sure seemed way less boring than mine. =D
And I think it was overall faster this way than to grind more before Lake and then use the escape-fight-and-row-back-as-single-man strategy.
Also note that I reserved >25 PP for Kazou to perform a Pray attack against Machete Man right before entering the Basement Area. I would have Asuka use the Potion/Tonic during the fight (much faster than to use it in the overworld).
<klmz> it reminds me of that people used to keep quoting adelikat's IRC statements in the old good days
<adelikat> no doubt
<adelikat> klmz, they still do
<klmz> it reminds me of that people used to keep quoting adelikat's IRC statements in the old good days
<adelikat> no doubt
<adelikat> klmz, they still do
Yeah, I knew this could be drawn better :p