linuxgurugamer

No problem, thanks for letting me know you won't be able to do anything for a while

Do you have KIS installed?

you added the vent to the launchclamps?

New release, 0.1.16.1 Fixed nullref after being shown 1st time

Great description of how to replicate it, thanks. And I appreciate the packaged files, saves time in asking for something. Anyway, I think I found the problem, missed changing one line, testing now

new release, 1.1.9 Fixed nullref in the editor Removed log spam during flight (once every 5 secs)

I'm sorry, what is the "icons" issue? If you are talking about this: In output_log.txt, I see this at line 6272, 6312:Texture resolution is not valid for compression: 'D:\Program Files\Steam\SteamApps\common\Kerbal Space Program\GameData\HaystackContinued\icons\button_vessel_flag.png' - consider changing the image's width and height to enable compression then you have an extra copy of the dll somewhere

I also don't consider printing a line or two every 5 seconds "spam". Spam is when there is so much of one thing you can't see anything else However,i've fixed the exception and the spam, will release in a bit

Absolutely right. Care to make the parts to do it?

If vaporvent is throwing NREs, i need to know, please post a log file in that thread. nothing onKURS yet. VOID is real soon now

New release, 1.1.4: Fixed nullrefs when doing symmetry parts Added toolbar registration Removed old toolbar code

I _think_ that will be OK, but ask @sarbian for a better answer.

You need to destroy the texture yourself, when done with it, otherwise it will remain in memory. Use something like: Destroy(tex); I have no idea why it needs a power of two, probably something to do with the compression. My method will load any size without a problem

I've been able to replicate the problem. I wonder if this has been there for a while, I tend to doubt it's 1.4.1 related.

More details, please. And a craft file, with a description of exactly what you were doing. Thanks

So, if the cameras are showing, then it's a known bug related to the Unity upgrade. If nothing else, I need to rebuild the shaders. This is one of a few mods that need significant work due to the upgrade, and it's on my list of things-to-do

For the first, try saving the ship first, and then doing the sim For the second, I need to know more about the flight. The wireframe is experimental, and may get removed if it's too much of a bother.

Lets start off with a log file. I understand you have problems, but you didn't give any significant info, such as which version of KSP, which version of the mod, etc. The log file will provide all of that

I've updated the OP with the correct links

The Ballutes are treated as if they are parachutes, so the same limitations which apply to the parachute apply here. I've adjusted the min pressure to be 0.01, that seems to eliminate the funny stuff with it. The altitude is because the max altitude for a parachute is hard-coded to be 5000m (nearly 15 miles high) And, without coding, I can't have staging cut the lines

Not really a difference, except the coding involved. But the default has to be the current behaviour, which means that the override will default to none, and priority will default to remote

No Soon

New release, 0.1.6.4: Added two methods, currently only working on the stock button: public void DisableMutuallyExclusive() public void EnableMutuallyExclusive() Fixed hovering over button in Blizzy toolbar not working

No, it seems to happen even when the stage has fuel. But I think I found the problem New release, 1.2.6.1: Fixed nullref which occurred after decoupling a vessel

I have to do some updates to the parts, hopefully will have that done tpmorrow