Robin_Hood

If there is no player available to lase the target, the AI JTAC should be able to do it for you, correct ? I never really worked much with the AI JTAC, so I'm not sure.

Thanks a lot Grimes, I just tested it, it works :thumbup:

I am unable to make the trigger.action.radioTransmission work in 1.5. I have tried the following DoScript in 1.5 and 1.2, and only in 1.5 does it not work. trigger.action.radioTransmission("radio.ogg", trigger.misc.getZone("radio").point, radio.modulation.FM, true, 30000000, 200, "radio1") Has something changed in how the function is called, or is it simply a new bug that makes it non-functional (or maybe I am missing something else). If needed, I can provide missions exemples for both versions. Note: I have been testing with a UH-1H, in case this is aircraft-related.

Fuel flow for FC3 aircraft can be extracted by LUA export, with an old Lock-on function (not sure how it works for DCS modules) : I think it is given in kg/s or something like that, I am not sure. For anyone interested in LO functions, they are described in export.lua

They would not work in reality. In DCS, well that's up to RAZBAM ; hopefully it won't either (for the sake of realism).

I don't know much, but here's what I know. One of the main everyday mission of the French Airforce is intercepting civilian aircraft (usually airliners) that enter a restricted area, are in distress or (usually) fail to make radio contact (eg. in case of radio failure). The fighters make the intercept to try and see what is the problem and communicate with the crew via visual signals, and they may escort them to an airport in case it is needed. This is done both to counter hijacking, and help aircraft in distress, and is called "Police du ciel" ("Sky police"). I imagine a mode in which the pilot can establish a radar lock but not fire any missile would be a good thing for that. There is also a Police light, which is apparently used at night for "identification" (says the manual). Not sure, but I would guess maybe it illuminates the Mirage 2000 (cockpit?) to show itself to an intercepted aircraft. PS: For training purposes, this kind of intercept is also practiced with non-distressed airliners (with the agreement of the crew).

I think the following line may be relevant:

Personally I used unlimited fuel to avoid inconsistencies. Hopefully it shouldn't cause any difference in the flight characteristics. I still do not have the heart to take on the Su-27 yet. Besides, I am waiting a bit to be sure the PFM is finished and stable.

Except that is not a fighter pilot during combat, it is a (rather excited) instructor teaching a pilot, telling him what to do. It is very different (but this video is very funny nonetheless :)).

Note that I am not defending the missile or the concept, or (God forbids) its addition to DCS, but I am curious. Just from a theoretical standpoint, why would a passive radar ARM need its target to be in STT ? I fail to see why it couldn't be launched at a scanning radar (RWR gets a signal, why wouldn't the missile? Probably wouldn't be as efficient without a rock solid signal, though). Besides, wouldn't STT from the target radar risk that the missile simply gets out of the radar cone and thus lose its homing source (cause in STT the enemy radar is centered on your aircraft). Actually, come to think of it, it seems in any case there may be a rather good chance for the missile to find itself out of the radar cone and in the dark. By the way, I noticed that the website provided also mentions the following (in addition to what has been quoted earlier, and ignoring the typo for IR): It almost sounds like this is more of a specialized Home On Jam missile rather than a passive radar-homing (unless of course the website is once again unreliable). Would be even worse in todays environment in that case, I believe.

I have found a manual for the MiG-15 (not bis) from the USAF dating 1955. Here it is. Of course, it is not a -15bis, but it can be interesting nevertheless, I suppose. Hope it helps.

No, it is not. The IAS/TAS conversion is only dependant on atmosperic conditions, as it is caused by the decrease of air density with altitude. I am not sure you understand what IAS and TAS really are. As has been said, pretty much all aircraft use IAS (or CAS, which is basically the same - just corrected for known errors). Here's a short explanation for anyone not familiar with the different airspeeds. Indicated Airspeed is the speed that the aircraft feels, ie. the rush of air around it, the impact of air molécules. The denser the air, the more the aircraft will feel the air. This is why IAS basically governs the behaviour of the aircraft. Your stall speed, never exceed speed, etc... will be IAS. True Airspeed is the velocity of your aircraft relative to the air (it is therefore your "true" speed). But note that for the same TAS, the aircraft will "feel" less speed if the air is thinner. So for a given TAS, IAS decreases the higher you go. And for a constant IAS, TAS will increase. At sea level, IAS = TAS. Ground speed of course is the speed of the aircraft relative to the ground, and takes the wind into account, as TAS = speed of the aircraft relative to the air and Wind = speed of the air relative to the ground, therefore Ground speed = TAS + Wind = speed of your aircraft relative to the ground The real question is not why would anyone want to rely on IAS, but more why would anyone want to rely on TAS, which is not very useful for the flying of the aircraft. Of course, TAS is used also, in relation to all things navigational, since it describes your "real" speed. After correcting for the Wind, TAS gives you ground speed. Hope it helps. PS: For the record, I don't have any particular problems with the Su-27 PFM, I am intrigued as to why so many people have trouble with it. Apart from the sneaky inverted departure and the annoying trim requirements (meaning the extreme variations in required trim at some speeds), it is quite pleasant to me to fly and fight in. EDIT: Aaaaand I was sniped by GGTharos!

