Подробно объясним как исправить ту или иную ошибку самым простым способом на Oshibkino.ru
Error 0x8876086c lego harry potter
Исправление ошибки / Fix Error “Failed to Create d3d device. Application will now exit. Error = 0x8876086c”
Overview
Исправление ошибки / Fix Error “Failed to Create d3d device. Application will now exit. Error = 0x8876086c”
Предисловие
При запуске игры на Windows 10 вы, с большой вероятностью, увидите ошибку “Failed to Create d3d device. Application will now exit. Error = 0x8876086c”. В руководстве описано два способа исправить эту ошибку – ручной и автоматический.
When you start the game on Windows 10, you are most likely to see the error “Failed to Create d3d device. Application will now exit. Error = 0x8876086c”. The guide describes two ways to correct this error – manual and automatic.
Ручное исправление / Manual fix
[RU]
Откройте файл %appdata%ttalesThe LEGO Movie – Videogamepcconfig.txt (можете скопировать и вставить в адресную строку проводника)
Whenever I try to run Lego Harry Potter Years 1-4 I get an error message saying unable to create d3d device, with error code 0x8876086. I have a an ATI Mobility Radeon HD 5470 graphics card and the newest verion of direct x. The games minimun requirement
is ATI x1300. Any advice?
Answers
Marked as answer by Cloud_TS Friday, December 31, 2010 6:15 AM
All replies
This is caused by a conflict with another hardware device, please check your device manager or reinstall / uninstall any additional hardware.
Professional In Computing — Please Contact for Help.
Proposed as answer by Vishdafish Monday, December 27, 2010 8:49 PM
Marked as answer by Cloud_TS Friday, December 31, 2010 6:15 AM
Posted: Tue Nov 29, 2016 8:08 pm Post subject: [SOLVED] Wine Steam Lego Batman and d3d device error
I’m having an issue starting a Lego Batman game on steam via wine.
Right after I select play…I get a blank white screen then the desktop returns… showing the steam gui window, a reduced blank white screen window and an error window. Here is a photo of the error window:
I have the «wine-steam-lego batman» setup on three other computers with intel and nvidia and they all work.
Also I have other lego games that work fine — Jurassic World and Lego Movie.
I have tried the following:
I have researched the error message «Failed to create d3d device. Application will now exit. Error=0x8876086c» and basically everything is windows oriented and doesn’t resolve the issue.
I have re-downloaded the lego batman game several times with the same result.
I have copied the lego batman game from another computer and the same result.
Current setup:
CI3 550
4 Gb ram
Nvidia GTX 750
Gentoo stable
Kernel 4.4.6
QT 5.6.2
Plasma 5.8.4
Frameworks 5.28
KDE Apps 16.08.3
Nvidia-drivers 361.28
Wine 1.9.20 with staging and s3tc
Any help would be appreciated.
Thanks
Last edited by davidbrooke on Tue Dec 20, 2016 5:32 pm; edited 1 time in total
Back to top
rh n00b
Joined: 19 Sep 2006 Posts: 58
Posted: Wed Nov 30, 2016 8:49 am Post subject:
You could try running it with setting the virtual desktop in winecfg. If it doesn’t help, there are some tips for debug info in this old winehq bug report, in case you haven’t seen it.
https://bugs.winehq.org/show_bug.cgi?id=27781
Since it should work, another option is to try a new, clean wine prefix both with 32 and 64 bits. I didn’t find a demo for this, so can’t really try it myself.
Back to top
davidbrooke Guru
Joined: 03 Jan 2015 Posts: 341
Posted: Mon Dec 05, 2016 8:52 pm Post subject:
rh wrote:
You could try running it with setting the virtual desktop in winecfg. If it doesn’t help, there are some tips for debug info in this old winehq bug report, in case you haven’t seen it.
https://bugs.winehq.org/show_bug.cgi?id=27781
Since it should work, another option is to try a new, clean wine prefix both with 32 and 64 bits. I didn’t find a demo for this, so can’t really try it myself.
Thanks for the reply!
Basically I had tried everything you suggested but the virtual desktop option. I tried that and the game worked. The «virtual desktop option» seems like a «less desired path»…My kids will be operating…so expecting them to get from steam to «virtual steam» would be insane. I will need to evaluate the need on that computer if no other options become available.
Back to top
rh n00b
Joined: 19 Sep 2006 Posts: 58
Posted: Tue Dec 06, 2016 8:40 am Post subject:
davidbrooke wrote:
Basically I had tried everything you suggested but the virtual desktop option. I tried that and the game worked.
It could be an issue with resolution. Have you tried to change the resolution in game menus to match your native screen res? If there isn’t an option for it you can propably edit in some config file. If it doesn’t work, we could compare xrandr output from working and non-working setup.
Back to top
davidbrooke Guru
Joined: 03 Jan 2015 Posts: 341
Posted: Wed Dec 07, 2016 12:58 pm Post subject:
rh wrote:
It could be an issue with resolution. Have you tried to change the resolution in game menus to match your native screen res? If there isn’t an option for it you can propably edit in some config file.
I had adjusted the resolution in two ways prior to your suggestion:
I changed the resolution from 1024×768 to 1920×1080.
2. While in Steam, I right clicked on the game and selected «properties» then added the following to the «set launch options» field:
-w 1920 -h 1080
Both efforts resulted with the same error message.
Quote:
If it doesn’t work, we could compare xrandr output from working and non-working setup.
Please post an xrandr example and specify the key points to compare.
Thanks
Back to top
rh n00b
Joined: 19 Sep 2006 Posts: 58
Posted: Thu Dec 08, 2016 8:35 am Post subject:
davidbrooke wrote:
Please post an xrandr example and specify the key points to compare.
Just running xrandr on a xterm as regular user should be enough. This shows the resolutions and refresh rates X can use on the connected monitor.
Code:
$ xrandr
Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 16384 x 16384
DisplayPort-0 disconnected (normal left inverted right x axis y axis)
HDMI-0 connected primary 1920×1080+0+0 (normal left inverted right x axis y axis) 598mm x 336mm
1920×1080 60.00*+ 50.00 59.94
1920x1080i 60.00 50.00 59.94
1680×1050 59.88
1280×1024 75.02 60.02
1440×900 59.90
1280×960 60.00
1152×864 75.00
1280×720 60.00 50.00 59.94
1440×576 50.00
1024×768 75.03 70.07 60.00
1440×480 60.00 59.94
832×624 74.55
800×600 72.19 75.00 60.32 56.25
720×576 50.00
720×480 60.00 59.94
640×480 75.00 66.67 60.00 59.94
720×400 70.08
DVI-0 disconnected (normal left inverted right x axis y axis)
DVI-1 disconnected (normal left inverted right x axis y axis)
If the one game is requesting is missing, that could be it. The game might request some more or less random resolution at start, before swithing to user configured resolution. Looking for differences in a working and non-working system might give a clue what the game wants. It should be something standard like 1024×768@60. Hopefully making that resolution available to X could solve the issue. This all is just guesswork on my part, but would explain why virtual desktop mode works, and the game works on another system.
Another option is that you could just try with another monitor that you know to work with this game. There propably is a wine debug variable to get some display related debug information, but I’m not familiar enough with wine to help you with that.
Back to top
davidbrooke Guru
Joined: 03 Jan 2015 Posts: 341
Posted: Mon Dec 12, 2016 6:26 am Post subject:
Here is the xrandr output:
Code:
~ $ xrandr
Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 16384 x 16384
VGA-0 disconnected (normal left inverted right x axis y axis)
DVI-D-0 disconnected (normal left inverted right x axis y axis)
HDMI-0 connected primary 1920×1080+0+0 (normal left inverted right x axis y axis) 1150mm x 650mm
1920×1080 59.93*+
Back to top
rh n00b
Joined: 19 Sep 2006 Posts: 58
Posted: Mon Dec 12, 2016 9:38 am Post subject:
I guess that’s your problem. You don’t have even the 1920×1080@60 mode available you set in game config. That could be an issue in graphics stack or monitor. One obvious cause could be a non-direct connection to your display device, such as home theather equipment or adapters. Trying a DVI connetion and another display device would help to rule out those as possible causes.
You could try to set the 59.93 refresh rate in game’s config file, but even if it works that’s a workaround, not a fix. Better way would be to find and fix the underlaying issue and make 1920×1080@60 and some other common modes available.
FWIW, here a link to wiki on adding new modes manually:
https://wiki.gentoo.org/wiki/Xrandr#Screen_modes
Posting to Kernel & Hardware subsection would get more attention of people with better understanding of the graphics stack. If you do so, please include your xserver log and xrandr output along information with graphics stack. If you want to continue here, please pastebin your xserver log and make+model of display device in that case too.
Back to top
davidbrooke Guru
Joined: 03 Jan 2015 Posts: 341
Posted: Sat Dec 17, 2016 6:03 am Post subject:
rh wrote:
You could try to set the 59.93 refresh rate in game’s config file, but even if it works that’s a workaround, not a fix. Better way would be to find and fix the underlaying issue and make 1920×1080@60 and some other common modes available.
I tried using the 59.93 Hz value in the config file but it didn’t help.
Sometimes it’s best to admit that the solution is that it just won’t work??? I think that is the route I’m taking at this point. So thanks for your help!
Back to top
davidbrooke Guru
Joined: 03 Jan 2015 Posts: 341
Posted: Tue Dec 20, 2016 5:31 pm Post subject:
Due to a new install on the problem computer…I decided to take one last effort to resolve the video issue.
I had a problem with a nvidia upgrade a few months back which broke my setup. This left me with my initial problem of setting up a 720p native TV to work in 1080p and fix overscan. I found CVT and was using it when I started this thread. I re-visited my nvidia fix and found a way to make it work again. I tested the «Lego Batman game on steam via wine» and it worked as expected. It appears that CVT was the problem. For those that are interested, the following is the nvidia.conf:
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
