deadpool

Deadpool - F5

Valid question would also be: Is there a way for the pilot to reliably see for a given roll angle how close to the gimbal limits he is? At the moment it's just me - as a RIO - yelling LIMIT LIMIT LIMIT at my pilot when be comes close.

This does not fix a defect. This is intended at the moment. By applying the changes above you are modifying the game to have an advantage over other players. If you do this in multiplayer without others being aware, I would strongly consider this cheating!

Source please. Otherwise: Pushing a Twoship defensive by firing at two targets? TWS EXP pickle TMS-right pickle profit?

Some things are only properly readable with a flashlight .. so I left it on .. and I guess battery technology of the 70s was not as great, after an hour the lightbulb burned through. didn't flicker .. didn't dim .. was just out :-) BR, Deadpool

Wait what? .. Chinese trespassing on copyrights? .. that's unheard of ... </sarcasm> .. If Car companies, etc. can't do something against it, I fear ED won't be able either. But yeah: Thanks for showing that it's not all who condone this!

No problem, just wanted to log it because I'm certainly not even going to notice it again :-)

Could you please link to what FM/FCS remarks Mover had?

The trapsheet in the kneeboard of the RIO does not properly show the usage of auto throttle by the pilot.

With either enough headwind or a very fast yet to be invented aircraft carrier, I suppose the F16 could also take off from it. If this is even remotely realistic or would find it's way into any operational manual .. Nope.

There's just one nuke in the game and I read that there should be none coming in addition, so .. it would be a lot of work for just one gadget.

Fix would be to include the line { down = iCommandAWACSBanditBearing, name = _('Request AWACS Bogey Dope'), category = _('Communications')}, below { down = iCommandAWACSHomeBearing, name = _('Request AWACS Home Airbase'), category = _('Communications')}, in the file Config\Input\Aircrafts\common_joystick_binding.lua

This is the bane of my dogfights. I can bend my head backwards as much as I want, I do not seem to be able to look up past the nadir. Something is stopping me. I do feel that I was able to do so in VR though.

As mentioned by Nineline: Will we get Dual Capable Aircraft capability and thus nukes for the F-16? It surely is a realistic loadout in terms of supported wartimes loadout.

The radar might be a tat bit better, yet the RCS is also quite significantly different. I'd like to see things play out later on. But yeah, it's a bit of a pity that the FA/18 comes without almost no restrictions on weaponry, and the F-16 has a preset limit to actuality. But we'll live with that. What the viper has over the hornet is the (what you would call nowadays) usability. In HTS, in the WPN page of MAV and HARM (which I can switch to using just hotas in the F-16) I use the same mnemonics than for the radar and the HSI. I just use the TDC and TMS UP to select. In the hornet when doing TOO with the HARM I am left pressing FLIR and UNCAGE and my brain is like: wat? Also the radar elevation selector in the Hornet .. just seriously wtf .. who thought of that thing? The navy did it right in the F-14. no idea why you'd do such a thing. It's incredibly hard to snap back to previous altitudes you had "muscle memorised". I am by now joking around that to later select targets for the HARPOON and fire it, you'll have to select IR COOL to ORIDE, deactivate the OBOGS and then handoff with the gear lever. That's Hornet usability for you. Every weapon requires a complete retraining. But on a serious note ... the CCIP version of the F-16 that we get has and is capable of carrying B-61s, right? :-D You can go into A/G mode, go MRM override and then instantly switch back to A/G modes through the HOTAS cancel.

It's a special version of the Maverick that does that, the AGM-65F which I doubt the F-16 will have. What the F-16 uses to attack larger structures like bridges is a mode called Force Correlation on weapons like the AGM-65 H, K or G.

So coming back to the initial point: Shouldn't the radar stay locked on that target?

Is this really a correct range for the FA18 radar to pick up a hot target? 20 nm? Sounds to me like you should have picked it up ages ago!

