sal_vager

You're forgetting the energy in the fuel itself there.

When KSP starts, it looks in the settings.cfg to see if you've allowed it to send data or not, if it can't find the settings.cfg it assumes it's the first run and it asks you, then it makes the settings.cfg file. If for some reason your system is preventing KSP from making a settings.cfg or from finding it, it'll always assume it's the first run and it'll ask you. So, something's up, maybe you run KSP on the desktop, maybe your antivirus updated and it's silently deleting the settings.cfg every time, because what you are describing isn't normal.

Hi ahyokata, putting all the files from the zip into your current folder might have messed something up, please try installing KSP again to a new folder and verify that it works, you can then copy your saves over

This may sound contradictory now, but you don't really need an xorg.cfg these days at least with Debian based distros, and you can do a lot of this stuff using Synaptic which is already installed in Mint. Synaptic is a graphical package manager, it can uninstall the driver from the Nvidia site, install the one from the repo that has been tweaked to work on your system, and set it up for you. This is a little old but Synaptic hasn't changed much, you'll most likely find the 346 driver in the Universe or Multiverse repo, which is easily enabled in Synaptic.

Could you upload the savegame please Invader Jim? Pop it on dropbox and we can have a go with your vessels

I'll just link this here in case anyone looks, the pre-PPFX glow still works, and doesn't flash annoyingly, I actually prefer it

There's two glows, the PPFX edge glow which looks like this and the Squad part glow that covers the whole part. PPFX needs the built-in Unity anti-aliasing enabled to function, even if it's overridden by your driver AA. -force-opengl has been a bit weird since 1.0, and doesn't work for everyone, it's a Unity engine command line switch so if it's broke there's nothing we can do to fix it. KSP still uses a lot of RAM for the pqs terrain stuff, so check your ram is levelling off, and not just continually climbing, if it's climbing all the time it's a leak.

Congrats to Van of the Monde, and I can put my feet up and watch him look after GD for me

KSP detects the card so that's something, have you rebooted since installing the driver? And are you using anything like Bumblebee?

Squad learns what players want from reading the suggestions forum, and many of those suggestions are for things that already have mods or are mods themselves.

Wow, because "better aero" was so unique, no one would have thought of that. Except maybe hundreds of players since KSP's earlier days when modders like C7aerospace made one of the most well known parts pack for KSP, who then went on to being hired by Squad, working with Squad for years and who's name is one of the Kerbal companies. But nope, a modder had that idea first, so Squad had better remove all the wings from the game eh? Because they stole the idea of flying. Ferram made FAR because flying was popular in KSP and the existing flight dynamics were poor, but no, a modder had an idea for better aero, better go back to pre .90 aerodynamics eh? Because they stole the idea of flying. Better remove re-entry heat then, and flags, that was an idea from a player first, also extra planets, all we're allowed is the Mun. Oh I see you can't provide any proof of Squad stealing mods, what a surprise.

Hmm are you using the KSP.x86 or the KSP.x86_64? The x86 version can fail to run properly without some i386 components from the mesa driver. Can you please upload your KSP.log to hastebin for me?

Hi cfusting, it's most likely the graphics driver, KSP really needs the proprietary driver for AMD or Nvidia cards, and make sure the driver is loaded, it's easiest just to reboot. Ubuntu 15.04 has the Nvidia 346 driver in the repos now.

Show proof KSP 1.0 uses any FAR or NEAR code, go on, I'm waiting. Players wanted aero updated, they got it, claiming that Squad used an existing mod is absolute crap, sorry, as you should be aware that FAR had to be remade to work in 1.0

Hmm that's odd as I have nouveau and the proprietary driver installed together, oh and on Ubuntu 15.04 the 346 driver is in the repo, so installing is easy Mint should have it too.

Hmm, looks like it might be transfer window planner. Also there's this. It should never be writing to 00000000. Can you try removing the plugin for transfer window planner and see if it helps?

Hi Sokar, yes you will need to download the Linux version of KSP, you already have access to both Linux and OSX versions as well as Windows, depending on where you bought KSP you will see the other versions available to download. Linux distributions usually handle all the drivers for you, with an option to install any proprietary graphics driver either during install or from the software repository for that distro. Many people will recommend Linux Mint as it is very complete and easy to use, it is based on the same distro that is used to make Ubuntu so KSP should work fine. There's lost of info online on installing Linux, and we'll be glad to help here as well

