Jump to content

Support request [OSX]


Recommended Posts

hi guys, i have been having increasing issues with ksp ever since i first started using mods in the middle of summer. my game sometimes crashes even with no mods installed whatsoever, but with mods, it crashes every time i go from VAB to launch pad. The is not unplayable as yet, because i can launch by clicking on the launchpad in the general ksc scene. however, the game has become so unstable that any time a loading screen pops up i get anxious.

my current set-up:

OSX Yosemite 10.10

Macbook Pro 15" Retina late 2013 (Summer 2014 purchase date)

2.3 GHz Intel i7

16 GB 1600 MHz DDR3 RAM

NVIDIA GeForce GT 750M 2048 MB Graphics Card, in addition to the integrated Intel Chip

KSP .25 through Steam

Firespitter

Trajectories

HotRockets

ModuleManager 2.5.1

KER

MechJeb2

RasterPropMonitor (including the replacement IVAs for Stock SP+ in .25)

NavHUD

PlanetShine

and i just removed KSP-AVC because one of the mods that works with it refused to check, so i was stuck with the unclosable "5 out of 6 add-ons checked" screen

any help you guys could give me would be fantastic. i am hopefully going to be switching to Linux XUbuntu soon; although i don't know when that will be, and would like to keep playing my favorite game in the meantime. I have used KW and EVE in the past on previous releases of both KSP and OSX (i believe it was 24.2 on the last version of Mavericks) and had less frequent, though not infrequent, crashing. i would very much like to get back to using EVE, if not both EVE and KW, as both mods really changed the way i played the game. A huge thank you for reading this ridiculously long post for anyone who replies.

Link to comment
Share on other sites

Ah... he's got the KSP version, mod list and his OS on the OP @Master Tao

Anyway, I +1 what Master Tao says about the player.log. But I have seen that many people have been having issues playing KSP on OS X Yosemite installs even while non-modded. That could be your issue, in which case is actually a unity player/OS X issue. I don't know too much about the issue, but I believe Master Tao does.

Link to comment
Share on other sites

Could your provide the information requested in the How to Get Support (READ FIRST) sticky?

Platform, KSP version, and mod list are good, but the Player.log and mod versions would help even more.

Ah... he's got the KSP version, mod list and his OS on the OP @Master Tao

Anyway, I +1 what Master Tao says about the player.log. But I have seen that many people have been having issues playing KSP on OS X Yosemite installs even while non-modded. That could be your issue, in which case is actually a unity player/OS X issue. I don't know too much about the issue, but I believe Master Tao does.

How do I go about getting the player log to you guys? And the mod versions should all be current. If not the absolute latest release, they are all very recent ones, as i have tried testing game performance with and without all of them several times in the past couple weeks, and thought it safer to redownload a new mod packet for each whenever i put one back into the game.

If the unity/OSX non-compliance is my issue, would the only solution be to switch to a different OS and have patience? thanks so much to both of you.

EDIT: ahh found the instructions for the log. here you are- https://www.dropbox.com/s/ihfjksx782mjacr/Player.log?dl=0

Edited by gkorgood
found player log
Link to comment
Share on other sites

Holy jeez, that player log is a mess. My eyes cannot concentrate on anything :confused: Master Tao might be able to better decipher it. And I've been glad to help. If you feel that you would like to show your gratitude even more, you can do so by giving reputation. How to do that? At the bottom right of the post is a little star thing. Looks like a Sheriffs star. You just click on that, enter a reason for giving reputation (if any), then click on the button "Add to reputation". :P

Anyway, been glad to help, but no way in hell am I going to be able to format that player.log properly. Sorry about that.

ToTheMun

Link to comment
Share on other sites

Going more on experience than actual evidence here. The end of the log is:

Receiving unhandled NULL exception

Obtained 12 stack frames.

99% certain you're running out of memory and I believe that actually explains most of the other errors in the log.

Try reducing the Texture Quality setting in the Graphics settings, or installing Active Texture Management. If you don't install any other mods, you may be able to get away with ATM-basic rather than the unnamed version formerly known as aggressive.

