Creating new task - after reading more details of this discussion, it might not be the same issue...although it seems very similar.

Cant reproduce

lol the phabricator version of "FIRST!!!!11!11ONE!"

It's because F1 + 3/4 doesn't rotate everything about a block. It's an old debug command that is well...old, don't think it's worth time fixing this unless the community demands it.
The issue you describe was also visible when copy/pasting displays with logic which was fixed before it got released, 3-5 weeks ago.
Displays themselves also leave meta data behind (doesn't get cleaned up properly) when removed which is most likely causing this behavior when forcing rotations like this.

Your issue was mentioned in another task, edited it a bit to make it more clear. Merging tasks.

-validated- & -confirmed-

-QA Testing-

Shouldn't the delay then be 510ms (17*30ms) instead of 555ms (18.5*30ms)?

In T1994#78724, @AramDol wrote:

That stopped it from briefly displaying the StarMade window at 1280x720 on boot, but it did not fix the mouse issue.
"Game doesn't work" sounds more like a game breaking bug than a support issue to me.

We had a display issue about shields going above 100% but that was fixed. Not sure if that was fixed before this task was made or after but in my mind it's "recent". This task is too outdated to still be relevant though, if it occurs again, please make a new task.

Looks like key registering got "stuck", alt tabbing is usually a good way to attempt to unstuck it which may have been the case here. I'm using AZERTY layout too and a non standard config but never got this behavior related to this.

That stopped it from briefly displaying the StarMade window at 1280x720 on boot, but it did not fix the mouse issue.

Could have used a log file but it's been a long time so nevermind. the revertBehaviorConfig is an incomplete feature, shouldn't work like you think it works.

Removing the AI block doesn't do anything except make the "deactivate all AI Turrets" not work properly for that turret.
Turret AI is stored in the ship itself, not the AI block.

Server updates aren't as frequent. They're 30ms each so the 500ms delay isn't entirely accurate resulting in this. Not a bug

Just done it again, Fired missiles in .246, these cratered a Target. Jumping to a star does NOT bring up a "Heat Damage Warning" or Proximity warning. Godmode was never enabled. will test it ion next builds when they are available

nvm, was apparently broken in that particular version but not in the ones that followed.

Can't confirm. I'm assuming something went wrong with missiles completely and no explosion damage is dealt which includes heat damage.

this is most likely a support case.

Still an issue:

Oct  7 12:16:01 stars SMStage: [FACTIONMANAGER] trying to add news entry: FactionNewsPost [factionId=10797, op=ADMIN, date=1475842561871, message=Ownership of System default(-141, 0, -21)
Oct  7 12:16:01 stars SMStage: has been revoked by ADMIN., permission=0] on Server(0) -> fid(10797)
Oct  7 12:16:01 stars SMStage: [FACTIONMANAGER] updated news on Server(0) for factionID 10797; delete: false

v0.19584 has the same behaviour in fullscreen mode, even though the game starts windowed.

-rejected-
known problem on fresh Linux install
Please change the texture package to default in the options menu or texture size to 64 pixel

This bug is still present with the new thruster plumes, it looks even worse now.

Ah, that explains why I never had it. I always click the tile, not release tab when I'm hovering over it.
This crash only happens if you do the latter so yeah, good find and thanks for the feedback!

I'm finding the ship design to be irrelevant and can trigger it with just a ship core.

very good.
have fun then

Still can't reproduce with that provided blueprint. I'll leave it open for now till we encounter it. If you ever have this issue again, please provide us a log -> logstarmade.0.log in your logs folder, make sure to not start up the game again before you've shared that log or it will be the wrong one. Else it's logstarmade.1.log but better give them both to be sure.

Some extra info so I'll merge this one into our existing task.

Merging another task into this since it's brought up too.

Duplicate of T1834.
You pressed Tab + 2 in the past or F1 + 2 recently, it messes up most of the rail textures. Only way to fix it right now is to delete your Starmade.jar and redownload it. (Followed by not pressing F1 + 2 again)

Ok, we figured it out.

not happening for me

Ok .. as far as i can see the Wireless and inner ship remotes broke (thats not a new thing at all)