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 (ベトナム語)
Українська (ウクライナ語)
翻訳の問題を報告
Yeah, you're probably seeing the performance issues that I mentioned earlier. And if your experience is anything like mine, you'll also find that the framerate plummets in select areas such as the Tower lobby or near Zere's trailer. The game triggers some suboptimal memory management in the driver that results in a lot of swapping between different areas of memory. I submitted kernel patches to fix this; they're in the queue for Linux 4.14. Hopefully it'll help :)
https://www.phoronix.com/scan.php?page=news_item&px=AMDGPU-VRAM-D-Games
Do you have a intel HD card?
Are the start options not working or did they change?
Arch Linux 64 bit, mesa 17.2.3 , kernel 4.13.9 on AMD RX480.
You definitely shouldn't be getting the version mismatch message with those environment variables set. I would carefully check the launch options for typos.
I can start up the game with MESA_GL_VERSION_OVERRIDE=4.4 MESA_GLSL_VERSION_OVERRIDE=440 %command% or MESA_GL_VERSION_OVERRIDE=4.5 MESA_GLSL_VERSION_OVERRIDE=450 %command% but after that I get a multicolor pixeled screen for a moment, which looks to me like corrupted memory output. Then it gets dark and a white line is slowly progressing on the bottom from left to right till after a few minutes, the game shuts down.
Now being on mesa 17.2.4 and Kernel 4.13.11
Without the launch options I get:
1. The unsupported version of OpenGL message
2. A black screen which slowly loads a white line at the bottom for a few seconds before crashing
With the launch options I get:
1. Garbled graphics for a few seconds
2. A black screen which slowly loads a white line at the bottom for a few seconds before crashing
I'm running Debian testing with kernel version 4.14.0, mesa version 17.3.3 on an AMD RX 470.
{07:00:04.229} INFO: [INFO] > [OpenGL] MajorVersionDetected=4 MinorVersionDetected=5
{07:00:04.229} INFO: [INFO] > [OpenGL] Extension ARB_debug_output is supported
{07:00:04.229} INFO: [INFO] > [OpenGL] Extension ARB_blend_func_extended is supported
****HERE****{07:00:04.229} INFO: [INFO] > [OpenGL] Video memory detected: 0 [MB]!
{07:00:04.302} INFO: [INFO] > [OpenGL] GPU's vendor id: 4098 [0x1002]; GPU's device id: 26607 [0x67ef].
{07:00:04.302} INFO: [INFO] > [OpenGL] Shader binary dir = 4_5_Mesa_18_0_4.
{07:00:04.302} INFO: [INFO] > [OpenGL] GL_UNIFORM_BUFFER_OFFSET_ALIGNMENT = 4
{07:00:04.302} INFO: [INFO] > [OpenGL] GL_MAX_UNIFORM_BLOCK_SIZE = 65536
{07:00:04.808} INFO: [INFO] > Texture streaming lowest priority distance set to 100m
{07:00:05.372} INFO: [INFO] > [SDL::WindowMode] Current SwapInterval: 0
{07:00:05.372} INFO: [INFO] > [SDL::SetWindowMode] Setting no vsync resulted in: 0 SDL_GetError: Surface doesn't have a colorkey
{07:00:05.372} INFO: [INFO] > [SDL::WindowMode] Current SwapInterval: 0
{07:00:05.428} INFO: [INFO] > [SDL] Resizing window to 3840x2160 f:1 v:0
{07:02:12.818} INFO: [INFO] > Texture streaming buffer set to 400MB
{07:02:12.834} INFO: [INFO] > >>>>> Audio init
{07:02:13.109} INFO: [INFO] > FMOD::Driver: Default Output Device
{07:02:13.225} INFO: [INFO] > FMOD is using (11) output type.
{07:02:13.225} INFO: [INFO] > FMOD Software Format Info:
{07:02:13.225} INFO: [INFO] | Out Sample Rate: <48000>
{07:02:13.225} INFO: [INFO] | Format: <2>
{07:02:13.225} INFO: [INFO] | Out Channels: <2>
{07:02:13.225} INFO: [INFO] | Max Input Channels: <8>
{07:02:13.225} INFO: [INFO] | Bits: <16>
{07:02:13.225} INFO: [INFO] > FMOD Mixer blocksize = 21.33 ms
{07:02:13.225} INFO: [INFO] > FMOD Mixer blocks count = 4
{07:02:13.225} INFO: [INFO] > FMOD Mixer Total buffer size = 85.33 ms
{07:02:13.225} INFO: [INFO] > FMOD Mixer Average Latency = 53.33 ms
{07:02:13.356} INFO: [INFO] > Caught signal 11 (Segmentation fault).
{07:02:13.390} INFO: [INFO] > /usr/lib/libc.so.6(+0x368f0) [0x7fc3d3d9e8f0]
{07:02:13.390} INFO: [INFO] | libengine.so(_ZN12CTextManager10InitializeEv+0x26f) [0x7fc3d58640cf]
{07:02:13.390} INFO: [INFO] | libengine.so(_Z13CreateTextMgrv+0x40) [0x7fc3d5864220]
{07:02:13.390} INFO: [INFO] | libengine.so(_ZN9CRenderer13LoadResourcesEv+0x2c) [0x7fc3d585187c]
{07:02:13.390} INFO: [INFO] | libengine.so(_ZN5CGame10InitializeEPciPvS1_jjP18IProgressIndicator+0x1944) [0x7fc3d53298b4]
{07:02:13.390} INFO: [INFO] | /home/user/.local/share/Steam/steamapps/common/Dying Light/DyingLightGame(main+0xa45) [0x43e315]
{07:02:13.390} INFO: [INFO] | /usr/lib/libc.so.6(__libc_start_main+0xeb) [0x7fc3d3d8b06b]
{07:02:13.390} INFO: [INFO] | /home/user/.local/share/Steam/steamapps/common/Dying Light/DyingLightGame() [0x4425d9]
Yes.
Would love to be able to play the game.
edit: Figured it out, looks like some linux enthusiasts solved the issue for the game developers. Check out the comments here:
https://www.gamingonlinux.com/forum/topic/2766/page=16
You need to download (from the thread) and copy libGL.so.1 to your ~/.local/share/Steam/steamapps/common/Dying Light directory.
There are occasional crashes, but those are also common place in the win version. Every 5 to 6 hours and when doing a special move, stabbing from above with extra force, those crashes happen. Nonetheless, it is very playable :D
Hope you guys finally get a fix.