Nealius

I had this happen some months ago, but I'm hard pressed to remember which module and how I rectified it.

This is a widespread issue with reports scattered all over the forums. So far the blame has been pinned on "external scripts" or "large track files" when missions without scripts and small track files also fail.

Every aircraft rolls with rudder deflection at high AoA, does it not? And official, period training videos make the same “blanket statement”, so I fail to see the issue here.

4 Mossie engines starting up and purring beautifully without a single tinny .38 racing pistol pop like we have in DCS.

Running at low graphics settings on my 4070Ti Super, the supercarrier causes horrendously unstable framerates, jumping around all over the place from the 70s to the 140s and everything in between. Looking away from the carrier they become more stable in the 200s.

Occasionally I will get a timed-out error "code -28" and get kicked into the ~2 day offline mode. My internet is working perfectly fine--literally playing a YouTube video--as this happens.

Does anyone know a way to mod the CBU-99 into the Tomcats' lua files? For most modules it's as simple as adding the CLSID to the appropriate pylon, however the Tomcat weapons luas seem to follow a different standard; I guess because of the adaptors needed for the Phoenix rails.

Yes. It looks cool, but is unrealistic and causing issues with basic taxiing. In addition to not being able to see deck crew signals on the carrier, on shore it's impossible to see more than 10-20 meters ahead, making navigation from parking to runway, and back, unreasonably difficult. In modules with flatter canopies (e.g. Tomcat) the raindrops pool up on the windscreen completely blocking visiblity of the carrier or runway on final approach.

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.