Santi871

Right now you have to do the procedure bignewy explained and if you're on a carrier use the carrier's tacan. When the color map shows it means it's done and you can switch to NAV.

Bit of an old post but GPS is not used in GND or CV alignment modes regardless. In GND the position of waypoint 0 is used if it exists (which it always does in DCS), so alignment should complete automatically pre-1994 or otherwise. CV is a bit more long winded and not really worth going over here imo. Afaik you can set it to the carrier tacan as of now, but the correct CV alignment procedure is different (think similar to tomcat if you own it), maybe it'll change in the future.

No, in manual acquisition raster when TDC is depressed and it doesn't find the target right away. Undesignate should return to search instead of stepping the L&S.

As confusing as it is there's only one correct (non bugged) way that it should work. As far as I tested, as long as I didn't make a settings mistake, it works, but if anyone finds it to not work then it should be reported. PP mode + QTY boxed or unboxed => each station has unique PP missions (ie they are not shared) TOO mode + QTY unboxed => each station has unique TOO1 and 2 missions (they are not shared) TOO mode + QTY boxed => selected stations share TOO1 and 2 Passing TOO missions to the jdams can be easy to **** up, mostly because: * TOO mode has to be set per station (ie you have to step through all them and change PP to TOO) * If you want to designate multiple targets, you have to make sure to step through every station once and once only, designate a target for each one, and when you have reached the last station, you HAVE to undesignate. This is because the currently designated target is passed to the selected TOO mission on the selected station, so if you don't undesignate, as you pickle and the stores management cycles to the next station, your current designation will overwrite what was in there previously. Have in mind undesignating does not erase the coordinates stored in a TOO mission.

I just tested it. Each station has its own TOO1/2 if you don't box QTY and step through them assigning different targets. In that case, to pickle you need to depress the pickle button once for every bomb. If QTY is boxed, then TOO1/2 are shared. So recap: TOO mode with QTY unboxed = each station can have its own TOO target = up to 4 different targets (or 8 if you also use TOO2) TOO mode with QTY boxed = all selected stations share the TOO target = several bombs on 1 target

If this is really the case then it's a bug

Helicopters can't be in the notch because of their rotor

When entering EXP or RAID modes, all onboard HAFUs are repositioned correctly, however offboard-only ones stay in place, which makes it quite confusing to read. FA18_RAID_OFFBOARD_HAFUS.trk

This used to work correctly until today's patch. If your radar picks up a track that corresponds to a L16 PPLI (eg another friendly Hornet), then it should be correlated to the PPLI and the PPLI symbol should take priority, thus continuing to show the PPLI. Since today, if your radar picks up a friendly PPLI, then the new HAFU "steps" on the PPLI and displays as a brick or regular HAFU instead of the PPLI symbol. FA18_PPLI_NEVER_CORRELATES.trk

MSI tracks should continue to be displayed in STT (ie while in STT it should continue to display other PPLIs, F/F tracks and SURV tracks). This worked correctly until it today, now nothing in displayed in STT. FA18_STT_ERASES_MSI_HAFUS.trk

In RWS with LTWS enabled, bricks should be displayed when only ownship is contributing to that trackfile (onboard track only) - if there is an offboard link16 contribution, then the full HAFU is displayed. This worked correctly until today - now ALL ownship detected targets are displayed as bricks, regardless of offboard contribution. FA18_LTWS_NO_HAFUS.trk

Friendly HAFUs are getting ranked, this is incorrect behavior, only Unknown and Hostile HAFUs should get ranked. This works correctly on SA page, but not on Radar page. FA18_FRIENDLY_HAFU_RANKED.trk

AUTO scan centering in TWS should center the antenna's elevation on the L&S's elevation (similar to the Viper). This currently does not happen. Hopefully this bug can be prioritized for Friday's hotfix. FA18_TWS_NO_ELEV_CENTERING.trk

I can reproduce following these steps.

thanks, keep it up

They appear as a SURV(eillance) hostile track symbol, which is smaller than the onboard+offboard HAFU. Check out wags' link16 video from earlier this year, he goes into the symbology there.

Not a bug

I've been having good results when I use TWS in the correct situations. It's good for sorting groups ~25nm or farther away, when you have time to let the radar sweep over them several times, and to appropriately promote the desired tank targets to system targets and manage all that stuff. If I need to find something quickly, or my target is getting closer (below 25 or so miles), then RWS+SAM is the way.

