Hulkbust44

Use the Bullseye waypoint as an OAP (offset aim point) and plug in the data. Go as you would to make a waypoint. HSI-DATA-UFC. And then select O/S for offset. Plug in you bearing range and elevation and you've created an offset waypoint with bullseye data. Mobius708

You program PP1 for each weapon. The others PPs are for alternative targets. Mobius708

While this is true, I don't believe the helicopter RCS is modeled in detail. I remember them being really tricky to find in DCS. I forgot that there is no low PRF outside of the ACM condition. I was thinking about using low PRF as in the Mirage. Mobius708

So the Hornet radar was severaly bugged last patch but is working great right now. (Well as it's designed by ED) Most likely you aren't adjusting the radar elevation to where it can see the target. You adjust the antenna angle with the HOTAS command "antenna elevation control." You can see the maximum and minimum altitude search values on the yellow TDC cursor on the attack format. The top number shows the maximum view of the radar cone at the cursors range, and the bottom shows the minimum value. Mobius708

INS (inertial navigation system) has nothing to do with the radar. If the mission date is after 1986 you should put the INS knob to IFA once the ground or CV alignment has been completed. If before 1986 use NAV. If you are in NAV when you should be in IFA your left DDI advisory line will display P/INS. Inboard of the INS knob is the radar operation mode knob. Make sure this is on operate. (Give me a minute, rereading you question) Mobius708

Well the TWCS has like 85% commonality with the Hornet throttle. Mobius708

Well at what range? Helos are slow moving small RCS targets so they are hard to find in radar. You should also use low PRF. Mobius708

If using datalink AWACS will generally ID the aircraft. The jet however does have the capability to positively identify aircraft type. This is with NCTR. Non-cooperative target recognition. Within 25 for a fighter sized target and an aspect no more than 15°, your radar will attempt to see the targets fan blades looking down the engine intakes. The WCS will then compare the radar return of the engine blades to an onboard database and match the returns to the known type of aircraft. With a successful NCTR you will see the aircraft type on the AZ/EL format and the SA format in the bottom right TUC (target under cursor) info block. Mobius708

As mentioned before disable the ALG(automatic level and gain), it helps a lot. You can also put the FLIR on the AMPCD and it with be grey scale. This is technically a bug as it's unrealistic, but it works in DCS ATM. Mobius708

Unpopular opinion, Viper HOTAS is disgusting. DMS is making up for poor avionics design to begin with. You better have a way to flip between three pages (SMS, INV, and WPN) because the Hornet has it all consolidated into one stores format. It really doesn't make up for the two tiny MFDs. Besides, what else are you going to put on the hot bar? In A/A you want radar, SMS, and HSD. In A/G you want SMS, TGP, and HSD. It would just be better to have another MFD. Back to the HOTAS. Again, we see a separate TMS and DMS...while this is great in the A-10 with it's unbeatable HOTAS, it's disappointing in the Viper because it had so much potential. In the Hornet TMS and DMS is replaced a single SCS, and it's function is a lot cleaner. In the Viper if you want to STT a single track on your FCR you need to make the FCR SOI, slew the RDR cursor over the track, then TMS up twice.(bug, then STT) In the Hornet, you hit SCS towards the attack format twice. Once to make the format TDC priority, twice to command AACQ to STT the priority track. It's really sad that the Viper can enter the ACM condition with the dogfight switch. In the Hornet it's all seamless as you can enter the ACM condition via SCS up. (And exit via TDC depress or NWS button) Another really big thing is the weapons select switch and being able to immediately select the weapon you want. Even if you don't have the weapon loaded, you can use it's system selection to set radar search parameters, I do this quite often. The HAFUs are the most intuative things possible...if you hate them, blame the Tomcat actually. Like seriously, red is hostile, green is friendly, and yellow is unknown. If you see the top half of the HAFU, your own aircraft sees it, if it's the bottom half, it's a donor datalink track. Only slightly confusing thing would be when you aircraft hasn't IFF'd a contact it sees. That's when you get the pentagon because the top half indicating what your radar sees is the "staple" meaning unknown, and the bottom half is a chevron as others on the net identified it as hostile. In the Tomcat, you don't even get colored HAFUs :) Mobius708

