AvroLanc
-
Posts
1323 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by AvroLanc
-
-
So I guess no one has tried a proper CASE III then.... It’s too clunky without the correct tacan indications on the HSD. Granted you can use the BDHI, but it’s hard to read and not ideal.
-
According to Natops (and the F-16 as well - same engine), in SEC mode the nozzle closes completely and there is a slight rise in RPM. This is not currently modeled in the F-14.
Agreed. I made post about this a few days ago. Someone said they’d take a look at it. Hopefully fix incoming soon.
-
Would it be possible to designate a target via the HUD and then release a JDAM on it?
This for missions where the current GPS isn't availible or accurate enough?
TOO will work with any target designation but proper HUD Designate is not implemented yet. Hopefully soon.
-
Ok then.
By curiosity, did that function existed let's say, in the F-14A for the AIM-9G, (or any other airframe/missile configuration) ?
Yeah, that was going to my question. Presumably yes, since they have at least some supporting documentation, in that case maybe we can get the functionality back when the A is released.
-
Can you link to where they said it wouldn’t be changed?
I’m all for realism and if it 100% doesn’t depict the DD scan then fine, but something smells fishy and I think a piece of SME information has been misinterpreted somewhere along the line.
-
No, I'm afraid they meant that, there will be no "double D" visible at the HUD whatsoever...
hmmmm that's not how I read Naquaii's post.
He says there should be no DD scanning in a slaved state with a STT lock. This was old behavior and admittedly was a bit odd. Indeed, this was the change that should have been made..... This leaves the possibility that with a non slaved state, we should see the DD.
I'm 90% convinced it's modeled wrong now.
-
Ok, was misinformed as I've been away for a while. The change is that when slaved to a STT or TCS track it will now be directly slaved to that line of sight, no scanning. Sry for that.
Ok, so just so that I can clarify....we should see the scanning cue (double D) when no STT (old behaviour) but when locked to STT then seeker head should jump straight to STT and not scan around that.... If so, then yes, this seems much more logical.
Maybe the old DD behavior will make it back?
-
It looks like there's an issue with the HSD Tacan information not being displayed with AWL selected. According to NATOPs and HB manual, the HSD should still show Tacan info in AWL / ICLS / ACLS modes.
It's pretty difficult to do a Case III without a Tacan radial and DME, but of course you still need ILS ACLS displays up as well......
Included are shots from manuals and missing info in screenshot.
-
hmmm... Feels like a backward step.
It's cheeky to ask but, is this 100% verified from more than one source? Your original modelling seemed more logical.
I was under the impression as well that the seeker could be uncaged from boresight mode, and this was a change being looked at?
Many thanks Naquaii, amazing work.
-
So one of the updates in the hotfix was 'Change sidewinder HUD movable reticle to show only center of scan pattern'
I'm assuming this was a correction that was needed? Was the old behavior wrong? I actually think the old Sidewinder behavior was better since it gave an indication that the seeker was scanning versus not scanning.
Can devs confirm that the seeker still scans in the new mode? Does the cage/seam button still have the same effect?
Playing around with it and it feels a lot less intuitive / clear as to what seeker head is doing.......
I don't like, but if it's real behavior......
-
That list is very useful, however, they don't list all of the missing functions on DDI pages, or aspects that are bugged, so it is still very difficult for users to know what is missing/bugged/reported previously etc.
I had another thread going on the same subject.
The truth is, there is no single list of features that are still to be implemented. Without going through the NATOPs manuals in detail, which is entirely up to you, you’ll never have a true idea of what’s still to come.
Use the ED provided list as a basis, look at non functional DDI options we have now etc and follow Wags updates. And maybe read the NATOPs, it’s full of useful stuff, albeit non weapons mostly.
-
I find SEAM to be completely useless, so I use PAL (or VSL-Hi) first which slaves the AIM-9 seeker to the locked radar target, then uncage, then fire the Sidewinder.
I also use VSL-Hi in a turning fight, especially a gun fight, to get the lock while I'm in lag pursuit before deciding to pull lead for the shot.
I don't know about you though, but 15nm is waaaaaaaay outside my visual range...
That’s the great thing about PAL , it’s a good half way house between the RIOs modes and pure WVR. When you know somethings out there but jester is slow.
-
What about the following:
- Check the target's coordinates in the briefing
- give Jester the coordinates to put in as Surface Target, which creates the required steering point
- set the steering cmd on the Display Control Panel to AWL/PCD
because:
AWL/PCD - All-weather landing/precision course direction, selects glideslope guidance (ILS/ACLS) for landing or PCD for air-to-ground engagement directions as steering command source.
Shouldn't that place a diamond on the coordinates (on ground level)?
No. AWL/PCD is a landing mode. Completely unrelated.
The F-14 simply isn’t designed as a sophisticated air to ground platform. The ability to drop dumb bombs visually was built in from the start, but it obviously needed LANTIRN to be an effective bomber.
Best bet is to use IP mode. It works well, you need distance in NM and true bearing, also altitude difference, from mission editor/planner. Only drawback is that once designated, the target can’t be adjusted easily, when the inevitable position error is noted during bomb run.
-
Still intrigued by this selection. Would be helpful to get some input from those in the know. I’ve worked out:
Default steering with an A2A weapon is LD PURST (lead pursuit). Seems self explanatory. You wznt the weapon to pull lead.
COLISION is supposed to provide intercept steering command I assume. Seems inop at the moment.
PURST (Pursuit) is selected when you have an STT target and ACM cover is flipped. Steers the nose onto the target direct ie. pure pursuit course. Is ACM Cover the only situation where this is commanded? Main tactical use?
LD COllSN ( lead collision) I have no idea, how do you select it and how is it different than lead pursuit.
-
Will look into this one...
Thank you.
-
I'm playing around with the Collision steering button in the RIO pit, but have no idea if it's working correctly ( I suspect not....). It's number 7 in the image below.
Can anyone confirm what it does? My take is that it provides azimuth collision heading for the currently tracked / STT target i.e. provides a collision course to the target. However in-game it doesn't do this. It just provides a wobbly steering T on the HUD that moves with the own A/C and actually points nowhere.
Am I using it right? What HUD mode, weapon selection etc should I be in to use correctly? Is it implemented? The HB manual is rather short on info for a lot of this.
-
The rad alt bit test works ok and produces correct indications but there's no green 'GO' light displayed.
Maybe the bulb can be added.....
-
I think there's an inaccuracy with the SEC Engine mode. Testing the SEC mode on the ground I'm expecting to see the Nozzles fully close and rpm to fall slightly. However, the nozzles just stay at full open with no change of RPM or EGT (TIT in this case).
I've included a very short track below.
The full manual states:
"In SEC mode, the exhaust nozzle is commanded full closed, the nozzle position indicator goes to the not-powered position(subzero indication), the IGVs are fixed full open,high-energy ignition is continuously energized, afterburner is inhibited, and idle lockup protection is lost."
SEC does appear to have some effect though, it does correctly inhibit Afterburners and does produce loud noises in some flight conditions. The Nozzles don't behave correctly though.
-
Be aware that the nav lights only flash when the anti collision light is off.
Does that change what you’re seeing?
-
Engine Fuel Shutoff Pull handles and the extremely hard to see Fire Extinguisher button
-
Ok, so further playing around actually confirms that the Fire Pull handles do work.
They just aren't instant, it takes 20 seconds or so for the fuel to shut off. Maybe simulates fuel in the fuel lines etc being used.
The click spots for the fire extinguishers do work, but the click spot is EXTREMELY hard to use, it requires lowering your head to the seat cushion to see.
Maybe this is a candidate for a key bind.
-
It appears that pulling either of the Fuel Shutoff Handles does nothing. There's no button behind them for the extinguisher either.
I'm not I'm not missing anything? Will this get added in the future?
Damage model is excellent generally, I just had a flap / slat overspeed and my right slats jammed open.
Hopefully engine fires and extinguishing will feature?
-
What's shown in the TID is the closure vector relative to you, ie if you're closing in on them the vector will point towards you regardless of whether their nose is also pointing towards you or not. That's in TWS, not sure if it's the same in STT.
Yep, that’s how I understand it. The ground stabilised display shows the actual true Velocity Vector but, it’s a pain to switch back and forth, and is still only very approximate.
-
You can read ATA (Angle Off) from the DDD. For angle aspect, I agree with Victory, you can read it from the TID display.
v6,
boNes
I’ve spent a considerable amount of time in the manual and heads down in the sim. Can you tell me where this readout is? Is it a numerical readout or do you mean just look at the approximate locations of velocity vectors?
[RESOLVED] Nozzles not closing in SEC mode
in Bugs and Problems
Posted
The F-14B NATOPs pocket checklist indicates that rpm should drop, not rise, during SEC mode. That’s on the ground at least.