Rob

Interested to see these videos if you have the links handy, I did a quick youtube search, and haven't found anything that unambiguously shows altitude, pitch, airspeed, etc.

That loft bombing in the video at 2min 20sec is great.

Please see the attached track. Order of events: 1.) Drop MK82 in CCIP, and show that it creates a target point. 2.) Undesignate to hide the created target point 3.) Fire rockets in CCIP, no target point created 4.) Fire gun in CCIP, no target point created Attached screen shots: shot01.jpg: Target point created after CCIP release of MK82 shot02.jpg: CCIP release of rockets, no target point created shot03.jpg: CCIP fire of guns, no target point created (not sure if working as intended or not, included for completeness) shot04.jpg: Screenshot at 1m48s of VMA-542 video prior to release, CCIP line up before firing rockets, no target point shot05.jpg: Screenshot at 1m50s of VMA-542 video after release of CCIP rockets, target point created Am not sure about the gun and CCIP target point creation, included in the track for completeness. AV8B_Rocket_CCIP_Target_Creation.trk

While I don't agree with with the delivery or tone of the message by the OP, I have a similar sentiment about the stability of the AV8B. In the 10 or more years I've been playing DCS, since purchasing the day-01 release of the Russian-only Ka-50, I've never experienced so many straight crashes in DCS, nor experienced such inconsistent and frustrating behaviour as the AV8B. At the risk of being crass and over-simplifying, I suspect that testers take hot-start jets, "test the $weapon once", and then call it done, and tick off their item in the bug-tracker/JIRA/whatever task managing software platform is used. Meanwhile us as users are flying more complex sorties and dropping a multitude of weapons and exercising the navigation system/EHSD/sensors more, and so experience more problems. Since I don't have a 15-second track or an exact bug report I accept that my comment will be dismissed. I don't care. I just want to express that the sentiment by the OP about the AV8B are felt by many virtual pilots in the community.

Thanks, I did a clean and repair and it no longer happen, I've never had cockpit or similar mods installed, but I should have done the clean/repair before posting. I have another bug posted about cycling waypoints with NSEQ boxed and a TERM waypoint set that continues to crash after cleaning the MOD folder and doing the full clean/repair. Would someone be able to see if they can recreate? Cheers, Rob

Hello, I can reproducibly get DCS to crash when cycling through waypoints in the EHSD, with NSEQ boxed, and a TERMINAL (TERM) waypoint selected. To reproduce: enter DATA mode, box NSEQ, using the Option Display Unit (ODU), press TERM, using the UFC keypad enter 4, Enter. Return to the EHSD by pressing Data, rebox NSEQ, and press the OSB buttons to cycle forwards and backwards through waypoints. Because it crashes, there is no track. Here is a video of a crash. Here is a video. It only takes a few seconds to test yourself and recreate. Attached is the .miz file that I was flying. It contains a single air start AV8B carrying JDAMS with 6 waypoints programmed in the mission editor, and some unarmed transport targets. dcs.log also attached. Once again, there is no track produced by DCS because it crashes, so I cannot add a track because there is no track to add.

Hello, I can reproducibly get DCS to crash while flying the AV8B and pressing the "DESG" button in the EHSD. It's happened on multiple maps, both cold start, hot start, air start. No mods. Because it crashes, there is no track. Here is a video of a crash: It's a hot start aircraft with 5 pre-programmed waypoints. As the EHSD is shown by default, just click the Left OSB 1. Attached is the .miz file from above. A single AV8B on NTTR carrying JDAMs, a bunch of Transports. Also attached is the dcs.log Once again. There is no track produced by DCS because it crashes, so I cannot add a track because there is no track to add. JDAM 02.miz dcs.log

Neither Fravor's aircraft, nor his wingmans were equipped with a pod for the incident. The video was recorded by a follow-up flight.

What sound settings do you have checked and what do you have your sound sliders set to? For example I have "hear like in helmet" checked, and the cockpit and helmet sliders down pretty low, and when I get in the aircraft I turn the AC/Defogger or whatever slider back to reduce the sound a little as well. Play around with these and you might get the sound more to your liking.

