Steam Controller Does Not Work

[Ignath]

It may be the issue @Beale...I have a plugins folder in KSP_x64_Data that contains a CSteamworks.dll file in it.

[kBob]

1 hour ago, Beale said:

Huh, I am missing a 'plugins' folder inside my KSP_x64_Data folder, is this the issue maybe?

To answer, yes, I have tried both 32 and 64 bit, launched through Steam big picture.

Yeah it's the only file in that folder.  Try creating it and putting the dll in there.  Or you could try making a backup of KSP and then installing a fresh copy.

[Beale]

57 minutes ago, Ignath said:

It may be the issue @Beale...I have a plugins folder in KSP_x64_Data that contains a CSteamworks.dll file in it.

26 minutes ago, kBob said:

Yeah it's the only file in that folder.  Try creating it and putting the dll in there.  Or you could try making a backup of KSP and then installing a fresh copy.

Sadly, does not work.
Thank you for the tip though.

 

[kBob]

Just now, Beale said:

Sadly, does not work.
Thank you for the tip though.

 

I think you should try installing a fresh copy of KSP, that that was missing makes me wonder if something else might be missing too.  Also my csteamworks.dll is 140KB but I'm on windows 8.1 so it might be a different version, still might be worth checking to see if you can find a different version of that file for Win 10 (though I suspect you'd have problems with other programs and steam if it was really the problem).

[Ignath]

Just now, kBob said:

I think you should try installing a fresh copy of KSP, that that was missing makes me wonder if something else might be missing too.  Also my csteamworks.dll is 140KB but I'm on windows 8.1 so it might be a different version, still might be worth checking to see if you can find a different version of that file for Win 10 (though I suspect you'd have problems with other programs and steam if it was really the problem).

I believe he said he already deleted and re-installed with no change.

@kBob is right though, my CSteamworks.dll is 140kb as well, not 131kb like yours @Beale.

[Beale]

2 minutes ago, kBob said:

I think you should try installing a fresh copy of KSP, that that was missing makes me wonder if something else might be missing too.  Also my csteamworks.dll is 140KB but I'm on windows 8.1 so it might be a different version, still might be worth checking to see if you can find a different version of that file for Win 10 (though I suspect you'd have problems with other programs and steam if it was really the problem).

Just now, Ignath said:

I believe he said he already deleted and re-installed with no change.

@kBob is right though, my CSteamworks.dll is 140kb as well, not 131kb like yours @Beale.

Yes, unfortunately, I have completed a re-installation just today also - no change  

Would it be possible to steal your copy of this DLL? 

Thanks for the continued help!

 

[kBob]

4 minutes ago, Beale said:

Yes, unfortunately, I have completed a re-installation just today also - no change  

Would it be possible to steal your copy of this DLL? 

Thanks for the continued help!

 

PMed you with link.

[Beale]

17 minutes ago, kBob said:

PMed you with link.

Much appreciated!

It works! Wow! It is great to play with the controller  
Many thanks for your help @kBob and @Ignath!

Now, the remaining question, why is it I am left without the correct DLL in the beginning, perhaps my Steam setup is wrong?

Edited July 26, 2016 by Beale

[kBob]

Yeah from my cursory reading that dll comes from steam and should be updated from steam.  You might want to contact steam and see what they say (if anything, or maybe one of the people who hang out in the steam forums will know why).  Anyway glad it finally works.  Don't forget to update your post in the bug tracker.

[Ignath]

7 minutes ago, Beale said:

Much appreciated!

It works! Wow! It is great to play with the controller  
Many thanks for your help @kBob and @Ignath!

Now, the remaining question, why is it I am left without the correct DLL in the beginning, perhaps my Steam setup is wrong?

Did you participate in the Pre-release bugfinding @Beale?  If so, did you switch off the pre-release branch and "opt out of all betas"?

[Beale]

On 7/26/2016 at 11:08 PM, Ignath said:

Did you participate in the Pre-release bugfinding @Beale?  If so, did you switch off the pre-release branch and "opt out of all betas"?

Yes.

Unfortunately, after a restart of computer.

It doesn't work anymore! 

The 140kb DLL is still in place, but the mode switching no longer works.

[kBob]

21 hours ago, Beale said:

Yes.

Unfortunately, after a restart of computer.

It doesn't work anymore! 

The 140kb DLL is still in place, but the mode switching no longer works.

Are you back to getting an error about not finding the DLL in the log file?

Just to be sure we are talking about it being in the KSP_x64_data\plugins folder and you are still running the 64bit version of KSP (as Steam seems to default to the 32 bit version)?

