Quoting: Purple Library Guy

Quoting: Guest

Quoting: ShmerlIt's just a Tegra tablet with some Nintendo DRM mess attached. So once DRM is broken, Linux should be runnable :)

Can we stop all this talk of DRM on just about every topic that's posted? (not pointing the finger, I mean in general)
Scrolling down through the posts only to see DRM being talked about instead of the actual headline, is getting...well, a bit boring and disappointing.
Serious gamer's are not all that bothered about DRM anyway, it's all about playing and enjoying the game, so it's pointless bringing it up all the time.
There is a forum for that kind of topic.

Ironically, you would appear to have gotten the conversation about DRM going rather than stopping it. I would suggest partly because you couldn't resist the crack about serious gamers. The lesson is, if you're supposedly trying to stop an argument, don't take a position in the argument as part of your intervention.
Although since nobody was actually talking about DRM until you said this, another lesson is "If you're already ahead, 'quit while you're ahead' means 'quit before you start'".

Yes, exactly. I did the very same (very tempting) mistake in the past too ;).

View this comment - View article - View full comments

Quoting: m2mg2

Quoting: jens

Quoting: m2mg2

Quoting: jens

Quoting: tuubi

Quoting: lucifertdark

Quoting: Comandante Ñoñardo

Quoting: m2mg2Game locks up with black screen. Tried with 390.48 and 396 Beta drivers. Tried with gamemode enabled and disabled. Started on Fedora 26 and upgraded to 27. Tried with SELINUX in permissive mode. No real useful crash info, just segmentation fault 11.

It seems that the game was developed for Ubuntu 17.10 in mind... I have 14.04.5 LTS and I have the same segmentation fault 11.
I'm gonna experiment with Xubuntu 18.04 and see what happen-

I had the same segmentation fault crash on Ubuntu 16.04 with the 396 beta drivers, I'm now using Ubuntu 18.04 with the 390.48 drivers, Rise is rock solid & I've managed to get 70% of the way through the main storyline with no crashes, the 396 Beta drivers give me the segmentation fault crash even with 18.04.

Even Ubuntu 17.10 with the 396 drivers was a crash fest for Rise, avoid those drivers for the moment, they're obviously broken.

Not quite that simple. For starters, with 390.48 the game gobbles up several gigabytes more memory, which explains some of the problems on systems with only 8 gigs of RAM. For me the 396.18 beta is almost perfect with this game on Mint 18.3, whereas 390.48 caused me to almost give up and wait for a fix.

This problem seems a bit hard to pin down, but I'm sure both Feral and Nvidia are working on it. And I hear it's not perfectly stable for some AMD users either.

Yeah, seems to be very system dependent which driver works well. I'm running the 390.48 driver on Fedora without any issues for ROTTR. That said I have 32GB RAM, which supports your observation. No micro stutters either, but could be that they are there, but me just does not noticing them that much due to having a fast system.

What version of Fedora are you running?

Fedora 27 fully updated, thus now kernel 4.16.3-200.fc27.x86_64.
I'm using negativo17 repositories for Nvidia, Steam and some other packages (https://negativo17.org/repositories/). I do not use rpmfusion.

Almost the same as me, although I do use rpmfusion. I have a GTX 980. I was using negativo for NVIDIA drivers, but I removed them to manually install the 396 BETA drivers. Game didn't work with either set of drivers. All other Feral games work fine. Must be hardware/driver issues, hopefully Feral get it sorted out soon. I've sent crash logs and I'm sure they have plenty of others.

GTX1080 here, may be that makes the difference..

View this comment - View article - View full comments

Quoting: m2mg2

Quoting: jens

Quoting: tuubi

Quoting: lucifertdark

Quoting: Comandante Ñoñardo

Quoting: m2mg2Game locks up with black screen. Tried with 390.48 and 396 Beta drivers. Tried with gamemode enabled and disabled. Started on Fedora 26 and upgraded to 27. Tried with SELINUX in permissive mode. No real useful crash info, just segmentation fault 11.

It seems that the game was developed for Ubuntu 17.10 in mind... I have 14.04.5 LTS and I have the same segmentation fault 11.
I'm gonna experiment with Xubuntu 18.04 and see what happen-

I had the same segmentation fault crash on Ubuntu 16.04 with the 396 beta drivers, I'm now using Ubuntu 18.04 with the 390.48 drivers, Rise is rock solid & I've managed to get 70% of the way through the main storyline with no crashes, the 396 Beta drivers give me the segmentation fault crash even with 18.04.

Even Ubuntu 17.10 with the 396 drivers was a crash fest for Rise, avoid those drivers for the moment, they're obviously broken.