We always ask for mod versions because many times players don't realize there have been updates – I had someone tell me her/his mods were all up-to-date, even though one hadn't been updated in more than 6 months. Old mods don't usually cause crashes, but they can cause odd problems.

Link to comment
Share on other sites

Going more on experience than actual evidence here. The end of the log is:

99% certain you're running out of memory and I believe that actually explains most of the other errors in the log.

Try reducing the Texture Quality setting in the Graphics settings, or installing Active Texture Management. If you don't install any other mods, you may be able to get away with ATM-basic rather than the unnamed version formerly known as aggressive.

We always ask for mod versions because many times players don't realize there have been updates – I had someone tell me her/his mods were all up-to-date, even though one hadn't been updated in more than 6 months. Old mods don't usually cause crashes, but they can cause odd problems.

Receiving unhandled NULL exception

Obtained 12 stack frames.

Holy jeez, that player log is a mess. My eyes cannot concentrate on anything :confused: Master Tao might be able to better decipher it. And I've been glad to help. If you feel that you would like to show your gratitude even more, you can do so by giving reputation. How to do that? At the bottom right of the post is a little star thing. Looks like a Sheriffs star. You just click on that, enter a reason for giving reputation (if any), then click on the button "Add to reputation". :P

Anyway, been glad to help, but no way in hell am I going to be able to format that player.log properly. Sorry about that.

ToTheMun

@ToTheMun thank you for everything you could do, and for even taking the time to help out those who need it.

@Master Tao i thought so too for the past several weeks, but yesterday i tried playing with activity monitor open right next to me. never went above 2 GB, even when it crashed. and i used to have ATM installed, but it causes strange things to happen to the graphics. odd shadows all over even in direct sunlight, shadows that are clearly of a defined object, or stencil, though what it is i can't tell. i have some screenshots here i believe https://drive.google.com/folderview?id=0B6zJ0kW58l-KZGNnSWh6T3ZKNU0&usp=drive_web

sorry about that long link. should work just fine though

and i have tried reducing the texture quality. the effect was minimal at best, and the lower quality really makes the game less pleasant to play.

Anyways, thanks for all of your help, both of you. if you need any other files or anything to help remedy the situation just let me know

Link to comment
Share on other sites

never went above 2 GB, even when it crashed.

That sounds about right for an out-of-memory crash – it seems that Activity Monitor only reports physical RAM currently in use by KSP. In any case, the 3.5 GB restriction only applies when you have that much available on your system. I have 8 GB total, but the way Mac OS X memory managment works since 10.8, it's all almost always in use.

and i used to have ATM installed, but it causes strange things to happen to the graphics. odd shadows all over even in direct sunlight, shadows that are clearly of a defined object, or stencil, though what it is i can't tell. i have some screenshots here i believe https://drive.google.com/folderview?id=0B6zJ0kW58l-KZGNnSWh6T3ZKNU0&usp=drive_web

That first screen shot definitely shows a graphical corruption – the long distance camera isn't using the same terrain shaders. BTW, you may also want to disable SM3 Terrain Shaders since they're poorly support on Macs. That does noticeably change the terrain graphics, though.

Link to comment
Share on other sites

That sounds about right for an out-of-memory crash – it seems that Activity Monitor only reports physical RAM currently in use by KSP. In any case, the 3.5 GB restriction only applies when you have that much available on your system. I have 8 GB total, but the way Mac OS X memory managment works since 10.8, it's all almost always in use.

That first screen shot definitely shows a graphical corruption – the long distance camera isn't using the same terrain shaders. BTW, you may also want to disable SM3 Terrain Shaders since they're poorly support on Macs. That does noticeably change the terrain graphics, though.

so with the RAM issue, i have 16, and activity monitor said i was only using 10, 2 of which were used by KSP when it crashed. so i should have had loads of memory left. and the graphics issue i found would persist on a version of ksp if i ever had atm installed, even after deleting it. but, if i reinstall ksp as a whole and never touch it with ATM, no issue. tested it twice