Get rid of all other copies of it in any other folders.

Edit:

I was just looking around I saw one reference to an antivirus checker interfering with csteamworks.dll, might be worth turning yours off see if it helps, this was for a different game a couple of years ago but given the sequence might be possible.

 

 

Edited July 29, 2016 by kBob

[Beale]

1 hour ago, kBob said:

Are you back to getting an error about not finding the DLL in the log file?

Just to be sure we are talking about it being in the KSP_x64_data\plugins folder and you are still running the 64bit version of KSP (as Steam seems to default to the 32 bit version)?

Get rid of all other copies of it in any other folders.

Edit:

I was just looking around I saw one reference to an antivirus checker interfering with csteamworks.dll, might be worth turning yours off see if it helps, this was for a different game a couple of years ago but given the sequence might be possible.

 

 

Good question, I think so yes:

[ERR 18:31:27.861] <color=orange><b>[KSPSteamController]:</b> Failed to initalize Steam API!</color>

The setup is still the same, I run the version that is 64-bit and suddenly have problems.

Thanks for the tip on Anti-virus issues, but no change.

[kBob]

3 hours ago, Beale said:

Good question, I think so yes:

[ERR 18:31:27.861] <color=orange><b>[KSPSteamController]:</b> Failed to initalize Steam API!</color>

The setup is still the same, I run the version that is 64-bit and suddenly have problems.

Thanks for the tip on Anti-virus issues, but no change.

Odd. 

That appears to be a somewhat different error message than you reported in the bug tracker.  It may be the same thing or not.

Do you have the following file somewhere and what is the size/date?

steam_api64.dll 11/11/2015 201KB

Also copy the csteam file again and replace the one in the plugins folder just so we can rule out some freak data corruption occurring.

And if that doesn't work try spamming it in a couple of folders main ksp root and the ksp_data\managed folder (I'm just trying to see if it will pick it up from a different location thinking maybe some config file or something got changed when you reset the computer, something had to have changed just not sure what...I'll sleep on it though).

And actually if you right click on the DLL files choose properties and then details (this may be slightly different in win 10) we can compare versions for example the above file is 3.3.47.38.

And one more thing run KSP directly from the ksp_x64.exe file, right click and choose run as administrator.

Edited July 29, 2016 by kBob

[Beale]

20 hours ago, kBob said:

Odd. 

That appears to be a somewhat different error message than you reported in the bug tracker.  It may be the same thing or not.

Do you have the following file somewhere and what is the size/date?

steam_api64.dll 11/11/2015 201KB

Also copy the csteam file again and replace the one in the plugins folder just so we can rule out some freak data corruption occurring.

And if that doesn't work try spamming it in a couple of folders main ksp root and the ksp_data\managed folder (I'm just trying to see if it will pick it up from a different location thinking maybe some config file or something got changed when you reset the computer, something had to have changed just not sure what...I'll sleep on it though).

And actually if you right click on the DLL files choose properties and then details (this may be slightly different in win 10) we can compare versions for example the above file is 3.3.47.38.

And one more thing run KSP directly from the ksp_x64.exe file, right click and choose run as administrator.

Thanks for the help, here is the information:

steam_api64.dll is 201KB and created 25/07/2016.

DLL properties:
My CSteamworks.dll is version 'v1.25-1.35'.

Unfortunately, I have tried everything you say and still no success  

[kBob]

Let me ponder on this, but a couple of questions.  It stopped working after you reset the computer so did you do anything after you left KSP and before you restarted (including playing another game) and after you restarted did you do anything before you ran KSP?  And one thing to try, after starting KSP unplug the controller then plug it back in and if it still doesn't work, exit and restart KSP (ok I'm trying solutions from like the 90's but you never know  ).

Edit: Actually I was wondering what the steam_api64.dll version is.  The csteam is the same version as mine...as we would expect .

Edit again: Also could you please validate the steam cache for KSP.

Edited July 30, 2016 by kBob

[kBob]

One other thing.  I plan on getting a steam controller hopefully in a week or two (big snafu and I didn't get paid last month and may not until sept, so I'm watching my spending just to be safe).  So if the above doesn't help...what I'm thinking is when I get mine, we can do a detailed comparison of some things (assuming mine works) see if we can't get yours working...so keep hanging on.  And we know it works, probably some dumb simple thing--that's usually the case when you've got it working and then it stops again.

Funny story: I once got called in because "the monitor in the pharmacy is just displaying gibberish."  I got there took one look and realized the brightness button had gotten bumped and only the bolded text (this was on a monochrome monitor) was showing. I made darn sure every employee knew about the brightness and contrast buttons after that  .