Nealius

I just experienced this today, but not sure if related as it was the entire SPI jumping to a point 130nm West of my position, rather than just the TPOD jumping. CZ would place SPI back on waypoint, but a second or two later it would always jump back to this strange point 130nm away. TMS-down would put me back on STPT, then suddenly jump to mystery point. I tried designating new SPI via JHMCS and HUD, however those too would jump to the mystry point after a second or two of designation. I never got it resolved.

I set both gradients off and added a 20 curve to roll for my 20cm extension. With both off and no curves, the roll axis was way too sensitive for me. So I'd say it is indeed safe to use curves with gradients off.

Syria, no scripts, no mods, no dynamic slots. Client replay fails to load. Server replay loads normal. Flown the same mission three times and 2 out of the 3 replays work fine. Only one of them is busted. No common denominator on what causes the load fail. Server track (works): https://we.tl/t-QrbnG5PVIB Client track (broken): https://we.tl/t-k8J4nE2T2P

The past couple of weeks, I've noticed DCS gets stuck on "Logging in..." for up to five minutes. Checking my internet speeds during the login process and all is fine: down/up speeds all in the 80s or 90s. The log doesn't indicate any connection issues. Log always stops at "device hotplug disabled," then 4-5 minutes later finally finishes the log in process.

Is airspeed to DISS required at present? For many months it was bugged and not required for the moving map.

That's a useful system. When did this get added to DCS?

The Master Arm switch in the Viper--and nearly all switches in the Hornet including air refuel--function as an "on-else-off" switch. Physical controller switch goes up, virtual switch goes up. Physical controller switch goes down, virtual switch goes down. However this does not work with the Viper's air refuel switch. The virtual switch stays up when setting Physical controller switch down. Air refuel switch should follow the standard of other switches, and other modules, and be more appropriate for use with physical controllers 2-way switches.

Oh nuts forgot I had those Saved Games mods; however those have been on in previous version where there had been no gear strut issues. One thing I noticed, however, is that the struts compress once turning on the APU.

Non-issue in DCS; not that it matters as I already stated you wouldn't even be doing that if landing roll distance is a concern, since you would do the standard "Navy plop" as I like to call it. Those citations still have not said anything about flared landings being prohibited. Now if we're going to be pedantic about full-aft stick versus full-aft deflection, sure.

Bumping this to add that we need the current true/mag display for the ruler in Mission Planner and Mission Editor. Planning happens before the flight, not after (in F10 map).

Problem was between the stick and the seat. I had the steer switch set to "unlock" instead of "steer." On another note, is the central trimmer messed up for anyone else? Before the update, pressing trim and releasing physical controls would keep the virtual controls in the desired position, but now the virtual controls become centered as well. Also on the controls indicator. Trim reset also doesn't appear to do anything anymore.

Board out and full aft stick typically resolves that problem, but if landing rollout is a concern you’re not going to be flaring anyway.

Ran another one. Landing in the grass okay. Landing on Andersen taxiway and the struts stay extended, attempting to taxi results in sliding all over the place. I hover-taxi to a parking spot. Struts still fully extended. Upon shutting down the engines, the struts finally compress.

Got a weird one. I'm assuming I somehow broke something by mishandling her, but I don't know what or how. Starting off at Andersen, taxi out a bit and take off normally. Do some practice approaches on the North Field runway with LHA deck markings. On first landing maybe I hit too hard? Power lever full down, torque reading 13, reset trim. Struts are extended fully and aircraft bobbles. Second approach, same thing, but this time I ease the stick forward thinking my trim reset didn't work. I somehow lift the tail and stand on my nose. Come back to Andersen and land on the taxiway I took off from. Struts still stay full extended, bobbling. I add power (about 16 torque-ish?) to taxi and the tail comes up. Forgot to turn of the AFCS, so I turn it off and try to taxi again. Now I'm spinning anti-clockwise and don't understand what's going on. Track is a bit long but should show the problem. https://we.tl/t-5TrpMx8iGM

Has taxiing gotten worse for anyone else this last patch? It seems the wheel only responds when I manipulate the steering knob via mouse. Using keybinds or an axis, the steering knob moves, but the wheel does not (yes, switch is set to unlock the wheel).

The only absolute "you don't flare a Hornet" is at the boat.

A second round of uninstalling/reinstalling the module and running a repair seems to have fixed it. No idea why the first attempts didn't work.

How do these axes deadzones interact with the axis tune? For example, I have deadzones set to 3 in the axis tune panel to deal with sensor jitters, mainly for autopilot to work reliably. If I turn these special settings deadzones to 0, I will still have that deadzone of 3 in the axis tune, correct? If I leave the special setting deadzone to the default 4.375%, is that added on top of the axis tune deadzone?

Tried a repair. Tried uninstalling and reinstalling (redownloading) the module. All liveries affected (stock and Saved Games). No idea what's going on.

The flare is the same as in any other aircraft, technique is just different. No pitch input, just add a bit of power to reduce your decent rate. This requires aiming a bit before your intended touchdown point.

Typical use is to roll in on dive angle with CCRP selected, visually acquire target in relation to TD box (it never seems to accurately be on the designated target), press NWS to switch CCIP for delivery. Press NWS twice to go back to CCRP if necessary, or flip the DGFT switch to sweep your egress.

In recent missions on the current DCS iteration the 9X seems stronger against flares, at least against Fishbeds.

Breaking force seems too low for me. I can't maintain a decent taxi speed while staying at sufficient RPM to not rattle the airframe to death.

They're not even in the right place. Those reflections should be showing the aft of the seat and whatever is in that compartment, not the front of the seat. The reflection as pictured would be physically impossible.

Reflections zero, visibility from 4 o'clock to 8 o'clock is trashed by these reflections