sal_vager

Yes like I said, I have not seen the sun like that before, so I do not know the cause from memory. If you have black textures it is likely your install is corrupt, please try reinstalling KSP.

The parachutes are spamming the log with errors, please test a new save and new vessel.

Hi tkw. Imgur is over capacity so I can only see the first pic, I don't recognize the issue though, can you please put your output_log.txt (it's in KSP_Data), settings.cfg (KSP folder) dxdiag (start, run, dxdiag, enter) and persistent.sfs (saves) on dropbox.com for me.

Glad you figured it out TheRocketeer

I should think that this behavior would have to be changed for ramps to work, or you wouldn't be able to unload rovers. I can tell you that the developers are are aware of the community concerns.

Hi smiles, please see here

Hi sillyforth, please see here

It is impossible to know this before the release, sorry.

I don't know, because this should and does work fine with DirectX, KSP is not intended to use OpenGL on Windows, there is no option in KSP for this, it's not tested for this, OpenGL is an engine option that is being forced by players. Your error suggests that it is a driver issue, Unity is asking for a resolution and is receiving an error from the driver, so it tries again with a lower resolution, but it can't use a lower resolution for the size set by the user, continues to fail, then ends with the error message. This isn't limited to KSP, it has been reported with other Unity games as well (Hearthstone, Unity3D), and with games that are made in other engines (Dead Island, Chrome engine) which suggests it is not an engine issue, but again a driver one. Some people managed to get it to work though, it is suggested here that (Unity forum) toggling v-sync can prevent this, you can do this manually in the settings.cfg or via the Launcher. It is suggested here (FORCED, Unity3D) that other programs running in the background cause this, so disable anything that can effect your graphics. If these don't work for you, try rolling back to an older graphics driver. There may a workaround however, because KSP works at 1680x1050 windowed mode if you maximize the window you will have KSP in a fullscreen window, you can do this by double clicking the title bar. If you use -popupwindow (There is an option for this in the Launcher) for borderless mode, use the keyboard shortcut "WinKey+ArrowUp" (Source, Microsoft Answers) to maximize the window. Or use "Alt+Space" to see the window options (Source, PCworld). Or set the program to maximized in the shortcut, see Computerhope. You can also add "-maximized" to the shortcut after -force-opengl and -popupwindow (Source, superuser.com). When you switch to maximized you'll find that some of KSP's UI elements do not change position, just change scene (go to Settings and back) and they will be redrawn in the correct place. If you do manage to fix this yourself let me know

I thought you said it crashed. If 1080p is working just use that, you can't go higher than your screen can support.

Hi TheReporter, please see the stickied thread and provide your logs, addon list and dxdiag report, the stick explains what these are and how to do this. Though this may be a known Unity3D bug, if you have any unused network devices or use hamachi, try disabling them.

Mines the good old LV-T30 Reliant, gets my Kerbals off the ground without that annoying shaking Gimbal? Training wheel more like!

Okay, your desktop resolution at the time you posted the dxdiag is also 1920 x 1080 (32 bit) (60Hz). Can you test KSP at that resolution, fullscreen, without -force-opengl please.

I like non-gimballing engines, the LV-T30 is my favorite.

What is your maximum monitor resolution ? Nevermind I found it. You say higher, but what resolution did you try?

It's intended, RoverDude posted about this recently, at over 100 warp the updates aren't shown because there'd be too many they over run the batteries, and it sorts itself out when you reduce warp again. I'll have a look for the post. Can't find it, it was in IRC, but anyway because of how warp effects e/c drain it's backgrounded until it's needed again.

Dcseal, getting upset over an issue is no way to have that issue addressed, what we need from you is your logs, your save folder, and the steps you made to produce this issue. If it's a bug, all this information needs to go on the Squad bug tracker. People are much less inclined to help someone who is being angry.

By the way, if you are using PrecisionX (and lots of people are, it's free) reset it to the defaults and uninstall it, as it is making KSP unstable.

That is a very old page with out-of-date information, so is not really much help to anyone. There are newer and more relevant pages in the Support section for unmodded and modded installs. If you find you are crashing frequently this usually means something is causing it, and if you provide your output_log.txt, dxdiag report, list of installed addons and their version number, and list of task manager processes we might be able to help you.

This is more about the nodes than the actual burn though, and the node rotates when you adjust the normal/antinormal, so something else must be going on here.

That's just what it does, and it looks incorrect if you don't know any better, but the real question should be this: "Is this what happens when spacecraft burn normal/antinormal and don't correct for it?" I'm not good enough with the math to figure this one out, and googling this has proved to be difficult as I don't know how to word it, but we have a lot of smart people here who have not called this out as being wrong yet, and I'd like to hear from someone who knows, or can do the math, does this happen?

Glad I could help

Can you get into the game proper? Also if you open your KSP.log or output_log.txt they should say what renderer KSP is using at the top of the file.

Happy birthday Kasper, I hope you have cake

Wow, you can predict the future Lets leave speculation as to the release date alone, thank you, especially when your guess is only a few days away, as you will get people overexcited for nothing.