Kopmatt88

Just want to say that -force-opengl works for me too. Thank you so much!

YES!! Thank you! This, from @Wyzard's post in that thread, works: "However, -force-opengl (which tells Unity to use its legacy OpenGL backend) seems to resolve the problem — no stuttering, even when running the game from an APFS partition. I've tested with the Steam version of KSP 1.3.0, on a 2016 13" MacBook Pro with Touch Bar and Iris GPU." I can confirm it works in 1.3.1 too. I can finally get back to KSP again!

As I said in my post, I tried the -force-glcore argument on Steam, and it didn’t work. I’ll give it a go again when I can later, but it didn’t fix it the first time. Both .log files (with and without the argument) are at the Dropbox link. I’ve got two other games on Steam, and they work fine with High Sierra. No graphics issues at all.

Hi, I'm having exactly the same issue. I've read through the above, and I tried using the -force-glcore argument in the launch options in Steam, but that made it no better. I've uploaded .rtf files of the player.log files to Dropbox, the link should be here: https://www.dropbox.com/sh/xxoy7rui5mpq753/AADjmREEFUCbPinoYO1WPzqxa?dl=0 I was running a couple of mods, but I removed them from the Game Data folder after the issue started, and logs above are without the mods. Today was the first time I've tried playing KSP since upgrading to High Sierra. I've tried two other games, both on Steam, and neither have any stuttering problems (Football Manager 17 and Euro Truck Simulator 2). The stuttering is so bad on both the first and second menu screens that the game is just unplayable once you get to KSC and beyond. My game version is 1.3.0.1804. I'm running a 2017, 13 inch MacBook Pro with Touch Bar, 3.1Ghz i5, 16GB RAM, 256GB SSD, Intel Iris Plus Graphics 650 1536 MB. I really hope this is fixed soon as I've finally got a bit of free time and was looking forward to getting a bit further on KSP. I hope I've included all the right information! Ps: I don't know if anyone else has come across this, but I tried to use pastebin (following the bug report link above) and the log files were too big for pastebin without a "pro" account, so I had to use Dropbox and upload them that way. Just FYI if anyone else tries to do that.