MGCJerry

There's a yearly bag limit on Kerbals!!?!?!?... Umm, whats the bag limit?

With my lack of rocketry ability, I can say I like how stiff the rockets are now. Before it seemed as rockets were made of silly putty and strutted with toothpicks. Rockets feel a little more like rockets, and you still have to strut those odd payloads. I'm fine with it, plus it reduces part count. If I wanted to play a slideshow, I have plenty of relatives that can do that for me.

Land on Mun with your transfer stage because its still about 66% full. Not to mention having missed a few burns and having to correct them in-route on top of having an inefficient transfer. However, I landed on a slope (oops), which caused the rocket to fall on its side (oops), but didnt break anything (yay) because the solar panel retracted JUST in time (yay) and was unable to right myself because it was an old design that carried no monoprop (oops), but in the end of fooling around crashed and killed Jeb (oops). Now my girlfriend and her mom is mad at me, they like Jeb (oops x2).

Sometimes I hit some of the crap around the launch pad, or destroy the pad itself. Whenever I "crash" I typically revert and being I play sandbox it doesn't matter to me much... My program is completely incompetent so they give themselves access to everything (Sandbox). However, sometimes The Director has other plans... "CrashCraft"... ... Success as Designed...

New sport! 15 Pin KerBowling on the runway. Created a "rover" that can hurl a 100 ton cheat menu "Whack-a-Kerbal" ball down the runway and a 15 pin "Pinsetter" machine for the willing (forced) Kerbals. Thinking about making it a challenge and posting it there. The hardware... "Pins"

I've actually done this several times just goofing around. I'll have to give this a shot again.

I will not go to space. Our space program is run by incompetent fools. So we decided to get back to our roots. Building Demolition!

Failed rendezvous 1. Failed rendezvous 2. Failed rendezvous 3. Failed rendezvous 4. Failed rendezvous 5. Failed rendezvous 6. Failed rendezvous 7. Even after watching some tutorials its just not working out... Failed rendezvous 8. Failed rendezvous 9. Failed rendezvous 10. Failed rendezvous 11. Failed rendezvous 12. Project Cancelled. Our program is completely incompetent... We will stick with demolitions. So we did what we do best, destroyed most of the space center... Updated our flag...

I've used the -opengl switch but makes KSP render 7 frames every other week. It seems to really despise my Radeon card as well. Recently I've went into Catalyst and created a profile for KSP and turned off all the fancy graphics options. I have not actually had a KSP crash for a few days now even after HOURS of crashing rockets, and "experimenting". I've actually got to see the exit dialogs! I have now moved over to .25 and left the previous version. I'm actually VERY wary about using mods because when I tried using Remote Tech, mechjeb, void, FAR, NEAR, (installed one at a time) it seemed to make the game less stable (back in the .21 days or whatever when I got KSP). FAR & Mechjeb gave me the most instability back then even as recent as ARM version. It seems turning off all the fancy graphics options in Catalyst, and lowering every KSP setting to the lowest seems to have resolved these issues on my machine. KSP has crashed once (lockup, today) since my last reply. I think we can mark this topic as Resolved. My solution that worked for me: WinXP (32bit) & AMD 8 core & Radeon video card * Create a Catalyst profile for KSP.exe and set all settings to the lowest and not "application controlled". * Set ALL KSP settings to the lowest possible graphics settings. * RAM was originally under-clocked by BIOS (1333). Set it to my RAM rated speed to 1600 (I doubt this makes a difference).

I would actually like to see a non-persistant "Testing Facility" added to KSP that goes like this. * In VAB or SPH, create a vehicle. (rover, plane, rocket whatever). * Next to the Launch button is a "Test this vehicle" * Click the button, and it asks where you want to test. There is a grouped list that includes the planets & moons (Duna, Eve, Gilly, etc), as well as a terrain list (Kerbal mountains, Duna Mountains, etc). Also maybe orbiting options for testing docking maneuvers. * Click "Simulate", and KSP loads up the specified location in a "simulated" environment. Your rocket on a simple launchpad, or your plane on a simple runway, or your rover in the specified type of terrain. Testing your rover somewhere without actually having to do a full launch, but you could do the whole trip as well if you wanted. * The "simulation" ends when you crash, or are done testing, then you get a similar screen like you currently get for launches. * No Kerbals harmed, not a lot of money spent (longer simulation = more $$$$). Just like doing a regular launch, but being able to chose your "start" location, but is not a persistent launch. * Destroying the testing facility removes the ability to test (and whatever kerbals you assigned to it). * Difficulty option to enable/disable 'testing'. So you elites can turn this kid gloves stuff off, and the people who want to simulate can use it. I know KSP is in beta with the final scope in mind, but this is an idea I just got. Sure, there's always hyperedit and the like but I think it would be cool to add a simulation to KSP as well. Simulation in a simulation since its inception.

