sal_vager

Just make sure the story doesn't cause any of the guys involved to go off the rails over details.

Should be fine, the problem with RP is the argument and fighting that occurs when some players take it too seriously and it gets out of hand, unfortunately that seems quite common when warfare is involved. If no one is participating (or participation has ended) then it should work as a story.

Those folders are still checked for addons as really old addons used that folder structure. Moving to Dev Discussion

Hehe I'm no expert with Fedora, I have to google that stuff I assume jstest is in the Fedora repository, there's good info on installing packages here. If it is not there there is likely an alternative, if you search for "joystick" PackageKit should show you what is available. You really just need to verify that your stick is detected and working. Also, please paste the contents of your Player.log and KSP.log to a paste site such as pastebin.com or hastebin.com, then post the URL's here so I can see if KSP is detecting your controller.

Oh one more thing, the KSP logs get overwritten every time you start the game so test your stick then upload it, if there's something being written to the log you'll be able to catch it.

Russia should challenge the US to a game of Quake.

A file sharing site is easiest, though many require an account, you could put all the files in a zip and put the zip on filedropper.com as you don't need an account for that, the files would expire eventually but that's not a prob for logs. One of the most important files is the output_log.txt found in the KSP_Data folder, though none of the files have been very useful when diagnosing any of these joystick problems. Things like axis detection are meant to be plug n play, they should just work, as all you're doing is telling Unity to listen for an input which KSP then writes to a file. Controllers have always been weird, but 1.0.x is the worst, supposedly the whole controller back-end in Unity5 is new though, so that should mean these problems go away.

Hmm okay, can you provide any more info? What you have is not much to go on. The support sticky details the kind of info we need to deal with support requests and bugs, things such as OS (which you mentioned, though I don't recall any issues with Win8 specifically), logs, dxdiag, save and settings files. Reproducible steps are also great, though you can bet that they aren't easy with an issue like this as everyone's PC is different and the symptoms of this controller bug vary considerably.

Yeah I spotted that after, but there's a lot of joystick issues and they all seem related. The settings should persist as long as KSP is started directly, not via shortcut, and the controller is plugged in before starting. As it is the whole shebang really needs looking at on Squads end. Also don't forget to check the bug tracker for your issue, the Support forum is really for support rather than bug reports

Okay, looks like the Edgers packages aren't there, and the fglrx packages are older than I'd like, I'll update the first post, as it looks like Ubuntu Vivid and Mint have newer drivers anyway. You could try the latest driver here, the Ubuntu install instructions should work for Mint, or wait for the officially supported repository to include AMD drivers. I've used the drivers from the AMD site in the past and they worked pretty well, just make sure you uninstall them before upgrading to a newer driver.

Merged post with existing thread.

It's not like we don't know that parts overheat and explode but Squad are concentrating on 1.1 and Unity5 now. I've been working around this issue by using other parts instead of the cubic strut, which due to its size has always been a problem in KSP, prior to overheating it was always the cause of other crazy physics issues such as causing craft to simply shake themselves apart, this always used to happen when using this part with wheels. So instead of the strut I use empty Oscar-B fuel tanks, they are light, small and they surface attach, they are also not subject to the overheating bug. Changing "PhysicsSignificance = 1" to "PhysicsSignificance = 0" in the strutCubicOcto.cfg might also prevent this overheating issue.

Moved to modded support. 64bit bugs are Moot because Squad does not currently provide a 64bit version of KSP. Please try a stock 1.0.4 install, and pleas see the support thread.

You can find the newer driver most easily by using Synaptic, which is a front-end for Apt, by searching for fglrx in Synaptic you will see the Edgers drivers as well as the basic driver provided by the Ubuntu repositories. Driver Manager is not useful for this, as it cannot see the Edgers drivers. Edgers is only a temporary measure until Ubuntu adds AMD drivers to their new proprietary repository, it is also possible to install the AMD drivers from the AMD site, as they offer a .deb package now so we don't have to manually convert from a .sh Hope this helps

Don't forget the licence terms, and the addon posting rules.

Don't forget that piracy discussion is against the rules here But the disabling of hardware is unbelievable, the potential for abuse and of false positives is disturbing, and could affect much more than chinese Xbox controllers.

There was a crash involving Mono and fglrx_dri, which is the proprietary AMD driver for Linux. AMD drivers are notoriously bad, and it is worth trying different versions of fglrx such as those from the Edgers repository or even the open source driver Radeon, which some regard as superior. As for what caused it it's hard to say, you have plugins loaded and they use C#/Mono, one of them could be causing this issue, so please test an unmodded KSP install. Also, try asking in the Other Linux Thread, as that thread handles modded installs.

Great! Keep a backup of that file in case this happens again, I'd mark it read-only as well, though it can be edited from the debug menu (can't be read-only for that).

Okay, please try the file here, it should work.

Yes that could be it, was the file ever deleted ? Also where is KSP installed?

Okay then this is a bug, not a gameplay question, so I'll move it over, it may be that KSP is using the old physics values, how do you start KSP ?

Are you absolutely sure about that? Press alt+F12 to enable the debug menu, select the physics tab, and then thermal, click the checkbox to enable thermal data in the action menu. Now open the action menu on various parts of your craft, you should see a lot of heat being radiated from the thermal control panels, in fact we can see exactly this thanks to the colour overlay. You should also see a very high heat level in the tank and engine, higher than the thermal control systems can deal with presently, as indicated by the brighter colour of those parts. Heat levels should be dropping, but if you're as hot as you look to be, it will take some time.

It pre-dates the GameData folder, has the wrong format cfg files and it's DAE+png, I might be able to re-export it with Taniwa's blender plugin but it'll look pretty rough. Now we have I-beams and basic winglets it's possible to make stock rods now too.

I can't run the Unity editor so it's going to stay un-updated, but it's literally just a rod and a winglet, not hard to make. Also I never uploaded it anywhere but here...

Thanks, can you also please post the log from dxdiag. Arnpld, please also post pics of your vessel that you use when it crashes, and try copying KSP to C:\Games and running the copy.