grid ai missiles not working properly after the fieldwork update

Space Engineers Support ●

Hello, Engineer!

We're sorry to hear you're experiencing issues. As you've posted a link to the Steam Workshop, we'll move your ticket to the PC side of the Support Portal.

Kind Regards

Keen Software House

QA Department

Reply URL

1

Space Engineers Support ●

Hello, Engineer!

Unfortunately we've been unable to reproduce the issue on our side. Could you please let us know if you're experiencing it in Single Player or in Multiplayer? Are any mods present in the world? Could you provide a video of the issue?

Kind Regards

Keen Software House

QA Department

Reply URL

1

jonathan farrell ●

hi i made a new world with out mods the tested is and the issue wasn't occurring and it also didn't occur when i added the mods to the world it was still not evident so I think the issue was isolated to the world.

Thanks

Jonathan

URL

1

Engi ●

I looked at your blueprint and did some testing. I do also see the bottom missile (one on each side) working as I think you intended them based on looking through the actions you have setup, but the top 2 missiles are delayed.

Firstly, you should name all the blocks on the missiles with prefix like missile 1, 2, 3, 4, 5, 6 so that the blocks can be told apart from the menu. This will help with diagnosing problems as that made it harder than it would have been if they were distinctively named. You can use a block renaming script like izzy's to just add prefix's to each missile before you attach them to the wrack an then blueprint it. I do this with mine. I build one missile, copy/paste more next to it, place PB on it and use script to add prefixes to each of them that are different.

Secondly, you want to set the offensive block Target Search Interval to 5 seconds. What is happening is that the top two missiles on each wrack are waiting 20 seconds after their offensive block is turned on to select a target so they are delayed. Why the bottom missile is not is kinda odd. I think that while they are on the wrack, even though they are disabled, they are selecting targets and because only one offensive can be enabled on a grid at a time (even though they are not visibly enabled), one actually is "under the hood." I suspect that the bottom missiles on each rack are the first missiles you pasted onto the rack during design so they are a sort of "primary." This is why they already have a target locked when they activate as the target is already in 2.5km range before launch. If you launch from out of range, there is no difference between them. So that seems to be a sort of...not sure if it is a bug... but quark to how they work with multiple ai's on one grid, even though they are technically not enabled in the UI.

However, once you set the interval to 5 for all of them, clear the blueprint from the projector, blueprint them changed, add the new blueprint to the projector, print new ones, they work normally, 5 seconds after the ai is activated, they all lock on and turn to the target at the same time. Even when they are all reset to 5 seconds, the bottom one does not have a target selected right when it is activated. All 3 missiles wait the 5 seconds and then turn. I suspect something changed with the update that made them...out of sync or something and resetting their timers to 5 seconds and blueprinting gets them back in sync. There is no real reason to set that search interval timer to more than the minimum 5 seconds. I wish it were instant, not 5 seconds, personally.

I looked at your blueprint and did some testing. I do also see the bottom missile (one on each side) working as I think you intended them based on looking through the actions you have setup, but the top 2 missiles are delayed.

Firstly, you should name all the blocks on the missiles with prefix like missile 1, 2, 3, 4, 5, 6 so that the blocks can be told apart from the menu. This will help with diagnosing problems as that made it harder than it would have been if they were distinctively named. You can use a block renaming script like izzy's to just add prefix's to each missile before you attach them to the wrack an then blueprint it. I do this with mine. I build one missile, copy/paste more next to it, place PB on it and use script to add prefixes to each of them that are different.

Secondly, you want to set the offensive block Target Search Interval to 5 seconds. What is happening is that the top two missiles on each wrack are waiting 20 seconds after their offensive block is turned on to select a target so they are delayed. Why the bottom missile is not is kinda odd. I think that while they are on the wrack, even though they are disabled, they are selecting targets and because only one offensive can be enabled on a grid at a time (even though they are not visibly enabled), one actually is "under the hood." I suspect that the bottom missiles on each rack are the first missiles you pasted onto the rack during design so they are a sort of "primary." This is why they already have a target locked when they activate as the target is already in 2.5km range before launch. If you launch from out of range, there is no difference between them. So that seems to be a sort of...not sure if it is a bug... but quark to how they work with multiple ai's on one grid, even though they are technically not enabled in the UI.

However, once you set the interval to 5 for all of them, clear the blueprint from the projector, blueprint them changed, add the new blueprint to the projector, print new ones, they work normally, 5 seconds after the ai is activated, they all lock on and turn to the target at the same time. Even when they are all reset to 5 seconds, the bottom one does not have a target selected right when it is activated. All 3 missiles wait the 5 seconds and then turn. I suspect something changed with the update that made them...out of sync or something and resetting their timers to 5 seconds and blueprinting gets them back in sync. There is no real reason to set that search interval timer to more than the minimum 5 seconds. I wish it were instant, not 5 seconds, personally.

Files:

Reply URL

1

jonathan farrell ●

HI sorry for the late reply I tried the method you recommended and it works fine. the 20 second interval was intended to keep the missiles from switching targets mid flight I have found a new work around for that too.

For the original problem before the latest update the missiles where working perfectly in the configuration they where provided in the blueprint. my best guess is that something on the ai block was changed which has caused the ai offensive combat blocks to not work if there is more than one on a grid

Thanks

Jonathan

https://steamcommunity.com/sharedfiles/filedetails/?id=3480808791

81f3ccbb12da8f7203557ac95aa1fb0b

Reply URL

1

jonathan farrell ●

also just wanted to confirm the second test I did only had one mod which was recolourable thrusters

Reply URL

grid ai missiles not working properly after the fieldwork update

Replies (5)