wilbur81

Fair enough... and, to be fair to them, the average user (probably like myself?) isn't streaming while they play. Regardless, I'd be nice to see a solution for you and the average user as soon as possible. eh..um... VulKan?

This seems to describe, exactly, the reduced-performance-behavior I'm seeing now. I wonder if all the DCS testing is happening on high-end systems so no one in the 'factory' sees an issue?

It's my main display...no additional monitors.

Hey, Nate. Several tracks provided would be super helpful to get a sense of all the factors at play.

G-Sync is a non-player for me as I play on a 55 in 4K TV that does not support it. I flew a cloudy mission today...and at 51 FPS, it stutters in a way that gives a sensation of a kind of 'slo-mo' effect... an effect that could always be eliminated by Alt-Entering before in all the previous O.B.s before the feature was taken away.

^^^ Ditto

agreed... it makes no difference. Additionally, for me... I do not have a FPS drop at all. It is a consistent, rhythmic stutter... particularly when looking at terrain. It's like there's nothing 'smoothing out' the transition between frames. What I need to do when I can find the time (though if someone can beat me to it, more power to you) is this: Film some game play on my screen with my phone (real time) playing the O.B. prior to the patch in question...then hit Alt+Enter to show the difference it used to make. Then, film the screen live again on the new O.B. without the Alt+Enter option to give a sense of what I'm experiencing/trying to describe above...

Agreed. My micro-stuttering is terrible now... with no solution (which the old Alt-Enter absolutely did provide quite definitively before).

Yep... My FPS are exactly the same, but the "slow-mo" stuttering effect is REALLY a frustration that can no longer be eliminated on my system (as it could with the previous usage of Alt-Enter for me).

You might be on to something there. My FPS aren't measurably worse with this new OB situation, but stuttering certainly is and I'm a TrackIR guy as well.

Indeed... and it is probably only a problem for people like me because I have a meagre 1070 GTX card. People with high powered GPUs aren't going to notice the problem, and thus say, "all is good."

What I meant was this: previously (when using Alt-Enter in DCS) Ctrl+Alt+Del would not exit DCS at all...the screen would go black for a split second, and I'd then still be in the cockpit. Now, it goes right to the action select page. Point being: I have a lower end machine by many standards and I needed the Alt-Enter option and would love, like some others, to have it back.

More possible evidence that "Full Screen" is not actually full screen any more: When Ctrl+Alt+Deleting before the recent update, it wouldn't go immediately to the task manager unless I exited Full Screen (with an alt+enter press to exit). Now, Ctrl+Alt+Deleting immediately takes me to the task manager... which is convenient, but I'm now quite a terrain-stutter-fest still without the alt-enter option...

I'm not sure about that. Simple test: When I was in full screen in the past, if I played with the system volume, the volume slider was hidden/could not be seen...when it was windowed, it could, right up in the top left corner of the screen. Now, you can always see the volume slider at top left when I play with it...this was always my little test to see if I'd Alt-entered yet.

This may be, but I've got some significant terrain stuttering that seems more pronounced (which was greatly alleviated with the AltEnter option)... maybe it's just placebo?

Ditto here. What's up with this?

Surprisingly, the Legacy Charlie (unlike the Super Hornet) could get supersonic quite nicely with three full tanks, down on the deck according to Wombat over at Mike's (absolutely excellent) Aircrew Interview podcast: (18:30)

^^^ Nice work. One observation/question I have as well: Why is the Hornet's MPRF not detecting as far as the Viper's MPRF?

No, 2 Bar.

From the changelog...looks like an improvement. However, it takes five B-Sweeps now to build a track for a hot target at 12 miles off the nose. Intended behavior? TWSsweeps.trk

Indeed... and the huge pitch up at the end of that roll with seemingly no airspeed. Amazing, really.

I've run the exact same scenario/mission with the Viper as the Hornet test in the post above...only this time, I rippled off all 6 of my AMRAAMS to further clutter the airspace. Note that the Viper's scope in TWS is perfectly pristine, only displaying the two J-11's (which have also launched at me, as in the Hornet test) that I'm targeting.

I suppose this raises the question: Then why is an Amraam pointed away (and moving away) from the Hornet out-rank fighters Hot and closing that already had a higher ranking? And, again, why is the other similar radar system in DCS (the Viper's) not seeing the same problem? I've tried to work out why a Viper, at the same speed and altitude, using the same missile, and having a very similar (slightly less powerful) radar, can so outclass the Hornet in DCS BVR right now. I think I know why: Ironically, our Hornet has had the TALD decoy for over a year now... in the form of the AIM120 (or any other missile). The DCS Hornet pilot has to do a good bit of work trying to decipher "what is the enemy?" and "what is the enemy's (or ownship's) missile?" The DCS Viper driver has no such decisions to make. It is quite frustrating at the moment. Case in point: in the screenshots below from the attached track, there are only two airplanes in the airspace other than me... chaos. TWSchaos.trk

Same. Additionally, how has that freshly launched -120C in the second screenshot already been given track-file status? The B-Sweep/dish hasn't even hit it yet. TWS screwed.trk TWS screwedB.trk TWS screwedC.trk

Hey, BN... is the team satisfied with the current state of TWS immediately picking up, creating a trackfile, and prioritizing own-ship missile launches? Additionally, if this is realistic, and most sources indicate that the APG-73 is a "slightly better" radar than the Viper's...why doesn't the Viper reflect this same behavior? Could you ask the team? Cheers!