Link to comment
Share on other sites

Definitely not the normal out-of-memory issue, then. Now that I've had a chance to look through the bug tracker, it looks like this is specific to Yosemite: Bug #3404. It would help the most if you can reproduce that crash in a stock install, and then upload your Player.log to that bug report. Reliable reproduction steps would be a bonus.

For the ATM issue, try it again, and copy your logs from both stock+ATM and stock w/ ATM removed. Then post it in the ATM thread.

Link to comment
Share on other sites

Definitely not the normal out-of-memory issue, then. Now that I've had a chance to look through the bug tracker, it looks like this is specific to Yosemite: Bug #3404. It would help the most if you can reproduce that crash in a stock install, and then upload your Player.log to that bug report. Reliable reproduction steps would be a bonus.

For the ATM issue, try it again, and copy your logs from both stock+ATM and stock w/ ATM removed. Then post it in the ATM thread.

Concerning bug #3404 I have posted logs on that site and commented how to reproduce the error. I would like to point out that I have a fresh OSX 10.10 install and a Fresh KSP install.

Same problem. I have noticed the logs have an erroneous file path for the ship saves. At least these files and folders are not in my local files after a fresh install with no mods. The following logs do contain mods, but it didn't matter when I tried it with them removed.I enter career. Build simple ship. Name ship. Click save, click launch. Game freezes and never gives crash report.

Mac info:

Macbook Pro (Retina, 15-inch, mid 2012)

-2.7 GHz core i7

-16 gb ram

-SSD hard drive

-Nvidia GeForce GT 650M 1024MB

Version: OS X 10.10

KSP Version 0.25

Modded: yes

I have found a end user solution and what the problem is. All games are created without the SHIPS folder in the career saves.

Go to local game files> saves/[career title]/ > add saves/[career title]/Ships/VAB & saves/[career title]/Ships/SPH

boot game and it works.

Link to comment
Share on other sites

@jbi1031:

Good catch! So you went to KSP/GameData/[your save name]/Ships and made two new folders called VAB and SPH, right?

In this case, it looks like the KSP.log did include the full error message. Usually, the Player.log is much more useful.

Thanks!

@gkorgood:

jbi1031 has a different error in the log than you do, but it's worth trying her/his fix.

Link to comment
Share on other sites

  • 2 weeks later...

Hey guys, I have been suffering several crashes on my new Mac, as well as having the beachball of death constantly.

Reading the forums I can see lots of people complaining about Yosemite so i am not going to waste anybody time...

Short version: I have run it with and without mods. Clean install and crashes, especially when switching between the space centre, space and launch pad. Have done step 1 to 6 of the list

of the sticky thread and here is all the info of my install:

Mac Info:

OS X Yosemite (OSX 10.10)

iMac (27-inch, Late 2013)

Processor 3.5 Ghz Core i7

Memory 24 GB 1600Mhz DDR3

Startup Disk Macintosh HD

Graphics NVIDIA GeFore GTX 780M 4096MB

KSP Info

Version: 0.25.0.642

Installed From: Steam

Modded: Yes

Mods:

KW Rocketry v2.6d

Near Future Propulsion [v0.3.0]

Near Future Solar [v0.3.0]

HotRockets! Particle FX Replacement (updated on the 11 October 2014)

Simple Part Organizer - Version 1.2.1

Here is my player.log for you guys to download it. Let me know if there is anything else that I can try.

Link to comment
Share on other sites

@rodrigoelp:

You're running out of memory:

KSP(538,0xa0a781d4) malloc: *** mach_vm_map(size=8388608) failed (error code=3)

*** error: can't allocate region

*** set a breakpoint in malloc_error_break to debug

Receiving unhandled NULL exception

Obtained 50 stack frames.

Please read the How to Get Support (READ FIRST) sticky for general advice about this problem. If you want more help, please post a new thread since your problem is unrelated to the other problems here.

Link to comment
Share on other sites

This thread is quite old. Please consider starting a new thread rather than reviving this one.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...