While what input method you use does affect how easy certain tricks are by a lot, I've never seen a leaderboard split up by what you used to play it. For example, on shmups forums, it doesn't matter if you used a pad, stick or keyboard to achieve your score, it's treated the same (although turbo on/off is a category for games where it matters, like Darius Gaiden). It's interesting to note of course, but ultimately you should learn the input method that's fastest for the game if you're seriously into it.
For the purpose of encoding or lua botting, would disabling graphics make it run faster? It still emulates it, but just doesn't show on screen (not sure if it makes sense).
I don't see what this has to do with CEN64 specifically.
lets say that this version of emulator emulates 100% and the only claim that one can make against it is "he uses a keyboard" or that you can't verify that he is playing legit since he is not seen actually play it.
would you guys say hes runs are legit?
You can never become 100% legitimate unless someone watched you play it live.
For example, you can take a TAS of an NES game and use a NESBot to play it back on real hardware and use a capture card to record that.
Remember, legitimacy, or likelihood a run is legit, is not a binary yes/no, it's a continuum.
Think about how ridiculously hard it is to make an N64 emulator.
Now imagine the same difficulty, except it's a different, rare console with even less documentation and almost no games or interest.
Why would anyone want to make an iQue emulator? It's extremely esoteric.
It’s not an issue of “too many keys”, it’s an issue of which keys you’re trying to press. I don’t know the specifics, but depending on what you’re trying to press at the same time it may or may not work. What I do with diagonal inputs is 7 = up+left 9 = up+right etc., I’ve binded those numpad numbers to the diagonal movements.
Every keyboard is built differently and with different combinations of keys that do/don't work based on the underlying design.
If you want to quickly test if holding down a lot of keys at once will work or not, open up notepad, (make a bunch of text if it's to do with arrow keys so you can see the result) then hold them all down and see if the last one registers immediately, or only if you let go of some keys.
I was rewatching this and wondered what 100% meant. Saving the game shows your %, right? Is this a 100%? Do they collect those boss medals that require you to beat them in a particular way (IIRC)? If not, then those don’t count towards 100%?
This is the YT vid description: “In this run, hellagels and red-crowned-crane collect all secret disks, life ups, BM upgrades and sub tanks, achieving a 100% completion rate.”. Is that what a 100% run is? I thought life ups didn’t matter…
I did not see your reply till now. I think it is quiet difficult to define 100% in this game, for the game do not show the %. Collecting medals, HP-recovering items and armors and completing missions can be count towards 100% in some way, perhaps it will double the movie length. Completing all missions sounds fun for me, I will do a run collecting medals, HP-recovering items and armors and completing missions if this movie ought to be rejected.
It's not going to get rejected now, no.
But if you made an 'even more 100%' TAS than the current 100% TAS, and it was just as high quality, it could obsolete this TAS.
The user of bizhawk may quite reasonably expect bizhawk to behave consistently among cores. The user of any software may quite reasonably expect to be in control of when changes are flushed to disk. Savestates dont appear without the user putting them there. Why should savefiles? Because the user indicated it to the game, OK I get it. That will work, right up to the point where it doesn't.
We'll probably add an option for all the cores at some point in the future, but I'm not sure what the default should be. I'd rather work harder on training the user to be in charge of things, instead of depending on mushly emulation metaphors and automagic.
The intuition of saving in a console is that you can turn the console off and on and the save file is still there.
For the emulator it's the same idea - you should be able to turn the emulator off and on and still have the save file be there. Except now there's a 'meta turn off and on', where you close and re-open the emulator entirely. Technically it's a different operation, but it intuitively feels the same as turning a console off and on.
Savestates are different because they don't exist on a console.
You need to record your normal playthrough and present to the audience as an input file when submitting your TAS.
In particular, it doesn't need to be a TAS, or even very fast, but it needs to be an input file that, when played back, results in the save data that you use for your TAS.
