AI Recorder breaks when changing AI Flight Block Settings
essentially copy of that topic, as i accidentially submitted a feedback instead.
when you change Collision Avoidance or Precision Mode settings it breaks AI Recorder functionality.
e.g:
- if you have e.g. 4 waypoints and change Collision Avoidance and Precision Mode at waypoint 3, it won't continue to waypoint 4.
- if you manually control and change the Collision Avoidance or Precision Mode setting, then trigger AI Recorder (ai behavior + play on) - it breaks
- if it is broken it e.g. goes through waypoint 1-2-3-4 almost instantly without moving actually the grid, if you flip the settings of flight ai block "pre mode, collision avoidance" and trigger play again on the ai recorder block - it might work as intended again.
cut&pasting the grid fixes it, but just for a moment and not permanently, next change of said ai flight block settings breaks it again.
this worked perfectly fine with the same drones i used in signal update and appearently broke in contact.
grid: e.g. "redbroken"
i already tried many different settings, like where to change what setting, and the only way i can "reliably" use drones is keeping collision avoidance off and pre mode on, which is not really practical way as you essentially created suicide drones and it is just a matter of time when they gonna kill you or damage something.
I have the same bug
actually, not only ai recorder breaks but also ai basic block.
i set a patrol route with a few waypoints on the basic task, it fails to execute that task if i make changes like collision avoidance and precision mode.
it cycles through the gps waypoints almost instantly without even moving the ship.
actually, not only ai recorder breaks but also ai basic block.
i set a patrol route with a few waypoints on the basic task, it fails to execute that task if i make changes like collision avoidance and precision mode.
it cycles through the gps waypoints almost instantly without even moving the ship.
Hello, Engineer!
Thank you. We have reproduced the issue and added it to our internal system. The thread will be updated once we have more information.
Kind regards,
Keen Software House: QA Department
Hello, Engineer!
Thank you. We have reproduced the issue and added it to our internal system. The thread will be updated once we have more information.
Kind regards,
Keen Software House: QA Department
I'd like to say 2 things.
1. After stressing for a few days about why a technique for drones that previously worked just fine no longer worked, it was reassuring to read this bug report. It describes exactly what I was seeing, thank you for taking the time to write this up.
2. I may have found a work around. It's down to the settings on the blocks when you make the recording. For example, if have
After I record Waypoint 2, I must make sure that I go and Set Precision Mode On, then move to the next spot and record Waypoint 3, then go to the AI Flight block and Set Collision Avoidance Off - any actions you want that involve touching the AI blocks should also be applied during the recording. In some very simple testing, this seemed to work for me. Also the starting settings of the AI Flight block did not seem to matter. YMMV.
An observation about the bug that may help the developers track the issue down. If you have "Show Path On HUD" and "Show Selected Points" enabled (and the other associated settings, all waypoints selected), when the bug occurs the path disappears from the HUD completely. The GPS-like markers for the waypoints do not disappear.
I'd like to say 2 things.
1. After stressing for a few days about why a technique for drones that previously worked just fine no longer worked, it was reassuring to read this bug report. It describes exactly what I was seeing, thank you for taking the time to write this up.
2. I may have found a work around. It's down to the settings on the blocks when you make the recording. For example, if have
After I record Waypoint 2, I must make sure that I go and Set Precision Mode On, then move to the next spot and record Waypoint 3, then go to the AI Flight block and Set Collision Avoidance Off - any actions you want that involve touching the AI blocks should also be applied during the recording. In some very simple testing, this seemed to work for me. Also the starting settings of the AI Flight block did not seem to matter. YMMV.
An observation about the bug that may help the developers track the issue down. If you have "Show Path On HUD" and "Show Selected Points" enabled (and the other associated settings, all waypoints selected), when the bug occurs the path disappears from the HUD completely. The GPS-like markers for the waypoints do not disappear.
9 Months of
"Thank you. We have reproduced the issue and added it to our internal system. The thread will be updated once we have more information."
and nothing?
9 Months of
"Thank you. We have reproduced the issue and added it to our internal system. The thread will be updated once we have more information."
and nothing?
Commenting for the issue not to die and be forgotten. It's extremely annoying.
Commenting for the issue not to die and be forgotten. It's extremely annoying.
It seriously still sucks but if you add enough blocks, which makes your tiny cargo drone not so tiny, you can workaround it though mostly .
Add 2 (or more as required... ) Ai flight blocks and switch between them, make all changes with e. G. Timer blocks instead of doing things at Ai recorder way points.
You may need like 10 additional blocks but it kinda works, but to be honest, I kinda lost the interest on my own drone fleet because of that issue.
Still curious how keen could break that functionality that bad and do nothing to fix it, especially because it worked already..
Even with workarounds, the drones get stuck and need so much babysitting which make that a bit pointless.
It seriously still sucks but if you add enough blocks, which makes your tiny cargo drone not so tiny, you can workaround it though mostly .
Add 2 (or more as required... ) Ai flight blocks and switch between them, make all changes with e. G. Timer blocks instead of doing things at Ai recorder way points.
You may need like 10 additional blocks but it kinda works, but to be honest, I kinda lost the interest on my own drone fleet because of that issue.
Still curious how keen could break that functionality that bad and do nothing to fix it, especially because it worked already..
Even with workarounds, the drones get stuck and need so much babysitting which make that a bit pointless.
Replies have been locked on this page!