Vibora

Hi, this depends on ED. You should report it on a general DCS bug forum. Thanks for your feedback anyway.

Thank you for your report. We'll take a look at it.

Could be. We'll have to investigate it.

No problem. Thank you for your support.

Hi. Please provide a short trk that works and shows the bug right away, in single player and in Caucasus map. Tell us the version you are using. You may look at it in autoupdate.cfg located in main DCS directory. In fact, you should use latest OB version which is 2.9.0.47168. You may take a look at ED's guide on how to report a bug: FYI, I can't open your trk either. Thank you.

It will be fixed in next main update, not in a hotfix like the one you got yesterday.

Our simulation was developed from real Mirage F1 engineering data, and we have constant feedback provided by SME, real F1 pilots. We keep working on improving the model based on all this. This said, it can happen that data is misunderstood, that some data is missing or unreliable (let’s say for example data at extreme AoA, etc), or that there are bugs in our code that make the simulated airplane behave different from the real one. We are currently working on a significant FM update focused on roll behaviours that will improve lateral stability, as well as other aspects of the flight characteristics.. We appreciate feedback when it is based on evidence, not on subjective opinions and, mainly, when it is transmitted in a polite manner.

New thread if it's another issue, please. Thanks!

We are working on it. Txs!

Already reported.

Are you sure you don't have any FFB device connected?

We hope to have it ready for next patch.

Thank you for your report. It will be fixed in next patch or even in next hotfix probably.

This is known and will be fixed for next patch.

Thank you for your report. We'll fix it.

Yes, the lack of the smaller pattern is a known issue, it is still pending. Now BE is taking a lot of effort as we are close to its release.

Thank you guys for your compliments!

Thank you travissgrey!

Thanks for reporting, we'll add it.

It is named "Cannon 300-600m and missile lock/unlock button" in Mirage F1 controls binding. We have explained it in our changelogs as we implemented it after F1 inital release. We'll eventually add an explanation in our Flight Manual. This is en extract of the said changelog: Sidewinder missile will not perform SEAM (scan pattern) anymore as this mode was not implemented in the real F1. 'Cannon 600/Identification P' throttle button will now uncage Sidewinder missiles (except AIM-9B). If no target was detected at this moment, the seeker head will drift randomly following the background IR heat. The seeker will return to the boresight once the 'Cannon 600/Identification P' button is released. I.e. if a target is tracked, the button must be held pressed to keep the seeker on the target. AIM-9JULI launch delay was reduced to 0.4 seconds (AIM-9B/P/J still have 0.8 seconds). Magic 1 and 2 scan now is a 5 degrees wide rectangular pattern. Fixed Magic missile scan pattern. Sometimes the scan pattern size was excessively increased. Updated Magic missiles instantaneous seeker FOV. It is now 3.4 degrees wide. The two first points is probably what you are looking for. Replace the naming 'Cannon 600/Identification P' for 'Cannon 300-600m and missile lock/unlock button'.

Hi Black. You have to do it on ground with engine off, or set it in the Mission Editor.

Thank you Ian. We keep working and it won't take long until you can enjoy the BE version.

Just set the throttle to idle (I key), between 300 and 600 RPM ideally. Do not advance it above idle as a normal praxis.

The radar is work in progress.

Yes, we'll add more axis key bindings. Please, take into account that we are working step by step to improve the module, and developing the announced Mirage F1 versions.