ok putting this up for grabbing. cant test myself .. no OSX what soever available to me

Thanks to nalem, we got a new trail to this.

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

ty

2015-12-16 22:00:05
Full thread dump Java HotSpot(TM) 64-Bit Server VM (25.51-b03 mixed mode):

what exact OSX version are you using ?
are you using the latest Launcher version V58 from
http://sm-launcher-test.s3.amazonaws.com/index.html?prefix=jobs/Launcher/ ?

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.

Yes .. that is expected to happen on sector borders

-QA Testing-

-QA Testing-

-QA Testing-

Both my accounts that had this can be used again. I'll wait a bit to close it till I'm 100% sure it's not happening anymore.

-QA Testing-

@PhaserArray
hm, the logs dont give any useful information.
(The server side ones are the wrong ones, but 3 days would be several hundred MB of logs to look through.)

Why not make "brake" use the lowest available thrust level?

be ware that if you hit 1 (maybe your weapons) and the entity you had TabF8 switched from has the docking module on 1 it will activate it

ah damn, i meant to do resolve

made it a time independent from reboot.

Nope, TabF8 breaks things again.

Reopening, the plan is to use the thrust that remains after subtracting the thrust that's distributed to the rotational thrust. So not 100% realistic but better.

closing again then

In T922#36316, @SmilingDemon wrote:

@Chandler ... any news on this now? ... havnt seen it happening to any of my three bases storages

How to reproduce: trying to redock a turret to a ship crashes java (especially after a restart/not with a "freshly" built ship)

Suspecting infinite loop as well.
Log gets spammed with :
[2015-12-14 22:54:06] UPDATE MASSS: 494.666; (68662.87, 120127.75, 138773.48)
message.

tested it, with Tab+F8 and there one gets the message.
If nobody has anything against it i would reject the bug as if it really is just about TabF8 it is not really a concern (with TabF8 being a little bit buggy in itself)

One thing I forgot to mention is that it happens every time I jump out of the sector that has the shipyard... And then jump back in after some pirate combat.

Happens in MP too, JVM stops responding, it's probably an infinite loop when updating mass.

I went back and gave warping about a shot as well but wasn't able to recreate it that way either. I'll keep tooling around for a little to see if I can get any better luck. Let me know if recreating the server fixed it.

Ok .. i tried this for a time now .. and sadly cant reproduce it.

@Chandler ... any news on this now? ... havnt seen it happening to any of my three bases storages

I agree with Ithirahad, I am on the fence as well, but I can see where this can be in both RP aspects and applying instantly such as in the case of Elite's "Pip" system and where it can be abused to gain a further advantage over a rival player by sudden, massive thrust vectoring and rotation changes. It will likely require a lot of user-testing, and perhaps a few PvP Events / Fleet Operations to determine what is best

Not sure which side of this I fall on, to be honest. Really, the only problem with this is turn speed (Particularly on larger ships), which makes me wonder if only locking in turn speed should require a reboot. Also, if changing thrust settings does require a reboot, then docking should probably also allow free modification after a short "engine cooling down" timer.

The logs seem to contain no related error as far as I can tell, putting the ticket up for grabs if anyone else may have an idea.

I'm sending you your 2 logfiles, plus the terminal output of the server.
It's a lot. You may want to not show it anyway.
Note: the 1st line below outputs VERION instead of VERSION.

To answer all questions:

issue happens as described. Placing 2 or more blocks of -any- type then removing them recreates the problem

Had it again when i destroyed a turret with missiles (right after it hit), debris was enabled.

-QA Testing-

type of block to be placed and removed to make rotation bug out seems to be not associated with thrusters

The reason it should only be applied after reboot is to stop Super-Capitals going from sluggish brawler, to lightning turn speed at a few clicks.

Armored entity does not lessen damage against a shielded entity behind it vs penetrating shot.

added some security. If still not fixed. I need new logs, as I added some extra debug info

This is not really possibly in a kind of logical way, and would if forced probably destroy gameplay:

What's the reason it should only apply after reboot?

-Confirmed-