Vatikus

Value is 25, this is the physical limit of flaps deflection. What you see there is the law function.

I made further testing and went so far to create my own vjoy ffb device. The result is that I can confirm that DCS uses curves and deadzone incorrectly if trimmer is simulated. Since trim effect is setting logical offset from the physical center, DCS does not treat new trim position as physical center and this results in making a mess for the end user. DCS most likely uses directinput API for setting curves and deadzone, but these two functions cannot be used if one wants a correct behaviour. Thus to correct this, ED needs to implement own logical deadzone and curves which move with trim position. It can be done. I've done it over the weekend. Since this problem effects all FBB users and that % of users is not small, it would be fair to push up fixing this bug.

EOS has 4x6 because its scan raster has vertical as primary axis, while radar it is horizontal and thus 8x4. 29 EOS does have wide and narrow search modes in real life, there is also possible to set gain of the IR sensor.

Yes, however in DCS it is wrongly scaled! Romb should not leave main HUD square... Only when circle and romb are aligned you should see exact position.

both should spin in the same direction..

I can confirm. I have this as well, so it is not just your setup Moltar... I use single 32" monitor. I suspect that the answer is close to what rrohde had mentioned - the way DCS renders the scene.

=37.Sqn= Vati - mig21

=37. Sqn= Vati - mig15

Chizh explained several times that there are no plans to have more functionality/animations in the cockpit as they currently are... only possible upgrade from what we currently have is if there is decided that we get a FF module (which we wont for a time to come) :/

I've made further testing... both deadzone setting and curve setting does NOT move with trimmer! Any reply from ED regarding this issue is warmly welcome...

could this bug be one of the possible problems regarding 29 pitch sensitivity? https://forums.eagle.ru/showthread.php?t=222759

Unfortunately no... there is no indication simulated in DCS apart from bombs and missiles when it goes for HUD (look at the pylon number). Gun none. In real jet it can be observed also by the switch position.

Exactly. As missile heads will not see eachother as they are launched almost at same instant. This was done to avoid issue of head locking onto the engine which will happen if you launch in series if not following the section you also quoted. As for your r27,r73,r60 example... you cannot select r73 if r27 is present and radar is also used. At least not on 9.12. 9.13 documentation I have does not give any r60 use no more as r73 replaces it so this problem is not present. DCS uses fantasy weapon selection and mixing, so it is not a problem for us either :D

Miscommunication 4tw .. No worries... ;) The way I see our conversation is that we are talking about 2 different things when it comes to "salvo"... one is using single(1) press to launch 2 missiles - timings are sub seconds, one is using 2 trigger presses to launch 2 missiles - timings (multiple seconds) and the reason are what you wrote.

Maybe I am not clear enough... we are talking here about DCS' SALVO firing mode! Not firing singles one by one in short interval! So as you have manual, take a look at the bottom, page 01.0.316 where it talks about KOMPLET firing mode. It's on the same page as you got info about pylon stations which I also already explained earlier. It is a WCS option selected and manual pylon order combo to get to the middle (i.e. using EOS only, radar missile will be ignored).

No, you are mixing launching IR & radar type... what I wrote is "salvo launch mode" of 2 missiles of the same type. In real life, 0.16s for r60/r73 and 0.4s for r27r between the missiles. In DCS dunno, but I think it's close...

in DCS Salvo mode will select all rocket pylons. Without only pair is selected. How many you fire is related to how long you hold your trigger. For bombs, same. For missiles, pair will launch with salvo mode. Burst is only for gun - either bursts (default mode), or continues.

Chizh, I understand that ED does not want to change avionics for FC mig, however is there any chance to get chaff/flare counter working?

Also to be noted... in real plane that "inboard/outboard" pylon switch only alters the sequence. from 1,2,3,4,5,6 to 5,6,3,4,1,2. WCS will of course help with selection as well.. for example, if "inboard" is selected, and target is under the Dmin for R27, it will autoselect short range missile... More recent mig29 versions have updated throttle quadrants with more controls on them.

This is in pylon selection in 29...

use trim on landing... i use thumb rule of having trim nose up in approach so that distance number on hud equals my touch down. Then do not exceed AOA 11 at touch down and watch your variometer not exceeding 5m/s.

+1 ...

DYK ANF is radar supported CCRP dive toss. DYK NAV is w/o radar. SAAB was first to produce dive toss bombing computers and were leaders in this field. There are few patents available on net from SAAB on the topic. Example of using laser instead of radar for slant ranging (might be helpful for RagnarDa): https://patents.google.com/patent/US3474704A/en And another viggen related: aiming solution for wind and moving targets: https://patents.google.com/patent/US3689741

Still present

17kg ;)