Vatikus

They are wrong, as is pilot size and ejection seat type ...

On ZX Spectrum: On PC:

Beamscanner, I am with you on this topic. I think correcting rwr on f5 means we get correct rwr on f4 later on. I am pasting here also a link to B52 EWO manual. It clearly describes audio and how it is constantly on except if you turn it off... great read: http://www.avialogs.com/index.php/aircraft/usa/boeing/b-52stratofortress/t-o-1b52h-1-13-electronic-warfare-officer-s-manual-b-52h.html

Will this issue with custom curves be ever fixed?

ALR-87 is virtually ALR-46 build for Swiss AF. And ALR-46 is digital version of APR-36/37 where the main change from analogue brother was its digital processor. All primary UX/UI functionality should be in the same ballpark. The following patent shows logic behind search switch: http://www.google.com/patents/US4176468 "The SEARCH switch allows for the display of search-type threat and airborne threats. If a missile activity of missile launch is decoded by the processor, the system will automatically return to the OPEN mode."

Ramsay, the problem with BST F86 is that is does NOT simulate what you wrote it should. The FFB stick acts as normal spring joystick. There is ZERO change in force in speed and G variation and that is the reason I posted description from real F86F manual.

Well, the reason I wrote my post is because I already did that. And I am not the only one... for example, how do you think all those GCI/awacs projects do it? How much detail you want to simulate is purely on coder. Anyways... Piston85, my findings are in the same lines as well when I tested m2k radar.

Sorry, but this is not true. Any user who is no 3rd party dev can already simulate A2A radar with what's available via export function in a great detail minus performance of the code since it's lua. So RB has all tools they need for a very believable representation and that includes all PRF, BW, noise, gains, filters, ... sim.

It's dead simple... manual should cover everything. full stop. The function of manual is to be the first and last thing you consult with. There should be no information hunting and time wasting on internet. I hope harrier will not be the same FUBAR and RB learn from this fiasco. Manual should be ready before the sim is released as all stuff you are simulating needs documentation in the first place.

I stand corrected. I went and reread the yuaf manual and you are correct.

Yes, each missile type has own launcher which is attached to the hardpoint. And launcher is the one which dictates the missile launching logic through its relays. Unfortunately I do not have any detailed info on the APU-13 series (launcher for R3 & R13). Regarding the seeker fov... the lock fov is quite acceptable from my experience... However I do not know how is granulation of sound lock volume in real life. In DCS we have prety much on/off past 2.5deg. For the E.L., the missile launches in the state it is, and you need to press button for every missile (if you have selected pair 1-2, you need 2 presses or 4 in case of double r60 launchers).

As title says.. since 1.5.7, my dcs does not exit cleanly if server switches mission. There are no crash dump files present in log folder, nor does log file say anything...

Frederf, my source is technical manual for r60 of yuaf mig21bis. By reading it the system is done as such as to try to enable successful launch. So if one missile fails to launch, you do not need to switch anything, the system will skip it... if you select pair launches, pair which has locks on both missiles has priority over switch setting, etc. Of course, if you have mixed missile types, you need to switch manually, as mentioned logic only works inside same type. As for launching w/o lock or ejecting missiles... you have extra button: Emergency A2A missiles launch button (located behind the stick where pitot heaters switches are)

He does not say what you think he says. I guess you are not a native english speaker? When he says that with stick position you control AoA, he does not mean that X stick deflection = Y AoA regardless of speed. What he means is that if you have AoA indicator, you use your stick to correct for the desired AoA, while with throttle you control the angle of approach.

I can answer you only regarding Mig29... LA signal is generated by the range finder (radar/eos) + target signal by missile. However if you do not use (or range reading is disturbed for some reason) radar/eos, pilot can launch when missile sends positive target signal to aircraft.

Mig21bis manual for R60 for example, states that pilot will be able to launch when one or more missiles send positive ir target signal. What might be intereseting to know is that, for example you had selected 1-2 station as primary launching pylons, but if missile which is on 3-4 gets the target signal (and those on 1-2 do not), it will be the one which will launch first.

What probably confuses you is the following: F5 has AUTO trailing and leading flaps switched ON ... these enable pilot, by constantly readjusting, to hold fixed position of the stick for selected AoA. In other words, if you turn them OFF (EMER UP), you will not be anymore able to hold constant AoA with the same stick deflection ...

Noticed in MP that other's top radiator flap can clip into lower with fully deployed flaps ... Also as seen from Fox One's photos, lip flap is not animated in dcs

Non-doppler radars are very poorly simulated in DCS. Ground clutter problem is a tad better simulated in f5 than in mig21. The processing excuse is just that - an excuse. We do not need SAR ground mapping done, all we need is noise picture when radar points toward the ground.

I have attached text from flight manual where it confirms that we should feel forces on the stick.

Just bought the F86 ... no FFB effect ... Mig15 is shaking but in F86 I can see only visual buffeting.

What I mean is that if you are using anything but the preset PPI option, azimuth setting, etc. you will not notice that it's broken. But if you change to B-scan, velocity vector is wrong. If you change Azimuth settings all goes wacky - antenna pointing in wrong direction after losing lock, RDO locking ghost, etc. Some buttons on the CP related to A2A do not have any function.... I've submitted bugs already months ago... then l lost the interest in bug hunting as Harrier became their focus...

I would also really like that radar is fixed as well... it's totally broken outside default settings ...

I've tested this idea... you are indeed correct! I noticed that when sun vector goes thru the bottom of the plane, we get this problem. If shadows are flat only or off, this glow effect will be reproduced.

Here is a nice article wrt AoA and what is effecting it ... http://www.boeing.com/commercial/aeromagazine/aero_12/attack_story.html