The broadcasting system of DDS seems to be slightly inconsistent and sporadic. I'll try to describe the current setup as close as possible:

In the current testing scenario I have three ships, one enemy vessel, one designator ship and one missile ship.


Enemy Ship
^ ^
| |
| v
| ~750m Designator Ship
| ^
| |
v v
~1.5km ~750m Missile Ship


Designator Ship:
Running DDS
6 Designator Turrets
3 Antenna (50km)
Targets tracked: 1

Missile Ship:
Running DDS (with customData for longer range)
3 Designator Turrets
1 Antenna (50km)
3 Guided Missiles


If I want to fire missiles it doesn't fire. The PB on the Missile Ship sporadically and randomly recognizes the broadcasted target from the designator ship for less than a second where the PB on the Missile Ship shows a tracked target, then it vanishes and shows tracked targets at 0 again. If I fire during that time, the Missile launches. If I miss the window I can't launch the missile.

During my own testing, im having an issue with the broadcast comms system if the script is loaded into the PB after world load. Not sure why the comms will be choppy and inconsistent like this, but when i i reload the world the issue is gone.

May need to change comms regiatering sequence to get around this possible Keen bug

Forgot something, tracks transmission is every 10 seconds. Auto delist (something like timeout to delist dead tracks) is 1 seconds. Its an oversight but you can quick fix it. Enter the following into the Custom Data


[DDS]
targetTracksTransmitIntervalTicks=30



Put the above in the Custom Data of the Sender ship's PB.

Transmission issue fixed. Now it transmits every 45 ticks (3/4 of a second). Update to new script and ur missile cruiser will work as intended. Let me know it there are other issues.

@Alysius, thank you! I'll try and see if it works!

EDIT: As of now it seems everything is working properly! Thank you for your hard work! :)

np

i have a problem with the turrets. im trying to make a remote designator for a vehicle that uses this script, but whenever a target is detected the firing vehicle with the turret seems to lag behind, and fires onto a point where there was a target, but is no longer there. i can fix this by respawning the vehicle or recompiling the prog-block, pls help

The lag is due to the network communication delay. Not sure if thisbisbpossible to fix, will have to test it out.

Ray casting has changed in Space Engineers since the last update and this script is broken now. Can you please fix it, I love this script.

Hello,
I have an issue with placing connector based missiles on my ship.
Basically DDS script does not see those.
However when I place the same missile on merge block it becoms visible for DDS

custom data doesnt appear to work for the PB... tried resetting the script and all kinda of stuff but still no go... only manually editing values through recompiling the script seems to work...

can the script lock on targets beyond the range of the designator turrets using raycast? if it cant can that be a feature?

I don't quite know how to explain this but: When I try to use the script in a PB on my launch vehicle and put the FIRE command into the tool bar, the PB only shows the script info for less than a second before it goes blank again.

I can confirm what Vlad Putin said - custom data doesn't show anymore.
There is also a problem with autoreloading of PDC turrets. It works but takes about 30 seconds to reload.
During those 30 seconds turret spins in both axis then stops with connectors next to each other (but is not locking them) then spins a bit more and reloads or repeat whole process.
Is it possible to determine which direction is the top of the turret?
After reloading sometimes it stays like it was but sometimes its upside down.

Hey, in your guide you said the turrets work with rotors or hinges, but when i load the script it doesn't seem to identify PDC's with hinges for elevation.