SleepyWeasel

Cantab: I don't think the stick was a special one as it was just an $8 cheaply deal I found at the local electronics store. Seret: That link is exactly what I was trying to do, however I didn't know about fat32 being the reason for the limitation until after I tried a bunch of things myself. The part about making a new partition and all that went find and it reported no errors. After further tests I'm fairly sure the stick was corrupted before I got that far. You may have a point about the Linux specific forum I just wasn't positive this was actually a Linux issue so much as a broken USB stick issue. Sal_vager: I am, in fact, trying to run KSP on this stick and actually I did it successfully once. The first time I had ever used this stick was when I first found out about the idea of a bootable drive and the reason I picked Linux(which I know absolutely nothing about) is because a friend of mine is a developer and suggested that it was the easiest way due to its simplicity and small memory footprint. I downloaded a Linux mint ISO and UUI for windows and just followed the on screen instructions then when it was done I booted it on my laptop and it worked perfectly but could only have 4gb usable space which was quickly used up by Steam and KSP. That's when I started down this path of things that are far beyond my skill level and here I am :/

Yeah I'm thinking that all the formatting and partitioning with all different operating systems that we did prior to finding the step-by-step process for what we were attempting is what ruined it because prior to that shennanigans it was perfectly happy operating as a boot device with a 4.1gb persistent file. I booted 2 different computers into linux with it and even played KSP on them through it. Then I decided it was a waste to have a 16gb drive with only 4gb of space to actually use(and I had filled it up in no time). I have confirmed that the device is the problem though because I used the same ISO and writer to make 3 other bootable drives while testing theories tonight and they all work fine. During my searching for a solution I have come up with a lot of people saying bad things about PNY devices so maybe they're just hyper-sensitive to excess formatting/partitioning. I've ordered a new SanDisk 32gb drive to play with from amazon but I would still love to recover this one if possible.

Well I actually don't know how to do that, but what I decided to do instead was just delete my ISO file and get a new one. I went ahead and formatted the drive again and installed the new ISO file and it did the same thing. If you could tell me how to check the md5sum and tell me what I'm checking for I would be extremely grateful. Edit: I just made exactly the same drive with a different USB stick, assigning the same persistent file size and using the same ISO file and the same USB maker (UUI) and it booted perfectly so I'm fairly sure that my 16gb stick got ruined by all the partitioning and formatting. Anybody know how to repair it?

Hey there all, As the title says... I was hoping to get some advice from someone more computer savvy than myself. I'm trying to make a LinuxMint 17 bootable USB stick with a persistence of more than 4gb. I've found a couple articles on the Google machine which describe how to do this and one seemed to work, see:http://www.pendrivelinux.com/create-a-larger-than-4gb-casper-partition/. My issue is that before I found this article there was a long series of failed attempts to figure it out on my own which included several re-formats and several different attempts to partition the USB stick using Windows 8.1, IOS, and LinuxMint booted from a smaller live USB. Now, after I found this article I wiped and reformatted the intended USB stick(a PNY 16gb low-profile model) one last time using Windows, Installed LinuxMint as a live boot thingy, and performed the steps in the above article using LinuxMint booted live on a different USB stick. All went well and seemed to be fine so I rebooted the computer with just the new, larger partitioned Linux live USB. It got about halfway through the boot sequence, and right after it displayed the LinuxMint logo it flashed to a black screen with a box made of strange variations of the letter U and overlayed was the following message: "(initramfs) mount: mounting /dev/loop0 on //filesystem.squashfs failed: no such device can not mount /dev/loop0 (/cdrom/casper/filesystem.squashfs) on //filesystem.squashfs" Right below the message I can enter normal Linux Terminal commands but the boot sequence won't work. After encountering this I booted back into my other Linux USB and wiped the broken one and formatted it again. Then I installed Linux on it as before only without the partitioning steps and extra stuff just to see if it would work in the default live bootable setup and when I tried to boot with it I got the same message. Now no matter how I format it or wipe it or partition it, that particular USB stick always returns the same message at the same point in the boot sequence if I try to make it a bootable Linux drive. This is my first ever experience with Linux of any kind and I have had some help from a developer friend but he is at a loss with this one so I thought I'd bring it here. Is there any way to repair the corruption on this USB stick or is it just hosed? I've tried a few "how to repair a corrupted USB stick" things I found on google, but no luck. Any help or insight from the many computer-savvy folks on here would be immensely appreciated as I'd like to try and salvage the USB stick, and/or avoid ruining the new one I ordered when I try to do this again. Thanks!!!

Ah yes I was afraid of that. I did know it was a physics-for-each-part type of issue I just didn't fully understand exactly why or what that meant. Muchos Garcias for the quick response!

