Vatikus

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

I can live with external model not being exact, but HUD is something I will be seeing most of the time and it is a turn off as it is. It feels more like a day version version's which is more narrow than a night one.

HUD shape is wrong and it would been nice that it is corrected before the release...

TV Mav is to be used against big targets (bridges, boats, sam sites, hangars, etc.) and not as plinking single vehicles... it works, of course, but it is not recommended if you need minimum time over target. That is how it would been used in rl. A version has no magnification so if you cannot vis target by looking out of cockpit it wont help you being glued to EP13. Easiest is that you popup, boresight your plane (might need to lower the seat to see aiming dot) with target and switch on EP13. This way you will be the quickest.

I think you are doing nice work, however if maps cannot be calibrated, it is all useless for serious use ...

in this video, you can see the hud flir ... randomization is imo not a way to do it, as we can see how it points to the proper objects (air & ground)...

IronMike & co. thank you for organising these fun events and cheers to all who fly them... I have always fun time flying them.. :) @Schnarre thx for winging up.. it was a blast! :)

http://www.peters-ada.de/standorte.htm maybe you can find a match via this website ...

We are talking about older model of Su25 which does not have HUD. In Su25T I did not experience problems like I do in non T.

I noticed that on random my bombs drop at the same time i press release instead of switching to CCRP. If you drop single bomb it works ok, but soon as you use ripples the CCRP premature (no orange light at all) drop will happen in quite high %. I am wondering if I am missing something or is this a bug.

What kind of bizzare question :) ... A: to have a realistic simulation of the plane and to be able to perform maneuvers using yaw component which are currently impossible to do since rudder is ineffective.

Ok, but not being able to deflect full rudder above take off rotation speed is odd. yes?

I am sitting out until they finish M2K.

... I cannot get full deflection past 160km/h. I understand that the forces build up, but 160 is a bit pessimistic. Saying 160km/h to be high speed is .. :music_whistling: On Spit, I can yank full deflection w/o any speed limit.

Yes, cleanup, update... I even deleted textures and run update to make it redownload.. same result :( this my md5 3ac262bf0f114dc32f48616883851c7f *FW-190D9-CPT-TEXTURES.zip