Jump to content

Recommended Posts

Posted

At 53 minutes in after take off (second flight) radar behaviour did not seem normal. All bars listed (1B 2B 4B 6B) could not reset to clear issue. Pressing the OSB key to change bars still cycled scan altitudes on the captains bars (TDC) without Bar indication. Some other radar functions did not seem to work and behaved strangely.

 

Other than the obviously noticeable problem with the bars I could not tell you exactly what the other radar behavioural problems are as I am just getting back into it and not certain with the functionality.

 

 

https://www.dropbox.com/s/xua6dkt3xrne610/Server_1_Operation_Urban_Thunder_V4_1-20200412-190718.trk?dl=0

Posted

So this very well might be my lack of knowledge on doing replays but when I loaded that track it was set to follow the E-3A. Not helpful. There were a LOT of F/A-18s in the list and I didn't see anything that stood out about a human controlling any of them and I was certainly not going to select every single aircraft in the F/A-18 list.

 

That being said what you are describing is basically what I see when the SIL (Silent) option is highlighted on the FCR screen which means your FCR is not transmitting at all. Whether directly selected or via some emissions control option. You will see the top and bottom numbers of the captains bars change without seeing the relevant change to the antenna position itself until you come out of silent mode.

 

Now I don't know if the captains bars numbers should change or not when in silent but that is what it does. If that is how it should work and if you were in silent it is neither a bug nor a broken radar but operator error.

Posted

Sorry OB1, I tried the replay three times but it only ever shows you taxi out of the HAS and then the plane just sits there on the deck not moving, so I could not get far enough to see what happened to your radar.

  • ED Team
Posted

Unfortunately the track replay does not show the issue, sometimes tracks can be problematic.

 

I will mark the thread can not reproduce for now, but will keep an eye out for this issue, if you do by chance see it again please attach the track.

 

Thanks

smallCATPILOT.PNG.04bbece1b27ff1b2c193b174ec410fc0.PNG

Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status

Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, PIMAX Crystal

Posted (edited)

I was able to replay the track OK and observe the problem. Maybe, it is a regional problem with tracks, as we are both in Australia. Or a windows 10 version problem with tracks...

 

 

Anyhoo....

 

I see what the problem is and I am able to repeat it with ease...

 

 

1:- Switch A/A RADAR to a DDI. ( I used the Right).

2:- Set the A/A RADAR DDI to SOI.

3:- Move the TDC up to the BAR Scan selection (Top Left area) , until you have all the options displayed (1B 2B 4B 6B).

4:- Move the TDC quickly back down from the BAR Scan selection, with all options still displayed. I find moving the TDC away in a Right Diagonal direction the easiest way to cause the problem, but it seems repeatable in any direction after a couple of attempts.

5:- All the BAR scan options will remain displayed in the DDI. (1B 2B 4B 6B).

6:- Pressing the PB key on the DDI for the BAR Scan options has no effect to the problem. Changing Radar Modes has no effect to the problem.

7:- To clear, move the TDC over any of the DDI TDC control area again. i.e Over the BAR scan selection area, Range selection area, etc..

8:- The Bar Scan Options will contract back to current selection. At which point the Bar Scan PB will work again.

F18.thumb.jpg.b67689841c10d16c8db2e2f29cddc115.jpg

Edited by gonk

Intel Intel Core i7-8086K

32 Gig RAM

1 Tb Nvme SSD

EVGA 1080Ti

Win 10 64 Pro

LG 34UM95 34 inch Monitor

Track IR 5

Oculus Rift

HOTAS Warthog...mod'd TDC

SIMPEDS Pedals

Posted
I was able to replay the track OK and observe the problem. Maybe, it is a regional problem with tracks, as we are both in Australia. Or a windows 10 version problem with tracks...

 

 

Anyhoo....

 

I see what the problem is and I am able to repeat it with ease...

 

 

1:- Switch A/A RADAR to a DDI. ( I used the Right).

2:- Set the A/A RADAR DDI to SOI.

3:- Move the TDC up to the BAR Scan selection (Top Left area) , until you have all the options displayed (1B 2B 4B 6B).

4:- Move the TDC quickly back down from the BAR Scan selection, with all options still displayed. I find moving the TDC away in a Right Diagonal direction the easiest way to cause the problem, but it seems repeatable in any direction after a couple of attempts.

5:- All the BAR scan options will remain displayed in the DDI. (1B 2B 4B 6B).

6:- Pressing the PB key on the DDI for the BAR Scan options has no effect to the problem. Changing Radar Modes has no effect to the problem.

7:- To clear, move the TDC over any of the DDI TDC control area again. i.e Over the BAR scan selection area, Range selection area, etc..

8:- The Bar Scan Options will contract back to current selection. At which point the Bar Scan PB will work again.

 

Exactly as gonk said. easily reproduced. Just move the TDC to the edge of the MFD under the OSB key responsible for changing bar scan, touch the edge and move it back (as if changing range).

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...