Is it an old settings.cfg? Some bindings changed with 1.0, try renaming it so KSP makes a new one.

Wow, just wow, so renaming the 64bit binary file from the Unity engine is now a "mod" ? It's literally taking the compiled game engine binary file from any exported Unity project, renaming it "KSP.exe" and putting it in the KSP folder! There is literally nothing to update! Squad didn't offer 64bit because it was unreliable, and it still is even with the binary people are getting for themselves, sure most stuff works but career is broken, and because the Unity4x editor is 32bit it can't be debugged! Calling that a "mod" or "stealing" is absolutely hilarious and a blatant screaming lie. Go ahead and make your own x64 executable, just download Unity, export a demo project to Windows 64bit, rename the exe to KSP.exe and go, well done, now you are a modder and Squad can steal your hard work when they release KSP on Unity5 with x64 support That guys claim is complete and utter bilge.

Okay, it's a memory issue but doesn't look like it's the leak as you have plenty of memory available. Error occurred at 2015-06-11_031210. F:\Steam\steamapps\common\Kerbal Space Program\KSP.exe, run by vvk. 62% memory in use. 3575 MB physical memory [1324 MB free]. 3410 MB paging file [1337 MB free]. 2048 MB user address space [176 MB free]. Write to location 00400000 caused an access violation. But KSP runs out of memory that it can use for textures. DynamicHeapAllocator out of memory - Could not get memory for large allocationCould not allocate memory: System out of memory! Trying to allocate: 16384004B with 32 alignment. MemoryLabel: Texture Allocation happend at: Line:411 in Memory overview [ ALLOC_DEFAULT ] used: 341859459B | peak: 0B | reserved: 377472362B [ ALLOC_GFX ] used: 329496239B | peak: 0B | reserved: 399458082B [ ALLOC_CACHEOBJECTS ] used: 323008B | peak: 0B | reserved: 12582912B [ ALLOC_TYPETREE ] used: 20472B | peak: 0B | reserved: 4194304B [ ALLOC_PROFILER ] used: 291348B | peak: 0B | reserved: 8388608B Could not allocate memory: System out of memory! Trying to allocate: 16384004B with 32 alignment. MemoryLabel: Texture Allocation happend at: Line:411 in Memory overview [ ALLOC_DEFAULT ] used: 341859459B | peak: 0B | reserved: 377472362B [ ALLOC_GFX ] used: 329496239B | peak: 0B | reserved: 399458082B [ ALLOC_CACHEOBJECTS ] used: 323008B | peak: 0B | reserved: 12582912B [ ALLOC_TYPETREE ] used: 20472B | peak: 0B | reserved: 4194304B [ ALLOC_PROFILER ] used: 291348B | peak: 0B | reserved: 8388608B (Filename: Line: 920) No Texture memory available to upload (Filename: Line: 585) [PlanetariumCamera]: Focus: Kerbin (Filename: C:/buildslave/unity/build/artifacts/StandalonePlayerGenerated/UnityEngineDebug.cpp Line: 56) UnloadTime: 54.410816 ms HighlightingSystem : Edge Highlighting requires AA to work! (Filename: C:/buildslave/unity/build/artifacts/StandalonePlayerGenerated/UnityEngineDebug.cpp Line: 56) HighlightingSystem : Highlighting System has been disabled due to unsupported Unity features on the current platform! (Filename: C:/buildslave/unity/build/artifacts/StandalonePlayerGenerated/UnityEngineDebug.cpp Line: 56) No Input Locks in effect right now (Filename: C:/buildslave/unity/build/artifacts/StandalonePlayerGenerated/UnityEngineDebug.cpp Line: 56) Crash!!! You mention using a certain savegame and craft, please upload that savegame so I can try it, also upload your dxdiag log.

Hi CaptainApollo, check your wings, the big ones hold fuel now but they start empty.

Hi OrangeTang, is this plane a probe? Try going to the tracking station and mousing over the top edge, you'll see filters, make sure the one for your planes vessel type is on.

No idea on the RCS, unless mechjeb is overriding it somehow, or fine control is on, they are supposed to auto balance with fine control but you tend to lose a lot of power, and the jets are hard to see.

Are probes off in the map filters? Try mousing over the top edge of the screen.

How hot are they getting? They can get very hot before they explode.