Vatikus

I have made a track... I did sequences of 2 speeds... the one where FBW introduces yaw by switching from ailerons to pitch forward, and at speed (400->) where this does not happen. I suggest that you should not just watch the track, but try it yourself as well. For me this shows some problem in control law in our implementation, is this true to life or not, I have nothing to back it up... Razbam or anyone with real documentation should ... m2k-roll.trk

I will record it tomorrow... The thing is that you are under control. No asymmetric load. There is no other pilot input except aileron, speed above 250kts and below 400, 7-8aoa... center stick at this condition, aileron in, AB power... and aoa will rise with each 360.. I have managed do get it near 50aoa, center stick, and aoa drops, and you are OK again.

M2k is not f18. But what is more, have you actually tried replicating what I am pointing out?

With 1.5.8 I have noticed that if I have around 7aoa level and I start successive aileron rolls, the aoa will keep rising as you tumble more and more... One would expect that FBW will try to keep yaw component down

The funny thing is, DCS by itself does not mean that FM is great... it is up to developer's competence. Remember Hawk? So getting all wet because of an aerobatic plane in the DCS is naive. M3 cannot even finish Mig21 FM, yet you are so sure this will be the best ever aerobatic plane? I hope you are right ;)

nvm

"On 31 August 1977, "Ye-266M" again flown by Fedotov, set the recognized absolute altitude record for a jet aircraft under its own power. He reached 37,650 metres (123,520 ft) at Podmoskovnoye, USSR in zoom climb (the absolute altitude record is different from the record for sustained altitude in horizontal flight). The aircraft was actually a MiG-25RB re-engined with the powerful R15BF2-300. It had earlier been part of the program to improve the aircraft's top speed that resulted in the MiG-25M prototype" :o

https://en.wikipedia.org/wiki/1977_in_aviation :juggle:

Which means that the box from yesterday is an aerobatic box: Hmmm

https://forums.eagle.ru/showpost.php?p=3314734&postcount=10688 by that post, it seems ED will do 23/27 sometime in future...

If I follow your line... Piper Super Cub :D ... has super... 2. hint had pipper.. and now cube :D

new hint: http://leatherneck-sim.com/guess-our-new-aircraft-hint-no-3/

maybe a suggestion to add [confirmed], etc. to the title, so we know what's been accepted & worked on ... or some sticky topic with a list of links to posts

CA module is way too simplistic to be of any indication of realism. If you are interested in SAMs, I would recommend free SAM Simulator: https://sites.google.com/site/samsimulator1972/home

Most ground based radars cannot mechanically or electronically scan 90 upwards. It is just how such systems are designed. In real life air defense is multi layered which means SAM units mutually support each other's weak spots. I have attached a generic SAM envelope. You can notice the V shape which dictates min range because of how the radar system is designed.

I do not think that's how it is made... it is waaaay more simple. The missile and radar tell RWR to and how to activate and if that happens in valid RWR scan volume, you get displayed the info.

read the patent: https://forums.eagle.ru/showpost.php?p=3256538&postcount=1

radar B-scope mode incorrect projection radar scan volume indication bugs after losing lock CCRP related bugs (INS, ...)

EP13 displays TV maverick sensor picture. It works by locking on contrast and not IR heat. So it's proper to say BW or WB. In one mode you lock dark target vs. light background, in other is inverse.

Filters?

You need to know that the error is indicated by number which represents km! So 0 means that error can be up to 999m. The proper way to set up the attack is that you set up an IP waypoint and do a visual nav fix on it as you overfly it. This way you will minimize the error for the BK90 deployment. However that being said, I do have feeling that nav drift is a bit high for the distances I fly. However I have no real world performance numbers to relate to it.

I did more testing... it seems flight time starts not at mission start but spawn time. And even if two clients then try to set same takeoff time after spawning (not using editor set one), it is impossible to sync clocks. If you enter popup waypoint, target waypoint display resets to 051000 (mach number). Is this intended?

I believe that there is a bug with TOT...

I do not think it is possible in DCS to make AI toss.

Also I would like to add that Timetable deviation does not work correctly either. Take off time countdown works, however then it all goes south... instead of "empty"/-, 0/9 is shown. Also after first waypoint is reached, time deviation shows time to target? (i've included a mission in which I made a test) ja37test-tot.miz