He tried, but the flight model was wrong

though USMC and not USN:

To me this seems like building in some deadzone automatically into the Auto Pilot mode in the hornet rather than into the control input curves is one of those seemingly minor changes that have a large quality-of-life improvement to the game. While it may not be the way that the real hornet behaves, the real hornet also isn't being flown with a huge variety of consumer grade joysticks in a variety of different physical setups. There are a lot of similar instances where we have to sacrifice 100% fidelity to allow DCS being a computer game running on a variety of hardware. Trimmer behaviour in helicopters, or the Hornets HMDs transmitting only into a single eye for VR users come to mind for instance as examples.

With a target in STT lock you are unable to silence the radar or enter the SIL sublevel by pressing the SIL OSB. Track file attached. Version: 2.5.6.49314 Cheers, Rob F18 Radar unable to enter SIL from STT May 26 2020.trk

Hello, On the ground in a hot jet with weight on wheels, the maltese cross displays on the radar page, but the scan indicator is going back and forth, new hits/bricks will display on the radar and the radar can enter STT mode. Track file attached. Version: 2.5.6.49314 Cheers, Rob F18 Radar STT WOW May 26 2020.trk

Off the top of my head: - APU switch will automatically reset to the off position after the engines have been running for two minutes. - Fuel dump switch will automatically move to the stop position once Bingo fuel has been reached. There are probably others.

Hello, Just getting started with VoiceAttack and VAICOM PRO, have licenses for both, really smooth installation and setup, and excellent documentation, thank you. I'm trying to call in with the JTAC with Vaicom, it's working fine, but the only thing is it does not read back the 9-line, it just posts the text in the top left corner of the screen. If I call in to the JTAC using the keyboard comms menu (ALT+/, F1, F2, etc), the JTAC reads back the 9-line in full in it's emotionless computerized voice. Just wondering if anyone knows how I can get the 9-line audio read back with Vaicom? Cheers.

Yeah, I guess it's the case that if you fully run out of fuel then that airframe is borked and you'll need a new one

It could be given an entry to deploy or stow the ladder in the ground crew radio menu, just like wheel chocks, ground electrical power, or ground air supply.

About 8 months ago I picked up a 32" curved 1920x1080 monitor, and I have to say, I love it. https://www.samsung.com/us/computing/monitors/led/samsung-32-curved-led-monitor-lc32f391fwnxza/ I'm probably in the minority of people who sought out a large size monitor at such a low resolution, but the computer is pretty much only used for DCS. The combination of the large size and 1920x1080 resolution make spotting fairly easy, though sometimes I think that the HUD and DDIs could be sharper if the monitor was a higher resolution.

Yeah, something sounds fishy. Did you confirm that they actually loaded on new stores on the pylons for you? just no fuel? They don't start loading the stores until the fuel is finished loading. Wonder if maybe it had to do with Easy comms being enabled that you were still able to talk with them. The IEFI only shows RPM and temp on battery. You could have tried calling for external power, and using the external power panel: 1. External power switch - RESET, then Switch 1, 2, and 4 - B ON (hold each for 3 seconds), though I'm not 100% sure if that would show you the fuel level until the APU is started though. I want to play around with cold starting on the ground now to see exactly how/when you can talk with the ground crew with/without Easy comms on now.

The AWACS calls it's bullseye calls relative to the bullseye for your coalition that was placed using the mission editor. AFAIK there is no way to verify what this location from within the cockpit of the hornet. There are a few ways to figure out what the bullseye location is though: - The mission creator may have placed the bullseye in the mission editor to correspond to a pre-programmed waypoint in the hornet, then can just use the A/A WPT on that point. - The bullseye might be available in the mission briefing information provided by the mission creator. - You can use the F10 map and visually find the bullseye location on the map, you can then get the latitude/longitude coordinate of the bullseye, enter in a new waypoint using your HSI->Data page, and then set this new waypoint as the A/A WPT.

If you've run out of fuel, then I believe that there is no GEN power to run the radios, so they don't hear you. If you can lift up the canopy it should work.