Unfortunately there is simply no way to fix the "mass reduces max speed" unless you make thrusters extremely overpowered or mass so little that it doesn't matter. It's a hard coded calculation.
Correct me if I am wrong, but WAL is not supposed to significantly increase write performance, rather it prevents reads from blocking writes and writes from blocking reads, thus it should mostly only increase write performance if there is significant congestion, like tons of reads blocking those writes, or massive writes that end up causing reads to pile up. However, it may notably improve stability and smoothness on busy MP servers, as significant blocking would appear like lag spikes to users. As for MEMORY, I assume that's mostly used for large organizations running massive reports, where their queries run super slow unless everything's already in memory.
Yes! Noticed that when fighting a Zirax frigate. Enemy ship kept jumping position, sometimes making its turrets face my poor little CV. Thanks for the fix!
Didn't play for too long but... I loved how everything looks less smoky and less dark in some planets. Even through window glasses the view looks better. Another thing: is it just me or Drill T2 (SV) feels more powerful and has a longer range now? Mining asteroids became such a joy.
or even more simple just edit your games gameoptions.yaml and turn off CPU and mass, etc , that way you don't have to worry about those game changes at all , i did it for my server and all players are much happier
2020-09-15: Experimental 1.1.7 (Build 3081) Changes: - DialogueSystem: added new variable types (dbglobalpf_int and dbplayerpoi_int) Fixes: - [MP] AI Turrets sometimes continue to shoot at dead NPC's that are not rendered - DialogueSystem: potential fix for losing variable content if there was a connection timeout when starting a dialogue - one CoQ and one item exploit
