Messages

It looks like 2.0 runs significantly slower than 1.2. for example, if you enter a time trial, and compare the game's timer with a stopwatch application, you should get something like this:



Turns out the time difference is about 6 seconds every 5 minutes. While I am unsure why exactly the game runs slower, I suspect it may have something to do with the framerate. When I was doing some sample video recording of version 2.0, I noticed that I would get a duplicate video frame once every 50 frames when recording at 30 fps (VVVVVV 1.2 has no duplicate frames at 30fps). I thought that perhaps the game was running at NTSC 29.97 fps but this only resulted in one duplicate frame every 54 frames. Then I noticed that under "nearest ms" heading of virtualdub (the capture program I use) there was an option of 29.41 fps, which incidentally enough seemed to be the exact framerate 2.0 was running at as my captures no longer had duplicate frames.

My hypothesis is that VVVVVV 2.0 runs the timer as if it were running at 30fps when in actuality it is running at 29.41 fps, thus causing a discrepancy in the timer. This correlates with observed data, as 29.41fps/30.00fps = .9801 and 306s(5min, 6s)/300s = .980.

So in fact version 2.0 is actually running at 98% the speed as version 1.2. while that doesn't seem much, the error really adds up over the course of a single play through.

Um... why do you still have 2.0? Terry released the 2.1 patch long ago.

Wow thats very strange.

I've found the issue. Its a minuscule rounding error due to the locked framerate on flash vs C++.

We never spotted it because Terry and our testers can finish most areas in about 30 seconds. :p

I'll fix that now.

Edit: Ok in game timers are now based on ticks and super duper accurate. Update goes live tonight.

I hate to nag, but it has been a month or so since this bug has been reported fixed, and we still haven't seen a new patch implementing it. Is the final release of 2.1(or whatever comes next) in the works, or is this bug fix never going to see the light of day?

Um... why do you still have 2.0? Terry released the 2.1 patch long ago.

I suppose i should have put 2.X as the behavior is the same in both 2.0 and 2.1.

It looks like 2.0 runs significantly slower than 1.2. for example, if you enter a time trial, and compare the game's timer with a stopwatch application, you should get something like this:



Turns out the time difference is about 6 seconds every 5 minutes. While I am unsure why exactly the game runs slower, I suspect it may have something to do with the framerate. When I was doing some sample video recording of version 2.0, I noticed that I would get a duplicate video frame once every 50 frames when recording at 30 fps (VVVVVV 1.2 has no duplicate frames at 30fps). I thought that perhaps the game was running at NTSC 29.97 fps but this only resulted in one duplicate frame every 54 frames. Then I noticed that under "nearest ms" heading of virtualdub (the capture program I use) there was an option of 29.41 fps, which incidentally enough seemed to be the exact framerate 2.0 was running at as my captures no longer had duplicate frames.

My hypothesis is that VVVVVV 2.0 runs the timer as if it were running at 30fps when in actuality it is running at 29.41 fps, thus causing a discrepancy in the timer. This correlates with observed data, as 29.41fps/30.00fps = .9801 and 306s(5min, 6s)/300s = .980.

So in fact version 2.0 is actually running at 98% the speed as version 1.2. while that doesn't seem much, the error really adds up over the course of a single play through.

This reminds me of a glitch that I found as well.

http://www.youtube.com/watch?v=TeW9Bfv1HSk

From what I can tell, this glitch allows you to save after most of the games variables have been cleared. The only thing that remains is your position, and the number of trinkets you have found. Keep in mind however, that if you use this glitch anywhere but the teleporter in Space Station 1, you will be unable to rescue Violet, or even complete the game.

How to reproduce this Glitch:
1) Save at a teleporter.
2) exit VVVVVV (Important: This glitch needs to be done from a cold start).
3) Load save, and press esc as soon as you can.
4) Choose to quit to menu.
5) If you did #3 right, you should be greeted with a black screen and "Game Saved" should appear.
6) You can still run around and flip, but when you are done, press esc again and you will go to the menu.
7) Voila! Your game save is reset, but your trinket count is not.

The biggest thing that you should note about the all-trinkets run, is that it is segmented, which means that I saved, and then loaded over and over until I got it right, which should make it considerably less unbeliveable. I can't possibly imagine going through in one contiguous play-through with that kind of perfection

Some of the more fun points to mention in the all-trinkets run, are where I abused saving in order get a faster time, like where I saved right before the cutscene with Violet in order to skip it by making the game think I had already watched it, as well as where I saved right after getting trinkets in order to skip the Trinket-get dialogue, as well as where I saved in the tower in order to make it so that when I loaded, the screen would be further along. There were some more glitches I found involving saving, but those just led to breaking the game in one way or another.

I figured I would resurrect this thread to post my times. 

Any%

http://www.youtube.com/watch?v=ctaRPXHJ3rU

100% (all trinkets)

(Obviously, I segmented this one considerably.)
http://www.youtube.com/watch?v=ctaRPXHJ3rU - Part1
http://www.youtube.com/watch?v=OjWkQGRZLns - Part2

Still considering doing a segmented any%, don't ask me to do a no-death run, I've given up enough of my life already 

Also, I think one (or more) of the challenge questions is broken (What's the second word... 'the' is apparently not the correct answer). I hope you figure out a better way to thwart those spambots soon. Seriously, it took me 5 minutes to get a challenge question that wasn't broken