Directx Problem For Windows 8
#21
Posted 28 March 2013 - 01:15 PM
#22
Posted 28 March 2013 - 01:22 PM
Mindfallen, on 22 February 2013 - 08:19 AM, said:
I had the same issue with windows 8 when I fist installed this game. Message support, they can help you, you have to download some files and put it in a specific folder, wish I could help but it was months ago.
#23
Posted 28 March 2013 - 01:26 PM
#24
Posted 28 March 2013 - 01:28 PM
DeathofSelf, on 28 March 2013 - 01:26 PM, said:
It's working really really well on my system, this same system was lagged like crazy under windows 7 and wasn't all that stable. So far I love Win 8, metro isn't my fav but I've adapted.
#25
Posted 28 March 2013 - 01:29 PM
Cearrdorn, on 28 March 2013 - 01:28 PM, said:
It's working really really well on my system, this same system was lagged like crazy under windows 7 and wasn't all that stable. So far I love Win 8, metro isn't my fav but I've adapted.
Windows 7 works great for me, I prefer not to turn my $2000 desktop into a tablet
#27
Posted 29 March 2013 - 05:22 AM
The above is the full redistribution. Unpack it to a temp location c:\directx then run the dxsetup.
On the web installer, may need to run with admin permissions, right click run as a admin.
#28
Posted 29 March 2013 - 06:28 AM
Cearrdorn, on 28 March 2013 - 01:28 PM, said:
Get Start8. For only $5 you can turn Win8 into Win7+ which is what it was meant to be in the first place.
It kind of sucks that all Microsoft has been doing when coming out with "new" operating systems is giving us massive Point Releases instead. We haven't actually had a new version since Vista. Vista and Server 2008 were 6.0, Server 2008 R2 and Win7 are 6.1, and Server 2012 and Win8 are 6.2. The same thing happened with Win2k through Server 2003 -- just some more Point Releases instead of new operating systems. Microsoft has apparently decided that Apple and Linux had it right all along -- give point releases a different name and people will accept them as new.
#29
Posted 04 April 2013 - 06:46 AM
#30
Posted 11 April 2013 - 01:43 AM
What you need to do is to 1) find the version of your DirectX. 2) reinstall DirectX with this DirectX toolkit. 3) if not work, download DirectX 9 and install it to your system. You don't need to reinstall your OS to WinXP or Win7. Many video games still don't fully support Win8... so, take it easy man.
#31
Posted 22 August 2013 - 01:49 PM
#32
Posted 22 August 2013 - 02:14 PM
Khan NTHunter, on 22 August 2013 - 01:49 PM, said:
Using complicated search terms like
"cryinput.dll" in google I arrived at a solution...
Visual C libs are needing to be fixed!
Darnit the source of your problem took more letters than using Google!
#33
Posted 22 August 2013 - 04:16 PM
Khan NTHunter, on 22 August 2013 - 01:49 PM, said:
Install directx 9c. Redistribution file, unpack it in a temp location, ie download\directx9c or such, then run dxsetup. I prefer this one as it will overwrite any possible corrupted files.
http://www.microsoft...on.aspx?id=8109
Or download the small package dxwebsetup.exe first, which will then download and install the 80meg+ files. Beware that there are several different dxwebsetup files. The size file is the one from 2011 with a size of 285KB. Earlier ones will through up an error message about it can only be installed on specific OS.
#34
Posted 23 August 2013 - 12:45 AM
Unfortunately, for some reason, both Directx9 webinstaller and redistribution do not address the problem, I've tried both and neither add any files nor update the system, messaging that it's up to date with the newest version. I've even manually unpacked some of the .cab from the redistribution but didn't work out.
Last think I can try is installing VisualC libs as recommended, but I'm puzzled why these would contain a CryTek Engine library within them. Most tech posts related to the absence of cryinput.dll point to CryTek's developer forums, and solutions include installing a whole suite of development tools.
Anyway, thanks for the help!
#35
Posted 01 November 2014 - 07:36 PM
I plugged in my Logitech unifying receiver and POOF Mechwarrior works! (I didn't even turn the mouse on!) Even more interesting is that the trackball still works to control my mech. I am betting that a few people here are using the Kensington software or some other alternative interface that is not compatible.
In short, even if you don't use it keep a mouse plugged in and you will have no problem.
#36
Posted 14 May 2016 - 10:01 PM
Garan Katare, on 01 November 2014 - 07:36 PM, said:
I plugged in my Logitech unifying receiver and POOF Mechwarrior works! (I didn't even turn the mouse on!) Even more interesting is that the trackball still works to control my mech. I am betting that a few people here are using the Kensington software or some other alternative interface that is not compatible.
In short, even if you don't use it keep a mouse plugged in and you will have no problem.
Sorry to necro this, but I just reinstalled MWO and it was crashing with this exact same error. Sure enough I have a Kensington Expert Mouse (aka trackball). I have to give props to Garan quoted here, because simply connecting an old usb mouse to an extra USB port fixed the issue immediately.
This also fixed my issue with Dosbox failing to start and Skyrim's issue of my mouse not being recognized, two issues I've been struggling with on the side that I had no idea were related to this.
Thanks so much, ... this is exactly the fix I needed.
5 user(s) are reading this topic
0 members, 5 guests, 0 anonymous users