jaguara5

For redfor i would prefer the Mig-29A.

if i remember correctly 2.3 . Good thing is that you can change the setting (at least in MP, must be the same in SP) while you are playing so you can find immediate a good compromise. 1.4 is way to low and not realistic either IMO. Something around 2 and little up should work but, that's also a matter of personal taste

The cockpit is dark but not to the point you can't read the dials (at least on a 27' 2560 X 1440 monitor and a 43 inch 4k monitor that i use, can't comment on vr). The labels on the side panels are harder to read. What you can do to increase the clarity. 1. Increase little the gamma settings in the game setup menu.. 2. use the mentioned mod, i have the brightest option selected , and yes, it makes a (not dramatic but noticeable) difference. 3. zoom little in.IRL the panels are not 1,5 m away from the eyepoint, as shown in the above posted screenshoot.

P. 253 , 254 , 255 The vertical scan is activated not only with Magic selected but also with CAN (with the CNM swtich) or witch POL modes selected. Also, MAV overrides default MAG, CAN or POL seeker movement. P. 102. should added that the AoA indication on the hud doesn't appear (as in rl) and can be activated only through the game menu.

In CAN mode the altitude and speed indicatons are moved down as in MAG mode, and don't stay up as in NAV or 530D mode. Can you change that or is it hard coded? At 0:52 pilot selects MAG form 530D and at 1:20 Air Air Gun.

P. 62 the The 31 AoA / 11 g FBW limits for stick mechanical stop position is missing. P. 176 i would add the descritpion of the ownship symbol (on the bottom) with the respective arrow that is proportional to the own speed. P178 i would add the description of the dashed azimuth reference lines In the radar /vtb chapter, i would add that the target intercept line starts blinking as a warning when the target is close to the radar gimbal limits . The exact azimuth value of that would be also nice (perhaps this could be incorporated in the new RDO / DO section). P. 136 , D/RLT , it says for WP01+ ''.Distance to WP (in minutes, seconds)''. Should be in nautical miles, as it's correctly described in the next descr. line. In the HUD chapter , the altitude allert arrow indication is missing. Would add also description of that in p. 91

p. 62 the lately introduced new AoA aural warning logic must be replace the old one (Zeus never mentioned what the new rules are).

P. 248 . According to Zeus, in case of a 530 lock, both G and D letters are circled indicating a succescfull lock of the missile head on the target. Also the picture must be corrected (since there is a lock and only one letter is circled. Should be added that the Flight director ring and the interception flight director also appears on the vtb (last update). On p. 187 the n. 9 current ''lock type designation'' should be corrected together with button 8 of the stick description on p. 35. The button doesn't lock a target but cycles between PIC / PID as the next engaged radar mode with TDC press button. Should be also metioned in the VTB chapter that the indication is always displayed on the vtb and not only after a lock (actually for that reason all the displayed pictures in that chapter must be updated). On the last page, the ρ/θ must be corrected to Polar Rho / Theta and not Tetha as it is now (this is how the greek letter θ is pronounced = θήτα).

So i have found the cockpit file. Is it possible to move freely in all directions? I can zoom in / out with right mouse click + mouse forward /back or with left mouse click rotate the view but can't move forward and left /right (have found that move left / right / up down is possible with camera left / right but again i can't move forward). Is it possible to do that?

Not familiar at all with the program so perhaps the question is very stuipid. Is it possible to see the cockpit with the program? I want to see as an example the shape of the throttle lever of the Mirage 2000.

i think in the manual should be written more clearly, that MAV search selected through PCA has priority over MAV search selected through Mag CNM, despite which mode is selected first.

I thought that was intented as to mee the symbology makes sense. vertical narrow search (common mode) is indicated by the brackets only and the horizontal arrow on the left side is there indicating the primary Mav mode (the mode you will swith to if you press mag unlock). Verical arrow is preserved for the Vertical wide scan , otherwise it could lead to confusion. Let's see what Zeus have to say.

Until now it's not possible. Magic MAV, which gives you magic and gun symbology will be available with the next update https://forums.eagle.ru/showpost.php?p=4257564&postcount=16

Thanks Zeus! Will we get the 530D lock tone, which was mentioned a while ago here in the forums? And how does this interract with the magic tone, if MAG MAV is selected in 530 mode and both missiles are simultaneously locked, have both missiles the same tone? Have already reed from you about both G and D indications are circled to indicate a succsesfull 530 lock.

Here is the weird vertical scan function (track file over normandy again). Can't lock initially a target that is about 5 degr. above me, after lock and as soon as i deselect target / revert to normal scan and dive, i can lock at much higher angles. CCM bug.rar

Hi Zeus! This bug isn't random , everytime when there is a magic triangle (via magic slave or by positioning the boresight cross over a target), selecting guns will cause the TD square to dissapear. While staying in guns, deselecting the target and reverting to scan, the TD doesn't appear if the target is locked again . Attached is a track fiile (over Normandy hope you can see it). If magic isn't slaved and guns selected, the target box remains visible TD bug.rar

Besides what the other guys have said above regarding the TD dissapearing bug (which is a core bug that exists already since 2019 and that on a module that is realeased few years ago, see also the official bug tracker on razbam's site for that) for your information the HUD needs a lot of work to replicate the real one 100%. Some missing / false indication are more ''cosmetic'' some others ''functional''. Example - magic indication (seeker circle / magic triangle) while on CCLT -in CAN mode the speed / altitude indications move down as in MAG mode - in CAN mode the DLZ isn't displayed on the right side when the pipper circle moves counter clockwise (1200 m at the 12 o' clock postion). - altitude alert arrow should be blinking and not be steady. - the -2,5 degr. lines arent' displayed for optimum landing angle (when the glideslope value is entered in the PCN). etc etc

And correct the vertical scan CCM . Currently it's something like + 5 - 5 degr that's limiting drastically the magic employment So we can at least practice effectively 1 VS 1 .

Razbam could you please fix the HUD TD box dissapearing bug in the next update?

Adjusting a new default position by moving the view little back (Righ Shift + Right Ctrl + /) and saving it (Right Shift + Right Ctrl + 0 or . if i remember correclty) doesn't solve the problem? i remember that in the previous version i had my own adjusted default view position

+ there is some missing functionality. radar memory mode, magic symbology while in cclt, 530 lock tone etc.Also, haven't seen so far anything from the respective simulator photo that razbam posted some time ago.

That's exactly what i personally want to avoid

Is a ''pilot without hands'' option considered, as shown in the photo, so we can operate the side panels while still having the body / legs? Or,, even better, is an animation possible where the respective hand will be moved back , or even act as a cersor, when the mouse is positioned over a side panel?

This is a quick scissor turns test. With 100 % internal fuel + an (empty) external centerline tank starting with 160 kts - 6.000 ft, i can barely drop the speed below 160. Speed varies between ~155 - 170 kts mirage 2000 low speed test.trk

Aboout the slow speed handling. Was reading an interesting article describing in deetail a backseat flight in a FAF Mirage 2000-5 with Dassault test pilot Eric Gerard. They took off with full internal fuel + i centerline tank (by the way bingo value was set to 800). After take off , climbing at 35K and completing a first engagement (so some fuel was already burnt) they descented ''at low altitude'' flying with 160 kts, 90 degr bank for a 2,5 g turn 28 AoA. Then they reversed to the left and again to the right performing scissor turns. During these turns the speed varied between 160 - 120 kts