[WARFARE 2 BUG] Custom Turret Block
Alright, here's what I've got
I have 3 custom turrets that were pasted onto a ship.
At first when pasting, each had its systems named the same as the others. Rotors were named the same, and the hinges that I was using to move the cannons up and down were named the same. Mentioning this because I don't know if it made any difference.
All three custom turret control blocks were placed onto the turrets themselves as part of their sub-grid above the rotors that connected them to the main ship.
I locked onto a target, and let my guns fire, but when they did so, only a single turret moved, and it kept moving in a circle past the target, and did not fire.
I tried to troubleshoot the problem and found that I had locked the target and then selected all 3 custom turret blocks at the same time through the K menu, and told them to copy the target that I had locked onto.
Here's the bug:
When I selected all 3 custom turret blocks at the same time, it automatically assigned the camera, azimuth, and vertical aim control blocks to the blocks being used in the first turret that I pasted onto the grid. I did not touch any drop down menus when this assignment occurred, and it was not done by user input.
I changed the block names to be more unique to see if that would help, and it did not help.
I set the turrets azimuth and vertical control back to where I wanted it, and then tried again by selecting all three custom turret blocks at once, and it changed it back to the first turret again.
I set the turrets back to how I wanted them again, and then set the turrets to copy target by hotkeys in the ship's control G menu from a control seat.
This caused no problems.
In summary: the bug is that if you select all three custom turret control blocks in the K Menu for three different turrets that have been pasted onto a grid, the settings for all three custom turret control blocks will be set to control the camera, azimuth, and vertical control for the first turret.
i've found a way to easily replicate this.
step 1: setup multiple turrets+controllers in a grid
step 2: copy and paste the grid OR group all custom controllers in a single group, then turn them off and on
step 3: check the turret azimuth/elevation
doing this seems to copy the first controller's(first placed) az/el settings.
the re-setting of azimuth and elevation seems to happen during initialization
video
https://streamable.com/srgioy
i've found a way to easily replicate this.
step 1: setup multiple turrets+controllers in a grid
step 2: copy and paste the grid OR group all custom controllers in a single group, then turn them off and on
step 3: check the turret azimuth/elevation
doing this seems to copy the first controller's(first placed) az/el settings.
the re-setting of azimuth and elevation seems to happen during initialization
video
https://streamable.com/srgioy
After some more experimentation, I've realized that the bug happens when selecting multiple custom turret control blocks. That's the trigger for this bug.
After some more experimentation, I've realized that the bug happens when selecting multiple custom turret control blocks. That's the trigger for this bug.
Hello, Engineers!
Thank you so much for all your information and I'm sorry you're experiencing this. I have successfully reproduced the issue and reported it internally.
Kind Regards
Laura, QA Department
Hello, Engineers!
Thank you so much for all your information and I'm sorry you're experiencing this. I have successfully reproduced the issue and reported it internally.
Kind Regards
Laura, QA Department
It appears that overwriting properties is not limited to Custom turret blocks. Exhaust pipes for example, also change exhaust effect to the same as last selected pipe. It would be wise to see if other blocks that have list selections are affected.
It appears that overwriting properties is not limited to Custom turret blocks. Exhaust pipes for example, also change exhaust effect to the same as last selected pipe. It would be wise to see if other blocks that have list selections are affected.
Hello, Engineers!
The fix for this is in v201
Thank you.
Kind Regards,
Keen Software House: QA Department
Hello, Engineers!
The fix for this is in v201
Thank you.
Kind Regards,
Keen Software House: QA Department
Replies have been locked on this page!