Not quite that simple. For starters, with 390.48 the game gobbles up several gigabytes more memory, which explains some of the problems on systems with only 8 gigs of RAM. For me the 396.18 beta is almost perfect with this game on Mint 18.3, whereas 390.48 caused me to almost give up and wait for a fix.

This problem seems a bit hard to pin down, but I'm sure both Feral and Nvidia are working on it. And I hear it's not perfectly stable for some AMD users either.

Yeah, seems to be very system dependent which driver works well. I'm running the 390.48 driver on Fedora without any issues for ROTTR. That said I have 32GB RAM, which supports your observation. No micro stutters either, but could be that they are there, but me just does not noticing them that much due to having a fast system.

What version of Fedora are you running?

Fedora 27 fully updated, thus now kernel 4.16.3-200.fc27.x86_64.
I'm using negativo17 repositories for Nvidia, Steam and some other packages (https://negativo17.org/repositories/). I do not use rpmfusion.

View this comment - View article - View full comments

Quoting: tuubi

Quoting: lucifertdark

Quoting: Comandante Ñoñardo

Quoting: m2mg2Game locks up with black screen. Tried with 390.48 and 396 Beta drivers. Tried with gamemode enabled and disabled. Started on Fedora 26 and upgraded to 27. Tried with SELINUX in permissive mode. No real useful crash info, just segmentation fault 11.

It seems that the game was developed for Ubuntu 17.10 in mind... I have 14.04.5 LTS and I have the same segmentation fault 11.
I'm gonna experiment with Xubuntu 18.04 and see what happen-

I had the same segmentation fault crash on Ubuntu 16.04 with the 396 beta drivers, I'm now using Ubuntu 18.04 with the 390.48 drivers, Rise is rock solid & I've managed to get 70% of the way through the main storyline with no crashes, the 396 Beta drivers give me the segmentation fault crash even with 18.04.

Even Ubuntu 17.10 with the 396 drivers was a crash fest for Rise, avoid those drivers for the moment, they're obviously broken.

Not quite that simple. For starters, with 390.48 the game gobbles up several gigabytes more memory, which explains some of the problems on systems with only 8 gigs of RAM. For me the 396.18 beta is almost perfect with this game on Mint 18.3, whereas 390.48 caused me to almost give up and wait for a fix.

This problem seems a bit hard to pin down, but I'm sure both Feral and Nvidia are working on it. And I hear it's not perfectly stable for some AMD users either.

Yeah, seems to be very system dependent which driver works well. I'm running the 390.48 driver on Fedora without any issues for ROTTR. That said I have 32GB RAM, which supports your observation. No micro stutters either, but could be that they are there, but me just does not noticing them that much due to having a fast system.

View this comment - View article - View full comments

Quoting: Salvatos

Quoting: Shmerl

Quoting: ScooptaI disagree simply because once you download a game from steam(assuming it doesn't use the steam DRM) nothing stops you from making a backup of it.

Did you even follow the discussion above? You aren't allowed to do it if you are using Steam.

You're not allowed to photocopy a paperback either, that doesn't mean there's DRM in your stack of paper.

There are very different definitions here in this thread what DRM actually is/what the scope of it is/what degradation it has (direct rendering manager, anyone?? ;)). That's one of the reasons why this discussion starts again and again and runs in circles forever. The question "Is Steam DRM" is the wrong one imho. A much better question would be "Do I want to fully legally own digital assets (and are allowed to do no matter what I want to do with it) or do I merely want to use digital assets as there are intended to use (thus buying a permission to play) after doing a purchase in a digital store?". The last one is really just personal preference, something which is very hard to influence by facts.

Edit: replaced some parts I realized that could be read differently than I meant it...

View this comment - View article - View full comments

Quoting: Guest

Quoting: Doc Angelo

Quoting: GuestYes, I have a source. Me. In details here, it was a demo, downloaded via Steam itself. It was later decided (either by Valve themselves, or a ratings board) that the demo wasn't suitable for the country. The next time I fired up Steam, the game (demo, in this case) was summarily removed in its entirety - without notification to me. I had to go hunting for what happened.

Thanks for the answer! Out of interest: Which developer decided to do that and which game was it?

Rebellion, with Sega as publisher. Demo was AvP (2010).

To be clear: Valve probably had a legal obligation to remove it based upon a review board, but I just like to point out their level of control that not everyone may be aware of. I was mostly irritated by their lack of notification on the matter.

yeah, it sucks when actions like this are not properly communicated and I can understand that you wouldn't trust Steam with your important stuff. It is indeed good to understand that Steam is much more an ecosystem for publishing content than just a wrapped browser for a store. That said, the ability to revoke games, e.g. when the key seems to originate from credit card fraud, is not necessarily a bad thing imho. There are still enough people out there thinking that key reselling is a sane business. I consider it positive that developers have something at their hands to act in cases of most easy/accessible/obvious forms of fraud.

