安装 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（越南语）
Українська（乌克兰语）
报告翻译问题
讨论规则及指引
1 
举报此帖
This does not mean Gallium or the d3dadapter9 shim are "broken". Rather it is most likely this has something to do with misconfiguring the d9vk vs d3dadapter9 priority.
Between Wayland migration and Nvidia driver issues it's not surprising to see out of trunk failures like this.
You're kinda right. Its a rather simple fix. What happening is that d3d9.dll to symlinks to the d3d9-nine.dll is replaced with the d9vk or wine3d dll in the proton's folder. Although to try to fix this with running proton from terminal and enabling galliumnine after game launches (launches to a launcher that doesn't use directx). I Also tired replacing the dll's to no fruit. Throws the "A fatal DirectX error has occured.(10000000)". Probably has to do something with other than dll swapping
Edit2: I'm now downloading pcmark10 to see if its a driver issue or not
Edit: the error code below:
```
utku3@utku3:~$ D3D_MODULE_PATH="/usr/lib/i386-linux-gnu/d3d:/usr/lib/i386-linux-gnu/d3d" STEAM_COMPAT_CLIENT_INSTALL_PATH='/mnt/ST1000DM/SteamLibrary/steamapps/common/FINAL FANTASY XIV Online' STEAM_COMPAT_DATA_PATH="/mnt/ST1000DM/SteamLibrary/steamapps/compatdata/39210" GALLIUM_HUD="sensors_temp_cu-amdgpu-pci-0300.edge,fps,cpu,GPU-load" PROTON_USE_CUSTOMD3D9=1 PROTON_NO_D9VK=1 DXVK_HUD=full gamemoderun /home/utku3/.local/share/Steam/ubuntu12_32/reaper SteamLaunch AppId=39210 -- '/home/utku3/.local/share/Steam/steamapps/common/SteamLinuxRuntime_soldier'/_v2-entry-point --verb=waitforexitandrun -- '/home/utku3/.local/share/Steam/compatibilitytools.d/Proton-7.0rc2-GE-1'/proton waitforexitandrun '/mnt/ST1000DM/SteamLibrary/steamapps/common/FINAL FANTASY XIV Online/boot/ffxivboot.exe' -issteam
ERROR: ld.so: object '/usr/$LIB/libgamemodeauto.so.0' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
gamemodeauto:
gamemodeauto:
pressure-vessel-adverb[177339]: W: Unable to generate locales: Child process exited with code 1
gamemodeauto: dlopen failed - libgamemode.so: cannot open shared object file: No such file or directory
gamemodeauto: dlopen failed - libgamemode.so: cannot open shared object file: No such file or directory
ProtonFixes[177348] INFO: Running protonfixes
ProtonFixes[177348] INFO: Running checks
ProtonFixes[177348] INFO: All checks successful
ProtonFixes[177348] INFO: Using global defaults for UNKNOWN (39210)
ProtonFixes[177348] INFO: Using protonfix for UNKNOWN (39210)
gamemodeauto: dlopen failed - libgamemode.so: cannot open shared object file: No such file or directory
gamemodeauto: dlopen failed - libgamemode.so: cannot open shared object file: No such file or directory
gamemodeauto: dlopen failed - libgamemode.so: cannot open shared object file: No such file or directory
gamemodeauto: dlopen failed - libgamemode.so: cannot open shared object file: No such file or directory
gamemodeauto: dlopen failed - libgamemode.so: cannot open shared object file: No such file or directory
wineserver: using server-side synchronization.
gamemodeauto: dlopen failed - libgamemode.so: cannot open shared object file: No such file or directory
gamemodeauto: dlopen failed - libgamemode.so: cannot open shared object file: No such file or directory
gamemodeauto: dlopen failed - libgamemode.so: cannot open shared object file: No such file or directory
gamemodeauto: dlopen failed - libgamemode.so: cannot open shared object file: No such file or directory
gamemodeauto: dlopen failed - libgamemode.so: cannot open shared object file: No such file or directory
gamemodeauto: dlopen failed - libgamemode.so: cannot open shared object file: No such file or directory
gamemodeauto: dlopen failed - libgamemode.so: cannot open shared object file: No such file or directory
gamemodeauto: dlopen failed - libgamemode.so: cannot open shared object file: No such file or directory
gamemodeauto: dlopen failed - libgamemode.so: cannot open shared object file: No such file or directory
gamemodeauto: dlopen failed - libgamemode.so: cannot open shared object file: No such file or directory
gamemodeauto: dlopen failed - libgamemode.so: cannot open shared object file: No such file or directory
ERROR: ld.so: object '/tmp/pressure-vessel-libs-MDVUF1/${PLATFORM}/libgamemodeauto.so.0' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
gamemodeauto: dlopen failed - libgamemode.so: cannot open shared object file: No such file or directory
gamemodeauto: dlopen failed - libgamemode.so: cannot open shared object file: No such file or directory
gamemodeauto: dlopen failed - libgamemode.so: cannot open shared object file: No such file or directory
ERROR: ld.so: object '/tmp/pressure-vessel-libs-MDVUF1/${PLATFORM}/libgamemodeauto.so.0' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object '/tmp/pressure-vessel-libs-MDVUF1/${PLATFORM}/libgamemodeauto.so.0' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
Unable to read VR Path Registry from C:\users\steamuser\AppData\Local\openvr\openvrpaths.vrpat
h
Unable to read VR Path Registry from C:\users\steamuser\AppData\Local\openvr\openvrpaths.vrpat
h
Unable to read VR Path Registry from C:\users\steamuser\AppData\Local\openvr\openvrpaths.vrpat
h
Unable to read VR Path Registry from C:\users\steamuser\AppData\Local\openvr\openvrpaths.vrpat
h
Unable to read VR Path Registry from C:\users\steamuser\AppData\Local\openvr\openvrpaths.vrpat
h
Unable to read VR Path Registry from C:\users\steamuser\AppData\Local\openvr\openvrpaths.vrpat
h
ERROR: ld.so: object '/tmp/pressure-vessel-libs-MDVUF1/${PLATFORM}/libgamemodeauto.so.0' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
err:d3d9nine:common_load_d3dadapter Failed to load d3dadapter9.so.1 set by D3D_MODULE_PATH (/usr/lib/i386-linux-gnu/d3d:/usr/lib/i386-linux-gnu/d3d)
Native Direct3D 9 will be unavailable.
For more information visit https://github.com/iXit/wine-nine-standalone
err:d3d9nine:d3dadapter9_new Your display driver doesn't support native D3D9 adapters.
err:d3d9nine:d3dadapter9_new Your display driver doesn't support native D3D9 adapters.
fixme:d3d9nine:D3DPERF_SetOptions (0x1) : stub
err:d3d9nine:d3dadapter9_new Your display driver doesn't support native D3D9 adapters.
gamemodeauto: dlopen failed - libgamemode.so: cannot open shared object file: No such file or directory
gamemodeauto: dlopen failed - libgamemode.so: cannot open shared object file: No such file or directory
gamemodeauto: dlopen failed - libgamemode.so: cannot open shared object file: No such file or directory
gamemodeauto: dlopen failed - libgamemode.so: cannot open shared object file: No such file or directory
gamemodeauto: dlopen failed - libgamemode.so: cannot open shared object file: No such file or directory
utku3@utku3:~$
```
There is a reason, to run software that the current hardware is too weak to handle. 32 bit software is still supported for Windows 10 and 11, albeit the former dropping support of 32 bit hardware as of version 2004.
Nope it never will with a market share of less than 5% of the PC userbase. Stay mad
And strong power of Unix philosophy is scaleability and portability.
Creating artificial obsolence of hardware like on Winblows is a sin.
- This should be easy to verify by running `gamemoded -s` before a game launches, then again while it is running.
As for d3dadapter9, it seems like making a few wine bottles to experiment with non Proton builds might be necessary so we can check alternate driver installs and vanilla wine builds against Proton.
This is Linux, people are allowed to have fun.
So they're in a cosmic sense defending every company ever involved with open source and/or customization of PCs, including (but not limited to): AMD (surprise, surprise), Antec, Acer, Arctic, AsRock, ASUS, Benq, Be Quiet!, Colorful, Corsair, CoolerMaster, Cryorig, DeepCool, ekwb, EVGA, Fractal, Gigabyte, G.Skill, HyperX, Intel (what do ya know), InWin, KoLink, LianLi, MSi, Nvidia (ironic ha), Patriot, ThermalTake, OBT, RaijinTek, Razer, Saphire, SilverStone, SteelSeries, TeamGroup, XPG, XFX, Zotac, and more. And by hating on consoles, the Scandinavian is also shilling for these corporations: Dell, Huawei, Lenovo, XiaoMi, Apple, HP, Sony (surprise, surprise), Toshiba, Samsung, LG, Qualcomm, ARM, Google (insert evil mocking laughter here) and bunch of other PC OEM vendors.
Reiterating facts regarding corporations =/= defending them or being a "shill". There's no point in even defending or criticizing specific companies here in these forums because they won't even read them, and nobody here receives any form of compensation for doing so. Maybe if this was YouTube or Twitter and one was into content creation, being a shill or critic would actually be worth it. Actually it wouldn't because ad revenue barely generates any income and begging people to donate to Patreon, SubscribeStar, OnlyFans, etc., doesn't qualify as working in a technical and legal sense. LOL the Scandinavian can't handle the truth so had to get the moderators to censor me again, cry more. :)