deadpool

I already filed a defect for something related. I could PD STT the carrier or another small moving ship that should clearly have been hidden among ground clutter or within the notch filter. Pick one :-D

Yes.. it is not SAHR, but while the Phoenix isn't a classical FOX-1 that preferentially uses CW illumination of the target, it is still relying immensely on the launch platform sustaining a lock to give it guidance information in flight. So the second part of the post by Tiger-II holds true. The active seeker in the phoenix has a very limited effective range. Break the lock before it's close and sufficiently change where you are from where the missile expects you and you have avoided the - now - mad dog.

would it be possible to remove the automated jump from TWS MAN to TWS AUTO upon launch up to the point where TWS AUTO is implemented? That would save some grief I'd think.

sucks a bit if you have targets off boresight painted with TWS MAN and launch, as it will go straight to TWS AUTO and boresight your radar :-/ it's a bit of a fight and will happen after every launch.

I - as a human RIO - also had it some times that before STT lock I wouldn't get an IFF return. I'd say in that sense Jester is nicely human in making mistakes that can cost you.

Don't know if it was changed in the manual, but in that case it's definitely not behaving like written in the manual.

That doesn't necessarily work, though for some reason. Going to investigate this further before filing a defect.

Hello DECOY, this has been posted already, sadly wasn't moved: https://forums.eagle.ru/showthread.php?t=234976

I - as someone not out to fly the F14 but just to RIO the shit out of it - have long thought about whether to respond here or not. This thread started with a simple request for a choice. A choice that a server owner can make, or could even now potentially make with the help of triggers in the missions or rules. It then went on to be a show of non-understanding and of solo pilots fearing that they will get shitty RIOs and want jester unless they can get a better RIO than him. Even going so far as to judge their fellow pilots as spiteful people jumping in as their RIOs and shutting down systems. (Is that what pilots think of other pilots?) I sincerely hope you guys help train those RIOs, as they do not have the training missions that you do, as they do not have the experiences from previous planes and previous pulse doppler radars that they can simply transfer over to the F-14. Because if you don't, I wish you all that you will be pitted against F-14s with supreme human RIOs that outperform your JESTER and tear you to shreds and make your solo-hormon-ego-trippy-brains explode and your eyes cry rivers of regret. Because: Yes, we will make mistakes, in a more unpredictable manner than JESTER. Correcting a typo or a mispronounced digit is something else entirely from having you chase a radar echo for 2 minutes. I doubt JESTER does that. I personally fly with a nice pilot who has more time than I do and seems to spent most of his DCS time flying with me as his RIO when I am available. That's good. But it's also quite some pressure when you have to justify (and I say this in a less strong sense of the word) your judgement because you are compared to JESTER (which is ok in some way). I just seriously doubt (and I have never seen JESTER do his thing or played with him as I don't fly the plane) that in specific corner cases like a 45° turn he just feels like having a better gyrostabilised coordinate-transforming azimuth / elevation control over the radar. But that's just an assumption on my part. While I am not mathematically challenged I find it hard to do cosine and sine multiplication for different angles of bank to my azimuth / elevation components. So hey .. before taking over a thread and steering it into a totally different opinion-piece, think about the RIOs that will be reading this and what they might think of you. Thank you :-)

Hello Nikola, the reason is that the supersearch mode used for this is only a 1bar mode. (see: http://www.heatblur.se/F-14Manual/general.html?highlight=supersearch#hcu-stick-in-radar-mode ) You surely have a 2bar or 4bar scan going and when trying to lock the target and "hover" over it on the DDD you're going to a 1bar scan. You need to compensate for that by manually finding the right bar the target was found with and then lock it.

the following situation: a cargo ship going 10 knots, relativ 78° left of ownship course (basically 12° away from a perfect beam) 10 knots * cos(78°) ~= 2.08 knots (relative to ground movement from my plane) I could lock that thing up easily in PD scan and thus PD STT and guide a phoenix onto it. This felt wrong.

no text :-)

no text :-)

lantirn was used from <= 10nm distance.

No worries. Didn't want to talk down on you. Sorry if it came over like that way. Could this be related to the defect from Ed where a plane lock from ai will trigger everyone's rwr?

Maybe for this defect report focus on point 1 then. There was no flashing of Impact number.

Your Rio should look at rwr and then at direction for immediate confirmation of launch trail. He has chaff control and also can advise whether it is going for you or someone else. He will also handle the call out via radio. Either ownship defending Sa something. Or Sam launch rough position and whether it goes high or low.

Agreed. Just adding these to be thorough.

Yes. If you select a target with radar mode hcu on ddd you will have a pd stt.

We launched two Phoenixes as two AI F-16A target drones (those are brave virtual people flying them!) and did that in TWS mode we had a solid TWS track on them the whole way through, yet one missed. Ok, can happen, but what was odd was: 1.) No flashing of Time to Impact numbers, telling me that they never went active? That might explain sluggish last second maneuvers of the #1 missile that lead to it being defeated. 2.) The enemy AI flights immediatly went defensive, even though a launch in TWS wouldn't appear different on their RWR and we were 30+ nm away with smokeless Phoenixes on board.

Sometimes the range indicator in modes like RWS gives no indication of the current setting. Changing ranges does not help there. What helps is if the pilot goes to A/G mode and back to instantly get the indicator.

Not sure if this is a defect. Today the LANTIRN generated drop cues for my pilot nice and easy as far as GBUs were concerned .. good hits on target, everything as expected. But we couldn't for the life of us get it to generate the same cue for MK83L. Is that how it's meant to be?

Even better: Start a multiplayer mission and sit down as rio with the game paused .. you can now roll back a cm and have look around inside his head :-) His yellowish colored eyeballs do suggest a liver problem!

To be fair that locking something up in TWS will result in a PD STT radar mode lock. What he is doing is scanning the sky efficiently for returns and then have the TWS system plot so called "tracks" onto the TID.

should be range while search instead.