sal_vager

For ages It just didn't register with my brain that the W and S rotation was in the opposite direction with shift pressed

Can you open the debug panel with Alt+F2 and check the thrust isn't hitting anything it shouldn't please

I can confirm this Skunky and Tiberion can be persuasive

Moved to the Kerbal Network. Yeah better do a virus scan, can you describe the issue a bit better though?

Yeah I think it should, it's solid, the size3 adapter shouldn't though, you can see through it

http://forum.kerbalspaceprogram.com/threads/38577-0-22-UbioZur-Welding-Ltd-2-0-Dev-STOPPED Désolé, il est vieux. Google translated

Guys, it's better for everyone of the thread stays on track and doesn't turn to arguments or insults, and from seeing many threads in the past like this I think that's the direction this is heading in. Different people play KSP differently, some like stock while others like addons, but neither way is more "right" if the player is enjoying themselves. It's true KSP has been in development for a long time, it's a complex game but the issue tracker is not a great example of what's wrong with KSP, many of the issues are duplicates, just crash logs, really minor, not really bugs at all, intended behaviour or already fixed but not updated yet. Squad is committed to finishing KSP, and will be adding much requested features such as better aerodynamics, in-situ resource utilisation and multiplayer. And of course there is mod support so players can tailor the game to their liking, even you Derfel, and if you are having trouble with running the game we'll try to help you with that

Hi jkacer, your KSP.log and output_log.txt may help, see the stickies for info on these. A google search for the stop error 0x00000116 gives me these two pages from Microsoft (1) (2) They mention AMD and Nvidia graphics drivers, and your failing module is also a graphics driver but in this case for Intel. It is probably a good idea to fully uninstall your current driver, reboot, install the latest driver and reboot again, that is the best way to ensure the driver installs properly with no traces of old drivers. If the problem persists please let us know

I'll close it I guess

What happened to Kaspers candy Red Iron Crown? Kasper gets his candy but he also gets toothache. Granted but now you lose your chance to be a moderator. I wish for a Kerbal style cake with green icing

Why are you blocking the thrust of those LV-T30's with those girder segments? Pipped to the post by Slam_Jones, my hat is off to you sir

This is so old. So old! It has grey hair and a tweed jacket. It's best this goes back to sleep

Missing the log there, but did it persist if you left and returned the save or re-started KSP? To be honest I don't know what causes this yet or how to fix it, it's most likely a bug but without being able to reproduce it it's harder to find out why it happens.

AMD is getting better supposedly, at least the occasional post on /r/linux seems to suggest that, so it may be worth trying the latest driver instead of the out of date junk in the Ubuntu repo. It takes a bit of effort to turn the AMD driver into a .deb that Ubuntu can install, but it's not hard See here for more info.

Pet peeve of mine are trolls who claim their posts were deleted or edited to try to cause controversy, who make claims with no proof then crap themselves when they are called out to provide the proof they don't have, and then act all insulted, but then this is the internet It's funny watching them make a fool of themselves though Oh right, this was about pet peeves in KSP, sorry, I know this is a small thing but having to raise the navball every time I first go to the map is a real pain in the butt, it'd be nice if it toggled on and stayed up

I guess you could use the Mk1 landercan for this but it's a bit late in the tech tree, but a titchy single-Kerbal can would be cool

Seeing the FPS of games in Linux is a pain if they don't provide their own method, though any game run in Wine can be made to show the FPS that's no use to us. You could try glxosd to put an on-screen FPS counter on KSP, it seems to work. To use it you need to start KSP from a terminal or a script with: glxosd ./KSP.x86 Or: glxosd ./KSP.x86_64 You should be able to just run glxgears as well and it'll output the FPS to the terminal, if your FPS drops in a game the FPS in glxgears should drop also, but it seems limited to the screen refresh rate. Glxgears is so light on resources it doesn't effect your game at all, but you have to be able to see that terminal Glxgears is garbage.

Looks like you managed to break it, it's a simple enough looking craft that you could rebuild it easily enough I think, but if you really want to try to save it you could try putting the file in the sub-assemblies folder and loading it from there

Try looking directly down on a rocket from above, you'll see

Or wait till one passes and flag him down Moved thread, our problem is probably the openGL switch, don't use it and see if it works, if not then post your logs

Hello Sampa, have a belated welcome to the forums

Players could just refrain from abusing it As far as I can see it's not really a problem that needs to be fixed.

Welcome to the forums Antiles, looks like a cool series, good luck with it and have fun

Except, KSP for Linux already uses OpenGL, there's absolutely no point in forcing it because it's already on. I'm not sure about the thread optimisations though, it is reported to work for some people and not for others, might be hardware dependant. But yeah, Steam starts x32 by default, but it's easy to change Changing to solved as players will be more likely to take a look here if they think they will find the answer to their question, good work Kerblam, I hope it helps people

This thread has now been closed at Arsonide's request