Skyrim Error Xinput1_3.dll

0 views

Skip to first unread message

Allen Yerke

unread,

Aug 3, 2024, 4:33:33 PM8/3/24

to drinmomapul

I have been reading everything I can find about Kerbal Space Program and crashing. There are NUMEROUS threads about it over the last FOUR years, but nothing in any of the threads here, or on Steam, or various reddits have done anything to fix the problem.

Now, I DO run about 100 mods, but I get them through CKAN and they are installed properly and with very few exceptions they are of the appropriate version to match the 1.4.3 KSP version I am running. The handful that are a for an earlier 1.4.x, I asked in the corresponding thread if they are compatible and the answer was yes.

Despite this my game was regularly crashing after trying to return to or exit the VAB/SPH after a flight. After leaving and entering the ship building buildings several times my game would crash. Since the game takes about 10 minutes to load with a lot of mods, waiting for it to load over and over to play for about 5 minutes is pretty damn tedious. I was spending more time watching the loading screen than playing the game.

I have about 20 crash.dmp files that I have no way to open or read myself and taking the time to zip them with the Output_log, error log, and KSP log files and then uploading them to dropbox to post a link here... and then get no response from any of the Devs is obviously not worth anyone's time.

Out of all of the Error reports generated with the crash.dmp files my RAM was averaging 50%-60%, but despite this Linuxgurugamer suggested I was running out of RAM or my RAM was bad. I put Memtest86 on a USB drive and ran multiple passes.....my RAM is not bad and has no errors. Since more then half of it isn't being used by the game or the mods, I don't understand how I could be running out of it. I don't have anything else running in the background. I disabled all my Windows startup processes.

I then did a file search for xinput1_3.dll and noticed it is located in several different places in my C drive. I also noticed that it came in different file sizes. So I Googled about it on the Internet. I learned that there is a 32bit and 64bit version of it. The 64 bit file size is about 105KB and the 32bit version is about 80KB. As you can see from my second spoiler above it is using the larger file size which makes sense because I am running the 64bit version of KSP.....I also learned that System32 is the 64bit program folder for Windows and Syswow64 is the 32bit folder.....that doesn't make sense to me and seems counter-intuitive....

What also doesn't make sense to me after doing my file search for that file, is WHY Kerbal Space program comes with two copies of it, one in KSP_Data\Plugins and one in KSP_x64_Data\Plugins and when I run the game with the KSP_x64 shortcut on my desktop it uses NEITHER of them? If you look at what is says in the error above it is using MY Windows copy of it in C:\WINDOWS\SYSTEM32\xinput1_3.dll. Why is it using the one in my windows folder when the game comes with it's own two copies?

Then I noticed BOTH the copies installed with KSP are of the 80KB variety, which as I stated is most likely the 32bit version of the file....WHY would the 64bit version of the game come with a 32bit .dll file....one it isn't even utilizing...

So I tried something crazy. I went in my windows\system32 folder and renamed the xinput1_3.dll there xinput1_3_fail.dll, and then I copied and pasted a copy of the file from the KSP_x64_data\Plugin folder into my windows\system32 folder.....which is something REALLY stupid to do, and I REALLY need to remember I did that, because it will probably break every other 64bit game I try play.

So far my game hasn't crashed once and I intentionally went in and out of the VAB and SPH buildings like 20 times each and launched and reverted flights like 20 times.....something I could normally get away with like 4 times and the game still hasn't crashed. So now the 64bit version of the game is most likely utilizing a 32bit dll located my 64bit Windows folder....

Could one of the Squad Devs please patch the game to actually utilize the dll files that come installed with the game, and ensure they are the ones in the correct corresponding plugin folder in one of the future updates please?

This is a list of all the .dll files in the plugin folder that MAY not be being utilized by KSP but probably should be: (I am basing this assumption on the fact it wasn't using the xinput1_3.dll in the plugin folder.....but maybe it is.....how can I tell? Maybe this was all because the 64bit plugin folder has the 32bit dll and windows 64bit is running the 64 bit version and this was some kind of mismatch error.....and now that I have the same file in both places they match now....I really don't know what's happening for sure. All I know is doing this made my game MUCH more stable in general)

That's a bit unfair. You run 100 mods, what do you expect the devs to do? If you cannot recreate the issue in a stock install, it is not an issue SQUAD has to care about and if it is a specific mod or combination of mods, you have to find the mod or mod combination on your own and report the issue to the mod dev(s).

DirectX is NOT required to run KSP but 'xinput1_3.dll' is a (redistributable) part of DirectX (If DirectX is required for any game, there is a separate sub-point in the list). So I have to assume, that if your system does not provide this file, KSP will use the one delivered with the game itself.

A lot of people run a lot of mods, that's why they have a modded technical support. Also this is a reference to another situation where I requested assistance almost a month ago and got no response from anyone. In that thread that is still the case.

It also crashes stock, it just takes slightly longer. All you have to do to recreate it is play the game....it eventually crashes to desktop it's just a matter of time. When I tried to solve my last issue no one helped me with, I uninstalled all my mods a few at a time and then eventually uninstalled the whole game, and then deleted everything left behind. I reinstalled the game stock and it still crashed. It's probably because of this issue I found.

If that is a link of the requirements, it says DX10....DX10 IS DirectX. You can't really have a game with graphics that runs at this point without it (well there's OpenGL...). Directx 9 has been installed with games for the last two decades. Directx12 is supplied automatically by Windows now, and there is no stand alone redistributable for it. It updates via Windows update. The most recent distributable version of Directx is from June of 2010.

This still doesn't answer the question of why the game installs with two copies of a directx file that it doesn't seem to utilize, yet it is running the one from my Windows folder. Or why both copies it supplies are of the 32 bit variety, even though one of the folders with the file is for the 64bit version of the game....

I know and usually people post their log and other people tell them which mod causes an issue. Sometimes it is possible to present a solution like 'you missed a dependency' or 'that's an old version, get the new one' and sometimes all you can say is 'contact the mod creator of mod xyz'. This is just possible if the log contains distinct errors. But sometimes there are no distinct errors in the log, than all you can do is removing mod by mod until the issue does no longer appears. It is a tideous task, so it is unlikly some will do it for you.

I saw the thread recently and I actually posted an answer, so this is not true anymore You may not like the answer, but there is one.
Usually, when no one answeres to a question, these reason is pretty simple: no one got an idea or solution. You cannot blame people for not knowing something. And if you really want a response from a SQUAD member, you can always ping one of them.

I'm not playing the game for years like other, I found it just recently and started with KSP 1.4.1. I had not a single crash in a stock game and just a few with mods installed, so I'm confident to say: I cannot recreate the issue in a stock game.

This forum is primarily community driven. We have chosen to take our personal time to help others as we can. When we are presented with an issue we do not know the answer to, usually we keep our nose out of the issue. The dev's are under no obligation (I believe) to come here and provide support, yet they still do when needed. If you need dev support in particular, then a bug tracker is usually required, yet I see no bug tracker link. When your install is loaded with mods, there is not much a dev can do anyways. So to try to drop the burden on them is also quite an insult.