Live data from Hacker News

Nightdrive

incoherency.co.uk

241–250 of 256 posts

Re: Nightdrive

#241

I'm amused that we share initials and a passion for this kind of project! Mine's https://rezmason.github.io/drivey . One key difference: this guy built his demo from scratch, whereas mine's a port of someone else's work. It's great to see another implementation, with its own techniques and features.

That is amazing, I remember seeing an early version of this on Windows, its so great to see it revived and with source!

Re: Nightdrive

#242

I'm amused that we share initials and a passion for this kind of project! Mine's https://rezmason.github.io/drivey . One key difference: this guy built his demo from scratch, whereas mine's a port of someone else's work. It's great to see another implementation, with its own techniques and features.

That is amazing, I remember seeing an early version of this on Windows and being impressed. It is great to see it revived and with source!

Re: Nightdrive

#243

I'm amused that we share initials and a passion for this kind of project! Mine's https://rezmason.github.io/drivey . One key difference: this guy built his demo from scratch, whereas mine's a port of someone else's work. It's great to see another implementation, with its own techniques and features.

Yeah. That is awesome.

Re: Nightdrive

#244
post #225

Reminds me very much of Night Driver , the arcade game from 1976: https://archive.org/details/arcade_nitedrvr

That's also the first thing I thought when I saw the title

Re: Nightdrive

#245
> I found it actually worked better if I omitted the x offset from the distance calculation (so just sqrt(y2 + z2)), otherwise objects near the edge of the field of view were weirdly distorted. But I wouldn't suggest doing that in the general case.

I think this is because you should actually just be dividing by y, the perpendicular distance through the screen. Probably adding z to the mix, while wrong, doesn't make it too weird because of the limited set of z values used.

If the result with just division by y looks distorted, then I would suggest fiddling with the value of k, which effectively controls how wide-angle versus telephoto things look.

Re: Nightdrive

#247

I'm amused that we share initials and a passion for this kind of project! Mine's https://rezmason.github.io/drivey . One key difference: this guy built his demo from scratch, whereas mine's a port of someone else's work. It's great to see another implementation, with its own techniques and features.

interesting that this is running very slow (like 1 frame per second) on Chrome, but runs very smooth on Firefox. I'm on the latest version of both for Mac.

That is very odd. I wonder what your Chrome browser's zoom is set to, that might affect its resolution.

If you create an issue on the repo, I'll try and figure it out when I have the bandwidth.

Re: Nightdrive

#248

I'm amused that we share initials and a passion for this kind of project! Mine's https://rezmason.github.io/drivey . One key difference: this guy built his demo from scratch, whereas mine's a port of someone else's work. It's great to see another implementation, with its own techniques and features.

Hmm, nothing happens for me on mobile (Chrome, Pixel 6 Pro). Just a black screen with some controls on the bottom.

Re: Nightdrive

#249
I have many many childhood memories of long journeys up and down the country visiting my grandparents sat in the back of my parents car at night with scenes just like this etched in there. And I'm from UK too so was delighted they did this the "right" way round :)

Brilliant work, love this.

And the music reminds me of Kavinsky too with the obvious association with Drive.

Also, I know it's not actually there, but my mind insists on filling in a "not quite black" sky over the road and the occasional tree or similar to the sides as shadows. Fascinating effect.

Re: Nightdrive

#250
Was that a helicopter I saw? Couldn't find anything about it in the source or discussion... nice touch!
Post reply on HN