Arthropode

Well, after a lot more test, I discovered that there is the bug when I launch KSP from the command line (directly or through primusrun/optirun). But when I launch KSP from my file manager (thunar), it is OK. I tested with a .desktop file and launching it whith my file manager and it is also OK, both directly or with primusrun. I didn't tested to launch the desktop file from the command line because I didn't find how. Apparently the bug can be bypassed with the desktop file. But I don't know why there is this bug from the command line. A problem of environment variable ?

I run a 5 minutes old installation directly (but with primusrun) and still the problem : https://www.dropbox.com/s/24d5410wno3n1qt/KSP_thermal_bug_2.zip?dl=0 What I really don't understand is that from time to time, the conduction works. But when I restart KSP, it disappears again. Ans I don't understand why sometimes it is OK. It's not just after a restart, but at random.

Sorry for the first uploading. I tried to set Physics.cfg read-only, but I still have the problem even if I have the correct file (md5sum confirmed). I put here a save, my logs and the Physics.cfg : https://www.dropbox.com/s/nt5fty7q43eczjm/KSP_thermal_bug.zip?dl=0

Here is my save : [snipped] I only added HotSpot to display thermal data and made a test with Kerbal X in a creative game.

No, it isn't a problem of Physics.cfg. I changed it and I ran the latest zip, and I still have no thermal conduction

I don't understand : I had the problem 2 days ago and yesterday there was no issue : the thermal conduction worked fine, but today the problem reappears. I restarted my computer and downloaded a new fresh installation, but it didn't anything. Why the conduction works every other day ?

KSP version : 1.0.4 Linux 64 bit without Steam Detailed explanation : There is no heat conduction inside the craft, so all engines I have tested heat very quickly. This problem happens even with a fresh installation. I tested in sandbox and career, and in both the engines overheated too quickly. To show the bug I used the mod HotSpot, but the problem is the same without the mod. System specs : [TABLE] [TR] [TD=class: field]Kernel[/TD] [TD=class: value]Linux 4.0.5-1-MANJARO (x86_64)[/TD] [/TR] [TR] [TD=class: field]C Library[/TD] [TD=class: value]GNU C Library version 2.21 (stable) [/TD] [/TR] [TR] [TD=class: field]Distribution[/TD] [TD=class: value]Manjaro Linux[/TD] [/TR] [TR] [TD=class: field]CPU[/TD] [TD=class: value]4x Intel® Core i7-3520M CPU @ 2.90GHz [/TD] [/TR] [TR] [TD=class: field]GPU[/TD] [TD=class: value]NVIDIA GeForce GTX 660M[/TD] [/TR] [TR] [TD=class: field]Memory[/TD] [TD=class: value]8069MB[/TD] [/TR] [/TABLE]