Jump to content

Looks like we broke the T-72B3's Fire Control System, in some specific (and possibly rare) situations [FIXED?]


Ssnake
 Share

Go to solution Solved by Volcano,

Recommended Posts

  • Moderators

This thread may not have been entirely warranted, because it seems to happen only in specific situations - so no need for there to be any mass hysteria here.  😉

 

But now that it has been mentioned (vaguely), I will follow up and provide an internal detailed description of the bug (see below), to limit "false positives" of observations of legitimate behavior (the T-72B3 has plenty of real life quirks represented). 


So, to be clear, here is a detailed description of this behavior to look for:

 

"

(In certain, specific situations) when a target is lased, the sight jumps far below the target (1 to 2 target heights) with auto tracking on (and possibly off too). Then when the user tries to bring the sight back onto target by elevating), he cannot. The movements of the gun/sight then becomes exaggerated, like 2 to 3 times the normal speed - and any left/right movement of the input brings about a seemingly opposite movement of the turret, as if it is fighting against the input (like when you have lead being calculated on [a single axis type] stabilized sight and you traverse rapidly from side to side). The AI also cannot aim the gun when this starts to happen; if you jump out  to F8 view (to let the AI shoot the target), you can instead see the gun swinging back and forth left and right, and the AI doesn't shoot. 

 

Also, if you are in the gunner position when this happens, the AI commander seemingly becomes completely inactive - doesn't  put the gun onto target, etc.

 

After going through all this, the user will eventually press P or O key to disable/reset the FCS and auto-tracking. When this happens, it goes away, until the user lases the target again.  So the only way to engage the target when this occurs is through the GAS (the old T-72 sight).

"

 

 If anyone encounters this described behavior then please post a test scenario here.  We have discovered this issue post 4.3 release and are having trouble reliably reproducing it... 😔

 

(The best way to get a test scenario might be to pause the game when you see it, then save in progress, and upload that here with a note on what vehicle on what side its currently being observed).

 

I should stress that there are many unknowns here, whether auto-tracking is actually a cause or not, for one thing, or whether it is a Network Session only bug or not (probably not). 

 

Normally we don't put out unknown information like this, but here we are. So, as I said, the main thing that would help at this point would be a test scenario where someone is able to reproduce the behavior (or possibly a save in progress of a scenario where someone sees it occurring right then, with a mention of what vehicle it is happening on).

 

 

Link to comment
Share on other sites

  • Volcano changed the title to Looks like we broke the T-72B3's Fire Control System, in some specific (and possibly rare) situations
  • Moderators
  • Solution

Looks like we may have fixed this already for the next update. Or at least something very similar. 😅

 

Still, if you observe this and you are able to provide a test scenario (or can do a save in progress scenario of it) then please post here anyway, as it might help us make sure its the same thing.

Link to comment
Share on other sites

  • Volcano changed the title to Looks like we broke the T-72B3's Fire Control System, in some specific (and possibly rare) situations [FIXED?]

Is it working as expected in regards to the difference in slew/track sensitivity compared to day sight?..day sight tracking /slewing is much smoother and controlled where as the TIS is a lot more sensitive. Its hard to manually track in TIS and often causes over compensating as well as getting more pronounced in higher magnifications. Shouldn't they have the same slew rate/sensitivity of inputs ?

Edited by Badger
Link to comment
Share on other sites

  • Moderators

You may be observing what was described above. Hard to say. You would have to observe it after the change to know.

 

But let's say that if you aren't observing the bug above (because the sight would be moving all over the place erratically no matter what FOV you are in); in general - just because you are zoomed in to maximum magnification doesn't mean that the turret and gun of the T-72B3 should be less responsive. The T-72B3's FCS doesn't know any better (as far as we currently know), so what you will get then is like looking through a telescope trying to track a moving object - any input at that level of magnification is going to feel exaggerated. The highest zoom magnification on the T-72B3 is really intended to be used on long range stationary targets, or in conjunction with the auto-tracking feature (that's the main reason the latter function exists IIRC). 

 

But I am also not saying there isn't another issue there either. Just a general description that the higher the magnification, the harder its going to be to move the sight around, and this this might be getting confused with the bug behavior described above.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...