Brass2-1

I believe this would be a desired and enjoyable feature across all tactical fixed-wing modules. I see it being valuable for BFM and DACT in particular, but practice intercepts would be excellent as well. I and many others spend a good portion of our DCS hours flying “training” and Red Flag type scenarios on NTTR, but to a large degree the immersion/realism is broken by actually destroying airborne targets. While air-to-air combat is incredibly rare in the last few decades, training occurs daily in every Air Force in the world and I would love better tools to simulate this. I would suggest either or both of two functions; Inter-flight BFM practice via radio call to wingman. “Two, push to butterfly set”. “Fight’s on!”, wingman turns in and ‘engages’ without expending ordnance. An amazing feature would be “Fox 2” or “GUNS GUNS” calls when in engagement parameters, with the player having hot keys for the same. ‘Perform Command’ option for AI aircraft/flights, with similar functionality as described above.

The Viper in DCS has never been terribly impressive out of burner - anyone who has tried lugging a heavy-ish air to ground loadout to 30,000 can attest to this. Edit - un-cited anecdote snipped. To add some credence to the current DCS setup, I have never heard it mentioned that Vipers can break the Mach in Mil power, and they cannot in DCS (not that I’ve achieved, anyway). The EPE Hornet I’ve heard at least one reference(Mark Vizcarra, Aircrew Interview) to breaking through supersonic (high transonic, I suppose, but M1.0) at Mil, and this is represented in DCS also.

Yes, huge quality of life upgrade.

Flying this beast in VR, as poorly as I do so, is truly like living a dream. My thanks as well.

Using a HARM as a poor man’s HTS is pretty effective as well. I was excited for the HTS on release as I love SEAD but wandered back to the Hornet in short order.

I prefer the man-machine interface of the Hornet hands-down, from HOTAS to DDI’s. The Viper’s cockpit looks and feels cool, but doesn’t work well for me. The JHMCS implementation is better, IMO, in every way. The HSI/SA combo is faster (for me) and provides more info than the HSD - though I don’t know how complete the implementation of either of these is currently. The Hornet’s AoA capability is both a powerful weapon and an alluring pitfall; the ability to point the nose and drag an opponent into a slow fight is scary when properly executed. Simultaneously, when abused or overused the AoA and corresponding bleeding of energy can be very dangerous to the Hornet driver. I prefer attack missions (off of a carrier, but I’m willing to forgo that for this conversation) but maintain enough skill to tangle with anything DCS currently offers in a BFM scenario. BVR is my weakest point, but also the one that I practice and enjoy the least. The Hornet’s radar quirks make it significantly more challenging in multi-threat BVR engagements and paired with less kinetic energy I do believe the Viper has an edge in BVR. That said, the datalink and RWR displays (SA, JHMCS) give incredible situational awareness when engaged in any AA arena. I firmly believe the array of weapons available to the Hornet are also superior, to the point that I get irritable in the Viper when loading/rearming. I can rarely accomplish quite what I want to, or end up loading the jet down and spoiling any energy advantage. I would love the dual maverick ejector racks on the Hornet, but that’s the only edge for the Viper (for me).

I’m now getting DCS crashes with vrperfkit installed after the most recent DCS update, which is disappointing. Anyone else seeing issues?

Is anyone willing to break down the install process of the VR Perf Kit? I have downloaded the 0.2.2 release and can copy the .YML and .DLL specified in the README to the DCS folder, but the portion below I don't understand. Any assistance would be appreciated, I'm just way behind the power curve with technology. ## Build instructions Clone the repository and init all submodules. Download the [Oculus SDK](https://developer.oculus.com/downloads/package/oculus-sdk-for-windows) and extract `LibOVR` from the downloaded archive to the `ThirdParty` folder. Run cmake to generate Visual Studio solution files. Build with Visual Studio.

Following up on this - my issue is that I had downloaded the main GitHub repository as opposed to the release zip. Fail on me.

Deleted. I did notice that the main directory name changed, and also I didn’t replace the keybind doc.

After installing 1.1, when I load the aircraft in a mission I have no cockpit; only gauges. The helo will also fall through the ground, unless I catch it with collective - from there it flies as expected, Just no cockpit visible. Ideas anyone?

The real Hornet is actually renowned for being easy to fly, as are most modern fly by wire aircraft.

It only works with the HMD, but with HMD blanking disabled the HMD symbology and thus Link contacts are visible in the HUD also. A bonus is that HACQ and LACQ are also permanently HMD slaved and no longer snap to the HUD.

@Jayhawk1971 is there any terrain and elevation detail in the NTC area currently? I’ve not explored that area, but both NAWS China Lake ans NAS Fallon have pretty decent detail already; albeit not an airfield. For Helos one could easily place a FARP.

Here also.

@Gripes323did you share that video publicly? I’m tinkering with the HMD now and would be interested in seeing it.

Bringing this back from the dead, does anyone know if a preferred ‘default’ HUD and JHMCS configuration could be saved in a config file, in the same way as CMDS profiles are currently ‘saved’?

If you’re nose-on to the bandit, the HUD blanking or boresight transition may be your issue. I personally shut off blanking and push MIDS display to 100 miles immediately upon startup. Doing so allows you to see MIDS tracks through the HUD, cockpit, etc; much better for SA in my opinion. When HUD blanking is turned off, the acquisition circle stays aligned to your helmet, as opposed to jumping to the HUD.

There are too many factors to just say “Max G”, or even add in an airspeed. Take a recording or track and we’re happy to help. The radar isn’t perfect right now, but what you’re describing is clearly an issue. The Hornet can hold its own in a turning fight with anything in DCS currently, if flown properly. The AI opponents do use a simplified flight model, but are by no means unbeatable.

Just an FYI...describing sounds is both tough and subjective *but* most people in the Hornet community use “deedle deedle” for the master caution advisory tone. It was mentioned above as well but just to avoid confusion. When examining the HMD or HUD and looking for critical/lethal RWR indications you’ll be looking for a longer “leg”. On the EW page, the threat emitter will have moved to an inner ring on its approximate line of bearing. Edit for clarity and spelling

RWR queues can be displayed in the HMCS (automatically enable when HMCS is on), HUD (EW page > box HUD), and SA Page (SA Page > Sensors > RWR > All, Crit/Leth, Leth (iirc)). There's a great kneeboard set in the user files that contains listings of all RWR queues and what emitters they correlate to, if that's your question.

For what it’s worth OP, I never bother with the wingspan setting despite being aware of it. I’m not a BFM junkie or gunfighter, so it has to be a bad day for me to even get to guns. That said, I do train to it and enjoy it occasionally. Learning to predict other aircraft and process symbology are key. The biggest thing truly is learning how to fight the Hornet to its strengths and weaknesses, and specifically when and how to use the AoA/nose pointing ability.

Long-standing thing, may be related to the TGT issue. They’ll typically return quickly, but hopefully it’s fixed at some point.

The link below is to an open-source document published by the University of Tennessee, and contains a wealth of information on the ACLS/Mode 1 system and use. https://trace.tennessee.edu/cgi/viewcontent.cgi?referer=&httpsredir=1&article=1356&context=utk_gradthes

Good to know I’m qualified for the DCS Apache.