Package Details: vkbasalt 0.3.1+37+g59463d0-1

Git Clone URL: https://aur.archlinux.org/vkbasalt.git (read-only, click to copy)
Package Base: vkbasalt
Description: A Vulkan post-processing layer. Currently the effects are CAS, FXAA, SMAA, deband.
Upstream URL: https://github.com/DadSchoorse/vkBasalt
Licenses: zlib
Submitter: gee
Maintainer: gee
Last Packager: gee
Votes: 10
Popularity: 2.20
First Submitted: 2019-10-21 10:32
Last Updated: 2020-05-17 13:44

Latest Comments

1 2 3 4 Next › Last »

gee commented on 2020-05-17 13:45

@DadSchoorse awesome, thank you!

If you ever feel like taking this over, feel free to ask since it's your baby. :)

DadSchoorse commented on 2020-05-17 11:28

Just a few notes: the reshade source is unnecessary, everything has been moved into the main repo and the dependency on vulkan-tools isn't needed

gee commented on 2020-05-17 02:32

This isn't supposed to be a dev package, so I didn't want to update it again till a release came about, but it seems it doesn't build anymore, probably because of GCC 10, so might as well.

Thank you @frankyboy for giving me a summary of the changes and saving me the time!

I have not tried the 32b version yet or even the 64b extensively, so please tell me if I made a mistake somewhere.

frankyboy commented on 2020-05-16 20:09

https://github.com/DadSchoorse/vkBasalt/pull/81

build type changed to meson :) Also includes the shaders in the binary so a shader directory isn't needed anymore.

gee commented on 2020-04-09 19:53

@I'm happy this work for you now @bajczyk, but please remember the real heros are the ones writing the code to make it work/build, not the ones doing the simple PKGBUILD stuff. :)

bajczyk commented on 2020-04-09 19:06

Hi guys, I just want to thank you for this work, you're awesome :D it compiles now, so thanks to you I can finally enjoy image sharpening!

gee commented on 2020-04-08 01:26

@yochananmarqos It's all good.

Well, I didn't want to force the newer dev version onto people that had a fine stable build, that's why I didn't do what you're suggesting. But maybe I shouldn't worry too much about that and let people ignore this or not as they want.

As for reshade, that's cool, it was annoying and error-prone to do it manually thank you!

yochananmarqos commented on 2020-04-08 01:18

@gee: Ha, I commented without even looking at the changes. Sorry, my mind is on other things.

What you did of course is what I was talking about. However, since its a release tag + a commit after, add a pkgver() function:

pkgver() {
  cd ${srcdir}/vkBasalt
  git describe --tags | sed 's/^v//;s/-/+/g'
}
0.3.1+12+g5b4ce45

You don't have to specify a commit for reshade since it's a nested submodule. It will automatically pull the right commit.

Hooray, it builds!

gee commented on 2020-04-08 01:06

@yochananmarqos wow that was super quick! Well that's kind of what I did, but I didn't want to force people with a working build to now use a dev one, in case there are issues. Not sure if the releases are actually tested and supposed to be more stable that your everyday commit though.

What do you think?

Thank you very much!

yochananmarqos commented on 2020-04-08 01:02

@gee You can still maintain this package as a "stable" release, but use a specific commit instead of the release tarball. See the gtk3 package for an example.