I've played KSP a lot since posting my previous reply but it ran great up until that point. I haven't had time to play it today to confirm. After reviewing my notes I also seen that I did change my RAM speed from 1333 (auto) to 1666 (manual. The cpu, ram & board is rated to run this speed) 2 days ago. However, I have tried the -force-gfx-st switch with KSP in the past and it runs as smooth as frozen molasses. Though the last several times I've loaded KSP last night, it ran well but I still went into my bios and turned off "Turbo Core". The funny thing about this is that it seems to improve the CPU scores in performance test by 1%. If this combination fixes KSP, I'll be very happy then I can finally move my space program to 0.25. I spent most of last night trying to blow up *all* of KSC with a huge rocket/bomb combination and had no KSP crashes. When I keep encountering weird things (like excessive crashing that nobody else is reporting) it makes me want to find out why especially since I love KSP. I'm going to compile another list of some stuff, and do some experimentation. This may be my last AMD build (but the price was right at the time) because there seems to be some AMD specific issues out and about. This is my first AMD build since the Athlon T-bird XP-xx00 days. For now, we can call this solved but I still want to run some more tests and get more play out of KSP before I call it.

Ah yes, I forgot to mention those. I had already reduced video texture size to the lowest possible resolution setting. Also setting -force-opengl runs choppy and is still as crash happy. I'll update my above post with this information as well. <starts KSP> System is eating 1.5GB with this window open, and KSP running. System Information: KSP process Only Current processes. Rarely do I run anything else with KSP besides firefox. But this morning I was also programming.

I have a few programs that I use all the time that do not work on 7, and it hinders my workflow. Win7 is a great OS overall, but not for my needs. I gave myself 8 months to use Windows 7 when I got a new laptop and while it has improved over the years, it still cripples a major part of my workflow due to an old application incompatibility (program does not have permission to read and write to some portions of the registry and files, even when given SYSTEM permissions). Sure I can update them for a small fortune just so I can do the same stuff I'm doing now while consuming 3 times the resources. But, if you'd be willing to donate $$$ for me to buy another copy of Win7, be my guest. Besides, 8GB was the minimum RAM I could buy, they were out of stock of the 4GB pair and the 8GB was on sale. Also my apps are 32bit, which will see no real world improvement on a 64bit OS. If server2003 wasn't graphics crippled, I'd be using it because though its 32bit it can address up to 64GB RAM. It ran great on my old DL580 w/16GB ram. BTW, I wont reinstall and reconfigure an OS to play a game, regardless of how much I like the game.

