sal_vager

New important issue - fixed in 1.2.2 so please update! The highlighter will cause KSP to crash after disabling the aero overlay, please disable the highlighter in flight or avoid the aero overlay until this is fixed, thank you. See here for the issue report. * KSP not starting on macOS OSX OS X Sierra? Important notes on the Patcher / Launcher -------------------- Issues new to the 1.1.2 release (and one or two old ones), and their workarounds if any, can be found here, so if you find something please check here first and PM me if you don't see your issue. I will add the issue to the repository, this makes it both easier to find in the future, and will help reduce repeated issue reports Also please check the developer articles, as many new changes may seem like a bug at first when compared to earlier versions, but are intended. If you're still on 1.1.1 you need to update KSP. Claw has made many small fixes for these issues which you can find here. Command line arguments! The Unity3D game engine which is used to make KSP has a lot of command line arguments which can help get KSP running on Linux/OSX, and allow players to force KSP onto a specific monitor in multi-monitor setups. See all command line args here. Standalone Unity commands, these can work on any platform, not just Windows. -------------------- Category list. -------------------- Aerodynamics. * Heatshields not slowing down the pod enough. (Gameplay change) Application. * KSP doesn't start. (Linux graphics drivers) * KSP does not start on macOS OS X Sierra. * KSP doesn't start. (Windows Hardware/OS) * Missing text (Fixed in 1.2) * Output_log.txt in appdata. * Window keeps minimizing to the taskbar. * Window keeps resizing then KSP/Xserver crashes (Linux). * Window on wrong monitor. Career. * Recovery funds missing. (Not really missing) * Satellite contract orbits not shown (Bug) * Sticky launchpad. (Bug) Craft. * Cannot launch craft. (Missing/corrupt files) Crashes. * KSP crashes when loading craft or changing scene. * OSX crash on decoupling the TR-38-D decoupler (Fixed in 1.2). * OSX frequent crashing. Controls. * Joystick axis won't bind. * Ship is steering on its own! * Steam controller modes (Fixed for 1.2) Editor. * Center of lift different between SPH and VAB. (Intended) * Editor freezes when launching a craft. (Fixed in 1.2) * Missing background in the editors. * Struts sticking out in odd directions. (Bug) * Poor performance / high CPU load in VAB/SPH. Flight scene. * Docking ports won't undock (Fixed in 1.2) * Jet fuel flow with a materials bay. * Kerbals stuck outside the ship (Fixed in 1.2) * Missing ground in the flight scene. * Navball has green triangle on it (Linux) * SAS is twitchy, overshoots, wastes resources. Graphics * Textures are missing. KSPedia * Missing text and cut-off sentences. Main Menu. * Resume saved doesn't. (Missing files) Map. * Map icons offset. (Bug) * Orbit lines disappear. (Fixed in 1.2) Official Addons. * Asteroid Day broken (Fixed for 1.2) Parts. * Aero parts in R&D. (Save migration issue) * Heatshields not slowing down the pod enough. (Gameplay change) * Jetwash missing from Wheesely and Goliath. (Intended) * TR-38D Decoupler won't decouple. (Fixed in 1.2) Performance. * Lag in KSP. * Long load times. R&D. Resources and ISRU. * Drills on asteroids are overheating Tracking Center. Tutorials/Scenarios.

Well, you sorta kinda can extend the launch clamps yourself... Craft file

S1gmoid, your log errors are very different to the logs in the report you linked, so they are not likely to be related, ie not the same cause. Your log is showing stuff I've not seen before, but it looks like something tried to allocate memory that wasn't available. The rest of the log is mostly just repeated lines and a stack trace with no indication as to what caused it. But that error has been reported on the Unity forums and looks to be related to parts. So my advice is to try removing addons one at a time, especially anything with animations even if it's just lighting effects, and see if this problem goes away.

