Nealius

Is there something specific that needs to be done so that certain aircraft appear on datalink? I've noticed that C-130, KC-130, and helo AI do not appear on datalink like they used to.

This seems to work fine for me. I have groups marked as "hidden on map," but I can still cycle through them in F2 view.

I'm working on a sandbox mission with a whole litany of random triggers, and one task in particular is driving me nuts. It should be rather straightforward: 1. F10 menu rolls random: pickup at LZ marked on F10 map. 2. Part of group from client CH-47s at Bastion enters 2nm trigger zone, blue infantry, red infantry+fire at point, and green smoke are spawned. 3. 10 seconds later, A-10 CAS support spawns and takes out the red infantry. A-10 is set to CAS, search and engage group "red infantry" with guns, if flag is true+"red infantry" dead, AI push task to switch waypoint for RTB. Here's where it gets weird. If I skip the F10 menu and do a timer-based trigger, with an AI CH-47F entering the trigger zone, everything works as it should. If I fly it as programmed above, with the F10 menu selection and a client CH-47F, the A-10 ignores the CAS tasking, the search and engage group tasking, and doesn't honor the group dead=switch waypoint programming either. It flies off without firing a shot. The only two differences between it working and not working are: A. Client CH-47F group instead of AI CH-47F group B. Task triggered by F10 menu random flag instead of time more than x-seconds Can someone take a look at this replay track showing the erroneous behavior and see what's going on, because I'm lost at this point. I set up a failsafe that explodes the offending infantry if they're still alive after some minutes, but ideally I'd like the A-10 to do it's job. The mission is a mess of triggers, but this one in particular is the set of 8 triggers labeled "Bastion-CH47-2" under the pink marked Bastion-CH47 F10/random flag headers. Big track file (AI voicelines): https://we.tl/t-Fg5scD2Z1J

Titled by how much what? Degrees? Percentage? Arbitrary unit?

For me I've maped, in adition to cyclic and power: -Trim -Trim reset -Chaff/flare -Steering knob L/R -Eng Cond levers up/down -Ramp up/down

Has anyone figured out how to taxi this thing with grace? I'm constantly getting into ground loops, having it turn the opposite direction I've fed in via the steering knob, having it refuse to respond to steering knob inputs, etc., with a left-turning tendency in general.

10 minutes for the rotors to stop (actually timed it).

They're still en route from the Indian Ocean.

I have encountered a sudden need for a lot of left cyclic when coming into landing, presumably to prevent a slide to the right, that isn't present when getting into an IGE hover from the ground. But it's intermittent for me.

Check the frame lifted from this video clip. About this distance from a Tomcat, the normal texture changes to this odd thing, causes a bit of a system stutter, then goes back to normal. Running textures "medium" on a 4070Ti Super. Any idea what causes it or how to mitigate it?

This is basic module functionality that is game-breaking in daylight, poor weather ops. 1 mile 5 miles 10 miles (the point where you should be visual on a CASE II) And we're still getting a CASE II in CASE III weather. SuperCarrierDebug.miz

Still not fixed. Dump is also not visible on other client aircraft online.

My nose attitude changes without any collective changes. Same TQ % and the nose still takes a dive.

This is supposed to be new? It looks like low-resolution steam sprites instead of the actual particle smoke we used to have. This is a regression not only from the more realistic no-smoke, but from the smoke we used to have as well. The steam from locomotives on Normandy and Channel maps look better than this...

That's more manageable, but still, it's not reasonable for us to need so much 3rd party peripherals in addition to basic flight controls and headtracking just to do basic flying.

As in, stay on 30 and press TMS-up, and it will go to 26 and overwrite? I've been manually selecting, say 26, and pressing TMS-up.

I've seen reports of issues with ship smoke in ST but not in MT. For a while we were missing the black, whispy smoke we used to have, but since the July update we have a very poor-quality white smoke now. Is it just me? I've removed mods and done slow repair, but still weird smoke.

I may have gotten it once or twice. Usually if VAICOM fires the shore-based comms I get a "fly heading blahblah blah" for the carrier.

Yes mine was in the default English version.

Same at Kandahar heliport.

Same here on a Warthog wth 20cm extension. Set attitude for level flight, press and release trim button, release stick to neutral. Attitude holds for less than 5 seconds before the nose starts to down or up, at an exponential pace if not immediately corrected. It's impossible to do any admin at all with switches/MFD. Using the same trimming technique in the Huey, Hip, and Hind, I can go 100% hands off for at least 1 minute, and any deviation after that point is minor. I've never seen such an extreme nose-down tendency after trimming in any other helo modules. Typically for me it's nose-down, but occasionally it will go nose up.

I have enabled dynamic cargo. Anything larger than the three items I mentioned, and the one doedkoett mentioned, refuses to load in the cabin due to size.

Can't use sim-shaker equipment without getting complaints from the apartment downstairs. Nor the space for a giant racing rig in a 30sqm living space. Solutions like thes are only valid for detached home owners.

Nearly every real-world helo pilot, DCS SMEs included, who is active on various DCS-related social media content, has stated that VRS is overdone in sims. Not sure why this is still debated.

Is embark broken for client aircraft? I can get it to work for AI just fine, but as a client there's no "embark" option under the F7-airborne troops menu. EDIT: Disregard. It seems the type of vehicle must be selected. If left on "any" it won't work with client aircraft.