If I'm not mistaken, there should not be an vocal "launch authorized" unless one "arcade-option" is on (don't remember what it's called - audio cues or something ?). This option also provides missile launch warnings. As for the audio cue for the IR missiles, they are (or used to be) only present in Longitudinal Mode (ie. weapon sensor mode - key 6).

The barometric pressure (which is tunable, by the way, key commands have been added to that effect) shows the pressure at see level. It is not derived from a sensor, it is manually set. You input the QNH (pressure at sea level) or QFE (pressure at airfield elevation) and then the altimeter uses that to compute your altitude above sea level or above ground level, respectively. On a side note, above a certain transition altitude, the altimeter is normally set to the QNE, which is the standard pressure (760 mmHg, 1013 mbar or 22.92 inHg depending on your preferred units) - this is so that aircraft coming from different locations can have their altimeter readings matching (otherwise, if you come from somewhere with a higher pressure, you will read a lower altitude than other people). Again, it is not a sensor. It only helps the altimeter deduce your current altitude (by comparing outside pressure - measured, but not indicated anywhere in the cockpit - and the ground or sea level pressure).

I doubt that the statement meant the system is shared with both aircraft. My understanding is that, having already worked on a similar system for annother aircraft will allow them to use the experience and possibly bits of code for the F-14 INS (because, an INS is still an INS, even though there are différences between models). You must note that the MiG-21bis does not have any system like that, so it's new for them. Same goes for the HUD. Oh, I know, there will have a mini-game in there: :D

They were talking about PFM (flight model only), not ASM (systems). If they can do a PFM for the Su-27 (as they recently did), don't tell me they can't do it for the MiG-29.

Radio assist is a voice that tells you stuff, like "missile 12 o'clock", or "launch authorized".

Salvo mode works fine for me (at least it did in 1.2.15). Go to A/G mode, press Ctrl-v, then when you pickle bombs should all release at the same time (at least in CCIP). BTW, when you have switched on the salvo mode, you can change modes (BVR, NAV, etc...) and it will keep in mind that the salvo mode is activated. I use just that as part of a fence check when needed.

I am happy to report that the issue has been fixed in the latest update (1.2.16.38741), as you can see by comparing the quick test I just did with the earlier ones (like post #32): Now you can see that before, when the nozzles were open, the velocity decreased in a straight line, no matter the RPM, indicating no change in thrust. But now, the acceleration can clearly be seen to depend upon the RPM. Thank you for fixing the issue. By the way, this has also fixed the taxiing problem (where the aircraft would suddenly jump forward at 80% RPM), so now taxi will be a lot easier.

I think he is referring to the Longitudinal Mode (the IR missile-sensor mode), that requires you to have the target exactly on boresight. As for maneuvering, I have no difficulty doing combat, with or without direct control (normally without, but when training I will sometime turn it on to very carefully gain a little more nose pointing authority at the expense of more energy bleeding - usually not needed against a dissimilar opponent). There must be something wrong with how you fly the aircraft. You have to trim it a lot (especially at certain speed ranges, namely around 600 km/h and between 700-800 km/h, not so much beyond that), or maybe adding some curvature to the pitch could help. PS: as far as the ACS/ASC/FCS is concerned, I think we should settle for the term used in the manual, namely, FCS, with its different modes : normal, landing, direct control. It may be less confusing than talking about ACS/ASC off or on (since technically, it is not really off, just in a different mode, from what I understand).

Yes, in that first screenshot, the radar is saying there is a contact at 25 km or somewhere beyond. Top of the hud is 25 km (as indicated by the scale on the left), although contacts that are farther are displayed at the top (so as to improve SA). Correct me if I'm wrong, but I believe that is something the F-15C display doesn't do, ie. it will not display any contact farther than the set range scale.

Boat switch, yeah, my bad.

By the way, there seems to have been some confusion between different things on this thread. There are two very different things: The Display range, or radar scale is what the OP was talking about in the first place, and has no effect whatsoever on the radar setting (be it the signal or the antenna position). It only scales the display. The Expected range to target, or search range, is what most have been talking about afterwards, and has been thoroughly explained by everyone (ie. sets the antenna elevation angle in conjunction with the search altitude). Note that if the search altitude is set to 0, changing the search range has no effect at all (untill you change the search altitude). Also, as have been said already, the radar does not require you to point up or down in order to detect or display contacts. In fact, since it is gyro-stabilized, pointing up or down has no effect (other than changing your altitude, which may in turn make a contact appear). Note that the EOS does work that way, though. Not only does it require you to point up or down to see contacts, but the plots on the HUD do represent elevation angle and not distance (so if you see a contact at the top of the HUD, it is high, and if you pull up, the plot will move down the HUD).

Simply change the TGP mode from CCD to IR (either WHOT or BHOT). Not sure which command does this, it's been a while since I've flown the Warthog ; maybe the China Hat?

I ran into this problem today, and after a lot of testing, I finally pinpointed the issue. When an AWACS (I tested only with E-3) is present in a mission with COMMS unchecked, no communication is possible (with ATC for example), and Radio Items Add will not work. It kinda seems like the AWACS is jamming communications (instead of just not talking).