Quoting: Ryuzaki

Quoting: edddeduck_feralWe have not had any other reports of that performance regression so it's likely an issue that was related to the git version / build method that Phoronix used on that specific day.

I have this issue on ArchLinux with a rx480, mesa 17.0.1 and llvm-libs 3.9.1

https://imgur.com/a/NNmyE [External Link]

I emailed you about this at day one. So no news for me?

I'd check for updates via support (forums are not the place for support) but it certainly looks like it's something with your setup, downgrading to supported drivers is likely the best first move until the next stable drivers are released.

View this comment - View article - View full comments

Quoting: jsa1983Good to see that bugs are being tackled. I had noticed the weird wheel trails, but not the other bugs (Speedometer and foliage).

What about the performance regression Phoronix reported while testing radeonsi with mesa 17.1 (http://www.phoronix.com/scan.php?page=article&item=rally-dirt-radeon&num=2)? Is that acknowledged and being investigated by someone?

We have not had any other reports of that performance regression so it's likely an issue that was related to the git version / build method that Phoronix used on that specific day.

Quoting: jsa1983I'm on mesa git-ish with llvm 5.0 (padoka packages) with a RX480 on Kubuntu 16.10 with an ultrawide 2560x1080 screen. My CPU is an AMD FX8370 with 16GB DDR3 RAM @1600MHz. I know this CPU pretty s*cks nowadays, but it should handle this game graciously (Autosport, for instance runs really well). (In any case I hope I can get a Ryzen in the mid term).

The possibilities of issues running git versions of drivers and compilers are numerous and not easily trackable. I'd revert your drivers to the supported ones Mesa 13 using LLVM 3.9 as per the supported spec and see what happens.

Quoting: jsa1983On another topic, edddeduck_feral, in your supported wheels steam page I asked if there have been any advancements with Fanatec. I'm looking forward to replacing my Logitech G27 pedals with something better like the Fanatec Clubsport Pedals. Is there anything you guys can share? Sadly I haven't been able to find anybody reporting the Fanatec pedals/wheels working on Linux.

(Sorry for the long post and for derailing the thread with the last question)

We're looking into it but new hardware takes time to get added and supported when we have news we'll certainly let everyone know.

View this comment - View article - View full comments

Yup, this one ( https://reviews.llvm.org/D30717 [External Link] ) specifically was an LLVM trunk regression from February causing white tyre tracks.

There were also a few other regressions to fix.

https://bugs.llvm.org//show_bug.cgi?id=31626 [External Link] caused some flickering bushes and another which was causing the speedometer issue Liam mentioned. This effected Mesa 17 (and Mesa 12!) but not Mesa 13 which is the version we released supporting.

https://github.com/llvm-mirror/llvm/commit/18b90cd7227909b1fdd3855786853ff065185382 [External Link] -> Flickering Foliage

https://reviews.llvm.org/D30609 [External Link] -> Speedo LLVM

A public thanks to Samuel for assisting in getting these issues in Mesa 17/LLVM fixed. Also thanks to many other developers who fixed some of the other regressions while we were looking for the cause!

View this comment - View article - View full comments

Quoting: GuestI’d love to play this but Steam-only + additional always online DRM means I’ll wait for a huge sale if I ever buy it.

There is no always online requirement for HITMAN. See the opening section from Liam's review for more details.

"To get the elephant in the room out of the way first: The game does have an online requirement for certain features, these are extras and do not affect the main single-player story, which does not require you to be online."

View this comment - View article - View full comments

Quoting: RedneckThanks for the explanation, i just wanted to say that specs ops and borderlands 2 ran pretty well after modifying the ini files. Didn't know about XCOM 2, sorry

No problem it's a pretty cool script and in many cases it might help out if the engine was not fully optimised for Linux :)

I just know for games like XCOM 2 we spent a lot of time optimising how the texture system worked (among other things) to get the best performance and remove stutters in the gameplay so modifying the ini files can cause negative effects.

View this comment - View article - View full comments

Quoting: LeflFinally!

I hope it fixes issues with XCOM: Enemy Unknown and Spec Ops the Line too, as both games had GPU lockups too

For people with Mesa/r600 we have had positive reports [External Link] that this issue fixes a hang in the AMD drivers. For some reason if you were using RadeonSI/Mesa & Intel/Mesa should not have been effected by this issue so they should have been alright anyway.

Quoting: Redneck

Quoting: LeflFinally!

I hope it fixes issues with XCOM: Enemy Unknown and Spec Ops the Line too, as both games had GPU lockups too

Spec ops and most unreal engine 3 games on Linux do not read the correct amount of VRAM causing bad performance, this script fix it by modifying config files: https://github.com/Kryuko/ue3_linux_opti [External Link]

It's perfectly safe and you only need to run it when you install new ue3 games, so it works for every game you have already installed (spec ops, borderlands and so on).
Hope it helps!

This will likely not help on Feral ports and with XCOM 2 (UE3 based) definitely will reduce performance compared to allowing the game to run on the default settings. We make changes to the engine and setup at a lower level and changing the ini files will impact the performance balancing lowering performance both in terms of frame rate but also in terms of frame smoothness.

View this comment - View article - View full comments

Quoting: boltronicsIt's way harder to get the game working at all on Machine 1. Could the issue be related to clock speed? I don't really want to undo my overclock, since it took many hours to perfect...

No, unless your CPU is failing in some way I doubt the overclock is a factor in your issue, I don't think you should need to undo any overclocking if everything else works perfectly.

Sounds more likely something in a subsystem what that could be is a mystery but I've logged your (super detailed) reports internally. If anything crops up that we think could be the cause of your problem we'll let you know but I would say the odds are fairly low due to the extremely low reproduction levels.

View this comment - View article - View full comments

Quoting: boltronicsAn update:
I'm running an up to date Debian stretch on amd64. I also tested Mesa 13.0.2 that's provided by the distribution, and that has the same problem as the builds I compile myself.

I had a little bit of time to look into this tonight. I didn't get too far since Mesa takes a long time to build (and then launching Steam and launching the game also adds time to each test). However I have identified the last good build was 12.0.5 stable. The next stable release is 13.0.0 which fails in the same way 13.0.2 does on my Fiji-based card. The timing sounds about right - it's probably been 1 to 2 months since the game has worked. Again, the game continues to work perfectly under Wine with 13.0.2 and the Gallium on Nine patches so it's not a big deal, just a bit annoying.

We have a Fiji card here (R9 Nano) it's pretty much the same hardware as the Fury X. We retested just now using running Mesa 13.0.2 (using the Padoka stable PPA Paulo Dias created for us the other day) our distro used is Ubuntu 16.10.

Everything runs perfectly with no issues on the latest release, we've also not had other reports. I suspect this might be related to something else linked to your system given stretch is the testing distribution it's completely possible some other related library in your distro is causing side effects. It's one of the reasons why we can't support rolling releases / testing distributions as things are in a state of constant flux.

Hope this helps you debug your issues further. Do let us know if you find anything we should know about.

View this comment - View article - View full comments

Quoting: liamdawePlease do not bring distro wars here, they are not welcome. All it does it get people riled up.

This seems apt :)

View video on youtube.com

View this comment - View article - View full comments

Quoting: boltronicsThat's fair. However checking the libraries would seem to be something fairly easy to automate for a bunch of different distributions, via chroots/schroot/pbuilder or some such.

There is a difference between assumption and reality on this problem, sadly it's not as simple as an automated script. :) The constant flux of a rolling distro combined with the steam runtime compatibility issues usually means a more manual approach is best/quicker, although we do have some automation present.

As we've mentioned our scripts are constantly evolving to work around issues with distros, certain libraries and hardware however when we make a change in the script we need to make sure it works well for all users with those effected by the issue and those that aren't.

Many workarounds posted are very specific to certain setups which means further analysis and tests need to be done you can't just paste them in, this is why you might get a delay between someones workaround for an unsupported distro on reddit and a similar solution built into the game launcher.

Quoting: boltronicsIt's a weird one, and I'm surprised nobody else has seen it since I've been experiencing it for a few weeks now. In fact, just last night I checked out the 13.0.2 git tag, and I still experienced corrupted graphics - built using llvm 3.9, with amdgpu as included in a clean Linux 4.9-rc7 build. This is on a Fury X (Fiji) card. Every time I click past the Feral launcher, all the graphics become garbled - something I don't think I've seen on any of my other games to date. It doesn't seem to be an issue when running the game under Wine, so I'm going to see if I can find time to do a regression test this weekend.

We haven't seen any major reports of issues from AMD GPU users which we would have expected if this was repeatable on multiple machines so I suspect it's related to a library you compiled or linked against. Every game will use OpenGL and other libraries in unique ways so you'll often see issues only on certain software and hardware combinations. If you do track something down that appears to be repeatable then do let our support know and/or log a bug with the Mesa devs so they can revert the change if needed or we can look at making a change in a patch as needed.

Edwin

View this comment - View article - View full comments