deadpool
-
Posts
604 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by deadpool
-
-
When firing in ACM mode you need to be within 10 miles of the target and have the nose pointed directly at it. (Put the little cross on the HUD on the target). The Phoenix should then be able to lock on to it and track as soon as it's off the rail.
Remember to flip the red ACM safe switch to UP, otherwise you will not be able to fire off the AIM54 without your own radar lock.
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.
-
As an experiment as RIO I had the radar on while my pilot was practicing carrier landings. I got a return in pulse mode. Initial thought was it must be the carrier! Locked the contact and landed... other friend who was in another aircraft on the carrier started taxiing to the catapult and I got a bearing change following him.
So the radar could see him but not the carrier which I dont believe is realistic behaviour.
Will attempt to replicate and post a track when I have spare time.
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
-
It's not. If it was the Tomcat wouldn't have its vaunted ability to engage six targets at the same time.
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.
-
The centroid and automatic scan volume is not modelled yet, it will be implemented during EA.
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.
-
1
-
-
But in the HB manual it says:
In-game it switch to 1 bar as you says. Mistake in the HB manual ?
Don't know if it was changed in the manual, but in that case it's definitely not behaving like written in the manual.
-
AWG 9 does this automatically. You can change them with Next target button I believe.
That doesn't necessarily work, though for some reason. Going to investigate this further before filing a defect.
-
As the title states, the RIO can click the switches in the front seat such as the gear, hook and master arm.
Hello DECOY,
this has been posted already, sadly wasn't moved:
-
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 :-)
-
It doesn't work for me... I see contact on DDD, press half action on HCU, try to hover over target with "TDC", but target disappears. When I release HCU half action, target appears again.
I can lock only form pulse srch mode.
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.
-
-
-
lantirn was used from <= 10nm distance.
-
Thanks for the tips, but that doesn't solve the bug. That happened because we were miles away from the action and we assumed the bug was triggering again (like it had 50 times before that). It would just be nice to have launch warning = being launched on, like it is in every other module.
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.
-
Thanks - I thought that was the case but wasn't 100% sure when writing this up. It did actually get me killed earlier - had a human RIO in the back seat as we got pinged and we both thought it was another false RWR hit, until a missile hit us :(
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!
TWS Auto? Question for Devs
in DCS: F-14A & B
Posted
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 :-(