Livers

I'm in step with @-0303- 100%, meaning the described behavior is what I see. I wouldn't know if I have an emoji problem, I try to ignore graphic fluff to a large extent. My own hunch is that it rears its ugly head when there are a large amount of quotes and/or graphics on the incoming page. @Flappie, that link for 'instant search' is ancient. Is that still a thing in a current browser?

My setting is to "Take me to comments I haven't read", yet it seems to want to take me to the bottom of the next page vs the top. Firefox latest. Very annoying.

"Fixed front armour M1A2 Abrams." Anyone have a clue what this means?

@Elphaba, FWIW, I see the same with vehicle movements. Very erratic, and doesn't always do it. Usually, the lead vehicle will creep forward some random distance until it hits a tree or building or something times out and it finally stops in a random orientation. I see no way to produce a track that exhibits the behavior consistently. Just a small rant - every time I see changes to the path finding, it gets worse. Consistently. I feel your pain.

Is it map specific?

Agreed. An AP or HEAT round should do a bit more than start a fire. They should blow through a treeline like they aren't there.

Agreed, single player here.

Not a problem, latest 2.8 Beta. In this one I conclude with an echelon left to demonstrate the difference better. Abrams_column_movement.trk

Yep, F2 view randomly does a complete hang for me. Logs say nothing, they just stop.

That is nearly a 3 year old blog post - what prompted the DCS change now?

As far as I'm aware, rearming will not start while the vehicle is in motion. The time needed depends on the vehicle and the ammo type being loaded.

And that is the difference we are talking about. What changed, Windows or DCS?

Why is that a better test? How is an application running full screen when the volume function overlays on top of said full screen? As far as the G-sync indicator, I see nothing functionally different - the indicator was always there, for me.

Well, I respectfully disagree - DCS was fine for a lot of users until this latest patch.

How is this the solution to the OP?

I'm on Windows 10 and 11, 2 different machines. Neither will enter Full Screen, either with the shortcut (Alt+Enter) or selecting the Full Screen option under Options. Both machines use Nvidia cards with G-Sync enabled, no V-sync. Identical drivers, though of some vintage. It's changed behavior, and I miss the option. I don't Alt-Tab at all, and there used to be an FPS advantage. Maybe that has changed, but how can we tell?

I'd call it a bug, the setting is still in the Setup, but does nothing. If deselecting in the setup cures a CTD for some, they have their workaround. I want the functionality back that worked fine for me. @BIGNEWY ?

At mission start, vehicles in a column group start smoothly and advance to a waypoint. If then given a 2nd waypoint and speed, they go into what I call Slinky mode, where it takes quite a while for all units to reach the desired speed and tighten up the group. Not shown in the track, is when given an echelon right or left formation they do not exhibit the slinkyness action. Why the disparity? Using the Abrams here as an example. Abrams_column_movement.trk

HighDigitSams mod required...

I've no experience with the Predator, so I can't speak to that. You may be right about too high for target detection, I've never tested that but I'm sure there are limits. My missions using the Reaper have them at 7500' to 10000' with good effect, and not knocked out of the sky by everyone with a MANPAD, or sniped by a tank. How would you expect a Reaper (or any aircraft) to defend itself in the pattern?

My suggestion is to fly higher and slow down. I don't know the real life capabilities of the systems, but at 3000' you are any easy target. At 8000'/170 knots, not a problem with those targets.

Fixed in the latest patch, thanks.

Right, that is the loadout that does work. Not as accurate, but has a big boom factor.

Thanks Flappie! I never gave it a thought that lasing might be the common cause.

Attached is a track with 3 Reapers with various loadouts, attacking a mix of random targets at Batumi. Of the 3, only one will engage. Can someone spot my error? This is new behavior in the latest open beta, BTW. Reaper_test_2.trk