Steamをインストール
ログイン
|
言語
简体中文(簡体字中国語)
繁體中文(繁体字中国語)
한국어 (韓国語)
ไทย (タイ語)
български (ブルガリア語)
Čeština(チェコ語)
Dansk (デンマーク語)
Deutsch (ドイツ語)
English (英語)
Español - España (スペイン語 - スペイン)
Español - Latinoamérica (スペイン語 - ラテンアメリカ)
Ελληνικά (ギリシャ語)
Français (フランス語)
Italiano (イタリア語)
Bahasa Indonesia(インドネシア語)
Magyar(ハンガリー語)
Nederlands (オランダ語)
Norsk (ノルウェー語)
Polski (ポーランド語)
Português(ポルトガル語-ポルトガル)
Português - Brasil (ポルトガル語 - ブラジル)
Română(ルーマニア語)
Русский (ロシア語)
Suomi (フィンランド語)
Svenska (スウェーデン語)
Türkçe (トルコ語)
Tiếng Việt (ベトナム語)
Українська (ウクライナ語)
翻訳の問題を報告
For games that will use the older D3D to OpenGL translation layer. Or (if you will be using Vulkan for DXVK/D9VK) you will need to ensure that the applicaion uses the nvidia vulkan layer, like:
Yes it is tedious to have to do that for every game you want to run on the discrete graphics adapter, but works much better than Bubmblebee and with far better performance, for the recod I have driver 440.64 on my Fedora 31 laptop.
Hope this helps. For further reference, check the documentaton provided by the nvidia-driver readme, chapter 34.
Just find and rename "user_settings.sample.py" to "user_settings.py" and modify it appropriately.
This file is located in the Proton installation directory in your Steam library (often ~/.steam/steam/steamapps/common/Proton #.#).
Any driver new enough to use GLVND can use Prime.
And since all Windows game I have use a DirectX backend, it's screwed.
@Aoi Blue is Prime an alternative to bumblebee? I struggled configuring bumblebee so if I have to spend days for it I think I'll pass.
Edit
That is the exact situation that lead me to investigate Prime on my laptop, and thankfully nVidida had been hard at work on bringing better support for Optimus and thus supporting Prime.
Since he uses 390 drivers in his setup, I'd assume at least a Kepler class dGPU or newer.
Edit
Did a quick check, the 390.132 driver supports back to Fermi class GPUs, but does not support Prime, at most, supports randr, which can be flaky.
pressure-vent.sh https://gist.github.com/evg-zhabotinsky/cd54c8d8bf3803599d3b33cc56e6fbc0
Long story short: Proton forces use of the Soldier runtime that is packed in a "Pressure Vessel" container, and the latter seems to just wipe LD_PRELOAD and LD_LIBRARY_PATH. The script cuts the container out of command line, leaving only Proton and the game.
You will have to install all dependencies manually, though. If some are missing Proton just won't start.