FR4GGL3

@Taurim perfekt wäre es jetzt, wenn du das nicht global setzen würdest, sondern im DCS Blackshark Profil. Ganz einfach deshalb, weil du durch "Höchstleistung" deine Grafikkarte immer unsinnig ohne Taktsenkung betreibst. Eben auch auf dem Desktop. Ansonsten: gut gemacht wenn du die Ursache für deine Probleme gefunden hast. So muss das.

Wenn du weiter probierst, lass dir bitte parallel immer die FPS anzeigen (im Spiel RCTRL + Pause). Dann kannst du zumindest die FPS Sprünge als Verursacher eingrenzen oder ausschließen. Im Idealfall hättest du aber noch einen Blick auf die Auslastung der einzelnen Kerne. Dazu bräuchtest du sowas wie den Riva Tuner. Es geht ja erstmal weniger um Mutmaßungen sondern um Beobachtungen was genau passiert während du die Ruckler und Zucker hast.

Die Idee ist folgende: angenommen du hast einen Monitor mit 144 Hz auf die du gerne Syncen möchtest. Dein System kann die 144 Hz nicht halten, fällt z.B. auf 120 fps ab. Folge daraus ist eine Halbierung der Frames per Second, um sich wieder in einem Bereich zu befinden, in dem Bildwiederholfrequenz und ausgegebene Bilder syncbar sind (hier in dem Beispiel z.B. ~70 Hz). Im nächsten Moment können die 144 fps (passend zu den 144 Hz des Monitors) wieder getroffen werden. Eine Umschaltung des Sync findet wieder statt. Dieses Hin- und Herschalten verursacht unschöne Ruckler und man merkt es an der Eingabe. * Ich sage ja jetzt nicht dass es so sein kann, aber das würde speziell diesen Fall schon erklären, wenn der TE vorher nur knapp 144 Hz nicht halten konnte, aber durchaus fähig ist 70 Hz dauerhaft zu halten. Aber ich gebe zu ich habe den Effekt selbst nicht auf dem System des TE gesehen und kenne das System nicht persönlich. Es lässt sich aber ganz leicht testen. Im Spiel und im Treiber VSync deaktivieren und schauen ob man dann diesen Effekt noch hat. Tearing wird man so sehen, aber es kommt ja auf die Ruckler und Slowdowns an. Versuchen könnte man es. Alternativ könnte man auch mit der alten MSAA Einstellung die FPS über den Treiber auf einen Wert begrenzen, den man auch im schlechtesten Fall immer schafft (z.B. mit MSAA anstatt SSAA auf 70 FPS begrenzen). *hier ein relativ alter Link der das auch noch beschreibt: https://www.nvidia.com/en-us/geforce/forums/game-ready-drivers/13/99710/how-does-triple-buffering-really-work-can-anyone-e/

Ich denke nicht dass es an der Art des Anti Aliasing liegt, sondern vermutlich an der erzielten Framerate. Es gab in der Vergangenheit bereits Schwierigkeiten mit VSync On, weil dort die Framerate halbiert wird, wenn man die Bildwiederholrate des Monitors nicht treffen kann (relative alte Triple Buffer Idee, die scheinbar in DCS integriert ist). Das Umschalten zwischen den gesyncten Raten kann dann diese "Zucker" bringen. Es half bei mir dann jegliches VSync abzuschalten und die max FPS über den Treiber auf "100" zu begrenzen. Ich habe aber auch einen VRR fähigen Monitor so dass sich Bildwiederholrate und FPS dadurch wieder syncen. Was auch noch helfen kann ist die maximale Framerate von DCS anders zu konfigurieren (maxfps = 300). Nur als Idee falls du doch irgendwann nochmal schauen willst. Ansonsten kannst du natürlich alles so lassen wie es ist.

You need to know what you want to do with your 4090. Do you want to overclock, look at the technical best cards (afaik Asus and MSI). Do you want to watercool the card with an open loop? An Inno3d with Watercooling block would be a good choice or maybe a Zotac, as they won't void the warranty if you swap the cooler (only if you don't damage it while you swap the cooler). But then again the Zotac Aircoolers are said to have a annoying noise/rattle. If you want a card that has the least chance of couil whine, you might want to avoid Asus and MSI... I use a Gigabyte Gaming OC as this card has almost no coil whine. Only at way over 300 fps. But the Aircooler has quite high rpm and isn't what I would call silent. And the Service of Gigabyte is quite horrible if you ever need it (but that might not only be a Gigabyte thing). It isn't easy to say get this or that card. It all comes down to your likings / preferences.

I would avoid Models that are known for Coil Whine. Just because this is REALLY annyoing. I've hat a whining ASUS TUF at first (last year as they came out, don't know if the recent models still have coil whine) and I had to return it just because I couldn't stand the noise. Everything else would be a matter of personal likings (Fan Noise, Design, Price and so on)