I copy that experience. Every hit so far lead to hydraulics problems and resulted in an unrecoverable airplane. The experience is also that going to idle thrust immediatly and dumping more flares than Air Force One in the movie with the same name did not reduce the pK of incoming FOX2s :-( Someone has to be the bad luck magnet!

STT is usually still pulsed .. CW isn't.

You should really fire your Phoenixes outside of the AIM-120 and AIM-9 envelopes. Flying high shouldn't be that much of a problem.

The main factor the Maverick is missing is energy for terminal guidance on fast moving targets (it is designed for targets moving at ground speeds). It will loft and it will fall down on the target. If the target is moving relatively slow, then you have a chance to hit it.

If you stay with the lightbeam analogy imagine this: Search radar -> light house. The beam is going to hit you once every second or two seconds for a brief moment and you'll be in the light. Pro: Enemies do know that you're there, and that they might have been spotted (if the return energy was enough and made it through your filters). Pro: The sender covers a larger amount of space and can get an overview Pro: The precise target you have in mind to attack won't know that he is singled out, he can only make assumptions about the risk factor. Con: The sender can only get data on you every 1-2 seconds. STT -> you get pinged more frequently, as the radar doesn't seem to be searching, but solely focused on you. Pro: The sender will know precisely what you're doing with little latency, he will have up to date info and it will be harder to get lost in between the sweeps. Con: You will only see the one target (it's a STT single target track) Con: The guy being painted will know that you have a high interest in him, most likely not because you like him. He might start going defensive or be at least more alerted in regards to your actions. CW -> All the radar energy the sender can muster is being shot at you, making you appear as bright as possible on the return. Pro: A target being this bright has a high chance of returning enough energy so that a semi-active radar guided missile can use it to guide on him. Con: The RWR of the guy getting painted will most likely tell him that he is the centerpiece of attention and most likely has a missile incoming on him, as there is no other reasonable explanation for this much radar energy coming towards him. But this is a mix up already, as there are different modes of STT and also different search modes. Modes like RWS, TWS, LTWS were all mentioned before and I suggest reading this bit of documentation http://www.heatblur.se/F-14Manual/general.html#an-awg-9-radar here to dive into further detail on them. As for missile guidance, there are different classifications: FOX-1 (AIM-7, 530, ...) These semi-active radar homing missiles will usually use the flashlight approach. As soon as you shoot them or a few milliseconds earlier actually, your radar will illuminate the target. The target will know why, and it will act accordingly, but it won't see the missile on the RWR itself, just your plane. And once it has defeated your plane's radar (terrain masking, etc..) the missile will be dumb until it reacquires the signal potentially. FOX-2 (AIM-9, Magic-III, ...) IR guided missile, no RWR warning unless the airplane has an additional system called a missile warning system. Airplanes that are known to have this might include the A-10, F-16, ... These systems work differently and try to detect incoming missiles by their emissions of light (UV mostly) due to their rocket motors. Don't expect this to work always. FOX-3 (AIM-120, ...) These missiles are more intelligent and they have their own (shorter range) radar. Imagine telling a missiles own navigation system before launch: "Ok, I'm going to fire you away now, the target is expected at intercept time to be at these coordinates, fly towards this intercept point and activate your radar X seconds after launch". Now as long as the target is still on your radar scope, your weapon control system can provide the missile with updates of the intercept point and activation times of its own radar. And since you don't need ultra-low-latency information in the first phase of the flight, you can use modes like TWS that don't cause the target to know what's going on. Once the missile is close to the target for it's own radar, it will turn it on for terminal guidance. This guidance is done with a single target track, so at this moment, the RWR of the attacked airplane will pick up a second source of radar emissions with an increased frequency. The RWRs internal libraries will match the frequency, the pulse repetition frequency / pattern and it will find out that it's a missiles seeker that's painting it. This is when the pilot will get the (M) warning in western AN/ALQ systems. This is when he considers going defensive as well. I would not be surprised if modern airplanes in reallife can pick up reflected radar signals that were emitted by someone else for their own computers to make sense of. But this is not modelled in DCS. the problem with flying low and nose-cold (radar off) to sneak up no targets is that data links and target donation only works with line of sight radio communication. So if you're down in the valleys, sneaking up on someone with the help of your AWACS, it's very likely that you either won't be receiving datalink, or that your AWACS doesn't have your position to give you a proper BOGEY DOPE. BR, Deadpool

I did ask the devs of the F-14 to disable the automated switch from TWS MAN to TWS AUTO on launch until TWS AUTO is correctly implemented. Otherwise and especially in times X engagements with azimuth or elevation angles involved it will lead to fades immediatly after launch :-(

In ACM mode the Phoenix should actually be active and lock the target before launch. In RIO Active launch switch mode it would be like you described. Launch and the first command the phoenix would get *after* launch is to go active. A slight but important difference.