Good. I’m glad that’s fixed.

This may have been fixed a couple of versions ago. The thing about integrity explosions not deducting RHP might be what caused this behavior, but I don’t think that had been reported as such at the time I found this.

In T2779#117011, @lancake wrote:

In T2779#116861, @Valiant70 wrote:

Tested on Macbook Pro 2012, Intel HD Graphics 3000 1024MB, OSX Mavericks.
I can't get more than 15 FPS in version 0.200.269. I only had a shop and a small wad of systems on screen.

This only happens if there is any energy stream visible? Or just bad performance in general even if there are no stabilizers?

Tested on Macbook Pro 2012, Intel HD Graphics 3000 1024MB, OSX Mavericks.

Seems to be fixed. Strands must be 4x4 to go positive with integrity.

Still an issue in 200.252

In version 0.199.654, this nonsense happens.

I haven't noticed it yet with build 158.

With initial + early generation >= 2GB, the slider will not slide below the next power of two. Below 2 GB, it will slide down to a value equal to initial + early generation. Whichever behavior is intended, something is inconsistent.

When I typed in "brusselsprouts" or "W/waffles" instead of a path, it read "there is no java executable in the specified path.

OSX: When initial memory is set to 2048 and early generation is set to 1024, the slider will not slide lower than 4096. However, typing 3072 is allowed, and typing in any lower value sets it to 3072 when the user clicks save. This does not appear to be fixed.

Fixed for OSX as well.

Fixed on OSX as well.

This issue or a similar one affects me in flight mode only. It acts like inertial scrolling is on or something. I can scroll fairly comfortably on my Macbook's trackpad, but trying to use a clicky mouse wheel causes erratic behavior. This happens only in flight mode; build mode and astronaut mode behave as expected with one wheel click moving the hot bar one space.

I'm talking about uplinking for game servers.
Yes, this is a Mac.

Workaround suggested by SmilingDemon:

I ran across this bug earlier and it's really annoying. I was trying to test something with shipyards.

A friend of mine who is working on turrets told me this bug does not affect AI turrets. I think AIs skip the raycasting step and just hit what the game already knows they're shooting at.

The issue seems to occur when launching with starmade already installed. I tried closing starmade from the game, main menu, and launcher.
Here's what I found:

OSX Yosemite version 10.10.5 (14F1509).
Yes, latest launcher version.

I restarted after the issue above and, the same thing continued to happen. The launcher came up momentarily, and then turned grey as the image above shows.

I have determined how to reproduce this bug on my computer, if this is even the same issue. After restarting my computer, I was able to run the launcher normally. However, if I close the launcher rather than pressing launch, then try to open the launcher again, this happens. (See attached image.) That large rectangle is the launcher. It flashes the normal launcher briefly as it starts up, then turns into this.

Better yet, here is a link to the ship resource. My friend uploaded it to the dock. http://starmadedock.net/content/sbs-171-masakari.3525/

It is absolutely related to non-cubic blocks and it is not related to either of those issues. This issue happens to me frequently onboard a particular ship while walking through a diagonal 3x3 hallway with beveled edges. I can screenshot the hallway if that would be helpful.