Probably was there for a while, apparently it's a message you get for all connection or runtime issues. Including being banned.

You're docking to something that is in 2 sectors at the same time, it is on the border. This causes misalignment issues.
For example, you dock something in sector 2 2 2 but the game puts the ship at the correct position, just in sector 2 2 3 (which is 1000 meters apart in your case).

That config option only touches point defense turrets. If it is enabled, your factioned PD turrets will target missiles of your own faction too. If it is disabled, your factioned PD target neutral/enemy missiles only.
That's it.

Relation to T1409 is possible, although what's unusual about this one, is that the lag-inducing entity cannot be referenced by UID.

Couldn't reproduce with ship targets, I could with a station though.
What were you shooting at?
Did the missiles keep doing this even when the nav marker was removed?

AI ignores this condition, or it straight up brute forces through it. Merging with other task.

-validated- & -confirmed-

Putting in queue for that flickering, assuming it was just some left over.

Seen it before although I don't remember a crash happened. The server didn't have asteroid respawning enabled though which might have something to do with it. Can only reproduce the log entry, crashes aren't happening.

Woah, I updated and opened my starmade this morning and everything was dark, like the lighting engine was turned off. So I set "CUBE_LIGHT_NORMALIZER_NEW_M = true" and everything is back to normal. But I know that I launched starmade multiple times last night with that set to false and it wasn't dark. What does that setting do?

Occured on Latest Version at the time of posting, can't seem to edit orginal post

Confirmed, I did a fresh install of the latest dev build in an empty directory, and couldn't replicate the effect there. Maybe it has something to do with the world that has been generated years ago.

(my internet is finally back up, and I can post this)

I am seeing this bug in the current version 0.198.477

Found back also the previous task where it was reported : T1539: Block lighting normalization issues

In T1690#66232, @lancake wrote:

Are you sure this only started happening after the new lighting?

Noticed by you in T489 but looks like it was missed during QA Testing.

Duplicate, merging tasks.

Are you sure this only started happening after the new lighting? Go to your settings.cfg and change:
CUBE_LIGHT_NORMALIZER_NEW_M = true
to
CUBE_LIGHT_NORMALIZER_NEW_M = false
Make sure to save the file and start starmade up.

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

Can't reproduce, tried out your settings and we both have the same GPU series. Except that your GPU has no drivers apparently, consider downloading the latest one from Nvidia.
Also you should probably delete your settings and change it again if needed, its using some old values that you shouldn't use anymore (like a disabled frame buffer).

True...There's probably a reason for it but I'll put it in queue. Schema can reject it if he won't change it.

Merging with other task.

@Sethroph .. your logfile is from a server start. so i do assume its the same effect as Croquelune described, where the dedicated server start wipes the settings.cfg back to default. i too cant remember that that was ever the case.

In T1689#65957, @Valck wrote:

That's to be expected, as both the server process and the client do write the config files, even if nothing has changed. Whoever goes last, wins.
As a workaround, have two installations, one for the server, one for the client.
As a suggestion for a possible solution, the server should keep its settings in the respective world directories; that would also allow several universes with different settings. Ideally that should include the blueprints and custom config xml files as well.

We'll have to take a look at it again, there's already a task about it so merging them.

Was fixed before release.

That's to be expected, as both the server process and the client do write the config files, even if nothing has changed. Whoever goes last, wins.
As a workaround, have two installations, one for the server, one for the client.

It's happen to me with 100% chance each time I use the starter.exe (old launcher) for launch "dedicated server" and then open another starter.exe for launching the game. While in game all my settings and keyboard shortcut are reset. So it's both settings.cfg and keyboard.cfg which are impacted. I'll bring the log next time I'll launch my private MP.

please just delete that log insert and drag and drop the whole file into the posting ... do not copy paste the content

I'm using El Capitan and the log is below:

not a general issue

are you talking about the Login at the start of the Launcher or
about the Uplink to the Registry for validation to game servers ?

Girders have been in a build before yes.

I feel like if you use the shipyard modules in a downward facing "C" shape, then you're fine. And that would be the most common shipyard shape, but stray from the path just a little and you're blocks might not align. The alignment I mentioned earlier could be used in a side "C" shaped shipyard, where it opens to the side. I wonder if they've always been like this?... I guess I usually make traditional shipyards.