LordFerret

I would think that, unless there's a serious chance of risk to a major population center (wherever that may be), they would want to see as much of it survive reentry as possible ... if for no other reason, to perhaps figure out why things went wrong. Yes?/No?

Not related to Linux, I'm using Win 8.1 here (for now), but in v0.90 I had a similar problem - leaving the machine running for extended periods of time at the Esc menu ... upon return, back into the game, I would experience extreme lag (on the order of 4fps). Restarting KSP solved the problem. I've not run into this with v1.0 yet, but I'll make a point of trying it. At some point, when I set one of my other Linux (Debian) laptops up with KSP, I'll test it there as well and see if I get a similar result. What version of Linux are you using ekimekim?... and what sound card/driver system (ALSA?) & desktop ?

KSP Version: 1.0, Windows 8.1, 64-bit, playing a Science game. What Happened: I built a rocket (Progress-1) which had an Mk1 Command Pod with one Service Bay beneath; The Mk1 had two Mk2-R Radial Mount Parachutes attached, as well as a Mk16 Parachute on the nose. After launch and one orbit, on reentry, both Mk2-R chutes refused to deploy, even after trying with the right-click menu option. The message given was: "Cannot deploy while stowed!" (see image #1 below). After attaining more parts and science experiments, a second (updated) version of the rocket was built with an Mk1 Command Pod with two Service Bays stacked beneath; Again, the Mk1 had two Mk2-R Radial Mount Parachutes attached with a Mk16 Parachute on the nose. Twice (because of unrelated catastrophic failures, reverting back to Launch) when attempting to deploy chutes, one of the Mk2-R's refused to deploy (and again) even after trying with the right-click menu option. The same message given was: "Cannot deploy while stowed!" (see image #2 below). After these two events, I began to prepare to submit this (potential?) bug report, but then remembered it had been suggested I try opening the Service Bay and then trying to deploy the chute(s) again ... because perhaps the game thought the chutes were stowed in the bay. {This suggestion resulted from a previous post I made the other day on the subject: which is here.} So, I went back into the game to repeat the event for a third time to test this. However, when I did, all chutes deployed without a problem ... as if exiting the game and then reentering magically solved whatever the problem was. I figure I will submit this none-the-less; Maybe it is a bug, maybe not, perhaps someone can take a look at it. In the mean time, I will continue to use this rocket and will report back here if it begins doing it again. My persistent file and craft file are linked below, saved and uploaded for this report before I tried to repeat and test the Service Bay open test. The output_log.txt file is also linked below, but, unfortunately, I didn't grab it until after the third test (sorry). Persistent Craft Output_log System Specs: ASUS laptop with Intel i7-4500U cpu, 8gb mem, Intel embedded graphics and Nvidia GForce GT 745M graphics. Thanks.

Ok, well, after gaining more science and attaining more parts and experiments, I've rebuilt my initial "Progress-1" rocket using the same radial chute setup as before. Catastrophic failures on two tests (from other reasons - overpower & oversteering) had me testing the chutes again unexpectedly. Twice in a row, I got the same resulting problem ... only this time it was just one of the chutes which failed to deploy. I was even mindful this time to mount the chutes higher up on the Mk1 pod too. I exited out and prepared my screenshot and files for a bug report, but then remembered the suggestion of opening up the Service Bay and trying to deploy the chute then. So, I reentered the game to give it a go. Lo and behold, after three launch tests, all the chutes deployed without a problem. Exiting the game and then reentering it somehow magically solved the issue(?). I'm still going to post it as a potential bug report. I'll also leave this thread as an unresolved issue (for now).

Sorry about that, my bad.

Talk about crazy physics ... Vanoss & crew & the 4-man sled. (foul language warning)

Scroll works fine for me (put in 15 stages to test) ... as do the Home and End keys.

I'll let you know after I unlock the entire Tech Tree ... which may be a while lol (Science game).

There's a mod made for that already? By whom? The only thing I've seen thusfar, and used, is a manual edit of the configuration files - see this post.

The heat shield has an indicator for its rate of ablation (Resources button, top-right of the screen). I'm finding however, that external parts on the rocket (antenna, radial chutes, science experiments, etc) are not protected during reentry ... I'm constantly losing my Communotron 16 antenna, which is ok - I guess. It would be cool if it flared off (sparks and such) instead of exploding ... which I find quite nerve-racking. I'm also finding issues with the Service Bay and 2Hot Thermometer science experiment ... I think the Service Bay should be protecting the internal stowed components from heat.

Stock Bug Fix Modules (Claw), updated for 1.0

The problem, I suspect, is the Service Bay. It should be protecting the instruments. I've got a test I'm going to run as soon as I'm done here, will post it later.

You've discovered a cloaking device?

I've gathered 6 surface samples so far ... 3 with Jeb, 3 with Val. Something is very weird, as viewing the 6 surface sample reports in the Science Archive says 11.25 science value for Tundra with a remaining 0.02 ... and there's only one surface sample report logged for Tundra. If I had gathered it elsewhere, even without realizing it, she attained something - that last bit should show as a second entry. There's also just one EVA report for Tundra, show all science attained. Very weird stuff going on, especially with the temperature scans too... notice the temperature scan of the Tundra. I've got some other tests I'm going to do. If need be, I'll reinstall 1.0 and start over and see if it duplicates.

I'll test that out before changing the thread status. Thanks for the suggestion. EDIT Oddly enough, after three attempts, I wasn't able to reproduce the problem.

You should put this information in GoSlash's Helpful 1.0 observations thread.

Would a Mod please sticky this thread? Thank you.

I'm puzzled by some odd behavior of science equipment stowed in the new Service Bay. Pilot for the mission was Valentina. In the first image below, after having landed on Kerbin's Tundra for the first time, I received no science for a temperature scan ... yet the thermometer registered 286.71' (?!?). Neither did I receive any science for the Mystery Goo experiment inside. In the follow images below, same mission, I wasn't awarded anything for Val's EVA report, and very little for the surface sample she took. Is that because she's not a "Scientist"? This is a Science game I'm playing, not a Career game ... does that matter any?

I had a very odd message pop up when I went to deploy Mk2-R Radial Mount Parachute(s)... "Cannot deploy while stowed!". Even clicking on the deploy button in the right-click context menu would not work. I'm not sure why this is happening. Any ideas?

I voted 'Other'. You didn't put an option for a 'Science' game, which is what I'm playing.

Don't know if you've seen this yet, Claw, nor (do I imagine) has everyone currently working with 1.0 ... a needed fix for the heatshield. There's a quick workaround here, but maybe it's something you'll want in your Bug Fixes?

Excellent!

I see. Thanks. Nice! I will look forward to working with this... resource mining is something new for me thanks to 1.0.

I use SCANsat. The newer version of it (not sure if it's still WIP) includes new resource scanning. Are you saying the NBS is like SCANsat's BTDT?... as far as resources go? I'm running a Science game with 1.0, so I've a long way to go before I hit the new items in the Tech tree. I'm wondering if the output of SCANsat resource scanning will indicate the same as the NBS (vice versa) ... which I'm assuming it would/should? (Also, shrugs shoulders and sighs, because he now must wait for SCANsat to update and then go scan all the bodies again lol)

Gees guys... poor Val. I must say, my Val is unusual (??)... maybe just a quirk? Most of the Kerbals make faces ranging from null to happy to even scared/worried at some point or another during a ride ... but not Val - she just sat there happy as could be.