Space Engineers

Space Engineers

Diamond Dome Defense Script
 This topic has been pinned, so it's probably important
Alysius  [developer] 14 May, 2019 @ 6:42pm
Final Suggestions Poll
We have gotten a few suggestions in the past week. If you have any others, post here. Any suggestions after this period will only be considered in the next DDS version v2.0.

**edit** If you have posted your suggestions in places other than GV Server Discord or Reddit, it may not have been captured. Please post it here again in that case.
Last edited by Alysius; 15 May, 2019 @ 12:52am
< >
Showing 1-3 of 3 comments
Hero 16 May, 2019 @ 4:53am 
It would be cool to have two extra lines in the PB's details window with the number of targets being transmitted and targets received from antenna network underneath the tracked target line to help with problem finding.
Alysius  [developer] 16 May, 2019 @ 7:16am 
Can add that easily. Adding once im back from vacation.
Alysius  [developer] 19 May, 2019 @ 7:09am 
Full suggestions list gathered from different sources:

1) Manual aiming for different turrets on board (for different players to paint different targets out of turrets range manually, for missile launches).

2) Have a simple launch control that receives data from DDS and allow players to launch missiles manually at their own discretion, from safe distance).

3) Hash enemy grids to give simplified naming (e.g. T1836) in LCDs. Because intergrid comms will sync targets to all DDS, and commander can say this simplified name in chat for all other ships to focus attack on same grid using Toolbar actions. Recall Picard Borg cube battle (e.g. everyone target this coordinates on my mark).

4) Extra Echo info to list stuff like how many targets engaged, how many from network intergrid comms etc.

5) Enter DEBUG command to show full list of PDCs configuration and detection, show on Hud for identification.

6) Auto check DDS groups to refresh PDCs and Designators list. This is for repairs to be done and accepted by DDS without recompiling.

7) Lightweight mode to greatly reduce CPU consumption, at the expense of higher turning rate of PDC (don't use rotor limits, just use velocity only... a.k.a PID).


All these suggestions are evaluated as achievable and will be pushed out within 2 to 4 weeks. Any other suggestions will only be considered when the next suggestions window is opened (i.e. When the next Version 2.0 Diamond Dome has begin construction).

Thank you all!
Last edited by Alysius; 19 May, 2019 @ 7:12am
< >
Showing 1-3 of 3 comments
Per page: 1530 50