A first-person engine in 265 lines of JS

Re:A first-person engine in 265 lines of JS by s-macke on Tuesday June 03, 2014 @08:17PM (#7843428)

Don't know. But here some possibilities:

1. No fullscreen

2. I update the screen only if a key is pressed.(No rain, that has to be rendered all the time)

3. I don't use any costly canvas functions. I render everything myself in a pixelbuffer.

4. Typed arrays

[ Parent | on HN ]

Re:A first-person engine in 265 lines of JS by hunterloftis on Wednesday June 04, 2014 @01:33AM (#7844172)

It's #2. Redrawing at 60hz (or as close as the machine can come) is what hits the cpu so hard.

[ Parent | on HN ]

Re:A first-person engine in 265 lines of JS by s-macke on Wednesday June 04, 2014 @03:04AM (#7844352)

No, I don't use requestAnimationFrame right now. I think when I wrote it, it was not supported by IE. But can't remember.

I calculate as close as the machine can but with a window.setTimeout(Update, 0); in order to be responsive.

[ Parent | on HN ]