Obviously with great power come great responsibility. I cannot imagine that Steam would revoke a normally purchased game, but if this is ever going to happen harsh responses from customers are justified. Excluded are cases where Steam would (be forced to) remove a game due to e.g. the game itself doing something not very legal, though proper communication is still a must in this cases. If my neighbor purchased a nuclear bomb I would also very glad that their are legal actions possible to prevent him from keeping it ;)

PS: Steam is only about games, similar with e.g. Netflix or Spotify it is only entertainment. I'm not that emotionally attached to it and would just move on. Actual personal data (e-mails etc) in cloud services is a different matter, though I'm much to lazy to maintain proper offline backups of that...

PPS: I had a reverse case recently. I wanted to remove a settings file from a game (Shadow Tactics) because after an update the game wouldn't start due to mangled settings. I had removed that file on disk, but initially it kept coming back due to Steam cloud synchronization ;)

View this comment - View article - View full comments

Quoting: Comandante Ñoñardo

Quoting: jens

Quoting: Comandante ÑoñardoSomething is wrong here..
They can not recommend a non LTS distro... A non LTS version is no more than a BETA.

The game must be the broken one, because I am not the only one with this SISSEGV (11) Segmentation Fault thing.

Well, I haven't had a single crash here, Fedora 27 fully updated with Nvidia drivers and Steam from Negativo17. Sorry to hear that you got such problems.

The only time I had crashes (on startup) with Feral games was with DX-MD. I tried to reproduce the crashes on a system they support on a spare disk. I could reproduce the issue and opened a support ticket. Turns out my CPU was to old. I rightfully got indeed the message in the launcher that my CPU was unsupported ;). I would advise to take the same approach.

While I recognize that it is time for me for to upgrade from my trusty Ubuntu 14.04.5 LTS to Ubuntu 16.04.5 LTS.. But I will Never upgrade to a non LTS... I will try 18.04 months later, when it became mature; Every new LTS Ubuntu has some problems.

I have afraid to brake something in the upgrade process...

I didn't touched my main system. I did a fresh install on a spare disk to having temporary a supported system where I tried to reproduce the crashes.

View this comment - View article - View full comments

Quoting: Comandante ÑoñardoSomething is wrong here..
They can not recommend a non LTS distro... A non LTS version is no more than a BETA.

The game must be the broken one, because I am not the only one with this SISSEGV (11) Segmentation Fault thing.

Well, I haven't had a single crash here, Fedora 27 fully updated with Nvidia drivers and Steam from Negativo17. Sorry to hear that you got such problems.

The only time I had crashes (on startup) with Feral games was with DX-MD. I tried to reproduce the crashes on a system they support on a spare disk. I could reproduce the issue and opened a support ticket. Turns out my CPU was to old. I rightfully got indeed the message in the launcher that my CPU was unsupported ;). I would advise to take the same approach.

View this comment - View article - View full comments

I really don't get all the fuss about the dependency to Steam authentication. When I purchase a game I do this with the purpose of playing the game on my preferred (and only) gaming device. Steam on Linux allows me to do this without any of the heavy DRM stuff the poor Windows people have to deal with (I would not accept that too). No requirement to install something as root or whatsoever. Combined with convenience Steam offers (e.g. auto update, just one party for money transfer, etc.) and the willingness of Valve to invest some resources in Linux the perfect match for me.

I should add that I'm not a collector. I rarely watch a movie twice or read a book twice. Same with games, I think I have never finished a game more than once. May be that is the reason why I can easily accept the risk that there is a very minimal chance that my game library ends up empty when Valve closes their doors. That said I don't think that this will happen in my life time. I think chances are much much higher that sooner than this my games wont start anymore* due to the game having a dependency to some outdated library that is no longer there. Having a game on your external hd wont't help you in this case either ;).

Steam has I guess indeed some limited legal and technical control over my purchased games. But hey, these are only games, not over something personal like my job, kids, personal photo archive, whatever. I can certainly live with the restrictions. And furthermore, if Steam authentication makes publishers and developers think that their have some control (and I sympathize with their wishes for control) regardless or not if this has any practical effect, then I'm happily willing to accept this in its current form and help them with this feeling to get more and more big games to Linux land.

Anyway, to each his own, I prefer to play my games now and easily move on, than to archive them till the end of time.

* without considerable effort

Edit: typos.

View this comment - View article - View full comments

Quoting: tuubi

Quoting: jens(I'm missing a word: something like extreme, it is either 100% one side or 100% the other, nearly no in-between, at least not outspoken).

"Polarized"? I guess people who don't feel strongly about a subject aren't likely to comment on it.

Thanks, yes, that fits pretty well.

View this comment - View article - View full comments