Just started playing this, and I thought the kick became super strong because of level up!

Also, just had my first night outside. Don't know if I'm willing to go through that much stress again :-S

View this comment - View article - View full comments

> If this is still correct and it has been a long time since you updated,

It would be great if this said how long a long time is.

View this comment - View article - View full comments

Quoting: subEdit: The base spec is currently > 2100 pages of rather dense content. Ewwww.

A lot of it is things you don't need to start with Vulkan! Renderpass subpasses, multi gpu, the many image formats etc. Like I said, start from the beginning, learn the basics (how to create a device and query its properties for example, then you will find yourself past 10% of the spec already.

View this comment - View article - View full comments

Quoting: subI wanted to learn OpenGL and didn't manage for years.
Simply couldn't find the time.
Now, I do have some time that I would like to invest in learning a graphics API,
but OpenGL seems to be quite obsolete by now.
Then again, Vulkan as a first graphics API without prior knowledge of GPU architectures,
sounds a bit too challenging.

What do you think is the best approach?
Thanks for any input! :)

I was in a similar situation as you 4 years ago when Vulkan came out. I just read the spec (make sure to get the one without extensions) and I can honestly say most of it is pretty simple. Synchronization is not so hard either, if you know them from operating systems. Vulkan is just verbose, otherwise there is really nothing too complicated there. Sure your first code won't be performant, and probably has subtle bugs, but it's easy to start.

I started with compute, as graphics has much more to configure, and it's pretty simple. Once comfortable with using buffers and images, graphics is not that big a step either.

Note that this was right after Vulkan was released, and there weren't any examples around. I approached it step by step, let's make a device, that was easy, now let's create a buffer, cool, now add a compute shader that increments every index, done and voila, a Vulkan program.

View this comment - View article - View full comments

Quoting: Phlebiac

Quoting: ShabbyXI myself would like to tackle this, but I have so much on my plate, I could use help getting the initial code done.

If you're not just trolling: there's already code being used by some distributions:
https://fedoramagazine.org/chromium-on-fedora-finally-gets-vaapi-support/

No I'm not trolling. That's fantastic, I didn't know about that. It's even better knowing that these patches are already running in the wild. I'm on paternity leave at the moment, but will definitely push to upstream the patches once I'm back next month.

View this comment - View article - View full comments

Quoting: Liam Dawe

Quoting: ShabbyX

Quoting: Liam Dawe

Quoting: ShabbyXIronically, the disadvantage of Linux with Stadia is that chrome doesn't support hardware acceleration in video decoding, so Linux will have a (slightly) higher latency than windows...

What's the latest on this, I'm a bit out of touch since I use Firefox.

The latest is what I just said?

*sigh* let me be a lot more specific then: What is the latest on getting the code accepted into Chromium/Chrome to enable it the same as it is on Windows?

Linux GPU support in chrome is primarily done by Linux enthusiasts volunteering their time (of which there are many in Google). This particular thing has been low priority enough that so far no one has volunteered to do and maintain it (and the bigger problem is indeed maintenance, and addressing the flurry of bug reports on all sorts of hw). It's a sensitive feature too, imagine how mad any Linux user would be if they couldn't watch videos on youtube, so it can only be enabled if it's entirely bugfree. The fact that the hw-accelerated video decoding libraries on Linux don't have test suites also doesn't instill confidence.

I myself would like to tackle this, but I have so much on my plate, I could use help getting the initial code done.

View this comment - View article - View full comments

Quoting: Liam Dawe

Quoting: ShabbyXIronically, the disadvantage of Linux with Stadia is that chrome doesn't support hardware acceleration in video decoding, so Linux will have a (slightly) higher latency than windows...

What's the latest on this, I'm a bit out of touch since I use Firefox.

The latest is what I just said? Firefox doesn't support it either FYI. They will both use software decoding which will add another few milliseconds of delay.

If anyone is interested in adding this support to chrome, I can try to maintain it going forward. Add me as reviewer (syoussefi, chromium, org) and I'll try to push for it.

View this comment - View article - View full comments

Ironically, the disadvantage of Linux with Stadia is that chrome doesn't support hardware acceleration in video decoding, so Linux will have a (slightly) higher latency than windows...

View this comment - View article - View full comments

QuoteFor the moment avoid downloading .desktop or .directory files and extracting archives from untrusted sources.

It's not windows, nobody downloads software off the internet already

View this comment - View article - View full comments

Does it need root password everytime it applies settings? Does the whole UI run as root on startup? If the latter, no thank you! I would like to see the developer think about the security implications too.

View this comment - View article - View full comments