From Vanishing Point Wiki
Jump to navigationJump to search


At the time of writing, is mainly a countdown timer and text entry box:


Typed out (so that Google can index), the text is:


[text box and submit button]

Come back when the countdown timer reaches the vanishing point.


The timer is counting down to 6:30PM on Jan 8th 2007 PST <ref></ref> and the text box accepts a number of Keys.



The keys have now been moved to their own page. Please be aware that the page may contain spoilers. If you enter an incorrect key, the following message is returned to you: Incorrect key. If you're stumped, try searching online for the tag "vanishingpoint" to see if other players have figured it out.

The following keys have been found on webpages or handed to bloggers (and one additional one was intuitively found by knowing how the other keys work and examining the block of ciphertext):


Decompiling Flash is always a controversial topic. In some cases, it will provide answers without doing the work to get those answers--thereby cheating players out of a solving experience. When a Flash file is written "correctly," it is just a GUI interface to a server-side component and does not reveal any secrets. Unfortunately, it is extremely difficult to determine what kind of Flash file it is until it has been decompiled. In the case of this Flash file, quite a lot of it is obfuscated, making most of the decompilation useless without a lot of extra work. Some of the modules indicate client-server communication, pointing to a "well written" Flash (i.e. one that decompiling doesn't reveal any secrets.) (Because of the work involved in further decompilation and the modules pointing to client/server communication, I am not going to take the decompilation any further. -Brian)

First of all, it looks like something is going to happen at The Bellagio. I'm assuming this will be revealed at the end of the countdown:


Reprinted as text for proper Google indexing:


Big things come in big packages:

January 8th, 6:30PM, Bellagio Fountains.

Second, the countdown looks like it is hitting a URL at 42 Entertainment for synchronization:

_constantPool "_global" "CountDownTimer" "homeurlparam" "homeUrl" "/now.asmx?WSDL" "webServicen" "mx" "services" "WebService" "" "thisCountDownTimer" "Date" "getFullYear" "MovieClip" "prototype" "CountDown" "objServicen" "ml" "sc" "mn" "hr" "dy" "mo" "yr" "ServerTime" "onResult" "returnSerial" "eventMillisecs" "timeToWaitMillisecs" "getTime" "localEventMillisecs" "correctionMillisecs" "onFault" "onEnterFrame" "remaining" " " "msecs" "launch" "gotoAndStop" "secs" "Math" "floor" "mins" "hours" "days" "toString" "length" "0" ":" "" "ASSetPropFlags"

This connection to 42 Entertainment appears to have been confirmed by Jordan Weisman during his session on ARGs at Dorkbot in Seattle