Submit Feedback

Assault turret stops working after firing with manual control

Jiangontrack shared this bug ago

Need More Information

I have encountered a bug whilst playing pvp with some of my friends, my assualt turrets would stop working after I take manual control and fire a shot.

Here are some steps to recreate the bug:

1. Spawn in an enemy grid. (make sure to decrease the range of the enemy turrets to under 600m to make later steps easier)

2. Spawn in a small grid vehical with an assualt turret, make sure that the vehical is spawned outside your own turret's ai targeting range

3. Create a hotkey action to manually control the assualt turret

4. Enter the vehical and move close enough for your assualt turret to automatically aim and fire at the enemy grid

5. Take manual control and fire a shot, you are free to aim anywhere

At this point, the assualt turret should stop targeting the enemy and the bug should be recreated

The only fix I found was by using the "Fire once" option, which seems to reset the turret and allow it to function normally. Additionally, I found that the assualt turret is the only turret affected by this bug

Files:

I have the same bug

Replies (1)

Keen SWH QA Agent 2 ●

Hello engineer,

Thank you for reaching out to us on the forum and for sharing the steps to reproduce the issue.

Unfortunately, we were unable to reproduce the issue on our side and the assault turret correctly re-aimed at the enemy grid after exiting manual control.

Could you please provide a bit more information to help us investigate further?

Does the issue occur only once, perhaps before restarting or rejoining a PvP session, or can it be consistently reproduced by following the same steps?

Is the issue specific to the vehicle/grid shown in your video, or does it also happen with other or newly created grids?

Does it occur in a specific PvP (or modded) world only, or can it be seen in other/newly created vanilla (unmodded) PvP sessions as well?

If the issue happens across multiple grids and in freshly/vanilla created worlds, we kindly ask you to send us a new save of the vanilla world where you've experienced the issue, along with the log files from the time the issue occurred. This will help us reproduce and investigate it more on our end.

You can access your single player world & Lobby (if you are the host) save files by typing %appdata% into your Windows search bar and you will be redirected to the hidden Roaming folder. After that just follow: \Roaming\SpaceEngineers\Saves. There should be a folder with your SteamID and your saves. The Dedicated Server save files can be found in the AppData\Roaming\SpaceEngineersDedicated\Saves folder.
Please zip the file and attach it here. If you are having difficulty attaching save files, you can optionally use Google Drive. When sharing a google drive link please make sure it is set to be downloadable by anyone with the link.
You can access your log files by typing %appdata% into your Windows search bar and you will be redirected to the hidden Roaming folder. After that just follow: \Roaming\SpaceEngineers. The Dedicated Server log files can be found in the AppData\Roaming\SpaceEngineersDedicated folder.

Kind regards,

Keen Software House: QA Department

Hello engineer,

Thank you for reaching out to us on the forum and for sharing the steps to reproduce the issue.

Unfortunately, we were unable to reproduce the issue on our side and the assault turret correctly re-aimed at the enemy grid after exiting manual control.

Could you please provide a bit more information to help us investigate further?

Does the issue occur only once, perhaps before restarting or rejoining a PvP session, or can it be consistently reproduced by following the same steps?

Is the issue specific to the vehicle/grid shown in your video, or does it also happen with other or newly created grids?

Does it occur in a specific PvP (or modded) world only, or can it be seen in other/newly created vanilla (unmodded) PvP sessions as well?

You can access your single player world & Lobby (if you are the host) save files by typing %appdata% into your Windows search bar and you will be redirected to the hidden Roaming folder. After that just follow: \Roaming\SpaceEngineers\Saves. There should be a folder with your SteamID and your saves. The Dedicated Server save files can be found in the AppData\Roaming\SpaceEngineersDedicated\Saves folder.
Please zip the file and attach it here. If you are having difficulty attaching save files, you can optionally use Google Drive. When sharing a google drive link please make sure it is set to be downloadable by anyone with the link.
You can access your log files by typing %appdata% into your Windows search bar and you will be redirected to the hidden Roaming folder. After that just follow: \Roaming\SpaceEngineers. The Dedicated Server log files can be found in the AppData\Roaming\SpaceEngineersDedicated folder.

Kind regards,

Keen Software House: QA Department

Reply URL

Jiangontrack ●

I tested this bug with a brand new vanilla creative world and immediately found the bug again, so I dont think it is exclusive to servers. I attached a video to show my process in finding the bug from a brand new world.

In the video you can see that the small grid I used was different from the vehical showcased in the first video, so I dont think the bug is exclusive to that particular vehical (the one in the first video named "IFV"). You can also see that the world is not modded, I also left all the settings on default (I think).

Unfortunately I do not have the logs of the server as it was just a multiplayer world I created on my computer which my friends joined (Not a dedicated server).

I have attached the exact world that is showcased in the video called "bugworld".

Please reach out if you need more info, I would love to help any way possible.

Files:

URL