Hiob

Apart from that - how do you get along with the 1.0? I'm starting to get more fluid with it - learned some lessons on my part (don't be lazy on naming your steps) as well that improved my workflow. Thanks for the link!

Did you receive any updates? Windows, Chipset, GPU-Drivers? Especially with updates to the game and gpu-drivers, you need to purge the shader cache. It will then stutter some on first loads while the shaders are recompiled, but should be better grom the second time.......

That doesn't help with stuttering unfortunately. If you want to eliminate the power plans as possible culprit, you need to disable the service entirely. Just open the services in windows, find the power service (or the translation for your region) and disable it. Don't worry, you can't break anything and you can turn it back on as easily the same way. Personally I have very good experiences with doing that, so I strongly encourage it. (A little bit of background on why that helps. The power service makes A LOT of interrupt requests to examine the powerstate and load on various system components. Every IRQ is a possible stutter. Unfortunately it doesn't stop doing the interrupts even on high performance settings.)

Unfortunately it seems that there is no "one fits all" solution, when it comes to such issues. There are so many variables at play that all need to work seemlessly together to have a really smooth experience. There are some things that I have personally put in the "pretty sure it is bad for performance" drawer - but even those are sometimes opposed by others. I would say it is reasonable to just build a toolbox of possible culprtis and solutions and then just apply it in the personal preferred order when necessary. Hyperthreading/SMT on/off is just one of those tools. Not the most important (imho) but one of the easiest to test. Therefore it is pretty high up on my personal checklist.

I think that‘s merely one tool in the arsenal of thing to try if you experience problems like stuttering. It probably depends on the make and model of your specific CPU and other system parameters if it is helpful or not. There where times when I had SMT (the AMD term for HT) disabled and had noticeable improvement on my 12 core Ryzen 5900. It wasn’t a problem, because I didn‘t use it for other heavy tasks except DCS. Currently I have it enabled (I think) but still don’t have problems.

Hyperthreading and Multithreading are different things. You can’t drop one in exchange for another. Multithreading is the workload of an application split into different distinct tasks (threads) that can be executed in parallel. Hyperthreading means that the CPU can execute two threads (simultaneously) on one core by splitting it into one physical and one logical. For the scheduler it looks like two cores. In other words -multithreading requires changes on an application level, hyperthreading is enabled by the hardware and microcode and managed by the scheduler. In short, it won’t affect DCS at all. The application doesn’t care if its different threads (multithreading) are executed on physical cores (no HT) or physical and logical cores (HT). If anything a cpu with physical cores is more performant than a cpu that achieves the same amount of „cores“ by means of doubling them with HT

Only if you 100% positively need them for anything. Geforce Experience (Legacy), Aorus/Gigabyte, Logitech G-Hub, Corsair iCue..... all that crap that runs in the background can be a potential source for latency, frametime spikes and overall problems. Emphasis on "can". If possible, I would keep my system as light and free of bloat as possible.

I did. And In still think it's voodoo. Personally I get the best results with everything set to 120 Hz. But I don't want to start a fight over it. I was just interested in the reasoning.

A little OT, but why? I know it's repeated over and over again, but it makes no sense whatsoever. When your display can drive 120 Hz why would it be of any use (apart from lower GPU usage) to stay below that? Or better phrased - not to match that.

Now that's a bold assumption.... My personal opinion on all of that (energy, heat, TOC) - that's all strawman arguments. There are mainly three relevant bullet points to that: - factual performance. For DCS (especially in VR) the X3Ds currently outperform Intel. As far as I'm aware...... - price. A snapshot issue. One needs to do proper due diligence on that at the time of the purchase - brand bias. An AMD-fanboy will prefer AMD, an Intel-fanboy will prefer Intel Currently (!) and personally I lost all my faith in Intel right now, and I will see how and when they will earn it back. My first AMD-System ever holds up well so far and I'm happy with it. Never regreted the switch. Doesn't mean I won't switch back when the next platform upgrade is due. Depends on the above.

true. raw dough can be a nice treat though..... I loved it as a kid.....

Unless there is a scripting error in the export .lua (as it was early on with DCRealistic) everything works just as normal. So you can use Simhaptic with DCRealistic and Rhino or any other buttkicker. They all simply read the telemetry that is output by DCS. Effectively though - probably depending on the mounting solution - the FFB devices (Stick and Rudder in my case) transfer the Vibrations through the whole rig. Making the additional "buttkicker" somewhat obsolete for me.

Just be aware, that mirrors in there current state already hit FPS with a ~10% penalty. Upgrading to 2048 e.g. (which I wouldn't mind as an option) would probably hit even harder.

As a customer: Nice idea, for sure! As a business owner: Yeah, will never happen! You could as well make a poll about free ice cream......

Not only load times. Also hickups during gameplay can be caused by the real time scanner. I make it a habit of deactivating the realtime scanning of defender before I start DCS. Simply less headacke.

Yes I know, however I‘m not aware of a similar tweak to clouds and cockpit displays. Are you?

Res. Cockpit displays 1024 and clouds ultra is the maximum you can set. Other than that there maybe ways to modifiy some .lua files as it is with shadows, but I don't know which and how. Sorry

I‘m not a fan of discord either. But all the community and support around the Rhino is there, so for this special case it is the best place to get information. You can start from here (if interested): Vpforce.eu

Not here, you find it in the VPforce Discord (it‘s based on the motor-kits and software of the VP Rhino)

I did the revised FFB mod for the V3 crosswinds with FreeCAD 1.0. No problems (stability) at all. Quite an improvement in topology related problems (or lack thereof) as well. But of course, some quirks in the user interface still. A price I am willing to „pay“ for open software!

Keine detaillierten. Die Kurzfassung ist, dass ich eine DIY-Lösung für die Crosswinds auf Basis des der VP (Rhino)-Hard/Software-Plattform gemacht habe. Wenn man sich grundsätzlich dafür interessiert macht es wirklich Sinn, sich den Discord anzusehen, da dort die ganze Community, der (hervorragende) support usw. zu finden ist. Einladungs-Link findest Du auf VPforce.eu (Ist ja streng genommen kein DCS spezifisches Thema)

Hey Leute, kleines Update zur FFB (Rhino-)mod für die MFG Crosswinds. Ich hab das Design so überarbeitet, dass es jetzt auch für die aktuellste Version der Pedale passt. Interessierte können die Dateien im VPforce Discord in der Knowledge-Base finden.

Why so touchy? I just said it isn’t a problem. They don’t interfere with each other at all. DCRealistic has a free trial - just try it. I only like s few of the effects really well, but those alone are worth it. Tire screeching on touch down is probably my favorite.

Why would that be a problem? DCSRealistic just adds sound effects (and some camera shaking), but nothing FFB related. I can’t say for Moza, but it isn’t a problem with the Rhino.

Oh the irony…..