mrkline

In some situations, AMRAAMs go pitbull, begin to pull lead on their target, then suddenly stop all fin deflection, flying a 1G arc into space. I can produce this reliably by firing an AIM-120 from a Hornet in STT and turning cold. Expected behavior (for a lost track) is for the missile to fly towards the last known intercept (extracting from the target's last known position and velocity), then turn on its seeker and attempt to intercept whatever target it finds. This bug isn't a case of the target being outside the sensor field of view - you can see it begin to maneuver more aggressively when it goes pitbull, then suddenly stop, even though it has the energy and angles to consummate an intercept. It's also unrelated to previous discussions about AIM-120 notch or chaff resistance - the target is in a hot aspect when the missile goes ballistic, and it doesn't home in on a chaff bundle. Track & Tacview attached. hornet-amraam-double-miss.zip

HUD designation in the Hornet is not only very sensitive (compared to cursor slew rate on the radar, SA page, or any other sensor), but the designation point jumps across large distances. In this video, I attempt to slew the cursor onto a target about 120 feet in diameter (a bunker surrounded by some containers and BTRs). Even with small movements on a very precise TDC (a DeltaSim TDC mod with no deadzone), the TD diamond skips over the target several times: https://streamable.com/aih1dt. With the stock TM Warthog TDC, HUD designation is nearly unusable. Compare to actual Hornet HUD tapes: In Jetstream the pilot has no issue making fine adjustments to the impact point while flying a similar dive profile: In Mongo's Gulf War HUD tape, he smoothly scrolls the target diamond across the HUD (almost two miles!) without any jumping: The same clip with a bit of sharpening to help see the diamond (watch the bottom of the screen in the first few seconds): https://streamable.com/uocex2

I expected the addition of AGR to fix https://forums.eagle.ru/showthread.php?t=285795, since an accurate slant range from the radar should give an accurate CCIP pipper or AUTO release parameters. But the issue persists. CCIP bombing set in 1973 falls 350-400 feet of the target, reliably. CCIP in 2010 is accurate. Attached are missions (the only difference between the two is the date), and several tracks and ACMIs for both. agr-ccip-inaccurate-by-year.zip

I have no idea what INS would have to do with the CCIP impact point, though. (And even if it was related, how would the INS drift sufficiently 30 seconds into an air-start mission?) I assume that until AGR ranging is implemented, slant range is just calculated with a raycast.

I took the Golan Heights BAI mission for the Viggen, swapped in the Hornet to practice dive bombing, and noticed that my bombs were consistently falling about 400ft short. I don't have this problem in other missions, so on a hunch, I changed the year from the 1970s to the 2010s and bombs landed right on target. Attached are video, mission files, ACMIs, and track files. In the first three runs, the year is 2010 and bombs land right on target. In the last three runs, the year is 1973 and the bombs always fall short. All runs use Mk. 83s and have no wind. https://streamable.com/gcugwn Edit: This definitely seems Hornet-specific. I can't replicate the problem with any other aircraft I own that can carry dumb bombs (A-10C, AJS-37, AV-8B, F-14, JF-17). ccip-test.zip

In the Viggen cockpit model, there's a rectangle outside the cockpit - left of the SPAK light - that glints in the sunlight: I can try to capture some video of it later if needed, but as you can see in the image, it's not a soft reflection that continues to rotate around the canopy as the angle to the sun changes. It has hard edges where the reflection suddenly stops. Edit: This seems to have come up in a previous thread as well: https://forums.eagle.ru/showpost.php?p=3775309&postcount=7

Vjoy isn't a factor - the config I fly with has all of those axes unbound, and I have the same issue with the driver disabled. There's only vjoy bindings in the first screenshot because... That's exactly what the first screenshot shows - I'm able to reproduce it with TDC Y -> DLC as the only custom bind.

So, the bad news is that this bug is still present in the current OB (2.5.6.45915). The good news is that I was able to isolate it a bit more. With the only binding change of mapping the DLC axis to my TM Warthog throttle's TDC: The pitch axis is disabled if and only if I launch the game with TrackIR running. With TrackIR, the row is red and the pitch axis doesn't function: But if I launch the game without TrackIR running, pitch works fine: To reiterate, this bug is unique to the Tomcat - I don't have any other axis bind issues with any other modules (A-10, AJS-37, AV-8B, F-18, JF-17, Mirage, FC3...)

In the current DCS Open Beta (2.5.5.41318 ), the JF-17 aircraft body doesn't seem to mask laser designation. In this clip I loft a GBU-12 in the CAS instant action mission. Despite intentionally masking the tpod and laser for most of the bomb's flight, the bomb hits its target. (Due to bang-bang guidance, an LGB should miss badly if the target isn't continuously painted all the way in.) Clip: Tacview: https://drive.google.com/open?id=1Q8zjMS-HuqxxFRPRUc46TD7PqrF2Ijt2

Awesome news! Can we expect fixes to the in-cockpit engine sounds as well? Like we discussed in February, there's some nasty looping effects.

VJoy. I see the same behavior whether it's populated with the default binds (as shown in the picture) or whether I clear all axes from that virtual input device. It's worth noting that I never see a similar problem with any other plane, or any other axis - just the Tomcat pilot's pitch. (RIO HCU is unaffected)

I wouldn't be surprised if it was exposed by my particular hardware setup somehow (Warthog throttle, WarBRD base + Warthog stick). But I can reproduce it reliably, even after clearing out my old input files in Config/Input/F-14B.

For the entire lifetime of the Tomcat, I've had issues where the pitch axis stops responding and turns red in the controls menu: Previously this only happened when a joystick (or TrackIR) was unplugged and replugged, but things got worse recently. In the current OB, the pitch axis is disabled any time I start the game with the DLC axis bound (to my throttle's TDC vertical axis, for what it's worth). If I delete that binding and restart the game, pitch works again. The only difference in the Lua file is as follows: diff --git a/Config/Input/F-14B/joystick/Throttle - HOTAS Warthog {F4D9B430-8AD7-11e8-8002-444553540000}.diff.lua b/Config/Input/F-14B/joystick/Throttle - HOTAS Warthog {F4D9B430-8AD7-11e8-8002-444553540000}.diff.lua index 9880e10..634882c 100644 --- a/Config/Input/F-14B/joystick/Throttle - HOTAS Warthog {F4D9B430-8AD7-11e8-8002-444553540000}.diff.lua +++ b/Config/Input/F-14B/joystick/Throttle - HOTAS Warthog {F4D9B430-8AD7-11e8-8002-444553540000}.diff.lua @@ -8,6 +8,14 @@ local diff = { }, }, }, + ["a3083cd57"] = { + ["added"] = { + [1] = { + ["key"] = "JOY_Y", + }, + }, + ["name"] = "DLC / Maneuver Flaps Retract", + }, }, ["keyDiffs"] = { ["d177pnilunilcdnilvdnilvpnilvunil"] = { I do not have any controls mods (e.g., the front-seat LANTIRN mod) installed.

The "Air-to-Air CAS" instant action mission is some CAS mission where you start with rockets and LGBs. I assume some of the instant actions just got mixed up.

When approaching a target for a waypoint/toss release (weapons knob to Luft/RR, Master mode to NAV), the following assertion trips: Weapons config: Sample mission attached - the game crashes reliably as you approach the target. Viggen-SEAD-bombs.miz