Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

I learned Vulkan and wrote a small game engine with it

edw.is

Post reply on HN
Print view View original

261–268 of 268 posts

Re: I learned Vulkan and wrote a small game engine with it

#261

Post by wtetzner »

cubefox wrote: post #260
wtetzner wrote: post #250

Earlier quoted context omitted.

> There are two poles I'm not sure I agree. I think you can write a simple-but-not-hacky implementation that does only what is necessary, and is also easy to maintain and extend later. Of course, you never really achieve that ideal, but you can keep getting closer to it as you gain more experience.

"Easy to extend" arguably means including more abstraction and making things more general than they need to be merely for solving the current problem. There is a trade-off here.

"Easy to extend" for me means keeping things decoupled (as opposed to adding extension mechanisms etc.).

Of course there's a tradeoff (there always is), I think my point was just that this option doesn't really seem like it fits between "quick and dirty" and "over engineered", though I suppose that probably depends on how you picture that continuum ;)

Re: I learned Vulkan and wrote a small game engine with it

#262

Post by _gabe_ »

johnnyanmac wrote: post #246
_gabe_ wrote: post #239

Earlier quoted context omitted.

There’s a very big difference between ultra realistic PBR graphics and running games at 60 FPS at 1080p.

You think the people trashing the switch know any difference? That's my point.

They do know the difference[0][1][2]. I feel like gamers are notorious for complaining about fidelity issues and frame rate issues. I’m not sure why you would think they don’t understand the difference. The reason people complain about switch frame rates is because it’s often low fidelity games that still can’t hit a consistent 60 FPS.

[0]: https://gamefaqs.gamespot.com/boards/189706-nintendo-switch/...

[1]: https://www.nintendolife.com/forums/nintendo-switch/the_fram...

[2]: https://www.reddit.com/r/FortNiteBR/comments/gyn32c/seriousl...

Re: I learned Vulkan and wrote a small game engine with it

#263

Post by johnnyanmac »

_gabe_ wrote: post #262
johnnyanmac wrote: post #246

Earlier quoted context omitted.

You think the people trashing the switch know any difference? That's my point.

They do know the difference[0][1][2]. I feel like gamers are notorious for complaining about fidelity issues and frame rate issues. I’m not sure why you would think they don’t understand the difference. The reason people complain about switch frame rates is because it’s often low fidelity games that still can’t hit a consistent 60 FPS. [0]: https://gamefaqs.gamespot.com/boards/189706-nintendo-switch/... [1]: https://…

"they" as in hardcore hobbyist with multi thousand dollar rigs who spend their time talking on old game forums. Sure, there's a minority that cares. But those gamers aren't why Fortnite sells like Fortnite. They aren't why the Switch is on pace to be the best selling console. They aren't why the indie market is viable as a potential livelihood if you get a bit lucky.

But this is all tangential. They may have all these fancy hardware but they either have no understanding of hardware, or are simply tonedeaf. If you're expecting the same specs out of a 2017 smartphone compared to a PS5, let alone a top end pc build, there's simply not much more I can say. Learn that a handheld has more considerations than a towering console when it comes to being a proper handheld. It's a 720p specc'd screen, of course any 3d game trying to be modern won't bother going higher.

I never saw people complaining about a 3ds not having ps4 performance, so this to me seem like a recent sense of entitlement or ignorance amongst said enthusiasts. The Switch doesn't have a GPU dock (which would cost more than the console itself, even if it didn't include a GPU), so just because you project it to a screen doesn't mean it's suddenly console hardware. You could project a PSP to a screen back in the day. Nintendo just made it work out of the box.

Re: I learned Vulkan and wrote a small game engine with it

#265

Post by eliasdaler »

rychco wrote: post #149

I’ve been lurking & following your project for months in the Graphics Programming discord as I work on my own hobby Vulkan engine. It’s been inspiring seeing all the progress you’ve made. I especially admire your willingness to ask questions & share your work-in-progress so openly. Keep up the great work

Thanks a lot! Good luck with your engine as well :)

Re: I learned Vulkan and wrote a small game engine with it

#266

Post by marcellus23 »

kllrnohj wrote: post #249
marcellus23 wrote: post #238

Earlier quoted context omitted.

> Both Vulkan and Metal support that. But, of course, Apple does it differently. Metal is older than Vulkan. So really, Vulkan does it differently.

Vulkan is a continuation of AMD's Mantle which is then older than Metal.

I wasn't aware of that. Fair enough!

Re: I learned Vulkan and wrote a small game engine with it

#267

Post by wizzwizz4 »

johnnyanmac wrote: post #207
eliasdaler wrote: post #77

Earlier quoted context omitted.

Indeed. I used as little CSS as I could because I love minimalist websites. And the lack of syntax highlighting was inspired by Go blog, for example. :) Raw HTML definitely looks much uglier, sadly (“Reader mode” in most browsers makes websites without CSS easily readable, though!).

reminds me a lot of http://bettermotherfuckingwebsite.com/ pretty much all HTML, with only the bare minimum CSS to make it somewhat responsive. I guess if you want one tiny piece of feedback, based on the above site: >A little less contrast >Black on white? How often do you see that kind of contrast in real life? Tone it down a bit, asshole. I would've even made this site's background a nice #EEEEEE if I wasn't so fo…

> Black on white? How often do you see that kind of contrast in real life?

In books. If you have really high-end hardware where you have enough contrast to be painful, turn down your contrast setting. On regular-person devices, grey-on-grey is needlessly hard to read, and there's no way to turn the contrast up without introducing clipping.

Re: I learned Vulkan and wrote a small game engine with it

#268

Post by 0x1ceb00da »

jcelerier wrote: post #220
0x1ceb00da wrote: post #161

Earlier quoted context omitted.

Do you have any references? I thought all wgpu objects are wrapped with an Arc >.

That sounds wild to me. In c++ I remember a time where I increased the frame rate of a particle renderer from 20fps to 60fps+ simply by going from passing shared_ptr (Arc equivalent) to passing references.

Nevermind. Just an Arc.
Post reply on HN