Wallygator

(Wallygator douses torch in water, places pitch fork against wall... Still within reach if needed...)

No worries. We will keep our pitchforks and torches in check till we hear back

Let the Devs take what time they feel they need based on the content planning that they mentioned is just about to get underway. Telling a team to go faster or slower without any knowledge of their planned workload is a formula for destroying trust. That said, I would highly recommend the Dev team consider showing a small bit of love for their dedicated OS X users in the next update. I don't even know what it is anymore - memory leak, poltergeist, Ghost of Steve Jobs, who cares. KSP is nearly unplayable for more than 10 minutes before graphics meltdown or crash to desktop. This is not a bug report - that's been done many times by many players. This a call for prioritising OS X reliability on the 1.1 agenda - take what time you need boys... I've got a old POS linux laptop I can sputter on with in the meantime - but I love KSP so much more on my 27" retina display (TL;DR eye-gasm).

Engineers improving the laws of thermodynamics? No thank you. Repair a part that is borked due overheating? Yes. He can stand by and repair when required. Yes. Give me a radiator and he can install it? Yes. Better add a new class of kerbal instead, call them MAGICIANS. But please let me fire them in the astro complex the minute they appear in a cloud of smoke and a drum roll. I'd like a long Shepard hook to come in from stage left...

I thought it was entertaining... for about thirty seconds. It's now permanently turned off. Two sliders? Huh? Where's the "toggle" we asked for? :-) Seriously, I can see why some people might like it, so it is likely a fine addition to the interface, but still.. I would have rather had more IVA activities and cabin control options - something for mental immersion not just overloading my visual.

Read my sig...

I have seen the "Half-life" of community resistance to change last about as long as it takes for their favourite mods to come back on-line. Modding is a core framework for KSP, I can be critical of both the Stock system and any mods I choose to explore also - all the while having fun. And frankly, 1.0 is causing me have more fun than I expected - even with a few pesky bugs. All will be fixed in time... But its important to call out bugs clearly and politely. This small crap storm will pass by soon... Clearer weather ahead!

I've tried to be sensibly and constructively critical of any output and or manner where decisions and processes are perceived to be faulty - this has never been about people from my perspective and comments. I'm sure everyone in the QA and Exp teams is doing their jobs to the best of their ability - and likely with little or no pay! I would buy them all an espresso, but I can't afford it or the air fair at the moment That said, I'm guessing here (but probably close to being accurate) that the core KSP team has been and is continuing to deliver a complex product with an expert small group of individuals. There is likely little time to spend documenting processes or improving delivery quality, measures, tracking and reporting, etc. All the while knowing that delivering quality software is a complex endeavour that boggles even large global organisations (Microsoft anyone?). Doing it successfully as an Idie team is close to freaking miraculous. (I help improve programs and organisations that deliver tech and SW as a profession - nobody does everything perfect - Nobody!) As a community we all should consider re-thanking our Squadies for this incredible road they have traveled, recommit ourselves to being a bit more focused in our criticism of product and process, and staple notes to our foreheads that remind us to absolutely refrain from personal attacks. As for Squad, you all might take learnings from this overall 1.0 event as well. How you communicate (when and where) matters a lot. Squandering trust is easier than building it. Thankfully, you still have a strong committed core of supporters (AKA critics) that can still contribute more than just comments - they might even feel that have a stake in the final design from years of input and support. Further opening up your design decisioning processes for comment prior to releasing features might be something to consider - but as always, it's your decision to make. (For Example: creating a carefully selected cross sectional group of key users to act as an external design review board - confidential NDA, non-binding decisions of course - maybe you already have that - would be nice to know about it). So from me... Thank you! I love 1.0 (Please post that on your Internal Jumbotron if it exists, and then get back to something more interesting like fixing those pesky bugs... and revamp career mode, and those fairings, and... and.... and...)

