Rongor Posted February 21, 2023 Posted February 21, 2023 (edited) I am flying with a heading of 139°. The radar crosshair in the GM radar format page is indicating the SPI. Radar range is 20 and the crosshair is dead ahead. I would expect the B/R showing like 139/16, instead it shows 074/77. It's clearly not to my left at 074° and also not 77 NM distant. Also the time to go doesn't show anything. What is going on? Edited February 21, 2023 by Rongor 1
Deano87 Posted February 21, 2023 Posted February 21, 2023 (edited) I think by default that's in ref to Bullseye not from your aircraft. Looks like the manual is out of date. Edited February 21, 2023 by Deano87 Proud owner of: PointCTRL VR : Finger Trackers for VR -- Real Simulator : FSSB R3L Force Sensing Stick. -- Deltasim : Force Sensor WH Slew Upgrade -- Mach3Ti Ring : Real Flown Mach 3 SR-71 Titanium, made into an amazing ring. My Fathers Aviation Memoirs: 50 Years of Flying Fun - From Hunter to Spitfire and back again.
Rongor Posted February 22, 2023 Author Posted February 22, 2023 (edited) Ok let's assume it's the bullseye or maybe the current steerpoint, By testing I can confirm its showing bearing and range from to the current steerpoint to the radar crosshair. This is contradictory to the manual and also I would of course prefer to know bearing and range to the crosshair from my ownship location. Also I can't find any way to have the time to go indicate anything but zeros. Edited February 22, 2023 by Rongor
ED Team Raptor9 Posted February 22, 2023 ED Team Posted February 22, 2023 The manual is still undergoing revision. The FCR chapter hasn't received the required updates yet. Afterburners are for wussies...hang around the battlefield and dodge tracers like a man. DCS Rotor-Head
Rongor Posted February 22, 2023 Author Posted February 22, 2023 (edited) Does this mean the manual in its current state is incorrect on this and what I described is in fact the way it should be? If yes, does this include the non-functional time to go data field in the bottom right of the FCR format page? Edited February 22, 2023 by Rongor
Rongor Posted February 22, 2023 Author Posted February 22, 2023 (edited) The B/R data field in the bottom left of the FCR format page isn't showing the bearing/range from ownship to the radar crosshair location. Instead it shows bearing/range from the current steerpoint to the coordinates of the radar crosshair. Only range data to the radar crosshair location is shown corrently in the HUD. Also the "Time to go" is shown in the HUD correctly, while it is always zero in the FCR format page bottom right time to go data field. The bearing from ownship to the radar crosshair is unavailable. FCR_no_br.trk Edited February 22, 2023 by Rongor 1
ED Team Raptor9 Posted February 22, 2023 ED Team Posted February 22, 2023 1 hour ago, Rongor said: Does this mean the manual in its current state is incorrect on this and what I described is in fact the way it should be? It means the manual is undergoing revision, to include the FCR chapter. 1 Afterburners are for wussies...hang around the battlefield and dodge tracers like a man. DCS Rotor-Head
ED Team Solution Raptor9 Posted February 22, 2023 ED Team Solution Posted February 22, 2023 To follow up on this. The issue with the Time-To-Go has been reported. The "061 28" data field on the FCR is correct-as-is, in that it reports the bearing range from the steerpoint to the FCR cursor if Bullseye isn't enabled, or bearing and range from Bullseye to the FCR cursor if Bullseye is enabled. This is the same behavior on the HSD and the FCR when in an air-to-air mode. You will however get a bearing/range displayed on the MFD from your ownship to the FCR cursor if you enter Freeze mode, either manually or by entering Fixed Target Track. 1 Afterburners are for wussies...hang around the battlefield and dodge tracers like a man. DCS Rotor-Head
Rongor Posted February 23, 2023 Author Posted February 23, 2023 (edited) Yes, I tried the bullseye thing and it is replacing this info with accurate bullseye information. Thank you for clearing this up, so it is only an outdated manual thing but working correctly. To the Time-to-go issue, I can add that I even had a time countdown displayed in one occasion and it seemed to be inconsistently connected to whether I had weapons loaded or not. Yet the timer clearly didn't calculate anything weapon-related (like impact countdown for a dropped weapon) and was in fact only affected by my flight path. Thank you Edited February 23, 2023 by Rongor
Recommended Posts