Rongor

Engine crank switch has left and right but not off. Off is needed in case you do the cold start by the book. So engine crank switch off position please.

yeah I did that so you guys could see I am actually attempting to move stuff Using my hardware lever on my Virpil throttle unit would have needed a second screen to document my inputs

So keeping my lever in that 68° and then waiting for the light to go out and only then pull the lever back beyond? Was a bit difficult when using a hardware lever as of course I slid is all the way back and then forth and back did never unlock the required HZ TAIL authorization. Never suspected this being a bug though, only problematic, depending on the way you actuate the axis.

Why is this so hard? Occasionally it works after some sliding up and down, often getting stuck with a jittering handle... 20230309_163436.mp4

Both the online and the installed manual are from March 2019. Would somebody be so kind and eventually update these? It's a bit embarrassing to even read in the manual that some aspects will receive more detailed explanation in the future yet apparently the team forgot about it since 4 years. Especially since the training missions like the startup procedures contain a whole ballet for the player to perform across dozens of systems and tests and there is no real sufficient documentation on what all this actually is supposed to mean. For people who only wanna autostart and get into the air quickly to blow up some stuff War thunder style this may be totally perfect. Yet for those customers around who take the "study" part in "study sim" serious, this is a real let down situation.

Is it accurate that the pilot has no way to override this forced slaving to the impact point?

I am sorry, it was my fault, for some reason the unit was set to hidden on the map in the mission editor. Thanks for replying though @razo+r

Disregard.

so like this? (actually worked, but no idea if its due notching) 20230223_152651.mp4

Good point will check on the history setting then. Got it as far as 81° meanwhile...

So there is no chance I can keep my lock on him I guess. I should turn inverted before pitching down I guess?

So far the only method seems to stay out of firing range (obviously). Yet what would you recommend to do when the missile is coming for you? Neither maneuvering nor CM did yield any success for me so far...

Having launched an AMRAAM on a bugged target in CRM, so in SAM mode, I turned away. Eventually the relative angle next to the target locator line in the HUD showed 79° with the radar still following the target. 1. I am a bit surprised to see this, as I expected the radar to only have a maximum scan zone of 60° off the radar boresight. So what is the actual maximum angle off the gun cross, the radar can still track targets? 2. Also considering the enemy being almost at my 3 o'clock in the horizontal plane, how can the smaller attack steering circle not be completely outside the larger ASE circle yet?

Thanks guys. Also thanks for the video link. So the manual is outdated on this and the little circle has switched to a totally different meaning. Gonna learn these M/A/F meanings now to make use of them

I have this HUD while going head on towards a Fulcrum which already launched at me and I am close to launching an AMRAAM myself. I am a bit confused about two things here: 1. What does this "12M" below the closing speed tell me? Couldn't find anything about it in the manual 2. This little circle symbol below the R aero triangle is very likely meant to be the Radar activation range (as the only little circle along the DLZ is representing exactly this as per the manual). So since the range to target marker has already wandered below it, wouldn't this mean I am already within radar activation range? Contradicting to this, the countdown to activation is still showing A15 (instead of a T-value), so something is wrong I guess...

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

Oh, sad to learn this inconvenience is actually how it is in realworld. So no bug, thank you for clearing this up.

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

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?

I am not sure how to interpret this. - is what I experienced and reported accurate and correct? - is it accurate and correct due to the refinements made and only are not reflected in the manual? - is what I reported indeed incorrect and inaccurate, yet refinements have already been made and are awaiting to be patched in to match the manual again?

As demonstrated by Wags in his Mark Points demonstration video (linked at the bottom), you should be able to adjust the dimension of the selected submode (EXP, DBS1, DBS2) by selecting the range with OSB 19 and OSB 20. Instead my track will show that pressing OSB 19 and OSB 20 actually resets the submode, returning to NORM, with the new range setting, often having the crosshair then being outside the displayed range. You then again have to cycle to the desired submode by pressing OSB 3, which leads back to the actual crosshair location but the whole process is an inconvenient step which also isn't appearing in Wags' video. Also while Wags can then change the scan azimuth with OSB 18 to enjoy faster image refreshing in the closer zoom steps of these submodes, this is currently not possible, as pressing OSB 18 is ignored and hence the submodes are stuck with a 60° azimuth scan and A3 and A1 are unavailable, leading to pointless long scan times. The only way to enjoy A3 or A1 for faster refreshing currently is to select one of these while still in NORM and then enter the submodes. GM_submodes.trk

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.

So like freezing the image and then flying into it? Interesting. Never considered this to be a thing

snowplow.trk The track will show 1. while in snowplow, TDC inputs are still accepted and moving the non-snowplow crosshair in the background 2. when reducing the beam azimuth, any crosshair location off the centerline will have the radar scan zone not being centered when activating snowplow 3. Using the TDC while in snowplow with reduced beam azimuth will move the radar scan zone off center and also have the crosshair begin at a different location when exiting snowplow.

How could my own aircraft possibly be inside the radar image? Wasn't aware we have 360° radar coverage...