How hard can it be to smash your keyboard and produce about twenty characters of noise? Just write the password down in a password manager application.
The only emulator that got the timing matching is missing something painfully obvious. The sword is missing at the four minute mark (and again at 8:40). That's a major accuracy failure.
RAII works badly with cyclic data structures. And those tend to occur when two object depend on each other. Which is very common, even in sane designs.
A plugin which 98 % (not a made up number) of the web has installed.
Also, you say that like it is a bad thing to depend on a plugin. I say that it depends on the audience and the content.
I think that you can do client side browser software in ActionScript 3 just fine.
I find it a good first language, since it doesn't bog you down with memory management, has an excellent graphical engine (unlike Java) and has classes.
Sure, the language has its fair share of idiosyncrasies, but it's nothing major. It's kinda like Java before it got generics and with a poorer standard container library.
You might want to read the Wiki: Ram Search article.
About hard mode, are you sure that it only affects minigames and does not have any subtle changes in the level layout? Things like additional enemies and what not. Those changes can be difficult to spot.
Are you using frame advance to carefully examine the collision response system and general physics? You really need to determinate exact values for things like character speeds, animation lengths and such. We are dealing with precision work here.
Finally, I am not going to compile your various tips for you, please collect them into one big text that I can review.[/wiki]
Give me a shout if you manage to write up something clear and concise that explains the tricks in the game. I can throw it up on the wiki for you, if I understand the text. I haven't played the game, so please include explanatory notes.
And please, test things with savestates and frame advance, we don't care about realtime results. Also, please include some ram watch addresses, there must be something useful there.
I say, just make a custom bootable hd image and preemptively cut out all the useless parts, like entering the command to start the game and any boot menus.
Your personal save is irrelevant, the emulator is not allowed to load it for the movie. The movie has to start from an empty state.
If your emulator doesn't automatically ignore save data when recording then you must move the existing save data to another location while working on the movie.
Of course, if you can present a clear need to start from saved data (like the game using unlocked content) then and only then can you use it. And if you do then you need a verification movie that creates the save.
Thing is, cameras in 3d space are more complicated than in 2d space. There are multiple possible representations, some aiming to avoid gimbal lock and some other variants just to make the math simpler. And then there are parameters like the field of view angle, as well as front and back culling planes.
And of course, there is things related to the camera movement, like inertia and camera control.