Jump to content

interslice

Members
  • Posts

    9
  • Joined

  • Last visited

Posts posted by interslice

  1. These are my system specs: Late 2014 13" Macbook Pro, 8GB RAM, Yosemite 10.10.3, 2.6GHz Core i5, Iris graphics

    The crashes happen on a scene change, after a few of them have already taken place. It is preceded by graphical corruption such as what you see below, usually you can fly one more mission with these "shadows" present and the game will crash on craft recovery, or in the VAB slightly later.

    http://i.imgur.com/qno9N5n.png

    Reducing graphics quality appears to delay the inevitable, but crashes happen nonetheless.

    Sorry, but I have to work and I won't be able to play bug hunter anymore for a while. I am quite disappointed that this hasn't improved a bit since 0.90.

    same thing here. mac pro 2013 hex core 32gb ram.

    it happens when the ksp app hits 3gb of ram usage according to activity monitor. time isnt exact but right before 3gb (2.95+) it gets those weird graphical glitches and then once its over 3 it crashes.

    player.log comes up with this:

     =================================================================
    Got a SIGABRT while executing native code. This usually indicates
    a fatal error in the mono runtime or one of the native libraries
    used by your application.
    =================================================================

    KSP(484,0xa03e61d4) malloc: *** error for object 0xed37a000: Can't deallocate_pages region
    KSP(484,0xa03e61d4) malloc: *** set a breakpoint in malloc_error_break to debug
    KSP(484,0xa03e61d4) malloc: *** error for object 0xc70db000: Can't deallocate_pages region
    KSP(484,0xa03e61d4) malloc: *** set a breakpoint in malloc_error_break to debug
    KSP(484,0xa03e61d4) malloc: *** error for object 0x12a33000: Can't deallocate_pages region
    KSP(484,0xa03e61d4) malloc: *** set a breakpoint in malloc_error_break to debug
    ipcserver restart: expected: 104, got: 0
    KSP(484,0xa03e61d4) malloc: *** error for object 0xecd01000: Can't deallocate_pages region
    KSP(484,0xa03e61d4) malloc: *** set a breakpoint in malloc_error_break to debug

    also has logs under system and user diagnostics reports.

    hoping this gets fixed quicker than the last memory hang issue i reported that lasted for 4 patches. would be a shame to have to use windows for this.

    TLDR Reproducible when app hits 3gb ram usage. takes longer with lower settings.

  2. Both look great! Where did you stick the SAS units?

    both have them as part of the chasis at wheel level. just thicker bottomed than most rovers. sas is so useful on a rover since they ALL flip, but other reflipping methods ive tried like rockets (runs out of fuel) and lander legs (looks dumb a lot of the time) have drawbacks. plus it keeps them stable when hovering or moving quickly.

×
×
  • Create New...