I've tried now for several days to pinpoint and reproduce a laundry list of bugs I have encountered since 0.25 to no avail... * I have done a complete hardware burn in test over 24 hours, and even under-clocked. * Memtest came up clean after 8 passes. * Did a complete overnight virus scan using housecall (19 "threats" - all php files from my honeypot, these are ineffective on windows, even with php installed). * HD surface scan using spinrite. Disks OK. * Furmark video burn-in test. (Saints Row 3 maxxed out runs great for HOURS on end BTW) * Hardcore rendering in Carrara Test scenes using all 8 cores. Here are my specs. MB: ASUS Sabertooth FX990 CPU: AMD FX-8120 8 core (Dihydrogen Monoxide Cooled 37°C while running KSP) RAM: 8GB g.skill Dominator (DDR3, 1666) VGA: MSI H6770 1GB (driver 8.961.0.0) I know its an old one, but the newest driver creates issues elsewhere) AUDIO: Realtek HD Audio (driver 5.10.0.6251) OS: Windows XP SP3 32bit HDS: 320GB WD Enterprise, 10K RPM (firmware up-to-date, 3 partitions - C:, W:, I: ) 1TB Seagate Barracuda, 7500RPM (firmware up-to-date, 3 partitions - L:, D:, E: ) 1.6TB HP MSA1000, RAID6, 15K RPM (multiple firmwares, 1 partition - S: ) BOOT: Acronis Loader -> Windows NTLDER boot.ini: multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Mah XP" /FASTDETECT /USEPMTIMER /NoExecute=OptIn Whenever I try to reproduce one bug, something else crashes, or something else. I've run KSP probably 200 times over the last 5 days and I have found only a single trend. I've gone as far as saving each output_log.txt but I have nearly a GB of logs (all are 15+MB each). I've done research, and found issues seem to be relating to AMD processors, and every thread I've seen referenced on google, I don't have permission to view (here on the forums). People have suggested the /3GB boot.ini switch, but it disables my 3D acceleration, and audio card. Removing the /USEPMTIMER switch creates all kinds of new and interesting system bugs, and its part of the AMD kernel mode driver for the multi-core AMD Opteron processors for Server2003 and stuff to correct RTC drift by using a different timer. However, today is an exception, and I cannot reproduce any of these bugs I have. Its working great, for now. During the day, the game seems to have all kinds of bugs and crashes. However between the hours of 2AM-8AM the game has not crashed (goofed off because I couldnt sleep). BUT, except for today during the day. It has run fine for 2 hours (no crashes) even if my planes suddenly start to Bounce Down the Runway (craft file link) after a couple seconds. Restarting KSP fixes it. Here's a list of the bugs, steps I've tried taking, and the result. Methodology: * When I get a crash (the "Oops" popup), its called a 'crash'. * Check the logfile size (my upload speed is TERRIBLE). renamed log to something else (1.txt, 2.txt). Quit after 80.txt, it got old... * Reboot after system configuration change. * Jeb a vehicle, means crash the vehicle. * KSP runs windowed. * Tried running with only REQUIRED processes early on. (no effect on crashing). * When reinstalling KSP, all files are deleted and every registry entry referencing KSP.exe, squad, & harvester. Followed by reboot. Background processes: * Firefox (not running when 'Kerballing' seems to have no effect) * ClamWin (file scanner only) * MS Office Shortcurt Bar (msoffice.exe only) * When starting KSP, I keep window focus on it until it loads to the menu. Edit: * Reduced video texture size to the lowest possible resolution setting. Also setting -force-opengl runs choppy and is still as crash happy. Bug List: * Walls of the SPH & VAB disappearing (SPH reference: http://2thextreme.org/forum_images/ksp/0.25_Bugs/badsph.jpg ). This randomly happens after starting KSP, and building something half-arsed, Jeb'ing the vehicle (crash it), reverting to VAB/SPH. Lauching results in an immediate crash (2 out of 3 times), with a crash on next revert guaranteed. Leaves behind a 17MB or 21MB, log respectively. * Crash on revert. This happens most often (estimating at least 75% of the time), usually only after 10 minutes of "playing". I can usually half-arsed build something, launch it, Jeb it, or whatever and I get a few reverts before the game crashes. Leaves behind a 50MB log. * Crash on 2nd vehicle launch This one happens quite often as well. I can build something, launch it, then Jeb it, land it somewhere, or get an orbit. Then click revert, and get an immediate crash. Creates a 5+MB log. * Parts 'x' not responding on startup This happens rarely as well. Sometimes when loading KSP, it takes much longer to load and gives me a popup that some parts aren't responding, then a windows crash dialog (This program has terminated in an unexpected way). No log file. I never have enough time to read it. Reinstalled KSP. * Crash on new game. Sometimes when creating a new sandbox game, KSP crashes to desktop. Sometimes without error. No log file. *Crash on going to Space Center Rarely after a half-decent launch and getting into LKO, I run into an issue where I click "Space Center" and KSP crashes. These are the smallest logfiles. but I HAVE NOT been able to get this far to reproduce it reliably. KSP has run fine today, so it hasn't happened. A 12+MB logfile is left behind. * Dim & unresponsive UI menu selection Rarely, when starting KSP when the menu comes up, its dim and completely unresponsive. Restarting KSP does not always fix it. No logfile. Reinstalling KSP seems to be the only DEFINITE fix. * Random bounce down the runway Sometimes when building planes, I can get them to fly good, & handle well. Then I'll make a modification (small or big), then suddenly it starts doing a discotech down the runway until it Jebs. Restarting KSP usually fixes the problem. Craft file is toward the top... Here is a output_log.txt from the bouncing craft play. This overall session lasted awhile. http://2thextreme.org/forum_images/ksp/0.25_Bugs/bounce_log.txt Honestly, I'm sure this 'report' is even acceptable. I REALLY want to be able to play KSP and I want it to be stable so I can enjoy it. I've spent more time pattern finding, troubleshooting, research, scanning, testing, etc than actually getting anything going.

Oh my I hope this experience thing doesnt mess with physics or controls (a difficulty option toggle would be good though). The experience thing annoys me to no end when it affects the handling of objects. Its absolutely infuriating when playing a game which the controls are not responsive enough because my characters "lacks experience". It makes me feel like a caveman bashing rocks together so he can drink water from a toddler sippy cup in an infomercial. However it does make me wonder how it will be implemented.

I hope bug-fixes are pushed hard. 0.25 is an absolute crash-fest, I can't even post support because the game chokes at different times because I cant trace the steps without something else crashing along the process. I've had nowhere near this much trouble with any previous version.

Yea. Its unbelievably unstable on my machine. I can't even get bug reports in because other bugs (crashes) keep getting in my way. No other version has given me this much grief.

I've ran KSP directly, and that seems to fix this. Then I continued to play around with the spaceplane parts and so far so good. I think we can mark this one as solved.

With all the issues I've been having with KSP, ive once again redownload the game and I'm now encountering a new bug. 1. Downloaded from store to desktop 2. Unzipped to folder 3. Ran Launcher, let it download the patcher. 4. Lowered display settings (turned off SM3). 5. Click orange "Play" button. 6. Fill in necessary credentials in the resulting "Run As" dialog. Click OK 7. KSP issues this error: "There should be 'KSP_Data' folder next to the executable". 8. "Ok" exists. No log created. 9. Rinse & repeat. 100% recreate rate. See attached: * KSP 0.25 non steam (32bit, stock, clean install, no modifications, even keyboard controls, re-downloaded twice this go round. downloaded ksp a total of 5 different times) * Windows XP (32 bit) * AMD FX8120 8-core (4GB RAM - 8 physical), older video drivers. Updating has no effect, and causes issues in other applications when I do. * RAM good (memcheck clean) NO OC. * HD surface scan clean. * Malware clean. * 24 hour full burn-in test passed. * KSP .24.2 runs ok.

Windows XP. Yes, I said XP Microsoft isn't supporting security anymore, but I'm supporting it just fine.

When I seen the title, I thought that as well... If I can rate myself. -60.

If I didn't bother with the demo or see one, I would have downloaded it from a questionable sources. Regardless, I would have bought it to support development, and I enjoy KSP and want to see it flourish.

Bought through store, play offline. I made the mistake of buying the Left4Dead bundle for $70 when L4D came out, and the loss of my internet meant that I could not play offline. "Offline" mode requires an internet connection to established with steam servers, but just shows you as "offline". This is an issue when steam cannot connect to steam servers for a period of 72 hours, and according to a steam tech guy, it wont be changed. This was YEARS ago. I dont want to be dependent on an active internet connection to play an offline game. Steam, great concept for multi-player only games. Just not my cup of tea when I don't want to fly in the iCloud 24x7.

Unfortunately, I can't reliably reproduce this bug. I tried documenting my steps later that night but KSP ran wonderfully for over 3 hours. Its never run that good. So I just decided to take advantage of it running great and have fun building stuff with the new parts, which are awesome as well. Then last night I had to start KSP 5 times before I could even see the space center. It kept crashing (Something about a non responding part, then the windows "Program has crashed" popup so I didn't get time to screenshot the error, it happens quickly). Now my log is over 343MB. During this slugfest with KSP the VAB & SPH did disappear again. I just keep running into different problems with 0.25 when doing the same things. I'm going to hold off on my bug reports until I do a more thorough system hardware check. * Disk defrag has already been done, its done weekly. (which I think is irrelevant to the problem) * I've already ran memtest several times and came up clean (21 hours wall-time, 15 passes, 0 errors) (did that the last 2 days while I was not home). * Going to run a spinrite surface scan (chkdsk comes up clean). * Going to restore "plain os" disk image restore. I did a disk image with all my drivers installed after I setup my os. * Another 3 day full burn-in test. It will be a few days for any ksp.

Uh oh... Sad news. Whenever something like this goes up for sale, its almost always destroyed by whoever buys it. But whatever it takes in the name of patents, & assets. How many times has something gone up for sale, only for the flagship product to "disappear" or be discontinued leaving its users behind, only then to find it used in some capacity in a much more expensive product. *Cough* Adobe, EA, Google Inc, Microsoft. But if EA gets it, don't be surprised if "you killed Jeb, you can get him back for $2", "new DLC, $15"... The day the KSP requires something like an online account (google+, microsoft whatever, EA whatever, etc) just to play it, is the day I walk away from it and stick to the old versions provided they aren't time-bombed. I remain hopeful of a decent sale (with the users in mind too), but I'm not optimistic.