Hiob

You’re looking at the wrong source in the first place. I recommend you to seek out the people that do actual proper gaming performance tests. Gamers Nexus, Hardware unboxed, pc games hardware, Jayz2cents…..to name but a few. The result is clear as a sunny day. Any(!) X3D mops the floor with Intel (for gaming). Including the one you already own.

100% agree though, as per the title of the thread, I think regardless of the „simulation quality“ of structural issues, being able to pull 20G instantaneously in a Tomcat e.g. (probably worth 40kgs of pull force) without any feedback is part of the problem. I stopped ripping wings of when I started the habit of pulling progressively (like you would/should with the brakes of a motorcycle) instead of yanking like mental. Eventually when I got a FFB stick it became virtually impossible to rip wings (other than intentionally).

Oh please, Yes! Make it the next makeover! I would be sooo grateful!

Apart from setting up the fog itself, a great part of DCS looking fabulous is always the time of the day. Make sure that the sun stands deep (early morning or late afternoon)….. nice colours, long shadows…….

You find screenshots on the store page.

Guilty. Of course I once or twice took a day off in anticipation of a big (content-)update. Half of the time it worked out, half the time it didn't. But when you are around long enough, you get more experienced and more chill about it and stop doing stupid things like that. Software developement is incredible complex and you will never stop finding errors if you keep searching. The key is to catch as many showstoppers as possible before release, which is why you keep on looking until the last possible moment. It's just the nature of the beast.

same. I didn't say anything because I thought I messed something up (hardware related) because I switched to DIY FFB-Pedals around the same time. It reminds me now of the Mirage F1, which was always very responsive (not to say touchy) on take off.

I have to agree on that. I had the same impression lately, that suddenly I can't seem to touch the pedals light enough to not overcontrol on the ground. I thought it was my hardware and just helped myself with a (hardware) deadzone... but yes, the Viper feels VERY touchy on the ground lately.

.... maybe it's just me, but actually - they do look exactly the same to me. Except that the real pilot was eventually successful (this time) and the virtual wasn't.

That’s all that matters!

This is self-contradictory. The latter is the textbook definition of "CPU-bound". Don't get me wrong. I don't want to lecture you or disregard your claims, but currently I can't make much sense out of the premise. Your old system should have reported CPU-bound.

userbenchmark is the worst possible source for unbiased realistic data. If that was the basis for your decision, you took an arrow to the knee unfortunately. Regarding your original post - there is no way, with this setup, you weren't cpu bound unless, the GPU was artificially limited in the first place (fps limit in the GPU driver e.g.) or you were playing with extremly high settings that you subsequently changed (maybe unintentionally) for your nwe system Even though the Intel wasn't the best possible choice for what you wanted, it is still way more powerful than you're old one. If the performance got worse, there is something not quite right with the settings or drivers yet.

Can‘t really help. Just a random thought. I remember that the bindings in the Kiowa were very quirky. In regards to momentary vs. permanent switched, three way switches, multiple variations of binding the same switch. Don’t know if this is still a thing. You might wanna check if you have exactly bound what you have intended.

Two kind of people here as always. First Kind: „Hey guys, I have a 12700K with a 3080 and 32 Gigs of RAM. What kind of performance should I expect, because I have the feeling mine is unreasonable low. Can you help me troubleshoot?“ Second Kind: „Hey, ED. With my undisclosed specs I only get 18 fps, stutters like hell and days of load times. Fix your frickin hot mess of a game!“ Guess which kind gets more support from the community….

Awesome!

I‘ll take it!

The debate is pointless, because ED has made it crystal clear it ain't gonna happen. For obvious reasons I might add.

Do you have any 3rd party banchmark programs (Cinebench, CPU-Z, OCCT, 3Dmark) where you could check the CPU performance? Aapje is right. It is impossible that you get that poor performance from that CPU unless something is seriously wrong with the system. I would start by applying safety defaults in the bios and rechecking. Also check for updated chipset drivers. oh... and check the ingame telemetry if you are actually CPU or GPU bound in those instances......

That pretty much depends on wether you fly in scenarios where you are CPU-bottlenecked (VR, heavily scripted missions with tons of units e.g.) Then when you are indeed CPU bottlenecked it would be a really significant upgrade. BUT when you mostly fly single player, perhaps with selfmade missions that barely feature a dozen AI units, maybe in 4K res. ....you would most likely notice no difference at all. DCS is still - in most cases - GPU limited.

IIRC he uses something like the paddle axis on the TM16000 Throttle and/or a twist grip. I can't point to it, but I think he mentioned it at some point in an Interview style video. Perhaps he'll let us know here.

Ist Quatsch. False positives sind leider ein andauerndes Problem. Norton ist leider auch eine besonders bescheidene AV-Suite. Da bist du besser bedient einfach den standard Defender zu verwenden.

Can't say I'm not happy!

Would it be possible to add the OH6A as an option to the Huey? I know, that's a lot to ask, but would be awesome. But either way, it is still one of the best user made contents out there!

Keine Panik. Ich hab‘ ne 4090 und der Rechner zieht in DCS nie mehr als 500W aus der Dose (wohlgemerkt der gesamte Rechner). In RTX Games wie Cyberpunk 2077 vielleicht mal 600….. Die nominellen Höchstwerte, wenn sie denn überhaupt erreicht werden, treten in der Regel ja nicht simultan auf. Und Dein Netzteil wird auch nicht gleich in Flammen aufgehen wenn es mal 90% liefern muss. Und Be Quiet Netzteile sind kein Ramsch, die liefern auch ihre Nennwerte klaglos. Schlimmstenfalls schalten sie ab.