sal_vager

From what I've been able to figure out, Unity will first search network adapters to find game assets, but doesn't give up quickly enough and try the file system.

There's no obvious cause here so you're going to have to test a few things. First, verify your game files in Steam, to make sure any corrupt or missing files are replaced. If that doesn't solve it, test the KSP.x86 and then the KSP.x86_64 in the game folder directly, this removes any interference from Steam and also any issue with starting KSP remotely (desktop shortcut). If it still crashes, try uninstalling the Catalyst/FGLRX driver, rebooting and running KSP with the built-in xorg Radeon driver.

Well, if you change things without knowing what's going on it's going to do some odd things It's all Dutch to me, but I do know this isn't suited to Support, moved to development discussion.

I really hope so, though it should be working now, it's baffling :/

Hi SatanSoldier, can you please put the full Player.log after one of these crashes on a file or paste site for us. You can find it in /home/user/.config/unity3d/Squad/Kerbal Space Program/ Also please test a new career or sandbox game.

Protip, ignore lame facebook ads.

Trigger1112, did you put KSP in C:\Program Files (x86)\ ? None of the installers I've used will put KSP there, the store installer puts KSP in C:\Kerbal Space Program, the GoG installer installs to C:\Program Files (x86)\GOG\, Steam installs to a Steam folder and so on. The only one I don't know about is the Amazon version but I assume it is nearly identical to the store installer. The reason I ask this is that putting any program in C:\Program Files (x86)\ can be bad, as it won't have a registry entry and won't be able to write files properly. Even if it has write permission (running as admin) it'll be continuously scanned by anti-virus software, and checked by data-execution-prevention (DEP), slowing it down. Copying KSP to C:\Games and running the copy would show an improvement if this is the case, but even if it's not faster, keeping it in C:\Program Files (x86)\ could lead to further issues.

Thanks for entering everyone, just PM me when I forget to check here and GoSlash.... yeah, little bit out of this world with that one

Hello everyone, it's been a light month as everyone has been distracted by Squads news, but let's see what you've been doing. ---------- We're starting the fanworks section this month, when a friend of Pandoras Kitten asked "What's the point of KSP?", well, there was only one way to answer... ---------- sdj64 provides the challenge this time, as how could I not mention THE ULTIMATE JOOL-5 CHALLENGE! ---------- Eat your greens! The crew of the ISS does, now that they have determined that growing their own lettuce in space is safe, though they still have to send half of it back to Earth for the NASA cafeteria Thanks to lajoswinkler for the thread! ---------- Endersmens is at it again and this time with a thread on stargazing, considering this forum is full of space geeks I think there should be more of this, and I think you all will like to take a look. ---------- Lime brings us craft from many different forum members this month with his Minicraft showcase. ---------- That's it for now.

Moved to the Kerbal Network as it's not a gameplay question.

Moved to modded support as Gameplay doesn't have a modded section. As you're using an addon for aerodynamics I suggest you try asking in this thread.

Have you tried restarting? Sometimes a terrain texture will become smeared out on one axis, it looks to me that it is being scaled to infinity, it's harmless and in some places it doesn't look too bad. I can see in your pic that the texture is there otherwise you wouldn't see any green at all.

When studios make their own games sure, Flying Tiger seems more of an outsourcing developer, and I just knew someone would post what you posted Flying Tiger do hardware testing, porting, themes and translations for other companies, on top of their game development, and it seems they tend to make engines for other studios rather than their own work. And yes I know that hook-ups game is on that page, no need to tell me.

You certainly can have an opinion, that is true at least But your payment to Squad only entitles you to a license to play KSP, but that doesn't entitle you to any influence over Squad as to how they use that money. Truth is many of you are formulating rather strong negative opinions based on little information, all we know has been covered in the devnotes, squadcasts and similar channels, the rest is conjecture. Take for example the aptitude of Flying Tiger, we're aware that they were involved with some older games, some which a few of you have played and didn't think much of, the rest form opinions based on reviews of these games or worse, on their titles and cover art alone. None of that tells us how much work went into these games or what Flying Tiger has done in the mean time, they have not only worked on the projects from the Wikipedia page as that alone wouldn't have kept them in business. But like most companies, their dealings are largely unknown to the public, not through any malice, just through the simple fact that they don't need to tell everyone what they are doing all the time, Flying Tigers business is such that they would be subject to NDA agreements with many if not all of their clients, and to maintain their business they couldn't make everything they do public knowledge. Squad has reason to trust Flying Tiger with these ports, technical demos likely exist that show this is feasible, but Squad is a business as well and like Flying Tiger, doesn't have to make all their decisions open to public or even customer scrutiny. We'll find out more as time goes by, when there's something to show you can bet Maxmaps won't want to wait

If you change these in ResourceGeneric.cfg RESOURCE_DEFINITION { name = LiquidFuel density = 0.005 unitCost = 0.8 hsp = 2010 flowMode = STACK_PRIORITY_SEARCH transfer = PUMP isTweakable = true } RESOURCE_DEFINITION { name = Oxidizer density = 0.005 unitCost = 0.18 hsp = 1551 flowMode = STACK_PRIORITY_SEARCH transfer = PUMP isTweakable = true } To these. RESOURCE_DEFINITION { name = LiquidFuel density = 0.005 unitCost = 0.8 hsp = 2010 flowMode = STAGE_PRIORITY_FLOW transfer = PUMP isTweakable = true } RESOURCE_DEFINITION { name = Oxidizer density = 0.005 unitCost = 0.18 hsp = 1551 flowMode = STAGE_PRIORITY_FLOW transfer = PUMP isTweakable = true } Your LFO will drain from each tank equally, starting on the set that will be discarded first and working its way up the chain to the root.

A friend of mine showed me this today, it's a film from 1966 putting forward the case for orbital telescopes, which lead to the Orbiting Astronomical Observatory, which in turn lead to Hubble, and the James Webb Telescope. Some older members might recognise the name of the second astronomer in this presentation. If it hadn't been for people like these advocating for space based science, Hubble and the ISS may never have happened.

Hi Bakslackjack. Please don't connect one tank to two or more with fuel lines, it doesn't work, at all. Connect your tanks in series or two into one, or you end up with issues like on your craft.

Moving to the spacecraft exchange

I also have not personally experienced this lag, and I have yet to see any evidence that it is the heat system specifically that is causing lag. I have noticed KSP can struggle a bit more with the hair shader than it did previously, and in case you don't know, the white transonic effect and red flame effect are generated by a hair shader. So all I do is turn aero fx down a notch. But neither of these operate in a vacuum, so something else is happening. By the way, heat while in space is under much less load than in an atmosphere as there's fewer things to account for, for example the only sources of heat are your own vessel and the sun, while the only means of transferring heat are via internal conduction and external radiation. Aerodynamics are also not in operation wile in space, so again it's something else.

Oh no you don't... -30 (+)

Yes pictures would help a lot, but it sounds like you need to shorten your vessel names, the vessel name box does have a character limit so if you've exceeded that (perhaps via manual editing?) it's not going to fit. Or increase your screen resolution so KSP displays properly, the minimum supported resolution is 1024x768.

Make a request for this behaviour on the tracker then, it's still working, even if it's not working as you'd expect

Yeah sorry but this has ended, thread closed.

Have you considered using the larger probe cores?

You can do this yourself in the debug menu, but you shouldn't be experiencing performance issues related to the heat system, it's really not that heavy. I suggest you upload your system specs and game logs, and post in Support, because it sounds like you have an issue that we may be able to resolve.