fairness or providing motivation to the author is not mentioned in the judging guidelines. Votes are not meant to show author appreciation, but to judge the movie. To judge just the movie, not the amount of work that went into it or the issues associated with production - because the movie is what'll be sitting on the published movies page.
If someone feels that this run does not deserve the yes vote because it's improvable (sloppy playing on the first parts, shortcuts not taken, ..), and would rather wait for an improved run before publishing, that's perfectly fine with me, and I don't see any reason to argue against that.
Given that Dacicus spent time to encode some avis of the WIPs, I'm sure he appreciates Guano's work, and Guano knows that already. No need to emphasize that by a vote that's meant for different things.
The universe requires me to download a plugin I don't have and that's not available for my operating system.
so, your theory is that the universe is evil and doesn't like me?
You can make a calculation vs. memory trade off, you don't need all 10^50 states in memory at once. If you can cut that down to by 10 orders of magnitude you're down to 48 554 118 149 334 kg.
if you just want to prove that it can be solved, you can discard a lot of game positions along the way. If you want it solved, you'll either need to store every position along with it's winning move(s) and formulate the winning strategy as "just find the current position in the archive and look up the winning move", or find a more generic strategy.
If we were somehow able to store information on the scale of a planck's length (a very long shot, used simply to illustrate, however, it is possible, because the energy of empty space is not zero)
care to tell me how you're going to read that data without destroying it? Or, write that data without destroying the data of nearby bits?
so, even if we keep up with increasing the memory density by 400.000 each 15 years, we'll get from 10^13 to 10^50 in about 120 years. That's definetly not in the timeframe Saturn mentioned.
Also, how are you going to store a whole chess-position as well as one of it's winning moves in just 1 byte? A computer with 10^50 bytes isn't enough, so expect further delay.
oh, and by the way. Even if you somehow managed to store one bit in each hydrogen atom, you'd need 8*10^50 atoms for the storage, which is
485 541 181 493 337 650 646 730 kg, or about 1/12th of Earth's mass.
Good luck.
I don't see the interest in decimating frames ; if the encoding codec is good enough, the compression between two consecutive equal frames will be perfect, ie the codec will compress the video at its maximum, whatever the framerate is... decimating frames will reduce size, but the gain would be minimal and the quality, inferior.
Have you (or any other encoder) actually tried to encode the same sequence at 20 fps and at 60 fps with the same quality, and compared the sizes? That'd give good numbers for proper judgement of the issue.
AzHP wrote:
It'd probably be really hard, considering cameras in 2d (just an x and y coordinate) are a lot easier to manipulate than cameras in 3d (x, y and z and also a direction vector)
the sonic camhack had one flaw: it required every frame to be calculated twice, and it required to save and load one savestate each frame.
try that with mupen, and the result will crawl slower than the guy who had his wheelchair stolen. There's also the bug with savestates sometimes causing desyncs, so having a lot of them won't do any good. Last but not least, the logic for this cam-hack would be more complex than the one for sonic: this one should change the camera only when backwalking. How should the hack decide whether the player is backwalking for a long way or just backing out of a battle for a couple of frames? sorry, but it's technically not feasible at the moment.
like CoolBumpty said: If you want an OoT-movie where you see what's going on, try one of TSA's older speedruns, they're good.
I don't see why it shouldn't. There have been other games that often desync, but still got published.
yeah, the delay is a little annoying, but IMHO that's not a reason to deny publication. After all, "WTF? I've never this on my console" is exactly the reaction we want to provoke ;)
I think it's ok to publish. The white-screen-issue can be explained in the movie description.
you're frequently noticing that you're misbehaving, and you even apologize, but you aren't even trying to change. Too bad.
This isn't the battlefield. There's no enemy behind the corner that could attack any moment - you don't have to rush your posts. Take your time to re-read your posts before submitting them (use the Preview-Button), and correct any spelling errors you find.
there are several reasons why implementing rerecording on pcsx2 is a bad idea at the moment. Rerecording needs more than just simple save states and input logging, it needs rock solid savestates, as well as host independant emulation, and I really doubt pcsx2 has either at the moment or in the near future.
Like someone said earlier, the white screen doesn't appear if you check "Copy framebuffer to RDRAM".
Like someone said earlier, this causes desyncs unless everyone has the exact same gfx board or there is a pure software gfx plugin.
and the only software gfx-plugin is still too beta to use.
it seems that you left your hower-boots equipped longer than needed. Should be avoided, as they slow you down.
other than that, looking good to me.
(thx NrgSpoon for the updated avis, I'll continue to seed them)
might as well link the original thread, instead of stealing the images from there and starting a new one..
(no, I won't search for the URL now)
edit: no, that link below me isn't the original thread either.
When Firefox cannot find a DNS address, it automatically tries again by putting www. in the front of the address.
wow, that's a "feature" nowadays?
anyway, while the DNS resolution isn't stable for me, I put this line into /etc/hosts
194.29.198.4 bisqwit.iki.fi tasvideos.org
What about a magic eye (sterogram) captcha? I doubt the computer could morph the image together and figure out which words/numbers are 3d.
actually, the computer should be able to do so with much more reliability than a human. I don't know if it's been done yet, but I'm pretty sure it's possible.
guessing the image is another matter, but here applies the same as to regular captchas:
- you either generate a random sequence of letters. OCR-software can read it as well, unless it's really scrambled - but scrambling on top of magic-eye will give humans a hard time registering
- you pick images, e.g. an outline of a horse to type "horse" into the field. Those images need to be stored on the server. If somebody manages to retrieve and manually label all of them, the captcha is broken. So, unless you wish to spend a couple of hours per day to replace the images, that won't help either.
basically, you'll have two choices to survive:
a) use a captcha that's not widespread enough, so nobody will bother to break it. Best is custom-made, replaced regularly. This offers about the same level of security as the bot-traps mentioned in the initial post, so I suggest spending your time on the non-annoying solutions.
b) get to the topic with much more knowledge about the matters than we do. Especially knowledge about the advances in image- and text-recognition are valuable. Sorry for the harsh words, but the concepts I've seen here were mostly wild ideas, maybe interesting, but ultimately worthless.
You need to find concepts where human and computer abilities differ. The trouble is, that a computer should be unable to know the solution, while it's still a computer that has to create the captcha and determine if the answer is correct.
That means, the most interesting tests for human behavior cannot be done, since a computer is unable to randomly generate them. Reliable tests could be
pictures of animals or other object groups, that need to be labelled
random words or images with the "what does not belong?"-question
a short story that has to be understood and summarized, or questions about it have to be answered (could be great for a forum, to check the ability for reading comprehension as well :p)
melodies you have to classify into genre (although computers get better at this, so it's probably not a good idea)
But as said, that's useless without random generation, as predefined questions can be answered from a database.
so, yeah, nobody read this far anyway, I'll stop here.
a dictionary attack on a scrambled word is easy, and even quite fast if the first and last letters are known. All a bot has to do is figure out which one is not an english word.
And even if you make sure to either have the password be a scrambled word as well, or to include spelling mistakes in the other words, this captcha still has a (1/(number of words))-chance of being guessed. Since you can't IP-ban on first attempt (you know, humans make mistakes as well), a bot has quite a chance to succeed.
Those Captchas you made have an advantage, because they're not widespread enough to be of interest. Unfortunately, I doubt their security, as most of the challenge can be removed by applying a trivial YUV-conversion and Y-Filter. Computers are much better at that than humans. The remaining false letters can be identified by splitting the image into distinct areas (simple flood-fill-like algorithm), calculating their sizes along the way, and picking the 6 largest. Recognizing the characters after they were split from the image can be done by cheap OCR technology.
The third one is a fresh idea, but once you got a basic OCR implementation, it's defeatable. Splitting the image into areas is quite easy, same goes for detecting their colors and text, and parsing a color name and a number from the instructions shouldn't be that difficult either.
Spam can't be tolerated, but if you spend that much time on a personal captcha, that time could also be spent on non-standard registration and post-forms with traps, or a system that'll prevent new users from creating posts that contain the same URL they put into their profile.
Last but not least, if the custom registration on this forum is bypassed, that probably was done by a human. An additional captcha wouldn't help there.
Tub, the generic strategy would be nice to hear, the optimal is one less than that though.
I thought so, because my strategy can handle up to 27 balls with 4 moves, not just 12. ;)
step 1: put 1/3rd of the balls left, 1/3rd right (equal amounts), leave the rest off the scale.
step 2:
- if they were equal, the oddball is in the last 3rd. Compare that last 3rd with an equal amount of normal balls, to find out if the oddball weights more or less.
- if they weren't equal, compare one of the sides against the last 3rd, that's known to be normal.
basically, after the first two steps, you have reduced the suspicious balls to 1/3rd, and you know if the oddball weights more or less.
step 3 onward:
put 1/3rd left, 1/3rd right, and you can reduce the amount of suspicious balls by 3 each step.
the number of moves for that strategy is:
ceil ( log3 n ) + 1
(for any amount > 3)
determining the relative weight of the oddball can probably be done without wasting a whole step. Unfortunately, the solution doesn't occur to me right now, but I'm currently just posting while waiting for my compiler. ;)
Find two steps that determine the relative weight and reduce the balls by 4 instead of 3, and you got your 12 balls in 3, 120 in 5.
however, you could create a 2-player-run on one game where the second controller is just a button-swapped version of the first. Like Contra III, with left/right swapped. Might be an interesting movie, and the relationship between both controllers is still visible.
@jimsfriend: accuracy gives more points in DDR, perfect accuracy isn't needed to hit the arrow though.
@topic:
the DDR-style input has a high probability of 'desyncing' - if you are off even a little when replicating the input sequence, the suggested input will become useless later. A fixed input sequence cannot react to different game situation.
I guess a skilled game player will be more succesful than a skilled DDR player in the end. It's a cute idea though :)
