sal_vager

Novapunch is large, check your KSP.log for out-of-memory errors.

August sees three new threads made Thread of the Month of their respective area's! First give a round of applause to Xeldrak and his Doing it Apollo style challenge, now with a new Mun to explore. Next up is czokletmuss' THE GRAND TOUR - VOYAGE TO THE PLANETS thread, his works have been ongoing for some time now and is well worth checking out. Finally, joppiesaus opened a can of nostalgia with the What's your favorite "old" game? thread in the Space Lounge, so dig up those old games that got you started as a gamer, and drop by

There's a lot of nostalgia here, all excellent games that many of us grew up on, it's a fun thread and It'd be cool for more people to see it. joppiesaus, Congrats for making the the Space Lounge Thread Of The Month, and for bringing back cool memories

Very creative czokletmuss More people should read this, so I am happy to announce that your thread is August's Thread Of The Month, thanks for all the work you have put into this

This thread has gathered a lot of attention and the challenge was a lot of fun, and now with a new Mun to explore It'd be great for more people to have a go So this is now Augusts Thread Of The Month, congratulations Xeldrak, thanks for the cool challenge.

Yep, this was meant to be fixed but wasn't, there's no workaround yet and it's cross-platform, we have to wait for the next update for a fix. Until then we have to restart KSP, this issue should not occur every time you play though.

Okay Albert, let us know how it goes

Yeah Albert, you are running out of RAM, are you running a stock install or a lot of addons? Post your KSP.log to www.pastebin.com for me

Yeah, so I don't think this is a RAM issue, an unmodded game can run in 2gigs, I'm still leaning towards a graphics issue as the main problems I have encountered with KSP for Linux are graphics related, or language. Though there seems to be a brand new issue for me at least, if I pause KSP with Escape, 9 times out of 10 KSP will exit to the desktop when I resume unless I revert or return to the KSC first. I get a SIGSEGV every time this happens in the player.log but nothing in the KSP.log Anyone else getting this?

That it works on Windows 7 is not very important, we are trying to get it running for you on Linux here The hardware of course is the same but the drivers are very different, I do not possess an Intel equipped laptop to test this on, but as I already said, running KSP on an Intel GPU is finicky, it may work, it may not. One issue is that even though the card and driver should support shader 3.0, Intel do not support every single instruction and feature of the shader standard in quite the same way as Nvidia or AMD do, and Unity is very sensitive to this especially with the new shaders used for re-entry effects and shadows.

Cartz, you have no idea, if you look up you'll see that DChurchill changed his mind and removed his comment. This thread has devolved into garbage, and it was such a good premise to start with too. I'm closing this before people start throwing things.

I'm not sure no, it's hard to diagnose these faults, the system seems to have 2011 megs of RAM which is odd and might mean that the GPU shares system RAM, with some allocated to it. Still, KSP should run on 2 gigs, it'd be interesting to know how much RAM the GPU is accessing.

Rookery, please see the challenge submission guidelines and rewrite your challenge, it's too confusing/unclear at this time

No idea MacDuckenstein, we'd have to follow the Unity dev boards (if we can even access them) to find out I expect.

It'll only be closed if it degenerates into arguments, feel free to discuss this topic until that point though

Unity already supports multiple cores, what it can't do (yet) is split a thread over two or more cores, so the biggest thread (the physics) hammers one core relentlessly. Your other cores will see much lower use, and might seem to not be used at all by KSP.

Woohoo! Well done Moach, that's pretty amazing

Great, it's just me then, I can click the ports but the target defaults to the root, so I cannot get accurate docking info unless the root happens to be the port.

johanhartman, KSP is really finicky regarding graphics cards and drivers on Linux, it ca work with the open source drivers but usually you need to update them, or give up and use proprietary drivers if available. I'm assuming you have an Intel graphics card and your logs show it does support shader 3.0, which is good, but it's using the Mesa driver, and performance or even the ability to run KSP at all can be a problem. This suggests it is indeed the driver that is the problem here, can you try other versions of the driver?

I'd like that Markarian421.

Can you select individual ports vanamonde? If you can I'd love to see pics.

It's not worked properly for me since 0.17 I think, I can't select an individual port, the selection keeps defaulting to the root part of the target vessel :/

Add to this a numerical readout of the center of mass and center of lift

Pictures of food? Genius!

Nope, this is actually broken, you just get the root part no matter what.