Problem was fixed a few builds ago, I assume this can be closed then?

This may prevent the crash from happening, so only do this after you uploaded that log file since we need that to provide a real fix.

Thanks for sharing that world but it seems the files are incomplete. It only contains the npcFactions, where as your world should also contain a DATA and index folder.

Unfortunately I'm unable to reproduce the issue following those steps to the letter.
Anything you did after the "Create a station" step that you forgot to mention? Even trivial stuff like connecting a factory to something could be a cause.

Its not happening as you do discribe it.
please take a few screen shots from what to shot at and please do add the blueprints of the shooting ship and the target
(maybe its weapon specific)

converting to bug report

May i close this ?

Hello
Please add the logstarmade.0.log file of one of those crashes (and anyother if it isnt the only log from that game session)
If possible also add the Blueprint that is causing this for you

1- Assigned buttons layout :

i build this ... and it rotates without a problem on a station.

the grey hull in the background is also a part of the entity from where you are using the build mode from ?

@Valck can you confirm my observation about the file creation in singleplayer but not in multiplayer ?

Was the reactor damaged?
Were chambers connected?

[2017-09-20 16:35:05] [SHADER] ERROR COMPILING VERTEX SHADER data\/shader/cube/quads13/shadowcube.vsh STATUS: 0
[2017-09-20 16:35:05] LOG: WARNING: 0:3: extension 'GL_EXT_gpu_shader4' is not supported

Examined it:

That would be explained by missing meshes, they will be created properly with the new version.
Should not happen again.

You can just drag an drop the file into the comment edit field

The issue has been addressed in the latest release and should not happen anymore.

Can you provide a sample blueprint for a station with this effect?
We would like to test and examine it for errors and possible problems.

Can you upload the logstarmade.0.log from the server-side from a broken startup?
There should be some error, that locks parts of the server.

Do the turrets or other docks that do not switch have permission modules beside the rails, rail docker or rail turret axis?
The does exempt them from any faction change propagation, to prevent takeover of docked neutral ships.

Well, can't reproduce it but at this point I'm not really surprised...These GL Exception issues happen seemingly random for players or if you're able to reproduce it consistently, it seems only you can do that and anyone else is just fine.
Might depend on GPU drivers but as both you and me are using Nvidia, I'm not entirely sure what's happening in your world compared to my test setup.

Yes it is.

@Lunchbox and @The_Onion
Can any of you upload a blueprint of the ship + thing docked to it that causes it? And/or provide very clear steps to reproduce for a simple example?

Interesting, found this:

[2017-06-07 09:59:12] Exception in thread "pool-2-thread-1" 
[2017-06-07 09:59:12] java.lang.ArrayIndexOutOfBoundsException: 10485763
[2017-06-07 09:59:12] 	at org.schema.game.common.data.explosion.ExplosionDataHandler.a(SourceFile:162)
[2017-06-07 09:59:12] 	at obfuscated.adN.run(SourceFile:313)
[2017-06-07 09:59:12] 	at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
[2017-06-07 09:59:12] 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
[2017-06-07 09:59:12] 	at java.lang.Thread.run(Unknown Source)

which is about a minute after your force-save started.

Depends on the amount of blueprints you have (and also on the server I believe). It freezes, but as long as you don't really do anything it will get through.
Would merge this one with T2176 but wouldn't mind your logstarmade.0.log after crashing to see if it's the same issue or some sort of exception that pops up first.

@Manithro
As this seems to be a specific problem, and not a general one,
may you please provide us a blueprint of the shipyard so we can test it?

They still appear just fine for me in the test sector, could it be something else causing it for you? There was a report about them not working properly when docked to stations or planets, or at least related to docking.

As I'm experiencing it too, then it can happen to other people as well. I do not need confirmation on that, just the questions I asked in my feedback suggestion.
Does width matter here and if off-center weapons cause this behavior to always trigger? From what I've seen it's no, but only the task owner can double check this for sure which is why the issue is set on feedback for confirmation.

Which menu are you talking about specifically?

Well, the defaults are:

Checked the behaviour and could not see a problem, possibly a slight oversight?

Looks like a broken blockconfig.

We released a few improvements on them again,
may you examine the behaviour again?

Did this happen again afterwards?
It could be some server-side rollback, and not really shipyard related.