-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Game] Wildstar - "Failed to Initialize Direct3D" #274
Comments
What card are u trying to use
…On Mar 9, 2017 4:23 PM, "PadreAdamo" ***@***.***> wrote:
Greetings! I am having an issue on game launch. A dialog promp displays
"Failed to Initialize Direct3D." I ran the game with NINE_DEBUG=all
My other WINE NINE games run perfectly fine without issue. The items in
the log that standout to me are:
fixme:ddraw:ddraw7_Initialize Ignoring guid {aeb2cdd4-6e41-43ea-941c-
8361cc760781}.
fixme:module:load_dll Loader redirect from L"C:\windows\system32\d3d9.dll"
to L"d3d9-nine.dll"
err:d3d9nine:present_has_d3dadapter Failed to load
/usr/lib/d3d/d3dadapter9.so.1: /usr/lib/d3d/d3dadapter9.so.1: cannot open
shared object file: No such file or directory
err:d3d9nine:present_has_d3dadapter
Native Direct3D 9 will be unavailable.
For more information visit https://wiki.ixit.cz/d3d9
err:d3d9nine:d3dadapter9_new Your display driver doesn't support native
D3D9 adapters.
fixme:system:SetProcessDPIAware stub!
fixme:module:load_dll Loader redirect from L"C:\windows\system32\d3d9.dll"
to L"d3d9-nine.dll"
fixme:d3d9nine:D3DPERF_SetOptions (0x1) : stub
err:d3d9nine:present_has_d3dadapter Failed to load
/usr/lib/d3d/d3dadapter9.so.1: /usr/lib/d3d/d3dadapter9.so.1: cannot open
shared object file: No such file or directory
err:d3d9nine:present_has_d3dadapter
Native Direct3D 9 will be unavailable.
For more information visit https://wiki.ixit.cz/d3d9
err:d3d9nine:d3dadapter9_new Your display driver doesn't support native
D3D9 adapters.
fixme:module:load_dll Loader redirect from L"C:\windows\system32\d3d9.dll"
to L"d3d9-nine.dll"
fixme:d3d9nine:D3DPERF_SetOptions (0x1) : stub
err:d3d9nine:present_has_d3dadapter Failed to load
/usr/lib/d3d/d3dadapter9.so.1: /usr/lib/d3d/d3dadapter9.so.1: cannot open
shared object file: No such file or directory
err:d3d9nine:present_has_d3dadapter
Native Direct3D 9 will be unavailable.
For more information visit https://wiki.ixit.cz/d3d9
err:d3d9nine:d3dadapter9_new Your display driver doesn't support native
D3D9 adapters.
fixme:win:UnregisterDeviceNotification (handle=0xcafeaffe), STUB!
fixme:win:UnregisterDeviceNotification (handle=0xcafeaffe), STUB!
fixme:iphlpapi:CancelIPChangeNotify (overlapped 0x4ba2e88): stub
------------------------------
In addition, a similar bug was posted some time ago here: #142
<#142>
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#274>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AIkEKigFzh3aYBV_JUdSGwGxzUAKbGGcks5rkJfzgaJpZM4MYz20>
.
|
OpenSUSE Tumbleweed |
Your missing nine support in Mesa
…On Mar 9, 2017 4:28 PM, "PadreAdamo" ***@***.***> wrote:
Radeon 7970
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#274 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AIkEKvvql-BKF2yMyJLHBPuzx_kDZYJqks5rkJkXgaJpZM4MYz20>
.
|
err:d3d9nine:present_has_d3dadapter Failed to load /usr/lib/d3d/d3dadapter9.so.1: /usr/lib/d3d/d3dadapter9.so.1: cannot open shared object file: No such file or directory |
Strange. I don't have this problem with other titles. This is the first time I have tried to get this one to run. -edit- |
Some games are 32 bits, and others 64 bits. Perhaps you have 32 bits nine, but not 64 bits. |
I am running the 64-bit client of Guild Wars 2. I wonder if I don't have 32-bit. Interesting. I will check this tonight and report back. Thank you. |
This is the 64-bit client. I also use the Guild Wars 2 64-bit client so that rules out the client bit being an issue? fixme:ddraw:ddraw7_Initialize Ignoring guid {aeb2cdd4-6e41-43ea-941c-8361cc760781}. I just navigated to the /usr/lib/d3d/ directory referenced above and I don't have it. This is strange because I don't have any issues with Guild Wars 2 on Wine Nine. The whereis command: Wine and Wine-32, Mesa and Mesa-32 are installed |
well, it is looking the wrong dir for 64 bits d3dadapter. |
If this was the case, would other games not work too?
…On Mar 10, 2017 6:01 PM, "axeldavy" ***@***.***> wrote:
well, it is looking the wrong dir for 64 bits d3dadapter.
Use symlinks, or compile wine yourself (it will detect the path)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#274 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AXmIWfxoddFfRVY4FclBtePmdHZoQfBzks5rkdY2gaJpZM4MYz20>
.
|
I am going to try symlink though. Perhaps this could resolve the same issue
with The Secret World. I will report back.
…On Mar 10, 2017 6:01 PM, "axeldavy" ***@***.***> wrote:
well, it is looking the wrong dir for 64 bits d3dadapter.
Use symlinks, or compile wine yourself (it will detect the path)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#274 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AXmIWfxoddFfRVY4FclBtePmdHZoQfBzks5rkdY2gaJpZM4MYz20>
.
|
I just ran two different programs, Steam and Guild Wars 2 (two different prefixes) Everything runs fine. Gren message for Native Direct3D 9 is active. |
Steam is 32 bits. Guild Wars 2 may be 32 bits as well. Thus likely you have 32 bits d3dadapter at the location wine is looking for, but not the 64 bits one. |
Guild Wars 2 is 64-bit client. It's okay though. Symlink did not fix the issue. I am loading up another distro and will try on that; Ubuntu w/Padoka PPA. I will report my findings back here. |
Is this issue fixed then? |
It is probably fixed. The library search code has been updated since. |
Greetings! I am having an issue on game launch. A dialog promp displays "Failed to Initialize Direct3D." I ran the game with NINE_DEBUG=all
My other WINE NINE games run perfectly fine without issue. The items in the log that standout to me are:
fixme:ddraw:ddraw7_Initialize Ignoring guid {aeb2cdd4-6e41-43ea-941c-8361cc760781}.
fixme:module:load_dll Loader redirect from L"C:\windows\system32\d3d9.dll" to L"d3d9-nine.dll"
err:d3d9nine:present_has_d3dadapter Failed to load /usr/lib/d3d/d3dadapter9.so.1: /usr/lib/d3d/d3dadapter9.so.1: cannot open shared object file: No such file or directory
err:d3d9nine:present_has_d3dadapter
Native Direct3D 9 will be unavailable.
For more information visit https://wiki.ixit.cz/d3d9
err:d3d9nine:d3dadapter9_new Your display driver doesn't support native D3D9 adapters.
fixme:system:SetProcessDPIAware stub!
fixme:module:load_dll Loader redirect from L"C:\windows\system32\d3d9.dll" to L"d3d9-nine.dll"
fixme:d3d9nine:D3DPERF_SetOptions (0x1) : stub
err:d3d9nine:present_has_d3dadapter Failed to load /usr/lib/d3d/d3dadapter9.so.1: /usr/lib/d3d/d3dadapter9.so.1: cannot open shared object file: No such file or directory
err:d3d9nine:present_has_d3dadapter
Native Direct3D 9 will be unavailable.
For more information visit https://wiki.ixit.cz/d3d9
err:d3d9nine:d3dadapter9_new Your display driver doesn't support native D3D9 adapters.
fixme:module:load_dll Loader redirect from L"C:\windows\system32\d3d9.dll" to L"d3d9-nine.dll"
fixme:d3d9nine:D3DPERF_SetOptions (0x1) : stub
err:d3d9nine:present_has_d3dadapter Failed to load /usr/lib/d3d/d3dadapter9.so.1: /usr/lib/d3d/d3dadapter9.so.1: cannot open shared object file: No such file or directory
err:d3d9nine:present_has_d3dadapter
Native Direct3D 9 will be unavailable.
For more information visit https://wiki.ixit.cz/d3d9
err:d3d9nine:d3dadapter9_new Your display driver doesn't support native D3D9 adapters.
fixme:win:UnregisterDeviceNotification (handle=0xcafeaffe), STUB!
fixme:win:UnregisterDeviceNotification (handle=0xcafeaffe), STUB!
fixme:iphlpapi:CancelIPChangeNotify (overlapped 0x4ba2e88): stub
In addition, a similar bug was posted some time ago here: #142
The text was updated successfully, but these errors were encountered: