jaguara5

In this HAF video (watch at 1:03 , 2:54) there is an M indication when the target lock is lost and running in memory mode. In game there is no indication (needs to be confirmed by AdA if this is valid for the Mirage 2000C's S5 also). In any case, an M indication appears on the radar screen of the french version, see attached image form razbam's first simulator trip (lower left picture). Funcionalty of this indication must be confirmed by AdA (can only speculate that this is the same M as above). Edit- sorry can't upload the picture posted from razbam's simulator session , i have reached the upload limit. If someone can attach the picture or guide me how can i expand the upload limit

It would be nice if you could have an emergency cheklist for some basic aircraft failures (electric, hydraulic, engine, oil etc) that can be triggered with the ME or caused by battle damage. Currently the manual has only checklist for normal procedures + on the left side of the cockpit wall is the placard for the engine restart prodedure. So while we have the funcionality of several switches (as en example pelles, souris, becs) it's not clearly stated when to operate them. Also, in the chapter of the electrical system it should also be explained wich systems are tied to which buses, without that the deetailed shematic diagrams in the manual are useless.

Hi Snappy! My report was reffered to the manual correction of the double circle indication of both G and D letters According tho the manual (p. 229) : '' 1. MISSILE PYLON SELECTOR. This three position switch is used to control the launch order of the Super 530D missiles. The positions are: ... '' So this switch doesn't affect Mag launch order. (and i really don't know what the launch order logic is). 530D launch order should follow the functionality of the above mentioned switch, that you have already posted

Have already reported this in the thread about the manual https://forums.eagle.ru/showpost.php?p=4290762&postcount=28

Several hud bugs / inaccuracies. 1. When guns are selected the altitude and speed indicators must be in the depressed position (in the middle of the hud), as in MAG mode, and not in up position (watch in the track file how the position of these indicators changes with the weapons change). References: (watch at 20:00 forward - with CAN speed and altitude in depressed position) . Tape from French Air Force (watch the weaponS change at around 1:20 speed and altitued indicators stay at the same position). Tape from HAF 2. MAG dlz scale / range indication. IRL with MAG selected, when the distance of the target drops to 1,9 nm, the indication on the range carret next to the dlz changes from (1.9) nm to meters (to 35 =3500m) and the range caret with the 35 indication moves up (so the scale of the dlz changes to). References (watch at 2:42 - 2:43). Tape from HAF. (2:47 - 2:48 watch the numeric range indication - 34 - and the caret position, which matches perfectly the indications of the previous video) . OFFICIAL VIDEO FROM EC 2/5 (watch 19:33 forward). In game the range indications changes when the distance drops to 0.6 nm (and not at 1,9 nm), the meters indication is 4 digit (=1200) and not 2 digit (35) and the scale of the dlz doesn't change. Watch the track file. 3. With guns selected and a radar lock. when the distance of the target drops EDITED - around 1000 m see also the last post - the dlz dissapears (IRL) and the range is indicated exclussively with counter clockwise moving piper. Already reported in the past (with reference picture, there are dozens of other hud tapes, i can provide additional videos if needed). https://forums.eagle.ru/showpost.php?p=2626854&postcount=24 (watch at 33 : 21 to 24 , there is also a delay in the symbology change). In DCS , the range scale remains always visible. 4. The closure speed indication in the provided track is totally unreliable (negative indication at some point while the targe is coming closer). 5. Gun snake bug. With radar lock sometimes the pipper circle doesn't appear. This was reported a long long time ago. It appears very very rarely, and i thought it was corrected, first time that i'm showing it in a track. Had it occassionaly the last month (during my limited gaming time). Watch the track file, when the distance drops to 0.6 nm and guns are selected, only the snake is visible without the pipper. 6. In the following videos there is a slight delay in the hud symbology change. 2:34 0:57 When a target is locked in magic mode, the inner circle appears first with the small intercept square in the middle, after ~ 0.5 second the second TIR outer circle comes in and onle after that the square starts moving (I think the computer needs some time to calculate the intercept path). In game the symbology changes instantly. 7. When the last MAG missile is fired (so no more active weapons are left onboard), the outer double circle , the TIR indication and the range markers on the DLZ are dissapearing (official 2/5 video). (watch 2:47 - 2:48, the TIR indications is gone with a slight delay, watch also that the firing magic missile is the only one carried form the shooting aircraft as indicitated by no G(auche) or D(roit) indications on the lower part of the HUD). In dcs those indications are still present (it's not showed in the provided track file but you can test it very easily). HUD bug 3..trk

