Hulkbust44

Problem is, in A/G without a HARM selected I get HARM on the HUD and whatnot, but upon weapon release PLBK appears for a second and nothing happens. Are you saying that you can't be in A/G without a weapon selected?

Random failures? That specifically sounds like a failure of the primary flight mission computer, MC 1. For that issue look to the back left of the cockpit for the MC OFF switch. Select the MC 1 OFF position. This will disable mission computer 1 and prompt back up subroutines for MC 1 stored in MC 2. I've actually had to utilize this a handful of times in DCS.

high_alpha_low_rate.trk EDIT: Now WIP Textual data did not post...would need to be rewritten. All turns were performed with full lateral stick and pedal with aft stick as necessary to maintain alpha. Turn 1. 14:50:50 41-49 alpha 90 deg turn time= 8 seconds Turn 2. 14:51:22 37-40 alpha 90 deg turn time= 7 seconds Turn 3. 14:52:59 23.4-26 alpha 90 deg turn time= 4 seconds Note that these tests were conducted at low altitude, where the denser air would be increase maneuverability compared to the chart constant of 35k. I hypothesize that this data set was released in the linked document due to the improbability of practical high alpha maneuvering at such altitudes. Thus, this performance data was considered non damaging and was approved for public release. This is in contrast to all other EM related data on Charlie model Hornets which would at best be: For Official Use Only. (https://core.ac.uk/display/268800728)

Bignewy, this is not a "wishlist" item it is a bug. If I select PLID the options on the left come up, but because I can not select them the display is stuck like that until something is selected that overrides the 1-5PBs. To even do this properly would be a stupid simple thing to implement. The symbology already exists and can be displayed from the AI aircraft. IF A/G PLID HOS PB selected, then display hostile A/G symbol at designation point. Currently not planned? The team already went through the trouble of making PLID appear, and making the selection of PLID bring up the HOS, FRD, UNK options. You're telling me they just want to leave it open ended there? If that ridiculous notion is true, at least remove the PLID option if it's never going to do anything, you'll save yourself dozens of bug reports in the future...

Remember that the Hornet's weapons manuals are all classified. Only one has been leaked. For what it's worth the TAC-300 says nothing about boresighting the MAVF but does detail things like HARM TOO Range Known/UNK.

As mentiond here, for a fine alignment the jet must be roataed at least 70° IRL, smart with the 18.

That I can understand, but the issue is that if you have HARMs on the jet in A/G, SP BLK will not work even without HARM selected. You can see it's trying as HARM appears, but pressing weapon release flashes PLBK and the weapon dosen't fire.

They are using AINS here, selecting just GPS making CCIP more accurate goes against all logic.

The 12 seconds is the *maximum* delay in the system. Think about data sourced from AWACS. F/F link as a 3x faster refresh rate, and I would think the PPLI data would be for accurate the closer you get. Having a 12 second delay for all information is wrong.

Perhaps the ranges were unofficially changed.

I was wondering about that, seeing as the 184 isn't like a 99 where it can generate it's own power.

Currently the FLIR AZ/EL subformat is displaying the tactical area identical to the radar AZ/EL. This should not be the case. The main tactical area itself should be shorter at the bottom. This is due to the snapshot video window. A 60 by 60 pixel snapshot video is displayed below the synthetic video. This snapshot window will display the current FLIR image for a selected target. If there is no TUC, then the L+S is displayed. Between the synthetic video and snapshot video there are two data positions. The top position displays the rank of the trackfile that is being displayed. Star for L+S, diamond for DT2 etc. If the target does not have a correlated MSI trackfile a rectangle is displayed. The bottom window displays the snapshot passive range in nm if valid. See A1-F18AC-FRM-000 012 01 Change 1 Figure 1 (sheet 3) Index numbers: 35, 36, 37, 38 This is as it is configured for an A+ model circa 2001. Our F/A-18C lot 20 certainly has all of these functions, I just don't have the specific data for it. If absolutely needed, I've seen a cruise video with at least a glimpse of it, I'm certain the team has much better data than I.

Nope, only the terminal parameters are implimented to some extent.

Still shouldn't exist in the image as it would be filled in with MAP resolution data.

No, it's definitely over-performing. Remember this is a very small radar. The 68v9 upgrade gave a 30-33% range increase as to see a 5m^2 target at a max range of 55nm. Max range means HPRF for the radar which isn't even available in RWS/TWS. HPRF is only available in VSR. Based on that, for the APG-68v5 we have, it is *way* too powerful. Max range in VSR HPRF should be around 41nm. Being generous, that would put the MPRF to 35nm max. 35nm for RWS/TWS should be realistic for our Viper. Actual sources (not just math) put the AN/APG-68v5 at 32nm for a 5m^2 target.

At least the radar isn't 100% disabled like the Hornet's... Outside of mode three neither aircraft should have the radar silenced due to the automatic channels.

What OFP did you find for the Echo or Foxtrot? Specific ones are identical for the Charlies. I might have something deep in the docs. I'll Check.

Nice thought, but HMD alignment wasn't implemented at this time...

Have we tried it when making sure that the ADI source is INS and not STBY? I mean it shouldn't work that way, but that's what came to mind.

Can you get up her up to 45 alpha? Thing is it just turns so slow in DCS. Can't get the airspeed down either. In Wags early video on it he was spiraling down at 90kts indicated... Depending on the alpha, the lateral stick won't touch the ailerons, input is fed to the rudders.

In A/G when you have MUD, a HARM will not fire regardless of PLBK override condition outside of SP. Only way to fire a HARM is to H-OFF via TOO despite the SP PLBK logic. PLBK.trk

Thanks swift, don't know how I missed that. I assumed those reticle were wrong as they look different in DCS and they also don't work as far as I can tell.

When inputting pirouette FCS commands (Full lateral left/right stick with full rudder in same direction) Spin recovery mode activates. During a commanded pirouette nuisance spin indications should be suppressed. Funnily enough, having spin recovery activate is the closet you can get the DCS aircraft to a pirouette. SPNAOA.trk

Just as the title says, in spin recovery the AoA data showed in the bottom middle of the display is pinned at -23.5 SPNAOA.trk

When UPLOOK is commanded only the radar HACQ circle is visible and the previous 9X LOS cue has been blanked. This means you can't use UPLOOK as it's sole function is to aim the 9X seeker. Also in UPLOOK a small cross is displayed at the top of the screen way outside of the JHMCS FOV, swaps places relative to the side you are looking at. -Most likely an old debug too that wasn't disabled. Edit: Appears that the crosses are the uplook reticles, seeing as I never got them to function I assumed that they weren't it, looked different too. UPLK.trk