Hacker News new | ask | show | jobs
by undershirt 5038 days ago
Hi, I'm the author. The framerate you see at the bottom right corner only indicates how often it is drawn. The game loop is actually sophisticated enough to keep the game updating at a solid 60Hz like the original, so the speeds are accurate because of that.

I feel like I hammered out the most of the critical inaccuracies, and I left out the original bugs because I found it preferable.

1 comments

You've done a great job, and I am in no way intending to be critical. My only concern was the claim of accuracy. It is an outstanding simulation of the original, and I commend you for your work on it.

However, leaving out the bugs, for example, makes it not accurate. As for the timer, I don't see how you could guarantee the frequency in a javascript VM. It could be similar (by continually testing how inaccurate it is and adjusting the frequency of subsequent iterations), granted, but this is not accuracy (it is emulation). As for memory, etc, many of these older games had "death screens" where a buffer overflows and simple crashes the game, preventing you from continuing past a certain point - that too would be very difficult to accurately model in javascript. The list could go on and on. And this is in no way critical of you, or what you have done - it is simply statement of fact about accuracy!

As an aside, Billy Mitchell (the first person to ever get a perfect pacman score) was one of the stars in the movie The King of Kong.

Again, I think what you have done is AWESOME. But it is not accurate (and likely could not be).

Urghhh... I wish i'd never posted anything now :(

no, not a problem. i am agreeing with you now. curious, what should i call it instead? perhaps, faithful? or near-perfect?
I have no idea, im afraid. I like the thought of an "ambitious reproduction", but "awesome" works just as well :)