Well... no one will win or loose anything in DCS. Because it is a Simulator and also not an actual combat situation. I get your point in real life, when you need to do your job and come home safe and not being grounded or killed. But this is a Simulator and it is nice that you can try all that stupid things without real consequences. I mean, nobody would also have used differential Thrust regularly in real life, but it is in the module (though I've heared about a F-18 Pilot that tried it once and got trouble because he split the handles too far). I also ripped the Wings off because I wanted to see how hard I can push and when they are gone. There are fun videos out there of someone cobraing a SU-27 on the Deck of a carrier. All stupid nonsense. The good thing is: as it is a Simulator, you can brake the rules without hurting somebody and sometimes it is interesting doing that. The next time you take it serious again. Do what you need to do. If it needs to go out of the module because of reasons, then do it.

I should have written the Guys that talked about using the MCB in real life are regarded to be some of the best. Nevermind.

Because the Guys that talked about it are regarded to be some of the best. That ist why people want to try the same. We only have DCS. We aren't blessed by flying the real Thing back then. And we won't get any closer. It might be foolish, especially from the point of your real Pilots. But it is at least my point of view. So taking such things out of the code would hurt a bit

Ooookay. Visual Fidelity... it is nice and funny (despite the fact a lot of people asked how to disable it as soon as it was brought into the Module). But it is still not "important" in any way if you think of it from the standpoint of the users. And that is why I compared it to something that people are wondering about although it is such a small detail. But I get your point. You are a developer of a Software. You might rank importancy on things like how many people will recognize feature X. The people here don't see it only as a Software, they love the plane and that is why they love your product and its detail. That is why they are so dedicated to the smallest things. I guess we have simply differnt views on the same thing. What I want to say is that all the questions and bug reports (even if they aren't bugs) are not here to upset you. The people here love your product so much that they want it to be polished as much as it could. And they/we also forget that we already got a lot for our money. Again: thank you. But plz don't get upset about Questions about things that might be completely obsolete in your eyes.

It might have no real advantage, but then again what advantage have modeled strings and patches on the instrument table to show the wear and tear? I guess both things are simply part of the Tomcat fascination. And that's the reason why ppl want every single detail. If you would have only simulated the things you really need for a Tomcat, the Module wouldn't be such a great Module. And I can't thank you enough for it. I get the fact that you need to choose which backlog items are worth it - especially if there is an entire F4 and a Eurofighter which have its on backlogs. But then we shouldn't discuss the "advantage" alone. No offense - I just want to get you an idea why people won't stop asking for it.

True, there are days when a boring Jester would be the better Jester. It would be cool if we could choose it situational. Just like in real life when you would tell him "please, not today". I mean it is funny and feels a bit less AI, but if you heared the Dale Earnhardt, Morgan Freeman, Illuminati stuff long enough, it gets a bit annoying.

I guess it really could be more realistic now. I remember some (youtube) stories of Okie in which he described that he had to hold the Stick with both Hands on low speed high AOA maneuvers. And he also said there was a point where he left roll SAS on all the time because the Tomcat didn't roll that good. Maybe I misunderstood something, but it would make sense by the way it behaves now. But then again Victory205 stated that they turned roll SAS off as it should be... don't take it too serious. Play with it. It is not as if you are in danger like the real Pilots would have been if they simply played around.

Wasn't there a thing with high friction tires as otherwise the planes would slip of the carrier? Maybe this sticky tires make this impossible?

Thanks, I didn't know that.

@jojyrocks That first Flaring Pilot you linked seemed to do it for show. It almost looks like a Wheely and the Pilot seems to balance it. At least if you look at the horizontal Stabilizer it seems like the Pilot plays with the Stick to hold her in Balance. But I could be wrong.

Yeah and if you land this "big fat Fanny" with Flaps and Slats, Airbrake, DLC and Hook, she really let it all hang out. If you listen to the song, you really think about playing it all the time by going round the boat. And simply don't flare her. It doesn't look good.

I know that. But some topics sound like people are really angry about such things. For me things like DCS are there to have some fun. So I tend to ignore some minor flaws and keep on having fun. Let the Flanker sharpshoot at the merge, let it jink like there's no tomorrow. It is part of the fun.

Sometimes it might help to accept the idea that DCS is still a game. Even if no one likes that. That mindset could help stopping frustration and accepting a few things that could be optimized - do it sporty. I mean, after all it is not the real thing. You can have almost all the fun without the pressure and the risk. Because of this, I would call it a game.

yep. I find the fixed pipper that you get by pressing the seam lock Button helpfull at times. But this might be me because it looks more like the typical 3D Shooter Crosshair. @ whoever it wrote: Don't get frustratet from the AI. I like the Fighting it does these days way more than the infinite YoYos they did before. And if you think the Caucasus Map Flanker is tough, try the Nevada Mig 29.

Well, if we have Strings, Tapes and Patches inside the Cockpit to simulate the wear and tear, I really like to be able to shake the Turkeys Tail Feather. And don't tell me that you won't - now that we can adjust the mirrors I have to say that I don't regret a single Cent that I paid for this Module. There is so much love in it.

Would be great. Especially for all that low speed Dogfighters. I remember a Story from a Tomcat Pilot (Youtube Video, but I don't remember who it was) who stated that there have been quite a few defects of the Lights on the vertical tails. They found out later that this was due to the low speed harsh handling on BFM training - because of the shaking and wobbling. So that could be interesting. But I don't know if there is any data to simulate this. /edit: I found it - full Story starts from Timestamp 7:55, the Tail Story is around Timestamp 9:00

That might be an explanation because especialliy with the A I tend to go faster in the merge (and also in general). I have at least 420-450 knots before the merge. So that might explain my feelings. It never felt that "light" in the first turn. Anyway. I like it and I am looking forward for similar finetuning for the B.

I tried the A yesterday. Flew the instant Mission against the Flanker. I don't know why, but the A felt almost a tad better than the B in the same Mission. Sure, there is some missing power, but it felt responsive, I would say it turned better.... even if I am wrong, simply "Thank you".

Alternative: You might think about a 13700K or you may wait for the new AMD X3D Processors. The 13900K shows its power over its lower brothers on Multithreading stuff and DCS isn't a Multithreading Task for now. I came from a 9900K and I felt both. The GPU and CPU. You can even feel it in DCS. But it is subtile in DCS. If you want a possible Update for the lowest invest, a 5800X3d might be a thing. But then again: the new X3D are around the corner. If I was you, I would at least wait and see how good they are.