lionhost.blogg.se

1. #THE GAME WAS UNABLE TO INITIALIZE DIRECT3D WINDOWS 8 INSTALL#
2. #THE GAME WAS UNABLE TO INITIALIZE DIRECT3D WINDOWS 8 UPDATE#
3. #THE GAME WAS UNABLE TO INITIALIZE DIRECT3D WINDOWS 8 DRIVER#
4. #THE GAME WAS UNABLE TO INITIALIZE DIRECT3D WINDOWS 8 SOFTWARE#

Maybe use my method if it works, otherwise someone will have to find yet another method for those that don't work.

Maybe I can play some MTW before directx 12 comes out and breaks everything again!Yeah I'm not really sure what to recommend, at this point. Now to try fiddling with these hacked dlls. DXWND still results in a black screen or a "failed to initialize direct3d yada yada". When I tried to quit back to the menu it hard crashed. I tried a custom battle and it was playable but at pretty low FPS. The resolution is still stuck at the lowest, the framerate is HORRID both in the menus and in battle. I have no clue why this worked, but I was browsing the mtw board on the total war forums and in the FAQ I was reminded of the skip intro trick: create a blank text file in your game folder called skipcredits.txt, when I did that the game started up! No crash.

I can also tell you by what allows it to work on my machine that they mix in GDI (native windows api calls - yeah you can, under controlled circumstances, use native gdi calls on a DX9 surface though you can run into the kind of incompatibilities that we are seeing, which is why I was told not to do it).Ī Shiny Gold Doubloon for whoever can explain this to me I think DXWND links in DX9 mode, though I don't know if that's the correct mode to override or not, maybe we need a solution that hits api calls for all three levels)

#THE GAME WAS UNABLE TO INITIALIZE DIRECT3D WINDOWS 8 INSTALL#

and 9 calls (by what version of the api they make you install for each upgrade - from base which is 7 to 8 for some of the upgrades to 9 for viking invasion. What version of directx did MTW run on exactly? What dlls did it use? Again I don't know a whole lot about this so if someone could explain it to me it would help, don't be afraid to get technical.I haven't dug deep enough. Until I found a program on VOGONS called dgVoodoo2, it's a hacked dll wrapper that emulates old Voodoo API (I think? I'm not too sure about this stuff) Anyway dgVoodoo2 doesn't help at all with MTW, but I'm on the lookout for similar API wrappers that can emulate older directx environments.

#THE GAME WAS UNABLE TO INITIALIZE DIRECT3D WINDOWS 8 SOFTWARE#

I also like to play an old game called Take No Prisoners, which runs fine in Windows 8.1 64-bit but only in software mode, not D3D. (potentially someone with aptitude could debug Dxwnd, as the source is available, but I think that's above my aptitude level.)

#THE GAME WAS UNABLE TO INITIALIZE DIRECT3D WINDOWS 8 UPDATE#

So basically, in the end, you either have to get lucky, someone has to update the source code for the game, or we have to hope that someone comes up with a new updated compatibility or windowing wrapper that works. On the other hand (getting off my soap box) on occasion, programmers have to do some kind of dicey/shaky things (yes, even in dx 9, though not like Dx 1-8) to make the software work efficiently.

The reason? There's no guarantee of long term compatibility if you mix gdi + directx or native windows api + directx (as we are seeing here, and by the hacks I had to use when I get it to work temporarily, I suspect they did all three at the time) That's part of the problem is that directx has changed so much but it's also because whomever wrote this software did something I was explicitly told not to do when I was still working in the video game industry: mixing gdi, directx, and native windows api calls (yeah we cheated from time to time, but generally this was something I was told not to do except under extreme circumstances.) Nevertheless, I do hope being wrong, because actually Med1 (especially Viking Invasion) and Shogun1 were great, great, great games.Yes and no.

#THE GAME WAS UNABLE TO INITIALIZE DIRECT3D WINDOWS 8 DRIVER#

I've already re-installed Direct X 9.0C and my video card driver is up to date, for a RADEON X700 Series card, it was installing the new driver when the problem started! Something went wrong with the install and I ended up with 4 bit graphics and 240 by 200 display.Even before changing my machine (now I'm running Win 8) at some point I couldn't play Med1 anymore, after some search here and there and after having tried all the ways to run the game, I discovered that it's a issue created by DirectX, that is, at some point of the evolution of DirectX (DirectX 9?) the game has become incompatible and in practice you have no hope to run it. I've placed the files where I thought they should go system 32 but I'm still getting the same error as before when I run the DirectX diagnostic tool:ĭ3D7 Test Result: Failure at step 8 (Creating 3D Device): HRESULT = 0x80004005 (Generic failure)ĭ3D8 Test Result: Failure at step 8 (Creating 3D Device): HRESULT = 0x8876086c (error code)ĭ3D9 Test Result: Failure at step 8 (Creating 3D Device): HRESULT = 0x8876086c (error code) I thought it would just install the software where it needed to be installed, just like DirectX but it doesn't. I've downloaded the Direct X 9.0b SDK extras software but I don't know where the files need to be placed.