sal_vager

Yep, ask, but it's rare that a thread is stuck due to asking, threads are usually stuck because they merit it in some way. And never bored of the forums, no.

When you start KSP it writes to a KSP.log in the game folder and an output_log.txt in GameData, these logs will say what's going on.

Yeah AA in KSP is broken, but a few things rely on the option being enabled, AA can be forced by the driver though. Supposedly it's possible to fix v-sync on Nvidia, I have not tested this yet though.

Please also test a new save, and if it still occurs please upload your output_log.txt

Okay not much stands out, the log says the highlighting system is off due to anti-aliasing being off, It's worth testing with AA on just in case. The PC specs seem fine, you're using Mint though and I have seen some reports of graphical and performance issues with Mint, though nothing concrete as a cause for them. If it helps to compare systems I am using an AMD A10 with a Nvidia GTX650, and Xubuntu 15.04 I don't suggest you change your OS, but you may see an improvement if you disable Cinnamons compositing, you might also see an improvement with a lighter desktop environment, which can be installed via synaptic and selected in the login menu (no need to reboot).

Nothing yet unfortunately, but be my guest.

This question on gameplay has been moved to Gameplay Questions

Okay it shouldn't be doing it to that degree, I get a stutter when I do that but it takes a lot longer for the unused reserve to fill up, and mine isn't anything like as severe. Your Windows demonstration looks like what KSP does on Linux for me. So maybe we can find a way to alleviate it for you until 1.1 replaces the UI, if you could upload your hardinfo report (sudo apt-get install hardinfo, and is called System Profiler And Benchmark when installed) and your Player.log after spinning the camera in KSP (/home/user/.config/unity3d/Squad/Kerbal Space Program/) it'd help with figuring this out.

I'd be a bit careful with these, x-swat hasn't been updated since 2013, so more recent versions of Ubuntu actually have newer packages. Edgers is up to date, and there is Oibaf if you would prefer open drivers.

Actually, the French system language may be the culprit, though you are not suffering the usual symptoms I'd associate with this. Long story short, some languages swap the comma and period in the cfg files, breaking things, the fix was to launch KSP via a terminal or a shell script with "LC_ALL=C ./KSP.x86" But, that command is built into the KSP.x86 now so it shouldn't cause an issue, and you would see other problems such as no attachment nodes in the editor and oddly scaled parts. Some languages can mess with the file paths though, but I hadn't heard of French doing this and everything else loads. But you have tried everything else so try setting your system language to English.

This isn't really asking for support for KSP, and I don't think it's right to imply that Squad somehow supports, even if we are volunteers, overclocking which has the potential to damage your hardware. Moving this to Space Lounge, good luck but I'd recommend against this.

Thought I'd better merge these.

If you restart KSP it stops this from reoccurring, a reload isn't enough.

Did you accidentally toggle the torque in the action menu?

Well it is a different OS, with very different drivers, and one of the issues with rotating the camera has been the UI redrawing, thankfully this is being replaced for 1.1 Why it goes up much faster for you is interesting though, can you video this so I can see how much faster? Simple screen recorder is probably the best tool for this.

Hi nyma11 and welcome to the KSP forums All testing of the PS4 version will be undertaken by the company making the port, Flying Tiger, and won't be open to KSP players unfortunately, so there won't be a signup. Thanks for asking though!

Yeah just posting it as a link or in [noparse][/noparse] tags would be fine though, or a small taster image that links to the full pic, like this. [noparse][/noparse]

Posting that image to the forum in [noparse][/noparse] or [noparse][imgur][/imgur][/noparse] tags would result in an excessively long post forcing members to scroll a long way to avoid it and view the post after yours, not everyone will want to view a long string of soldiers waving guns, and I'm surprised I have to explain this. So no, for others sake please only link to the image so others can choose to avoid it. Redninja'd

Considering how much scrolling a member would have to do, and how much trouble this is on mobile, I suggest you just link to images of that dimension instead of embedding them here.

This seems to be turning into a parts wishlist rather than discussion of the parts coming in 1.1, moved to Dev discussion.

Whoops, sorry I saw , I normally see that on 64bit and thought it was loading them on 64bit, the KSP.log shows your system specs , plus I see so many files in a day it's easy to lose track. Yeah two files always come up as corrupt after launching KSP, but it's never caused an issue, I think one of them is the Settings.cfg as KSP writes to it on every launch, changing the timestamp. Obviously re-installing didn't help and I'm at a loss as to what to suggest. I found this in the last log though and I don't have it in mine: It's straight after the input devices, don't know what it means though, maybe unplug whatever "LIS3LV02DL" is, I can't see how it'd be a bad file path unless you were using a non English locale, some such as German will corrupt cfg values, and others such as Chinese can cause KSP to break. This is odd as well: My file doesn't have "Changing real window size" or "Ignoring window size change", so it's strange that it is happening here. The stacktrace does mention Mono code: But KSP uses the Unity engine's own modified Mono library, so this tends to pop up with every stacktrace anyway. I'm stuck to be honest.

Lets not argue please. Thank you pizzaoverhead for clearing up this issue, the matter is reported to the correct place, until it is fixed we can use the workaround of clicking the save button.

Perhaps on some other forum yes, but not here.

Moved to Dev Discussion, though the original question is moot as Squad already intend to add multiplayer and are developing it. As for how any part will work I'll leave you with these sage words... "All content is subject to change"

I can shed a little light on some of these warnings at least. This means that anti-aliasing is off, and can be ignored. This may be a red herring as I also see this in my log, "[RESOURCES]" tells me this is an issue with the resource system, "BaseConverter_SetupModule" appears to be part of the resources code, I assume it's a constructor that is called when you enter the flight scene and it's job would be to set up the resources system. "Object reference not set to an instance of an object" means the data couldn't be found, most likely it wasn't loaded yet as it only seems to appear in the editor. I'm able to , so I'm a bit stuck as to why this is happening.The log says anti-aliasing is off, maybe something on the MPL is causing the graphics to break so try turning it on in the KSP settings. Your Player.log says you are running KSP on a 64bit version of Ubuntu so you may be lacking some Mesa components KSP needs, try "sudo apt-get install libgl1-mesa-glx:i386" in a terminal, it'll complain but should still add a few things you may be missing. If that doesn't help you may want to consider removing the fglrx driver and using the built-in open source driver instead, fglrx is not as good from all accounts, as the open driver sees more frequent updates and better hardware support.