Quoting: tuubiThe PPA method is still safer and simpler. Only consider using Nvidia's installer if you actually have problems with the PPA packages.

Indeed, repairing your distro after using nvidia's installer really isn't worth it.
There is a reason I always liked ATI's distribution, because it always had a "build deb package", and it had a kernel source module package, so you can build the kernel binary module next to the kernel binary on your compilation rig, and leave all dkms stuff off your system.
The few times I used nvidia's installer, I always regretted it later.

View this comment - View article - View full comments

Quoting: tuubi

Quoting: ArdjeI spent 40 euro on ark, and it was a 40 euro well spend. I have glitches and bugs, but if you look at the size of the game of course it will have problems.

It's big and complicated so of course there'll be bugs and glitches? Developers just love customers like you. :)

Maybe because I am a developer too. To be clear: I've seen some sad cases of development in my life, and I had to teach a few. And I occassionaly see things in my own code that have me like "How could I think that could work".
Being toxic doesn't help, being realistic helps. And in that light, ARK: is a pretty good project.
If it was a pacemaker, the stakes would be different, but even in pacemaker land the programmers are average, and the design is crap. But why? Because they never thought anyone would willingly hack a wireless controlled pacemaker for instance.
And let's not forget the second generation radiation equipment used against cancer. How many people died on the table because the software was buggy.
And the biggest question of all:
If everybody is dissing you, comparing you to the worst of the world, why would you even listen to them. There are about 100k players, 30k continuous players and about 200 of them continously release toxic on the forums.

View this comment - View article - View full comments

Quoting: GuestI think the more we request an ARk fix for linux maybe we will get one! Or am I just crazy hopeful because I love this game?!

I think it doesn't matter what we request... Any helpful or good bugreport usually gets drowned in acid and salt of disgruntled people that don't know the concept of beta, and can't do anything else but repeat what another has said but only louder and with bigger letters.
I spent 40 euro on ark, and it was a 40 euro well spend. I have glitches and bugs, but if you look at the size of the game of course it will have problems.
For now I think as linux users it's best to only submit engine bug reports in a polite manner, and only in the expected forums. They are already drowning in acid and salt, let's not add a portion of acid and label it "from a linux gamer".
Unfortunately linux is for the masses, so the linux thread on steam is already gaining toxic comments :-(.
Actually, I am fed up with that toxic community. On each patch note update in the steam forums, there are about 10 nice comments, and 200 toxic whiners (see http://steamcommunity.com/app/346110/discussions/0/594820656447032287/ [External Link] ). As ark gets almost daily updates, that's too much to weed through.
Yes, I myself am being salty about the saltyness ;-). But that's the reason why I don't think that adding to that we will get heard. We might get noticed if we are nice and following procedures.

View this comment - View article - View full comments

Quoting: liamdaweIt's hard to hit Windows levels with games that were never designed with Linux or anything but DirectX in mind.

The biggest thing Linux excels in (according to a windows game player/linux for work user) is disk I/O. He said that pressing quicksave is not noticable on linux (using wine), while on windows the whole system freezes during the save.
All my encounters with windows confirm this: disk I/O, swap and network I/O is what linux excels in. Any windows virtual machine on a linux system (using KVM) is also pretty fast. Windows native usually needs a few gig's extra RAM to cope with bad design.
The bad swapping behaviour can be handy in loading. Although a good mmap should work wonders.

View this comment - View article - View full comments

Quoting: Doc AngeloSadly, it segfaults on me. :( Normal version works fine, though.
I'm on Debian Stretch, using Nvidia driver 375.39 from the Debian repository. "vulkaninfo" seems to report that Vulkan works. I sent a mail with logs to Feral support.

I think you need the 375.27 branch, as that seems to be the version for vulkan and vr development.

View this comment - View article - View full comments

Ok, did anyone get vulkan to work on steamos_beta?
I have the "right" drivers (the vulkan branch, but one release short of the one needed for VR, so just what's in steamos_beta), but none of the vulkan versions work...
mad max of course does not work.
But The talos principle also doesn't work.
The talos principle bails out after trying and failing to set the resolution.
Mad max just has mdmp files.

View this comment - View article - View full comments

Quoting: ArdjeConstruct 3 is said to work on chromebooks. I just need to keep my chromebook updated. Well, I have, but it still refuses to work, because the chromebook release is 56 and not 57.

Heh, v57 has been build last night... It took an hour for the forced update...
Let's retry.

View this comment - View article - View full comments

Construct 3 is said to work on chromebooks. I just need to keep my chromebook updated. Well, I have, but it still refuses to work, because the chromebook release is 56 and not 57.

View this comment - View article - View full comments

Quoting: Cybolic

Quoting: HailToTheGrail

Quoting: CybolicI wish there was a way to not have to put in my password on every change, maybe someone knows how to work around that?

You could give setuid a try. Make a shell script as root, and then: chmod u+s script.sh
You should be able to run it as a user with it's owner rights, which are root.

No go on my Arch system. I've also tried editing the sudoers config file with visudo and using sudo instead, but that still asks for a password :/

I don't know what the discussion is, but running scripts as root is easy:
You create a script that's owned by root in a directory that's only writeable by root (security).
In your script you do
if [ "$(id -u)" -ne 0 ]; then
exec sudo -u root "$0" "$@"
fi

In your sudoers file you can say:
<user> ALL = NOPASSWD: <full path of your script>

That's the easiest way to perform a script as root: make the script safe, and then hand out rights to users to run that script.

View this comment - View article - View full comments

I think it was at fosdem last year that I heard how enlightenment developers used a cpu-intensive thing (busy loop) to let the governor upclock the cpu before starting any graphical updates. Just to prevent this.

View this comment - View article - View full comments