Quoting: Dorrit

Quoting: tuubiCan you be more specific? At what point in history exactly was Europe a better place to live? Just curious.

1914 was a watershed.
After that governments never stopped absorbing more and more power, never let a crisis go to waste. We were finally left with crumbs of our former liberties, in exchange for sclerotic leviathans we call States, EU on top as a rotten cherry.
Now they're taking away even the crumbs, in the name of health security.
I pray for all to crumble back to that August, when Governments were small and people free to decide for themselves.

Ah, the glory days back when European empires were still free to exploit their colonies, women could not vote, the majority of people were servants, peasant farm workers or factory workers who had no rights to speak of, and so on. Oh and my own country was still a few years away from winning its independence, but I guess your definition of Europe is quite specific and excludes large parts of it.

View this comment - View article - View full comments

Quoting: Dorritthe return to healthy individualism will return Europe to its former glory.

Can you be more specific? At what point in history exactly was Europe a better place to live? Just curious.

Or do you perhaps mean something else when you say "former glory"?

View this comment - View article - View full comments

Quoting: PhiladelphusOn the other hand I've never actually used Krita, I don't think. How does it compare to GIMP (which I'm moderately familiar with)? Not in a "which is better" way, I just want an honest evaluation of the strengths and weaknesses (or maybe the different design goals) of each. I'm always interested in finding and learning another cool FOSS tool. :)

Gimp is a general purpose raster graphics editor whereas Krita's main focus is digital painting. If I need to manipulate an image in any way, I grab Gimp. If I feel creative and want to doodle a picture, Krita's slick UI and workflow can't be beat. Oh and Krita also has tools for keyframe-based 2D animation, but I'm not very familiar with that side of things.

View this comment - View article - View full comments

Quoting: Purple Library GuyWe still as far as I can tell have nothing decent to wrangle .pdf files. Nowadays trying to edit .pdf is the only time I ever wish I had my work Windows desktop when I'm on Linux at home, because I know of nothing remotely analogous to Acrobat pro. And I mean I don't even really like Acrobat that much as software, in terms of how it handles workflow or whatever, but when it comes to taking scissors and tape to a .pdf file nothing else seems willing to do much at all. I dunno, maybe some of the art-type programs can, but that's from a completely different paradigm, not much use dealing with text and merging files and shuffling pages.

Simple merging and page shuffling you can achieve easily with pdfshuffler. It has no editing features, but it does what it says on the tin and it does it intuitively. Just drag and drop files and pages, then save the result.

View this comment - View article - View full comments

Quoting: fagnerln

Quoting: tuubi

Quoting: fagnerlnIt's really awesome, because of it I discovered a big inconvenient, Vulkan uses A LOT of VRAM, I played some games with pretty bad performance and my GPU is good enough to run it, and I noticed that my VRAM was filled up, so I need to turn down some effects to put the game on <4GB range.

I have a 580 4GB, it's like driving a good car with the hand brake applied.

Vulkan doesn't use any more VRAM than any other API. A Vulkan renderer might, but that's up to the developers.

Dude, please...

I remember that I've read some post explaining some differences between Vulkan and high level api, and one of the points are about vram, that uses a slightly more of it (which is not a bad thing), but I can't find it anymore.

The point is that same games uses more VRAM on Vulkan, I don't see any reason to a dev "choose" to use more VRAM on different api without needing, on Doom 2016 have problems in 2GB card on Vulkan, Rainbow Six Siege have people complaining about low vram messages when using Vulkan, I have some games that uses considerably more VRAM on Linux (native and proton using vulkan) than Windows (DX11).

Before I post this comment, I did a small test using the Dolphin Emulator with Mangohud, 2 runs with Vulkan and 2 runs with OGL, the same configuration, the result is that on OGL it uses aprox 1,0GB and Vulkan aprox 1,3GB, 30% is a lot.

I know that the API itself doesn't use more VRAM, but a API without application is useless. I know that there's a lot of variables that changes the VRAM utilization (like the GPU vendor), but my point when I said "Vulkan uses A LOT of VRAM" is that the GAME that uses Vulkan uses more VRAM that the same game on other API, wasn't my intention to said that a API uses more RAM, doesn't make sense.

I know you didn't mean that the API itself uses memory.

My point was that with a lower level API like Vulkan or DX12, the developer is in control of memory allocation. Of course MangoHud will also reserve some VRAM, but any large differences are most likely down to the graphics backend implementation of whatever game you're playing, or emulator in this case. Wouldn't hurt to test without the hud or external Vulkan layers in general though, with a command line tool like radeontop or something.

And as for why a developer might choose to reserve more memory with Vulkan, well that's something you might want to ask them. Might be a simple case of inefficient code, or maybe a different allocation strategy (pre-allocation vs. ondemand). Could be a combination of things.

Of course I am always happy to educate myself if you've got a good source that shows that I'm talking out of my ass. I'm no graphics developer so I won't pretend to be an expert.

View this comment - View article - View full comments

I remember following Inkscape development back when it was forked from Sodipodi. Apparently that happened in 2003. I guess I've been a fan for quite a while already. I've used it for everything from UI mockups to illustrations for documentation in my day job as well as for random doodles like my silly little avatar.

And Krita is just a perfect match for our Cintiq.

View this comment - View article - View full comments

Quoting: EikeI really like modesty, but making a 1.0 after what feels after a decade of usefulness seems to be too much for me. (I can't remember what other famous example there was. Was it Gimp? One not so famous would be KDiff3, which I'm using for a decade at least 17 years :O and which never got a 1.0 by its original maintainer.)

Unlike age, a version is just a number. ;)

View this comment - View article - View full comments

Quoting: fagnerlnIt's really awesome, because of it I discovered a big inconvenient, Vulkan uses A LOT of VRAM, I played some games with pretty bad performance and my GPU is good enough to run it, and I noticed that my VRAM was filled up, so I need to turn down some effects to put the game on <4GB range.

I have a 580 4GB, it's like driving a good car with the hand brake applied.

Vulkan doesn't use any more VRAM than any other API. A Vulkan renderer might, but that's up to the developers.

View this comment - View article - View full comments

It's available on GOG Connect [External Link] as well if someone already bought it on Steam.

View this comment - View article - View full comments

Quoting: GuestThey've already removed the necessary files by the looks of it - didn't even give people a warning who might otherwise have had a chance to download and backup everything (assuming it could be run without Steam), or provide an archived copy somewhere.

I can still install the Linux versions of We Were Here and We Were Here Too just fine.
EDIT: First one missing the launch config like Liam says.

By the way, this announcement only shows up in the Steam news feed for the first game. I know their wording makes it pretty clear that the sequel will lose support as well, but is that actually confirmed?

View this comment - View article - View full comments