I don't know exactly why, but I have never liked that song.
I also detest S&G's lyrical butchering of El Condor Pasa. "I'd rather be a hammer than a nail"? WTF?
Your video, Sylvian joululaulu , may include content that is owned or administered by this entity:
Entity: Music Publishing Rights Collecting Society Content Type: Musical Composition
The authors of the song in question have been dead for over a hundred years. (More precisely, they died in 1871 and 1898).
Btw, I just love the name of that company: "Music Publishing Rights Collecting Society". It sounds very similar to "patent troll".
If hard resets are allowed then i don't see why opening the disc tray wouldn't be allowed.
Agreed.
Then perhaps we shouldn't allow hard resets either... ;)
Anyways, let me give you a good reason why resets and opening the disc tray are not comparable: A reset can be emulated at frame-perfect accuracy, while opening the disc tray, which produces a mechanical action, cannot.
The speed at which the physical disc tray moves is non-deterministic, independent of the CPU or any other timed hardware, and may depend on the individual console (the speed might vary by several frames between consoles, and even from ejection to ejection within the same console, especially if it's done often; it may also depend on the age of the console, as the physical components involved degrade physically).
An emulator can guesstimate the delay when opening and closing the disc tray, but it will most probably not correspond to the delay in a real console (measured in frames). How much should the delay be? If this were an option in the emulator (ie. there was an option where you can set how long the emulated delay of opening and closing the disc tray is), it's then up to the author to set it. To what value should he set it? If he sets it to too small of a value (eg. 0 seconds) that's tantamount to cheating. No different from speeding up the CPU.
So should we allow disc tray opening and closing in TASes? Definitely not.
If hard resets are allowed then i don't see why opening the disc tray wouldn't be allowed.
I agree - I think that if we allow a player to arbitrarily hit the reset button during a TAS, then we should allow the disc tray to be arbitrarily ejected. As far as I'm concerned, while playing, you can arbitrarily rip the game out of the console, drop it in orange juice, and then put it back in (arbitrarily), if that gets you to end sooner.
In theory, if you had god-like powers in real life (the ones that would be required to play a game perfectly), you could scratch the game disc just in the right places so that reading the FMVs would cause reading errors, possibly causing FFIX to skip them. This can perfectly well be emulated (simply make the emulator emulate reading errors at certain parts of the disc image).
However, that doesn't constitute playing the game. That's hardware abuse at its finest.
I don't see all that much difference with ejecting the disc, really. Rather than scratching the disc just on the right places, you are simply disallowing the machine from reading the disc at the right places by ejecting it. It sounds to me like the same type of hardware abuse. I want to see the game pwned via gameplay, not via kicking the console and dropping it on the floor.
HAHAH you really expected me to watch half an hour of this BS?
Could someone post a short summary? I know it probably won't convey the same emotional feelings as this video probably does, but it would still be nice to know what the message of the video is and not have to spend 30 minutes to get it.
Are you suggesting there is something wrong with death-warps or reset-warps?
I don't understand what dying in a game has to do with hardware abuse. As for pressing the reset button, if it were up to me, it would not be included in the list of allowed input (with the possible exception that some individual game has it as gimmick, ie you cannot proceed in the game unless you reset; this possible exception would definitely not set a precedent). Resetting is not playing the game.
What about pressing opposing directions?
If the rule is that only certain buttons are allowed as input to the game, then it would be up to discussion whether some combinations of buttons should be disallowed.
I doubt newer version of phpBB will solve the issue if it still ties viewing to sessions. We're currently having an issue with MySQL which affects PHP sessions which I doubt has little to actually do with the version of phpBB.
Is there anything on the client side that can be done to alleviate the problem, or is it purely a question of server issues?
I am repeating myself a bit here, and I'm a bit venting my frustration, so I apologize. But...
Now that the site has been regularly experiencing connectivity issues it sometimes happens that it logs you out for some reason. The extremely, extremely annoying "feature" of the current forum software that if you log out it will mark all topics read (I don't know if this is intentional or a bug, or something else) can be really frustrating. Dozens and dozens of unread posts, gone. *puf* Then you have to just try to guess in which threads there might be posts you missed.
Any plans to even try to upgrade to a newer version of phpbb (where I assume most bugs have been fixed)?
If it were up to me, TASing would be just about playing the game, not about abusing the hardware. No sending reset signals to the CPU, no cutting power, no ejecting disks in the middle of the game, no modifying RAM with external devices, nothing. The only allowed input is the basic controller buttons and nothing else, the set of allowed buttons being tightly defined on console-by-console basis. (I might even go so far as to dictate that the TAS should not use the game's saving feature unless there's an extremely good reason for that. Abusing hardware is not such a reason.)
Of course it's not up to me, so this is completely moot. I apologize.
If that's all it takes, then gamegenie and other such cheating can also be done with hardware, so let's just use some code that skips directly to the end of the game and be done with it. We could probably do this with all games (at least for the older consoles). When every TAS is a few frames long, perfection has been achieved. We can shut down the site as needless.
i don't have a favorite smartphone game because i don't like to carry around a tracking device in my pocket that the government uses to track my every move.
Yeah, the government is very interested in your every move.
Knowing the language itself is not as important as having experience at programming (and, when speaking about Java, programming in imperative and object-oriented languages). Of course knowing the language itself thoroughly helps a lot (so that you know how things should be done with that particular language, what are the efficient and the inefficient ways of doing things in that language and so on), but programming experience in general moreso.
When I get back, I intend to move the (J) rule to guidelines.
Perhaps retain in the rules at least something like: "If the (U) and (J) versions of the game would result in practically the same TAS (in terms of completion time), the (U) version should be preferred."
Troll 2 is the most utterly confusing movie I've ever seen. It's not just epically bad, it looks like the entire crew has been drugged, because clearly nobody there even understands what they're doing.
Apparently the director, who also wrote the script, was not fluent in English, and consequently all the dialogue was completely broken English. The cast, most of which consisted of native speakers, offered to deliver the lines in proper English, but seemingly the director insisted that they be delivered as written.
It would seem it gives the impression that it's okay to break the rules at will to get a faster time, so long as it's a popular game and/or one's a well-known TASer.
Which rule exactly is being broken here? As far as I can see, using the J version when there exists a U version is not forbidden, simply not preferred. The J version being faster because of faster text speed could be considered to be mentioned in the rules as a bad reason (as "a shorter text"), but it still doesn't forbid it. It simply says that it's usually a bad reason to use the J version.
Choosing the J version because of faster text might go against the recommendations of the rules, but it doesn't break them.
I think a good question would be: Should the rules be loosened a bit for cases where the J version provides a considerable time saving because of text speed, especially if subtitles are provided separately?
10. Manos the Hands of Fate
9. Hobgoblins 2
8. The Amazing Colossal Man
7. Child's Bride
6. The Viking Women and The Sea Serpent
5. The Creeping Terror
4. The Conqueror
3. Puma Man
2. The Beast of Yucca Flats
1. Mommie Dearest
You are clearly not being serious. That's quite evident because of the lack of Troll 2, the best movie ever made.
