Proton
Proton copied to clipboard
ValveSoftware
No Man's Sky (275850)
Just to document it: Rendering in No Man's Sky don't work at this moment with amdgpu or radeonsi driver correctly. It seems to be a mix on crappy shader code and some issues with mesa. But there is a bug ticket on mesa's bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=107581
Processor Information:
CPU Vendor: AuthenticAMD
CPU Brand: AMD Ryzen 7 2700X Eight-Core Processor
CPU Family: 0x17
CPU Model: 0x8
CPU Stepping: 0x2
CPU Type: 0x0
Speed: 4000 Mhz
16 logical processors
8 physical processors
HyperThreading: Supported
FCMOV: Supported
SSE2: Supported
SSE3: Supported
SSSE3: Supported
SSE4a: Supported
SSE41: Supported
SSE42: Supported
AES: Supported
AVX: Supported
CMPXCHG16B: Supported
LAHF/SAHF: Supported
PrefetchW: Unsupported
Operating System Version:
Ubuntu 18.04.1 LTS (64 bit)
Kernel Name: Linux
Kernel Version: 4.17.13-041713-generic
X Server Vendor: The X.Org Foundation
X Server Release: 11906000
X Window Manager: Xfwm4
Steam Runtime Version: steam-runtime-beta-release_2018-06-14
Video Card:
Driver: X.Org AMD Radeon(TM) HD 8800 Series (PITCAIRN, DRM 3.25.0, 4.17.13-041713-generic, LLVM 8.0.0)
Driver Version: 4.4 (Compatibility Profile) Mesa 18.3.0-devel - padoka PPA
OpenGL Version: 4.4
Desktop Color Depth: 24 bits per pixel
Monitor Refresh Rate: 60 Hz
VendorID: 0x1002
DeviceID: 0x6810
Revision Not Detected
Number of Monitors: 2
Number of Logical Video Cards: 1
Primary Display Resolution: 1920 x 1080
Desktop Resolution: 3840 x 1080
Primary Display Size: 23.54" x 13.23" (26.97" diag)
59.8cm x 33.6cm (68.5cm diag)
Primary VRAM: 2048 MB
Sound card:
Audio device: ATI R6xx HDMI
Memory:
RAM: 16035 Mb
There's a fix for it but I don't believe its available right now. Should appear in mesa-dev soon.
https://www.phoronix.com/scan.php?page=news_item&px=RadeonSI-GL-4.5-Compat-Patches
This game actually has a issue with nvidia cards, it can't allocate vram correctly so you end up with texture and terrain mesh pop in that is quite bad.
If you switch between windows and linux and just pan/walk around you can see this effect quite obviously. Do 180deg turn and the textures slowly load in along with tessellation mesh etc...
this is probably a result of the game unable to detect correct amount of vram for the videocard for some reason and auto assigning quite a low amount instead of utilizing the GPU's full amount.
The warning can be turned off in NMS config but it doesn't fix the issue, no amount of setting fixes it.
Hello, today it seems now NMS is finally working, in some case... The white screen is gone and the game is playable. But the ground textures are glitching around. I use this ppa to get the newest mesa build: https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers They have merged the workarounds that i mentioned before and where discussed in this mesa bug report: https://bugs.freedesktop.org/show_bug.cgi?id=107581 I hope somebody can report back if he have the same issues with the ground textures.
No Man's Sky (App ID:275850) black screen on resolution higher than 1920*1080
Issue transferred from https://github.com/ValveSoftware/Proton/issues/1034. @Liodinis posted on 2018-08-30T22:52:04:
Ubuntu 18.04.1 LTS I7 6700K @ 4.00Ghz Nvidia GTX 1070 Nvidia driver 396.54 Proton 3.7-3 RAM 16Go SSHD 1To Toshiba H200 Display Acer Predator 24" 2560X1440
"No Man's Sky" doesn't work on resolution higher than 1920*1080.
Launch the game is displaying a black screen, but the game seems to be working, because sounds can be hear in background. If you put your screen resolution at 1920*1080 or edit the config file TKGRAPHICSSETTINGS.MXML with the native resolution of your screen at the place below :
/home/username/.local/share/Steam/steamapps/common/No Man's Sky/Binaries/SETTINGS
restart the game, and it will become playable.
No Man's Sky [App ID:275850] Crash on nvidia
Issue transferred from https://github.com/ValveSoftware/Proton/issues/1072. @hitchhiker54 posted on 2018-08-31T13:42:44:
The game plays flawlessly so far except for scanning when an npc base is in view. Tested on Minor Settlement and Observatory type, if the base is in view the game instantly crashes to desktop when in visor view. Player bases, ships, exocraft all seem to be fine. Using gtx980ti, i76700k on Ubuntu 18.04, Nvidia drivers 396.54
[edits additional] Game version 1.58, issue also reported to Hello Games
sudo lshw results : https://www.dropbox.com/s/xxu34qjfnjp7f01/specs.txt?dl=0
Ubuntu 16.04, NVIDIA GTX 970, Proton 3.7-5 Beta:
| Test | Result |
|---|---|
| Singleplayer | Working as expected |
| Local Co-op | N/A |
| Online Multiplayer | Working as expected |
| Configuration | ... |
|---|---|
| Input | Steam Controller |
| Display | 1920x1080 |
| Fullscreen | Yes |
| Preset | Medium^ |
| VSync | Off^^ |
| API | OpenGL |
^ Default graphics preset is High ^^ Default VSync setting is On
Tried with Proton 3.7-3.
The game worked flawlessly. With my setup. Attached pastebin shows the specs of my machine and versions of all relevant drivers/software.
My specs: https://pastebin.com/9hQP94N1
Yes it works technically better then on windows for me because on windows I can't remove screen tearing without vsync enable which seems to cost fps. But under linux with vsync off there is no tearing.
I did find the game caches textures a bit slow on NTFS, you can speed it up a bit by using big_writes in the disk drive mount options. Or move it to BTRFS or EXT4 drive.
No Man's Sky seems to actually run smoother on my aging graphics card in Linux! Seems to be working out of the box.
Fedora 28 Core i7-4770 Nvidia GTX 760 Proton 3.7-3
I had the same black screen issues as comment: https://github.com/ValveSoftware/Proton/issues/438#issuecomment-417493922
In the same TKGRAPHICSSETTINGS.MXML file, setting "Borderless" to True will also allow the game to run properly, even if the desktop resolution is higher than the game's resolution. I want to run games at 1920x1080 for any recording/streaming, but my desktop is set to 1920x1200, setting the borderless option allows me to do so.
In Windows have no problem just setting my monitor to 1920x1080 when needed, but in Linux I am having an issue which I suspect is with my DVI cable, that's not letting the system recognize any 16:9 resolutions for this monitor, and I've been unable to add them with xrandr (keep getting a BadMatch error when trying to add it to DVI-I-1.) I've got a DisplayPort cable on order that I'm hoping will open up the full range of resolutions my monitor is capable of. My second monitor connected via HDMI has all of it's modes properly recognized, my main monitor doesn't have an HDMI port or I would have tested it to be sure it's the DVI cable.
Update: It was the DVI cable. DP cable came in last week and all display modes/resolutions are available now.
[ISSUE] No Man`s Sky no sound ( 275850)
Issue transferred from https://github.com/ValveSoftware/Proton/issues/1459. @Rainakins posted on 2018-09-15T09:23:49:
Compatibility Report
- Name of the game with compatibility issues: No Man`s Sky
- Steam AppID of the game: 275850
System Information
- GPU: GTX 1050ti
- Driver/LLVM version: Nvidia 396.54
- Kernel version: 4.15
- Link to full system information report as Gist:
Computer Information: Manufacturer: Unknown Model: Unknown Form Factor: Desktop No Touch Input Detected
Processor Information:
CPU Vendor: AuthenticAMD
CPU Brand: AMD Ryzen 5 2600 Six-Core Processor
CPU Family: 0x17
CPU Model: 0x8
CPU Stepping: 0x2
CPU Type: 0x0
Speed: 3400 Mhz
12 logical processors
6 physical processors
HyperThreading: Supported
FCMOV: Supported
SSE2: Supported
SSE3: Supported
SSSE3: Supported
SSE4a: Supported
SSE41: Supported
SSE42: Supported
AES: Supported
AVX: Supported
CMPXCHG16B: Supported
LAHF/SAHF: Supported
PrefetchW: Unsupported
Operating System Version: Ubuntu 18.04.1 LTS (64 bit) Kernel Name: Linux Kernel Version: 4.15.0-34-generic X Server Vendor: The X.Org Foundation X Server Release: 11906000 X Window Manager: GNOME Shell Steam Runtime Version: steam-runtime-beta-release_2018-06-14
Video Card: Driver: NVIDIA Corporation GeForce GTX 1050 Ti/PCIe/SSE2 Driver Version: 4.6.0 NVIDIA 396.54 OpenGL Version: 4.6 Desktop Color Depth: 24 bits per pixel Monitor Refresh Rate: 60 Hz VendorID: 0x10de DeviceID: 0x1c82 Revision Not Detected Number of Monitors: 1 Number of Logical Video Cards: 1 Primary Display Resolution: 1920 x 1080 Desktop Resolution: 1920 x 1080 Primary Display Size: 20.08" x 11.30" (23.03" diag) 51.0cm x 28.7cm (58.5cm diag) Primary Bus: PCI Express 16x Primary VRAM: 4096 MB Supported MSAA Modes: 2x 4x 8x 16x
Sound card: Audio device: Nvidia GPU 80 HDMI/DP
Memory: RAM: 16052 Mb
Miscellaneous: UI Language: English LANG: en_US.UTF-8 Total Hard Disk Space Available: 194192 Mb Largest Free Hard Disk Block: 107787 Mb VR Headset: None detected
Recent Failure Reports:
- Proton version: 3.7-6
I confirm:
- [ x ] that I haven't found an existing compatibility report for this game.
- [ x ] that I have checked whether there are updates for my system available.
Symptoms
The sound was working initially for about a week and for some reason yesterday the sound completely stopped working everything else still runs fine and performance is great but the sound simply does not work any longer
Reproduction
for me its easily done by launching the game
For me the game freezes after difficulty selection. I just get a black screen, and GNOME becomes completely unresponsive. The sound for the game continues, however, I am unable to interact with the computer further, and a hard reset is required. I have tried manually changing the game to borderless and windowed modes to no effect.
I'm using an R9 Fury, Mesa 18.3, LLVM 8 from Padoka unstable as recommended by Proton, and kernel 4.18.8.
What does ulimit -aH tell you? could be a limited open files issue which is often associated with load freezes.
output of ulimit -aH
core file size (blocks, -c) unlimited
data seg size (kbytes, -d) unlimited
scheduling priority (-e) 0
file size (blocks, -f) unlimited
pending signals (-i) 63415
max locked memory (kbytes, -l) 16384
max memory size (kbytes, -m) unlimited
open files (-n) 4096
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority (-r) 0
stack size (kbytes, -s) unlimited
cpu time (seconds, -t) unlimited
max user processes (-u) 63415
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited
Hello @viggy96, give https://github.com/zfigura/wine/blob/esync/README.esync a read and increase the max open files limit on your system.
@kisak-valve I thought I did it properly before, but apparently not, LOL. However, regardless, No Man's Sky still fails in the same way for me. output of ulimit -aH
core file size (blocks, -c) unlimited
data seg size (kbytes, -d) unlimited
scheduling priority (-e) 0
file size (blocks, -f) unlimited
pending signals (-i) 63415
max locked memory (kbytes, -l) 16384
max memory size (kbytes, -m) unlimited
open files (-n) 1048576
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority (-r) 0
stack size (kbytes, -s) unlimited
cpu time (seconds, -t) unlimited
max user processes (-u) 63415
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited
I still can't seem to get past the black screen on this game. Not sure what could be causing this. I've increased the max open files limit, as above, but still no dice.
Nvidia 396.54.09, Geforce GTX 1050ti, Proton 3.16-1 Beta, Slackware 14.2 multilib. After this morning's update to Proton 3.16-1, I'm getting an error saying No Man's Sky needs at least 1.5 GB of VRAM and that the adapter (blank) is reporting 0. The game loads and plays just fine, if you click through, though. Bug? Or something I need to change?
@SwooshyCueb Yes, I am. I still can't get past the black screen. I've tried editing the game settings file to use borderless mode, as some other have suggested, but still No Man's Sky doesn't work for me.
I'm using an R9 Fury, Mesa 18.3, LLVM 8 from Padoka unstable as recommended by Proton, and kernel 4.18.8.
Only thing I can suggest is don't use experimental drivers and LLVM8, go back to release mesa version 18.2.x and try LLVM 7.0
I know Ubuntu repos are terrible for getting latest stable version drivers sometimes, I use antergos personally.
@viggy96 If you're feeling adventurous, you could give https://launchpad.net/~kisak/+archive/ubuntu/steamvr a try (kernel and xorg-server should not be needed for this), otherwise https://launchpad.net/~paulo-miguel-dias/+archive/ubuntu/pkppa is a relatively safe bet.
@kisak-valve Unfortunately, the stable Padoka PPA does not solve the issue for me. I also tried disabling the Steam overlay, but to no avail. Also, to update, I'm using kernel 4.19 currently. Its a very strange issue, as even the GNOME desktop locks up, and I am forced to hard reset my computer.
Might be a Fury R9 and AMDGPU driver issue perhaps? not many people have the Fury cards anymore.
I have a 1080Ti because 4k and AMD has yet to support 4k gaming at 60fps, once they do then I'll move back to AMD GPU's and be able to experience all the AMD related steamplay bugs people get.
ATM the major issue with NVIDIA cards is the libraries some games attempt to use are incompatible with Wine/Proton, which is why they introduced the spoofing trick recently.
I have an issue with rendering all 3d content in game (all black in loading, white in game). All menus works well.
Changing settings has no effect. Tested on Ubuntu 18.04 LTS and Solus 3.99 - same result. (On ubuntu also try the latest amdgpu drivers from amd website)
specs: Radeon RX 580 Series (POLARIS10, DRM 3.26.0, 4.18.16-97.current, LLVM 7.0.0) AMD® Ryzen 5 1600x six-core processor × 12 7,8 Gb RAM
The drivers off AMD's website are amdgpu-pro
The ones you will want to try are oibaf package on launchpad which should be compatible with any ubuntu based distro (not sure if solus is).
@jarrard solus is ubuntu-based, but it have it's own package system. I returned to ubuntu 18.04 and tried oibaf repo and it works well now, thanks a lot.
Works on my system (Ubuntu 18.04 with Mesa 19 Git R9 290)
OpenGL vendor string: X.Org OpenGL renderer string: AMD Radeon R9 200 Series (HAWAII, DRM 3.26.0, 4.18.19-041819-generic, LLVM 7.0.1) OpenGL core profile version string: 4.5 (Core Profile) Mesa 19.0.0-devel (git-fbf95ce 2018-11-29 bionic-oibaf-ppa) OpenGL core profile shading language version string: 4.50 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 4.5 (Compatibility Profile) Mesa 19.0.0-devel (git-fbf95ce 2018-11-29 bionic-oibaf-ppa) OpenGL shading language version string: 4.50 OpenGL context flags: (none) OpenGL profile mask: compatibility profile OpenGL extensions: OpenGL ES profile version string: OpenGL ES 3.2 Mesa 19.0.0-devel (git-fbf95ce 2018-11-29 bionic-oibaf-ppa) OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20 OpenGL ES profile extensions:
It has some visual glitches, some trees display white artifacts on the border of the leaves and branches.
Bush-like plants and grass appear and re-appear in front of you as if they disolve due to distance, but they're in front of you.
Other than that 100+ hours playing on Linux!