Avionics, looks, handling, more useable pylons, standoff weapons, 4 HARMs, onboard ASPJ, carrier ops, easier refueling. Pilots who have flown both say that if you want a joyride take the Viper, but it's the Hornet you want in combat. Is is just overall a vastly superior platform in capability. It may not seem like it at first glance, but the Hornet avionics are leaps and bounds ahead of the Viper's giving it a ton of flexibility. You have displays twice the size, +1 more display, imo an immensely superior HOTAS, you can communicate with everyone with the 2 ARC-210s and 2 MIDS VOC channels. The Hornet sensor fusion called multi sensor integration (MSI) is an incredibly powerful tool, and it's basically not implimented in DCS yet. Everytime I try and fly the Viper I get so frustrated by poor design of the avionics system, and it's lack of functionality. It is the most clumsy thing possible. Only nice thing is the quick ability to create a stearpoint by pressing STPT when DED is CNI. But why do you need three separate pages (INV SMS WPN) to employ say HARMs or MAVs when you could have a single STORES format as the Hornet does? The 16s comparatively dinky radar is another turn off. I could compare avionics all day but I've gone on long enough. Most people overlook the Hornet's communication capabilities as many tend to be using discord to talk to their buddies instead of SRS. That is save for the milsim groups who want to keep the immersion. You get 2 radios which can hold 20 manaul presets each. You can effortlessly change the presets by rotating the corresponding radios knob on the UFC. You can see the preset number AND the corresponding frequency simultaneously. These radios can be either UHF, VHF, AM or FM. There's a preset for guard, cue, and maritime channels. With MIDS, you have to digital voice channels to communicate with other Hornets. What this means is that I can talk to my flight on MIDS VOCA, another flight on MIDS VOCB, AWACS on COMM 1, *and* choppers running CSAR on COMM 2 The Viper can't do any of that. Hell, in the Viper you could have you interflight on UHF 253 and AWACS on VHF 134, but when you RTB tower is on 249.5 so you need to change your interflight frequency over to a VHF freq... I'll leave it at that. Mobius708

Yes, removing the parking brake stops the alignment. Mobius708

Are you sure? I thought that toggles CCD and FLIR rather than FLIR polarity. Mobius708

Can't look at the track right now, but was the parking brake set and air source set to off? Mobius708

So nothing was changed with the lastest update unless you are using stable. (If that's the case just don't) PLBK is part of the HARM automatic self protect modes. If you get mud (surface radar spike) and you have a HARM onboard the WCS will prioritize the HARM. So, when you get mud the EW suite will target the emitter and the pickle button (weapons release) no matter what weapon is selected, will fire the HARM at the emitter. PLBK (pullback) is displayed when this function is overridden. On the bottom right of the stores format, EW format, and a few others, you will see "TOO OVRD" or "SP OVRD." When these are boxed the HARM prioritization is removed. With it unboxed, HARM will replace PLBK when the SP conditions are met. When using the HARM unbox the TOO override. Per the TAC manual. Mobius708

The range of allowed deflection. Maneuver flaps are controlled via the DLC forward and aft commands.(when DLC is not used) Landing flaps use the flap lever outboard of the throttle. The range of motion of the maneuver flaps is shown on the flaps indicator as the small white arc. Mobius708

Flap over speed is 225 kts. Do not use flaps on take off, via the flap lever. You use the maneuver flaps. Maneuver flaps are controlled with the DLC forward and aft commands. Mobius708

It's so nice to see these researched, concise bug reports. Just what we need. Mobius708

At least I still have the old RWR BIT : ) Mobius708

I was devastated when I was no longer able to mess with my pilot... Mobius708

With 2.7.1 the Hornet was corrected in that the map can only be displayed at scale of 40 and below. However, on some maps there is a bug and some scales below 40 don't display. Mobius708

The reason the FLIR stops tracking is because it is slaved to the L+S and is not actively tracking the target. You must castle towards FLIR to command a track. When the FLIR is tracking the HUD TD box will display F. If the track is also L+S a C for correlated will be displayed. AIM-9s will be slaved to FLIR LOS. There is a FLIR button on the AZ/EL format, just not top level. Castle (SCS) to AZ/EL with the TDC OUTSIDE OF THE TACTICAL AREA. It defaults to this position over "stores" when TDC is assigned. You can ensure this works by castling away and back to reset the TDC position. Once you have castle towards the format when it was TDC priority you will be brought to the FLIR pointing sublevel. Default TDC position is the same, but stores is replaced with FLIR. A simple TDC depress then will cue the FLIR image to where the AZ/EL is. Also in this FLIR as sensor mode you are changing where the pod looks with the TDC rather than interacting with the radar. You *should* be able to exit ACM while retaining a STT with TDC depress, but not yet. The display of datalink HAFUs on the AZ/EL should also be possible, but that should come with an MSI rework. Mobius708 Of course Harker beats me to it by typing faster, GRRR. Oh well, your explanations are better anyway. Mobius708

I was just reading through the Hornet manual and found this line about PPLIs, "Precise Participant Location and Identification (PPLI). This is the data that allows the display the location of the donor, what its sensors are doing, and payload remaining." I'm questioning that last part of "payload remaining." Is that not implemented yet, am I blind and haven't noticed, or is it just wrong? This is on page 384

Yes, but it's not necessarily a bug as it is completely fictional. No LGB through the GBU-24 can "talk" to the aircraft, codes are set by bomb on the ground. Mobius708

Well the Viper dosen't have any kind of sensor fusion. The Hornet TOO is probably more efficient because the RWR talks to the HARM. My guess is that the HARM uses the RWR data to decide what to scan for. The ASPJ is also tied in, in some way. Mobius708