cannot reproduce Attempting to command a ship to attack causes GUI elements to disappear and some additional problems

[meltingSnowdrift]

Everything described here occurred in version 2.7.1.6430. It appears to occur every time I perform this procedure in this version.

 

Steps to reproduce

1. Use the attached mission file. Alternately, make a mission file with a Ticonderoga class cruiser and a tactical commander on the same side as it.
2. Run that mission and take the tactical commander role.
3. Give the ship a single waypoint and a speed so that it moves.
4. Command the ship to fire at a point on land.

Expected behaviour

The ship should fire a single cruise missile at the targeted point while continuing to move. Things such as the user interface should continue to function.

 

Actual behaviour

Upon completing the last step of the procedure above, the following happens.

1. Many GUI elements disappear. This effect continues even after exiting the mission. Buttons that have disappeared appear to still be clickable despite not being visible.
2. The ship slows until it stops.
3. The ship fires a large number of cruise missiles at the targeted point.

Evidence

The very simple mission file required to demonstrate this bug is attached in case what happens depends on the details of the mission file.

This video shows everything described above: 

 

21Y21 ship bug.miz

Edited May 22, 2021 by meltingSnowdrift
clarified title

[NineLine]

Interesting, I will check it out.

[NineLine]

So I tried it out, with you mission and I am unable to reproduce. Perhaps make sure all mods are removed and do a repair?

[meltingSnowdrift]

I did another test after having done those things. Repairing removed a number of CA-related files the installer did not think should be there. Upon starting the mission and entering the tactical commander role again, I did not see the CA control panel upon selecting the ship in the map. This of course made it impossible to conduct the test.

 

Further testing will follow shortly. I intend to delete and reinstall CA.

 

Update after reinstalling CA:

The bug occurs again exactly as described in my original post. What additional evidence should I provide at this point?

Edited May 22, 2021 by meltingSnowdrift
update after reinstalling CA

[meltingSnowdrift]

Attached are several files as additional evidence. These are the DirectX diagnostic text file, a track file, and logs.

ship problem.trk Logs.zip DxDiag.txt

[BIGNEWY]

Hi Snow, 

 

I was not able to reproduce on my machine. 

 

Please try this

 

Make sure windows and your display driver are up to date. 

 

then go to C:\Users\canki\Saved Games\DCS.openbeta

 

rename to C:\Users\canki\Saved Games\DCS.openbetabackup

 

run a slow repair on dcs

 

restart, login and redo your settings and test. 

[meltingSnowdrift]

I have just done those things. The problem still occurs. I did not even change any settings away from the defaults after performing that procedure. What testing should I do and what additional information should I provide at this point?

[Yurgon]

I just ran the mission as described in the first post; everything was fine on my end, all GUI elements stayed in place.

 

Never seen the problem that your video shows. This seems to be a pretty rare occurrence. The good thing is that it's reproducible, so that should make it easier to narrow it down.

[Flappie]

@meltingSnowdriftYou're probably refering to this bug:

 

 

Do you have an AMD GPU?

[meltingSnowdrift]

Yes. I do have an AMD GPU. See the DxDiag.txt file I attached earlier in this thread for details.

 

I hope that, despite the at least partial duplication of another issue, this report at least provides a new, simple, and highly reliable way of reproducing the bug.

 

I continue to be willing to perform new tests as necessary to continue to help understand and fix this issue.

[Flappie]

11 minutes ago, meltingSnowdrift said:

I hope that, despite the at least partial duplication of another issue, this report at least provides a new, simple, and highly reliable way of reproducing the bug.

 

Yes, your track might be useful to reproduce this bug.

 

EDIT:

I've just tried it but I cannot reproduce the issue (I have an NVIDIA GPU):

 

Thanks for the video. It clearly shows the Target icon could be the cause of this bug.

Edited June 28, 2021 by Flappie