Hi, I'm making this post as a request for ED to keep working on the Hornet radar after TWS is added. Sadly, there are a lot of bugs and missing things that have been unaddressed for a long time, some even since launch. It would be nice if these bugs and missing features were addressed to bring the A/A radar closer to completion. So here's a recap list of the things that still need to be worked on with associated bug report threads: Bugs: General - 1 bar scan shows incorrect TDC top/bottom altitudes of scan , by Captain Slow, 10 months ago General - Radar does not range gate when attempting to STT by myself, 4 months ago General - Radar emits with Weight On Wheels by myself, 4 months ago General - PRF and RESET options not TDC-selectable by Jak525, 5 months ago General - The top of the radar ("dugout") is included as part of the radar display (only Angle Only Tracks should appear there). by Jak525, 6 months ago PRF- Interleaved HI/MED PRF does not alternate correctly between frames by LazyBoot, 4 months ago PRF- PRF cannot be properly selected with AIM-7 selected by backspace340, 1 year 2 months ago RWS - RWS brick logic incorrect (affects Viper too) by Beamscanner, 2 months ago LTWS - LTWS is able to guide missiles by Papa Saubär, ~1 month ago LTWS- FIXED - LTWS target under cursor and L&S/DT2 do not display bottom half of HAFU (the donor portion) by theinmigrant, 5 months ago MSI - MSI targets displayed with PPI projection instead of B-scope by myself, 2 weeks ago MSI - MSI donor-only target under cursor not displaying mach/altitude by theinmigrant, 4 months ago MSI - Inconsistent behavior when attempting to STT an MSI donor-only target by myself, 4 months ago ACM - ACM GACQ return to search logic incorrect by Jak525, 5 months ago ACM - Radar directed gun pipper is twitchy/jumps/vibrates by Kim Jong-un, 8 months ago ACM - ACM modes can be uncentered if antenna elevation was uncentered (affects Viper too), by M0ltar, 3 months ago AACQ - AACQ logic is placeholder/incorrect/incomplete. by Rex854Warrior, 1 year 4 months ago - see below for full logic STT - RTS button missing if STT entered from RWS by Jak525, 1 day ago STT - Radar elevation gets stuck if changing settings while in STT by Captain Slow, 10 months ago Bugs missing formal report: LTWS/TWS tracks should be aged/dropped based on frame history, ignoring the ageout-seconds setting found in DATA page LTWS/TWS tracks should need at least 2 successive hits on a target to be formed. Brick under cursor should only display altitude if the radar has only hit that target once Radar contribution circle symbology missing from HAFUs RWR strobes on the radar display should appear below the dugout, rather than below the very top and overlapping the dugout HUD TD box should be blanked when the radar directed gunsight overlaps it to declutter the target Missing features: RWS/VS - scan centering RWS - 1 LOOK RAID RWS - Spotlight search RWS/LTWS - Point Acquisition cue (small cross positioned over the #1 priority HAFU that indicates where the L&S will be created upon depressing Undesignate and where AACQ will acquire if actuated) ACM - Uncaged WACQ mode HOTAS shortcuts: SCS Right in A/A mastermode brings up Attk Radar page on RDDI SCS Left in A/A mastermode brings up STORES on LDDI, then SCS Left again brings up Az/El page SCS Aft alternates between HSI/SA page in AMPCD Undesignate creates L&S on #1 priority HAFU if it doesn't exist, steps L&S if L&S exists, alternates L&S and DT2 if L&S and DT2 exist. [*]"GO STT" HUD indication when radar is in RWS+LTWS (or TWS), L&S is designated and AIM-7 is selected [*]Velocity Search mode [*]Jamming strobes (angle only track) [*]Az/El page [*]Fleshed out AACQ logic STT priority: STT HAFU under cursor ("fast acq"), the idea of this is to skip having to double TDC depress to STT STT L&S if no HAFU is under cursor STT #1 priority HAFU if L&S does not exist STT RWS Acquisition Point cue (which is the #1 priority HAFU when the HAFU is not displayed in RWS) The closest target in RWS with LTWS disabled The fastest target in VS AACQ should ignore friendly HAFUs If in STT, return to search and exclude the previously STT'd target range and azimuth, then STT first detected target ("bump acq") Of course, I'm not saying all of this needs to be fixed quickly or anything, but it would be nice if at least some of these get addressed in the near/medium term (especially the bugs). If anyone has anything they want to add to the list or any corrections, let me know and I'll edit it. Happy holidays! PS: Please don't just tag this post with [LATER IN EARLY ACCESS], I spent like 2 hours writing this :(

Nope. It's all detailed in the natops if you want to read, but a summary is A normal alignment (GND or CV) doesn't reference GPS, in the case of GND the position of wp0 is used, which can be there either from the mission card or made manually. The GPS alignment is started by moving the knob to IFA, but it takes approx 10 mins. There's also a stored heading option that should appear in the HSI DATA sublevel. CV is done either via the ship's position supplied via RF or a cable, or via manually entering all the data, similar to the tomcat. Where GPS makes a difference is in that if you do have it you should move the knob to IFA after alignment is done to prevent the INS from drifting, whereas with no GPS you would move it to NAV and you'd have it drift over time. To get a bit back on topic: yes, they should model INS drift at some point, but also when they model IFA to keep the GPS correcting the INS, we would be back at no drift.

Waypoint 0 is actually the "normal" mode we use right now in DCS when you flip it to GND. IFA would use the GPS to align, but it would take longer. ED need to fix the fact the plane never aligns if it doesn't have GPS (ie if it's not in the US coalition).

ED is already working on a PRF audio library. 1 hard coded sound per threat/radar is enough, even though in the real world it would depend on a lot more variables, that part is way out of scope.

yikes

What I mean is that ingame it's like 99% precise and they should model in more error (sorry if I didn't express myself correctly).

Current modeling is nearly 100% accurate so not really.