So, forgive my ignorance here, but does this help reduce the chop and frame rate reduction when flying in or near ships(stations) with huge parts counts? I'm about half done building a Minimus-based Station Science station(also has MP and LF storage for "miscalcuations" during ordinary exploration missions) and the parts count is already getting high enough to halve my frame rate. When I send up complicated parts deliveries(i.e. solar arrays, KAS crate deliveries, fuel trucks, etc...), or when my satellite passes by, it gets pretty hard to dock anything. If this helps alleviate that I'll use it in a heartbeat. I'm concerned that its going to get pretty ridiculous by the time the rest of the parts are attached...

I've just installed this mod and I'm really looking forward to using it to improve the Station Science station I'm currently building around Minimus! To be able to adjust the inclination of the station without the terrifying death wobble is gonna be really great. Today while I was building the rocket to deliver the next part (the first 2 of 6 solar arrays) it occurred to me that it would be really cool if there was a way for a part to be added that could tether a kerbal to the station on EVA. I was imagining another winch type part with like a 50m(ish) small cable which would be grabbable or connect in some other way(not sure if he could hold the cable and still be able to grab other parts while holding it) so that the kerbal could safely EVA around the station and add parts or perform maintenance (or in my case also board the external command seat of the service tractor) without the risk of flying off into his own orbit if he were to overestimate his EVA propellant. I'm sure the idea has been suggested before(doesn't seem that original) but I figured I would throw it out there.

This is really neat. I just installed Banana For Scale and I'm looking forward to this. One thing that occurred to me... What if the solar panel hub could be activated by action group to have the panels unfold into 1x6s for higher power needs like data transmission or a small ion engine... Just a thought.

YUP! Tested with the same rocket in sandbox with the adjusted staging sequece and it worked flawlessly! Thanks for pointing out my error there I was going crazy.

Hooray! The issue actually isnt an issue... It was me doing it wrong... shocking:rolleyes: Thanks to modbox555 for helping me out in the KW Rocketry Mod thread!

No that makes perfect sense. I recognized that the base shows up as a stack decoupler and the fairings show up as a triple group of radial decouplers, I just put them all in the same stage. I'll try separating them into two stages and see if it works. Thanks!

OK I see what happened. I misinterpreted that part of the sticky the first time I read through it and thought it was referring to the crash logs that pop up in the KSP folder and didn't think I'd have one for this since it isn't crashing. I'll try and get the log uploaded later today. Sorry about that.

Hey there. I dont have a crash log for this or any specific conditions under which it happens because it happens under ALL conditions, ALWAYS. I have searched as far as my googling skills will allow and while I have found that the decouplers have no force bug is/was a known issue, I cant seem to find out if it was supposed to be fixed in .24.2 or if it was still ongoing and I need TweakableEverything to fix it for now. I've started using separatrons (KW Ullar(sp?) motors) to fix the radial stages blowing up my main tanks/engines, but when i build a rocket with a KW fairing (specifically in this case a 3.75m expanded fairing, 3 panels high plus nose thirds) and get it into space and stage it the ship inside just gently floats forward and clips through the nose cone as if it weren't there. The fairing thirds don't split open, and i have to carefully maneuver my ship out of the tube formed by the fairings. I suppose this could be an issue with KW Rocketry but I can't seem to find any evidence of others reporting the same issue either. Any help even just leading me to the answer of whether or not the decoupler force bug was actually fixed or if I need to install TweakableEvertything for now would be greatly appreciated. To replicate: build a ship with a central stage composed of the tallest and shortest KW Rocketry 3.75m LFTs and a stock KSP big 4 nozzle engine(cant remember the name of it). Install a KW 3.75m expanded fairing base. Build a ship on the base tall enough to need a 3 panel high fairing. Install the KW 3.75m expanded fairing nose thirds then the 3.75m expanded fairing thirds to cover the ship. Get it into orbit and stage the fairing and base together and watch your ship gently float out through the still-closed fairing nose. I wanted to clarify that I am also aware of the special requirements for not staging the KW Pedal Adapter Fairing but this is not that and I couldnt find anything i was doing wrong based on the instructional videos posted with the KW Rocketry mod. Thanks again for any guidance.

Hey there, I'm having a relatively annoying issue where my 3.75m expanded fairings dont blow apart when staged. I'm running .24.2/32 bit/Wndows 8.1 and I dont have any tweakable mods. This may be an issue with all the fairings, I'm not sure, the only one I've tried to use is the 3.75m expanded so far. Is there a height limit for these to work properly? My build is using a fairing thats 3 panels high plus the nose thirds. I get into orbit and hit the stage with the fairing base and the fairing in it and the ship inside just floats gently around inside the fairing and then clips through the nose cone. Any guidance would be great. Also, I love this mod otherwise. It looks great and adds needed variety to the mix of parts. Thanks.

Hey all, I've gotten some good info here so I decided to make an account. I've been addictedly playing for a month or so and its one of my favorite games ever. I'm curious, though, about why it says my account doesnt have the required access to view the post about the decouplers have no force bug. Also wanted to generally say thanks to those who've taken the time to build the great mods and help those of us who aren't awesome with math and physics and all the other help provided by the folks who know the game inside and out.