Well, 70 fuel cells on a single craft is an unrealistic vessel to expect a player to build unless they were going out of their way to find performance limits, like trying to fill the entire map of an RTS with tanks, yes it will cause problems but then it really should be expected to do so. All games have limits even if the developer has hidden them from the player, examples include using sprites and different levels of detail at a distance, simpler rendering when moving the camera and per-calculated "physics" on debris and other scenery objects because the players attention should be elsewhere. Also, the UI is being replaced for 1.1, so you should see some improvements As this thread is now less about support and is more about discussion it doesn't belong in here, moving!

Hi PB666, due to the complaints the moderation team receives regarding your "link and no supporting text" posts I have closed this one, I invite you to try again though, with a sentence this time

You know an update is soon, right? Moving thread.

Green Iron Crown was a test account to see what negative reputation looked like, and was repped by members to make him "good", resulting in his destruction (banning).

Hi Plusck, do you have a save from before this happened so we can see what contracts you had? Also if you can reproduce this the logs from that event would be really useful. Unfortunately restarting KSP overwrote your log so I can't see anything wrong there.

Yeah it's the controller bug, if you have a controller bound but not plugged in, the settings reset, but if you plug it in and start KSP, the bindings are back but the gfx settings are still gone. Hoping (crosses fingers) that they fixed it for 1.0.5

Do you also use a controller at home but that you don't take with you?

Suggestions go in Suggestions and Development discussion, not General Discussion, this should be common knowledge to anyone with over 100 posts to their profile. Also please keep this thread civil.

Hi Tactical Bacon, Kerbals don't realize the utility of fuel transfer until they upgrade to the tier2 R&D complex and discover that they have to fix all the plumbing.

Hi Kacogg5, the tutorials need updating again, make a smooth gentle turn and you'll be fine.

Hi unfnknblvbl, there are several issues with controllers, hopefully fixed in 1.0.5

Well the thread I linked does explain where to find the logs. As a wild guess I'd say you are using saves from a modded install, and module manager has broken them, the TechTree line in the persistent.sfs file needs to be changed to this: TechTreeUrl = GameData/Squad/Resources/TechTree.cfg If that doesn't fix it then I really do need your logs and save file.

More stock parts are definitely not a worry.

Please see this thread and provide your logs and the affected save Darkened Planet

Hi hargin, this sounds like the joystick bug, your gfx settings will reset if you start KSP with a controller bound but no controller present. And __GL_THREADED_OPTIMIZATIONS was never necessary, it's just reported to help for some players (though I never saw a difference). We will need your Player.log from after this occurs wingman KSP on Linux and OSX uses OpenGL, this is normal, the VRAM thing is a Unity bug however and there's nothing we can do about it, thankfully it's completely harmless. We will need your Player.log from after this occurs and your hardinfo report (plain text, not html) please PolNoch, see the first post for details

Hi mickdc, it looks like your fonts are corrupted. There's many more lines like these in the log, so please try clearing your font cache. Here's one way, and many others can be found via an internet search

It's not just the OS though, hardware manufacturers are not providing Win2000 drivers for current graphics cards, sound cards etc. Also if the hardware is of similar vintage then it won't be capable of features that were developed later and which the Unity engine requires. Not to mention that the error message is Windows2000's, and not something from KSP. While this may be an interesting project for curiosity's sake it's not realistic to expect much support, so it's time to move this to a more appropriate home.

Hi twiglet, please post links to your full dxdiag system specs and your output_log.txt

If the part fallback shaders are on try turning them off

Well, seeing as this thread is only really connected to KSP in the most tenuous of ways (seriously, it's three letters) I'm moving it to the Space Lounge.

The right place may end up being the Google Chrome bug tracker, as Google is ending support for NPAPI plugins such as the Unity player, meaning that NPAPI content will only work on older versions of Chrome that still have plugin support. This means Unity (and others) will have to replace their plugin by targeting WebGL directly, which will be built into most newer browsers. Until this is available it is not possible to update the Kerbalizer, sorry.

Hi jj5437, you might like to check out this thread, it's a little old but still very useful, and KSP's aero and drag models have improved since so planes fly even more like they should