Regex, your work here is the napkin and straw that should have come with my delicious KSP 1.0 happy meal. I now stand up, face west and salute you. (I could have faced east as well, but there's this bookcase...)

I fully support this also. Either through tweaking or through locking of stages. Give me both? Anything that improves quality of play life is good.

It might also be nice to have the staging column on the left converted to a ship systems display where all parts in each stage could be shown (they could be collapsed or expanded of course) Then if a part is overheating, it could show up in the associated stage in an appropriate flashing color. Click it, and the temp data could pop up adjacent. Throw in the audible alarm and bobs your uncle!

Probably not too well. But your comment provides direct support of my point. NASA pays spaceX to do something for them, not the otherway around like in KSP.

I don't think it looks very polished but I can live with it. Would be nice if they allowed a player to select the cursor size and shape instead.

I think it is an excellent attempt. Many good changes, many bugs remain. More importantly, I hope we can all finally learn that this NOT the a final product from early access, but rather the latest output from an "Open Iterative development" model (maybe not so open as most would like and likely going to get less open) but still... More versions to come. For me, I'm still mostly disappointed in two things 1) that squad refuses to break open and away from their grind fest career framework - which should be more refined and actually appear to BE a space program. The player(s) should be working for theirselves rather than for a bunch of silly subcontractors. Give me an annual budget and public opinion, shifts in macro economic or political mood to stir things up (as if my failed missions were not enough!) 2) that we remain saddled with a deterministic tech "tree" framework - come on guys! Everything else I can live with. These two things... This is where squad needs to pull their finger out and get innovating and stop copying old ideas.

Claw - Your work is absolutely amazing and most helpful. Now I truly know why there was an awesome movie made about your forum name! http://badmovies.org/movies/giantclaw/

That would be me. I created the graph (Bows) but Red Iron Crown has been kindly updating it (Bows again in the direction of Red Iron Crown).

I stand corrected regarding the editing of fairing and that there may be a way to construct an interstage version - need to try that tomorrow. Now... regarding the whole mass issue... I installed KER and checked it out. No need to launch anything really. Unless KER is providing the wrong info, the fairings once ejected did not change the mass of the vehicle.

You haven't convinced me - but please continue... As I indicated above, I checked the mass of a simple construction on the launch pad before and after ejecting fairings - no change was indicated. I'll do another test in a different manner and see if I can change my own mind.

Yes, The mass of a vehicle's fairing "base" changes as the size of the fairing on top of it is increased during build - BUT all the mass is placed in the base. When the fairing ejects, it does not change the vessel's mass. You can check it on the launch pad. This is counterintuitive and should be addressed. Also, while I find the fairing build schema to be entertaining (for about 30 seconds), it is rather clunky and lacks real usability - you cannot edit a fairing (from what I can see) - must always rebuild it. Finally, it looks like these are ONLY aero fairings and there is no support of interstage constructs (Am I wrong here?) Summing up... I am throughly disappointed. I can't help but think someone tried to be quite clever but then just ended up getting distracted (like focusing on the initial build sequence rather than overall interface and functionality) I think Stock fairing must go through a redo.

Im shocked and amazed my little lol-graph is catching on. I declare it to be open-source and set it free into the internets. Snaps to Red Iron Crown for quietly taking on the maintenance of said graph. That said you can put me in "Rarely post" and a bit left of center.

I'm feeling that the OS X glass has been left empty since .25 Frankly, I'm very happy with the changes implemented with 1.0... BUT the reliability and crashing to desktop is still present. I sense this is due to very poor QA and testing coverage regarding OS X in general. Still... Love the game, but my patience with it has fallen. In the past when I has a crash, I would reload. Now I just walk away for awhile and release my anger. EDIT: Regarding the general sentiment that the community has become negative and tolling... NOT SO. What we are experiencing is the result of a constantly maturing and evolving community that through the entire early access process has developed a feeling of comradeship and joint ownership regarding the content and configuration of the final product of KSP. When the Devs appear to not listen, the volume of response rises, when a release continues to deliver persistent bugs identified multiple releases prior then the volume of dissent rises. Its only natural. Where are you on the graph???

Same issues here. Im just plain tired of sending crash logs, etc. I find it hard to believe there is no effective testing going on internal to the QA or experimental teams regarding OS X. The same crashing behaviour has been occurring since .25 I'm really tired of this, as I expect all fellow OS X users are. This is not the level of reliability one should expect from a released product. We are now past early access and the gentle tolerance that comes with it. I hope the folks at Squad are sensitive to the disappointment that comes with this recurring behaviour - and I hope a solution can be provided soon. Still, Love the game... but my patience for it has been drastically reduced.

Thanks for that.

The 1.0 release is not available for download from the KSP store - due to a "server Migration" Any word on when this will be completed?

I'm running out of things to do on my "Stuff to fix around the house"list... Need 1.0 soon...