klesh

Oh, this looks like something I could participate in. I do this style of missions quite a bit in KSP! How about some points for a monopropellant-only (hypergolic simulation) Lunar Ascent stage?

So get used to it? I've never seen someone more abrasively helpful. The only words he could've searched to be brought to your post is "violent" and "veer". "Runway" would've been buried in results. You should cut "new guys" some slack. Sheesh.

A great man once said you can't swing a dead cat around Duna without hitting the sphere of influence of Ike.

Have you missed the part where they decided not to do it?

Running either of those as launch options resulted in what you would expect as normal behaviour. Regardless of AA or Part Highlighting, the fairing stays. I then cleared the launch options, and re-ran the tests again and found the original results. AA off will see the fairings disappear. I'm using Windows 10 Home, version 1607, OS build 14393.693

Oh goodie, so I am not crazy! Well, maybe not. I'm off to hang out with some peeps. I'll be able to fiddle more in a few hours.

At you leisure, friend. Thanks to you for the guidance.

Oooh, look at you. Someone is a smart cookie! Yes, since I was running AA outside of the game from the Nvidia Control Panel, I had it turned off in the in-game settings. But part highlighting was turned on. Turned part highlighter off (while AA was off) and tried, same fairing issue. Keeping part highlighter off, and put AA to 2 on the ingame settings results in the fairing actually staying as intended! Turning part highlighter back on, AA still on 2, fairing stays. While in the same settings menu without closing it, I can turn part highlighter on and off while AA is on and the fairing stays. If I turn AA to off with the ingame settings, regardless of the part highlighter setting, the fairing will disappear. Can you guys re-run the test with the in-game AA turned off and see if it happens?

Hi Sal, thanks for the help. To be honest I don't know the answer to your question. How would I find out? Oh wait, you mean like special launch perameters. Just checked. No, I am not; no special launch instructions.

Okay, here are the results of some fiddling: Verified game cache through steam, 2 files missing. They auto acquire. Ran it, still had the fairing issue. Deleted installation, deleted KSP folder. Re-install. Verify game cache before starting game. All files okay. Start the game, set screen resolution, texture resolution, fullscreen etc. New sandbox game called "test". Straight to VAB, open the GDLV3 ship, launch. Settings game still results in fairing issue. So here is some more information: GeForce Game Ready Driver Versions 376.33 Release Date: 12/13/16 Checking for Updates says it is up to date. Here is output_log.txt from KSP_x64_Data: http://pastebin.com/cb5MZZuj Here is settings.cfg from the KSP root: http://pastebin.com/XYRAn4DW After all that, I closed the game and deleted the Nvidia control panel presets for when I run ksp64.exe, such that the game's AA settings etc are used instead of being overridden. Still have the same fairing issue.

I remembered seeing the bug report for it previously, and trying it and seeing that it did used to delete the fairing in 1.2.1. I was going about a quick test flight with the stock GLDV or whatever its called and checking some settings when I stumbled upon it. I installed it and immediately played, I got the version number from the corner of the pause menu. I deleted and reinstalled a couple times after I noticed it, but I'll verify integrity of cache when I get home, indeed perhaps a wonky install. I know I neglected to verify cache integrity when I was doing clean installs. I'll have to get that at home. From memory, a GTX970 with the latest drivers. Graphics settings were full res textures, but I think I am overriding the game's AA with nVidia's AA from the control panel. Word! Thanks for you help, mang. I'm glad its something on my end and not with the game itself.

KSP Version: v1.2.2.1622 Windows 64-bit, fresh install from Steam What Happens: You use the Settings menu "in flight" (landed, whatever) with a craft using a fairing. When you click Apply or Accept, the fairing disappears. Hitting "cancel" on the settings window returns you to the game with the fairing in tact. Mods / Add-Ons: All Stock Steps to Replicate: 1) Place any root part in the VAB, then put any fairing around it. Any size will have the problem. 2) Launch craft. 3) On the launchpad, hit Esc to bring up the menu, then click Settings. 4) Without changing any setting, click "Accept". (Or alternatively "Apply", same outcome) 5) Press "Resume Flight" Result: Fairing with visually disappear, though the option to deploy is still available as well as the option to stage it. Fixes/Workarounds: - N/A Other Notes/Pictures/Log Files: - This was listed as fixed in the patch notes for 1.2.2 but does not appear to be fixed for me. http://bugs.kerbalspaceprogram.com/issues/11520 Any of you guys seeing this too?

My mistake. I saw the giant red text and simply read the line " GPP Install Instructions Create a new install of KSP and run once without mods. Then you may install GPP and other mods. Otherwise backup and remove your saves. Any existing campaign that uses the stock planets... " and didnt realize you intended me to visit that as a link. It's just a little confusing and I'm passing on my experience trying to figure it out as someone new. Thanks for placing the blame at me though, I appreciate it.

I have it running now. The instructions on the first page don't mention Kopernicus being necessary. Changed the .md to .txt to find that out. (Windows 10 suggest you find an app to open a .md file) Instructions on Page 1 neglect step 2 found in the readme.md. This is what threw me off in the OP: You might consider adding that on page one for those of us who don't know Kopernicus is required. Thanks for the help fellas.

Clearly I am doing something wrong. I attempted to follow the installation instructions on page 1. 1. Fresh install KSP. 2. Run once, quit. 3. Install GPP 4. Install other mods from the GPP.zip 5. Run the game again I start KSP again, and I'm looking at Kerbin. The Kerbonauts have different glass on their helmets, so at least something is working. Help? I tried the readme but my computer has no idea what to do with a .md file. Edit: Manually changing readme.md to a .txt file let me open it. Contrary to the instructions on page 1, it looks like a mod named Kopernicus is needed as step 2. Might want to update that part in the OP?

I just put 2 Jumping Flea's next to each other, and advanced time for 26 days with both regular and physics warp. The ships didn't move even 0.1m. http://imgur.com/a/tgnhR Edit: Just tried with 2 rovers off the runway at 2.9m distance. Same results, zero slide. OP, screenshot of the craft please. Leafbaron, what wheels were you using? Screenshot?

Well sure, the people here are into the game, they've been bitten.

Thread title made me think of Kickstart My Heart by Motley Crue. Possibly the only other reference to "top fuel funny car" I've ever heard.

To you. You already know KSP can be great despite its graphics. I have friends who refuse to play it because it "looks like its from 2002", and they're not interested in modding a game right out of the box for it to look modern. I don't agree with them, but you have to consider the perspective of someone who has yet to be bitten by the KSP bug.

I too, quite liked the old spark. I started using the LV-303 from Porkjet's fantastic parts pack that Squad decided to re-prioritize as a replacement.

Dont forget to thank dalmator! I didnt do anything other than be nerdy enough to remember him posting it ages ago.

This is a temp version of kerbal maps a forums user is hosting until the regular one returns: http://ksp.deringenieur.net/

Older versions had a very pronounced slide across planet surfaces, but its been fixed. Did you update your game to 1.2.2, or is it a fresh install?

Are you expecting us to provide you with a reversed audio and translated text? Reverse the audio and present it if you can't speak Spanish.

The CH-J3 Fly-By-Wire Avionics Hub. I used to use it when it was called the Sensor Array Computing Nose Cone. Since its been turned back to SAS only, not so much.