Nice initiative! Do you also have the 530 lock tone?

1. If boresight close combat mode is selected directly after vertical scan mode, the radar cone is positioned incorrectly in a higher posiition. If boresight mode is selected after horizontal scan mode, the cone is alligned correctly with the coresponding hud boresight cross (in the middle of the scan area). Watch the corresponding line in the left side of the radar screen (it's not a graphical error of the radar screen but a functional one). Plz fix this, very old bug that is annoying in dogfights. 2. Autopilot cannot track correclty the altitude in low speeds (it bounces and commands fpm below the asterisk),as can seen in the downwind leg, making it difficult to fly correctly the pattern Attached are 2 track files. Edited the message, boresight is buggy after vertical scan mode not horizontal boresight bug 3..trk autobpilot bug 3..trk

Have you guys flown a bfm fight against a mirage 2000?

Thx! At what speed and altitued should i start turning to downwind?

Does anyone know how IRL the touch and go pattern exactly flown is?

In this video (4:10 forward) we can see the throttle and stick inputs during takeoff sequence. The F-1 requires large aft stick input for take off.

I get this message when i put my pc on sleep and after that i use DCS, or after having used my pc for long hours before (perhaps some program that i have running is interfering with the game?). For me the solution is simple and works 100% - complete pc reboot, nothing else required. But as you have said, you already have done that so i really don't know.

Since i don't have the slighest knowledge, may i ask if the currently displayed HUD and radar screen symbology of the FC3 module is very simplified to the real one or does it come close to that?

Nice home cockpit build (from the son of a former F1CG pilot). Only the module in DCS is missing https://www.modellingnews.gr/el/editorial/%CE%B5%CE%BD%CE%B1-mirage-f1cg-%CE%BE%CE%B1%CE%BD%CE%B1%CE%B6%CE%B5%CE%AF-%CE%BC%CE%B5%CF%84%CE%AC-%CE%B1%CF%80%CF%8C-15-%CF%87%CF%81%CF%8C%CE%BD%CE%B9%CE%B1

Some time ago i was talking with a HAF M2000-5 pilot about the flight characteristics of the aircraft and he praised the carefree handling the delta wing/fbw combination gives. Then he described a fligth behaviour (if i remember correctly where the aircraft changes hard direction from the one side to the other demonstrating it with his hands, have already forgotten the technical name of the aerodynamic rule he mentioned) and said that the mirage can do it without problem and that maneuver have killed some A-7H/E pilots, since the aircraft was prone to depart from it. Does anyone have a clue what this can be? If i wll see him again will ask for sure.

https://theaviationgeekclub.com/libyan-mig-23-pilot-remembers-a-memorable-dogfight-with-u-s-navy-f-14-tomcats/

Not for me

Have that to occassionally. Solution (for me) : complete pc reboot, solves the problem 100%. Try this out.

Thx! Must forgot to replace the material file. Indications are normal!. Thx for your time and effort to update the fix!

For the altitude only the last 2 digits appear on the hud. For speed only Mach is indicated on the left side

There is a problem with the altitude and speed indications

43 inch monitor and problem solved. Best hardware upgrade i've ever made. I'm also on trackir. Besides the reasons stated in the first post, i 'm suffering from very serious motions sickness the few times i 've tried vr.

ok everything works fine.

Just received the rudder pedals. Having watched this video i thought that they would work out of the box with no program installation and callibration needed. Currently the pedals are recognized in windows but they are not working. So if i press a pedal no movement is initiated. On the device i have a blue and a green button . As it is my first vkb product could someone explain what i have to do make them work?

I'm interested also to see some dcs benchmarks for the 10900k. Running currently a 4790k /1070 combination in 4k.cpu usage is about 50%, gpu at 95% so it seems to me (if i'm talking bs correct me) that the gpu is the bottleneck. I" m wondering if i would benefit in that resolution from anew cpu. Gpu upgrade is planned