sal_vager

Heh, if you're seeing these while using -force-d3d11 or -force-opengl I don't think I can help, they are completely dependent on Unity's support for those things

I think all the science gadgets should open up a minigame style thing based on each one with buttons and dials, so you have to tweak them to get the science result. Might be a bit tricky taking a Gravioli reading while aerobraking at Laythe but that'd just add to the fun

That'll be good for Nvidia owners, I heard someone got CUDA to work on Linux as well, it'll not work for AMD or Intel users though. Oh hey looks like it is supported!

Funny how other games companies also don't seem to make roadmaps available, unless it's a driving game The only software roadmaps I was able to find after some Googling are the Logitech Squeezebox roadmap, which looks a lot like the changelogs / Dev blogs / articles that Squad provide, and the Introversion Prison Architect "roadmap" which is just a forum thread. It seems that in almost all cases, internal documents are internal, and neither Indie developers like Mojang or big companies like EA are willing to make them available. Unless those documents are the roadmaps, then you already have info on what's coming next

Cuda is the Nvidia graphics card thing, Unity physX is run in software.

Being under the MIT license is good and it does mean there won't be any license issues using it with GPL software, but only the core is free, everything else is either "shared source" or is proprietary. So while nice, there will still need to be non-Microsoft compilers and IDE's to work with it, that is where Mono and Monodevelop can come in, we're unlikely to see Visual Studio free and open source any time soon if at all.

Moho used to have an atmosphere and was hot as vindaloo, you had to be really careful when taking off from there, we hoped Moho would get lava one day. Not likely to be this V thing though, something to do with the 5th planet maybe?

I miss hot moho.

Is this a hint of Kerbal origins and they are really lizards?

You need to eat more cereal Kryten

Can't view the log unfortunately, but like the others said it's the card not rendering the textures but we have to find out why. Please reupload your logs or make the ones on googledrive public, also, have you restarted the PC since updating the graphics drivers? It's probably a good idea to disable antialiasing and the fallback part shaders, those are for legacy hardware only.

It might be

Hi Sinsis, though I don't know if this is the exact reason I'd assume the memory use you are seeing is due to KSP terrain caching, as you move around on a planet or moon a lot of terrain data is generated, it is freed as you go but it still needs a fair bit of RAM. Add in terrain scatters and water and memory use soon adds up.

Chemical spills can have extensive knock-on effects, there may be no way to know how much damage something like this can do :/

There's no limits on receiving reputation, it's not even an option in vBulletin

ATM takes a looong time to do its thing on first run, it mentions this in the thread, it could take an hour if you have a lot of addons. Leave it running while you go do something else, like watch a movie

I've never seen this before, this is going to take some work to figure out I think, we'll need your logs Suseika, please see the stickies for info on where to find them and upload them. It'll be interesting to see the logs immediately after this occurs, you should still be able to alt+tab out to the desktop when this happens, but if you restart KSP the logs are overwritten.

I'm waiting on size 11

Okay the very last thing before the crash appears to be the final frontier addon: FF: destroying Final Frontier (Filename: C:/BuildAgent/work/d63dfc6385190b60/artifacts/StandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49) FF: storing configuration in C:/Program Files (x86)/Steam/SteamApps/common/Kerbal Space Program/KSP_Data/../GameData/FinalFrontier.dat (Filename: C:/BuildAgent/work/d63dfc6385190b60/artifacts/StandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49) FF: storing window positions (Filename: C:/BuildAgent/work/d63dfc6385190b60/artifacts/StandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49) FF: writing 5 window positions (Filename: C:/BuildAgent/work/d63dfc6385190b60/artifacts/StandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49) [SmokeScreen PersistentEmitterManager] : OnDestroy (Filename: C:/BuildAgent/work/d63dfc6385190b60/artifacts/StandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49) UnloadTime: 12.171533 ms Crash!!! But that may be caused by a lack of memory: 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 FF was definitely the last thing active at the time, so I'd test without it if possible, but it looks like it's a memory issue. Something else to try though would be Active Texture Manager to reduce the load, I didn't see it in your log.

Only so much RAM can be accessed by a 32bit program, more info here, so KSP can't use all of your 16gigs. We're hoping Unity5 will solve the problems as it supports 64bit more fully, it even has a 64bit editor which will make dealing with bugs in 64bit builds possible. Google drive is saying your file is inaccessible, you may have to make it public or host it elsewhere.

Memory allocation error, could be just running out of RAM, but your output_log.txt could tell us more.

Everyone can have a bit of fun with this GIC thing, even you RaS

We all want to keep up the game, now stay on topic please, GIC must perish!

That's enough spamming now Kenbob, your post is deleted, but you know what I'm talking about

Hmm, those contracts usually state that you need to either stage the TT-70 or right click it and "Run test", though it's usually the former. Can you show us screenshots of the contract and of your craft in space please? I recommend you use Imgur.com for the pics, take them with F1.