Nealius

Real pilots feel the yaw happening in the seat before they see it happen visually. All we have is a visual cue. Once the brain realizes there's movement, the movement is already established. That's why they fight it less than we do. For us it takes repetitions to predict what the aircaft will do and proactively counter things before they happen. I just tested slamming throttle IDLE to MAX in the Spit. She did a 90-degree roll to the left (would have done more if I didn't stop it) with the slip indicator pegged full right. So I don't know what this lack of torque claim is about. Maybe it's not strong enough, but it certainly is there and something that needs to be dealt with by the player.

No. These are instantaneous movements caused by throttle and/or RPM changes. Speed changes have longer dwell time, and in formation flying we're talking speed changes of +/- 1mph or less. They're extremely noticeable in the Spit. Less so in something heavier like the Mustang or Jug.

I believe this one may be backwards. Testing today, TMS LEFT cycles threat tables (implemented), but TMS RIGHT cycles selected threat (missing).

That's true in DCS, though. Are you sure you don't have game mode or something turned on? Every power change I make in the warbirds requires rudder and aileron adjustment to deal with the change in torque. Formation flying in particular.

Evidence PM'ed, though a chat would SMEs would be great as well, since evidence alone provided by users often gets dismissed for arbitrary reasons.

The Spit has never given me too much trouble in terms of torque, but the K4 and A8 have gotten me into trouble on numerous occasions with a stall/torque-roll to the left on takeoff.

I'm surprised Isoko hasn't started on a GSDF livery yet. I suppose most are waiting for the official template.

The M60 struck me an odd choice as this isn't a Vietnam-era bird. Did the US Army use the M60 at all post-2000? Wikipedia says the M60D has been replaced by the 240H in US service.

The torque is certainly there, it's particularly noticeable on lighter modules like the Spit and K4. Is it not modeled strongly enough?

Is it meant to simplify that action? Currently you could (or should, haven't tried recently) achieve the same by telling the group to expend x-rounds then switch to next waypoint.

Pop-in affects the targeting pods as well, making things a bit too easy. If you're 30nm away or so, you can find vehicles and infantry easily because the trees and buildings aren't rendered until you get closer.

In my experience, part of the performance problem is from the absurdly huge 4k textures on some modules eating up more VRAM than they should. Reducing them to 2k via paint.net and repacking them into DCS has solved some of my issues, but not all of them.

A couple updates ago we got four "Light Rain" presets which are nice, with better visibility and small pockets of rain, but the cloud coverage is still too dense for sunshowers and squalls.

Don't know what to say other than during the winter period when I was exclusively flying the Viper, I messed with XMIT 1 and 2 in MAN mode to see what they did and they came on just as XMIT 3 did. But feel free to continue gaslighting me into thinking I'm imagining that experience.

I haven't found the Spit to be bouncy at all in 3-pointers or 2-pointers. The only time I've gotten bounces has typically been 3-pointers where I misjudged my flare.

False. Back in February XMIT 1 and 2 worked in MAN mode. Now they do not. They only work in SEMI and AUTO. That's what changed.

I understand CASE III starts "30 minutes before sunset," but either the carrier doesn't seem to follow this, or the Navy definition of sunset is different than the civil definition. E.g. sunset for Marianas on 25AUG2024 is 18:37, so I would expect CASE III to start at 18:07. However it does not. When flying, I got CASE I instructions when calling in at 18:15. Trapped at 18:20 and had NC grade because it apparently switched to CASE III while I was in the pattern. Testing without aircraft in the pattern and time acceleration, the carrier lights--which I assume in DCS signals CASE III--came on at 18:32. I couldn't find anything about a nautical sunset time, only a nautical twilight, which doesn't seem to apply here. When does the module make the switch to CASE III, and how do I figure out what time this occurs via the mission editor when it doesn't seem to follow the 30 minutes prior rule, nor appears to be consistent when testing same date on the same map. EDIT: Doesn't seem to help that official documentation disagrees on CASE III timing as well. CNATRA says "between 30 minutes prior to sunset to 30 minutes after sunset." DCS-focused comunity documentation written by former Charlie drivers and former/current Rhino drivers agrees with CNATRA. CVNATOPS says "one-half hour after sunset and one-half hour before sunrise." The latter sounds odd for CASE I considering the low light conditions.

A few updates ago the way the jammer works changed and I haven't figured it out myself. Sometimes I can get it on and sometimes I can't. Previously it would work with the switch in any position 1-3 and CMDS knob in MAN, but now it seems to only work in SEMI or AUTO modes. I'm probably describing it poorly as I can't recall the switch names; my spatial memory focuses on where they are not what they're called

No idea. All I know is I had JTACs that I specifically had to adjust because trees were blocking their LOS when I first built the mission. I tested them all before the hotfixes, they all worked. I tested them after the hotfixes and they immediately called "no further tasking." Upon investigating in the ME, there was now a forest or orchard blocking their LOS that wasn't there during the pre-patch testing. Here's one from my older mission build where trees seem to have been added. The JTAC had a clear LOS to that target when I placed the units. The orchard to the southeast of the target wasn't there before. The trees to the east were there, but they didn't extend so far southwest as to interfere with LOS. In this one, I don't recall if the trees were there before, but I do recall playtesting this task and JTAC had no issues due to the 80+ft elevation over the target. Now for whatever reason these trees interfere with LOS, whereas before they did not. Barring new trees sprouting up, the only other reason I can think of is some JTAC logic change where it's targeting a different unit than it was before. Especially in the first pic, there's a narrow LOS window to a couple units in the middle that they could have been targeting instead.

I've had to do many dead-stick landings after a MANPADS hit shredded my fuel tanks. Insta-kills seem to be for anything larger than a MANPADS warhead.

Will the introduction of the Sniper XR remove the LITENING from the module entirely, or will we still be able to equip it to simulate non-US users like how we can simulate non-US Hornets with the option of LITENING as well?

I haven't been able to reproduce the crosswind, but I have seen similarly odd wind speed and direction shifts on the same approach. It seems like it happens when the 33ft and 6600ft winds are set to the same direction. If you set them 180 off from each other the wind direction/speed is more consistent.

Per -34, when auto-lasing the laser should automatically stop lasing 4 seconds after estimated impact time. In attached track you can see the laser continues to fire for up to 30 seconds after estimated impact time, only stopping when approaching the pod's masking area. The only way to stop the auto-lase is to cycle the laser switch off and on, which is not listed as a procedure item in the DCS F-16 manual for LGB employment. Other modules utilizing LITENING also have laser auto-off after x-seconds of estimated impact time. Looking at up to 2 years of YouTube tutorials, this seems to have been a long-standing issue. Perhaps it was just never added after the auto-lase feature was rolled out? Auto-lase-time.trk

Recent hotfixes added more trees to areas of the map; didn't see it mentioned in the changelogs. Any mission builders out there should double check your JTAC placement, as I had a couple whose LOS became interrupted by those new trees.

Both the airfield AND the heliport must be blue for the ground crew to work. Same at Kandahar. It seems to be an Afghanistan issue, since the ATC/AI traffic also has issues with the combined airfields and heliports. They're treated separately in the ME, but the ATC/AI treats them as one.