protonscr

RIFT

protonopen appid 39120Game compatibility - UnofficialRegression
ValveSoftware/Proton#689 · opened 2018-08-26 by supashang · updated 2025-11-23 · 17 comments · github · game page · search this game
Ssupashang 2018-08-26 github

Observed: Game launches but game gfx are all blacked out on menu and in game.
Steam Play: Proton 3.7-4 Beta

screenshot at 2018-08-27 18-00-22

Description: Ubuntu 18.04.1 LTS
Release: 18.04
Codename: bionic
Kernel: 4.18.4-041804-generic #201808220230
Full System Info: https://gist.github.com/supashang/6050de4e5ed8854f58d7152521048170

Gist: https://gist.github.com/supashang/56406a31d70a6992f17f1eec98ed34b0

Intel Core i7 4790K @ 4.3GHz, ASUSTeK COMPUTER INC. Z97-PRO GAMER (SOCKET 1150), Corsair Vengeance Low Profile 16GB Dual-Channel DDR3, 4GB NVIDIA GeForce GTX 970 OC STRIX, Samsung SSD 840 & 850 EVO

Nnstgc 2018-08-26 github

For what its worth, I've had extremely good luck with Rift for the last several years, so this is a regression from normal Wine. Shame the servers are deserted.

Ssupashang 2018-08-26 github

Yea, I've had it working under normal WINE in the past too. However, there are graphical bugs. The UI was flashing constantly and world graphics and gameplay was stuttering. In Proton the UI displays fine and the FPS seems to faster - if only the game graphics would display it would be silky smooth.

Nnstgc 2018-08-26 github

Really? As of. . .20015(?) I had it working nearly perfectly. I'd occasionally there were would graphical errors on recently loaded stuff (as you're moving around) but it quickly returned to normal. I ran content and everything.

Kkisak-valve maintainer 2018-08-26 github

Hello @supashang, please copy your system information from steam (Steam -> Help -> System Information) and put it in a gist, then include a link to the gist in this issue report.

Ssupashang 2018-08-27 github

System info Gist included in original post. Thanks.

?ghost 2018-11-05 github

Any update regarding this issue?

Ffls2018 2018-11-06 github

Fix it with winetricks using this in terminal:

WINEPREFIX=/path/to/steamapps/compatdata/39120/pfx winetricks d3dcompiler_43 d3dx9_43

?ghost 2018-11-06 github

Works like a charm!!!

Bbenbrockn 2018-12-26 github

Can confirm, worked for me as well. Thank you all so much!

Proof: https://gist.github.com/benbrockn/04aad8ec6ce4f0d8fd46cb53a4c0bcc2

Ssupashang 2019-02-13 github

Works great with

WINEPREFIX=/path/to/steamapps/compatdata/39120/pfx winetricks d3dcompiler_43 d3dx9_43

No more black texture bugs.
Thanks fls2018

Ooxr463 2019-05-24 github

This game runs flawlessly for me.

Ubuntu 18.04 LTS
AMD A10-6700 APU with Radeon(tm) HD Graphics / Asus GeForce GTX 750 TI
Proton 4.2-4

Bbenbrockn 2020-11-16 github

Rift is broken again as of Proton 5.13-2, works fine on Proton 5.0-10.

Loads to the character screen, then when you click 'play'. it loads the actual game, freezes at about 10-12% loading, then crashes with a RIFT error box asking to send an error report to Trion (game dev).

steam-39120.log

@kisak-valve

Aalasky17 2020-11-16 github

@benbrockn I'm not seeing an issue playing either Rift or Just Cause 3. Could you attach your system specs? (output of Help -> System Information in Steam) Did you try these games on 5.13-1?

Bbenbrockn 2020-11-17 github

@benbrockn I'm not seeing an issue playing either Rift or Just Cause 3. Could you attach your system specs? (output of Help -> System Information in Steam) Did you try these games on 5.13-1?

Specs:

  • OS: EndeavourOS Linux x86_64
  • Kernel: 5.9.1-arch1-1
  • Shell: bash 5.0.18
  • Resolution: 2560x1440 @ 144Hz, 1920x1080 @ 60Hz
  • DE: Xfce
  • WM: Xfwm4
  • CPU: AMD Ryzen 7 2700 (16) @ 3.966GHz
  • GPU: NVIDIA GeForce GTX 1080
  • Memory: 32 GB @ 3200 MHz

sys_info_gist.txt

I don't have access to Proton 5.13-1, only 5.13-2. Other Proton versions available:

  • 3.7-8
  • 3.16-9
  • 4.2-9
  • 4.11-13
  • 5.0-10
  • 5.9-GE-7-ST
  • 5.9-GE-8-ST
  • 5.13-2
Kkisak-valve maintainer 2020-11-17 github

Hello @benbrockn, it looks like OpenGL is misconfigured on your system. While you intended for it to use the nVidia GPU, mesa's faster software renderer, llvmpipe, ended up getting used. I'm not familiar with EndeavourOS to make any suggestions on how this happened, but you should be able to use glxinfo -B from mesa-demos to test quickly.

Bbenbrockn 2020-11-17 github

Hmm that's weird, I'll check that out and report back. EndeavourOS is just a graphical arch distro, if that helps.

Bbenbrockn 2020-11-18 github

Updated

@kisak-valve

In order to install mesa-demos, I had to update my system with sudo pacman -Syy && sudo pacman -Syu.

Here are my updated specs:

  • OS: EndeavourOS Linux x86_64 (Arch-based Distro with GUI-installer, spiritual successor to Antergos)
  • Kernel: 5.9.8-arch1-1
  • Shell: bash 5.0.18
  • Resolution: 1440p @ 144Hz, & 1080p @ 60Hz (Using 1 X-Screen)
  • DE: Xfce
  • WM: Xfwm4
  • CPU: AMD Ryzen 7 2700 @ 3.966GHz
  • GPU: NVIDIA GeForce GTX 1080, 8GB VRAM
  • Driver: 4.6.0 NVIDIA 455.38
  • OpenGL: 4.6
  • RAM: 32 GB @ 3200 MHz

Here's the output of glxinfo -B:

name of display: :0.0
display: :0  screen: 0
direct rendering: Yes
Memory info (GL_NVX_gpu_memory_info):
    Dedicated video memory: 8192 MB
    Total available memory: 8192 MB
    Currently available dedicated video memory: 7973 MB
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: GeForce GTX 1080/PCIe/SSE2
OpenGL core profile version string: 4.6.0 NVIDIA 455.38
OpenGL core profile shading language version string: 4.60 NVIDIA
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 4.6.0 NVIDIA 455.38
OpenGL shading language version string: 4.60 NVIDIA
OpenGL context flags: (none)
OpenGL profile mask: (none)

OpenGL ES profile version string: OpenGL ES 3.2 NVIDIA 455.38
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

Proton versions

Launch options