AI Recorder drifts away from paths, skips waypoints
Investigating
When you Play the recorder on a ship, it often goes completely off the given path, sometimes in the oposite direction, then after a few minutes goes back. When it drifts away, the recorder's terminal says "idle", even though there's AI Behavior ON and Play ON.
The recorder has a beacon provided by other grid.
This makes the recorder completely useless in mining applications, and quite uneffective in other applications.
Files:
AI Rebugger.zip
I have the same bug You can't vote. Please authorize!
Also the recorder tends to skip waypoints a lot, even when there's no obstacles in the way.
Also the recorder tends to skip waypoints a lot, even when there's no obstacles in the way.
I agree that it needs some work.
I agree that it needs some work.
Hello Candy,
Thank you for sharing the world save with us.
We were able to observe the reported issue in the provided world. At the same time, we already have a similar issue reported internally, and we need to determine whether this is the same issue or a different one. To do that, we’ll need a bit more information from your side.
We noticed that the world contains backups indicating that it was previously modded, with around 16 MODs present. Could you please confirm whether the issue originally occurred while those MODs were still active, and the issue continued after the MODs were removed? If the issue initially occurred in a modded world, removing the MODs does not always resolve mod-related issues, as MOD dependencies can remain embedded in the world save and continue to cause unexpected behavior even after the MODs are removed.
To help us confirm this, we kindly ask that you create a new vanilla (unmodded) world, paste the affected grid’s blueprint into it, and then check whether the issue still occurs.
If it does, please share that vanilla world save from a point where the drone is still attached to the main grid, along with the steps we can follow to reproduce the issue from that point.
This information will help us determine whether the issue is caused by MODs or if it matches the issue we already have reported internally or possibly represents a separate issue altogether.
Thank you again for your time and for helping us improve Space Engineers.
Kind Regards,
Keen Software House: QA Department
Hello Candy,
Thank you for sharing the world save with us.
We were able to observe the reported issue in the provided world. At the same time, we already have a similar issue reported internally, and we need to determine whether this is the same issue or a different one. To do that, we’ll need a bit more information from your side.
We noticed that the world contains backups indicating that it was previously modded, with around 16 MODs present. Could you please confirm whether the issue originally occurred while those MODs were still active, and the issue continued after the MODs were removed? If the issue initially occurred in a modded world, removing the MODs does not always resolve mod-related issues, as MOD dependencies can remain embedded in the world save and continue to cause unexpected behavior even after the MODs are removed.
To help us confirm this, we kindly ask that you create a new vanilla (unmodded) world, paste the affected grid’s blueprint into it, and then check whether the issue still occurs.
If it does, please share that vanilla world save from a point where the drone is still attached to the main grid, along with the steps we can follow to reproduce the issue from that point.
This information will help us determine whether the issue is caused by MODs or if it matches the issue we already have reported internally or possibly represents a separate issue altogether.
Thank you again for your time and for helping us improve Space Engineers.
Kind Regards,
Keen Software House: QA Department
Replies have been locked on this page!