Hiob

Sure, no doubt about that. Still it gets a lot of positive coverage. Add that to the upcoming Steam cube, which will certainly have an impact, and windows getting worse by the day...... I'm about to build a second machine (the parts are already collecting dust in the cabinet, I just need to add a CPU and GPU), all with AMD (Nvidia can go to hell, too), that will be a Linux gaming machine* (Bazzite or Nobara). If it goes well, my "main" PC will be just be a dedicated Flight Sim Machine. *(Plus all the non gaming relates stuff, like internet, email, office and CAD) **and I will buy the Steam Cube as well when it releases. Having access to my Steam pile of shame from the couch in the Living room with this awesome controller..... what a time to alive.... and I'm happy to support a business like Steam.

There’s definitely blood in the water…. The current wave of tech tubers fuming about windows and embracing gaming on Linux is remarkable. It’s getting a lot of main stream attention now. Microsoft has crossed too many lines lately.

I doubt that the 3D models and textures would look any different in Vulkan API. Why should they. Maybe Vulkan will enable different/additional Visual effects like raytracing e.g. but the basic Assets.... I would be very surprised if they looked much different.

Exactly.

Yes it is. That's exactly what I meant. When replaying a track on a different machine, it is rendered from scratch and completely independent from what is happening on the machine the track was "recorded" on. A trackfile is just a collection of values like positions, input values, direction, speed and acceleration values and a ton of other variables.

Trackfile won't help with diagnosing performance issues. It is just a table with some numbers, not a recording. It rendered independently on the machine that "replays" the trackfile. Microstuttering when panning around usually comes down to a) a messed up combination of refresh rate (fps), and settings like v-sync, g-sync, max fps.... etc. or b) a choppy frametime graph due to e.g. background processes running. When it happens in other games all the same, it doesn't make much sense to try to find the problem in DCS.....

sorry, I didn't really catch the drift of your post.... as you can see by me repeating your useful tip!

I guarantee you that is a TrackIR issue and has nothing to do with DCS. Track file won’t help. @Ddg1500 are you using the side clip? Make sure that when you look straight ahead the camera is aligned with your markers. The offset when you move your head should be the same in all directions (if possible).

I’m pretty sure that comes down to settings (curves) in TrackIR (provided that the tracking definitely isn’t lost by turning your head too much). Try to adjust the gain on yaw axis in TrackIR…..

“Microsoft is bad” is not so much the point as “Microsoft is not well suited or optimised for gaming”…. the “Bad” part though comes by virtue of the <profanity>ty “telemetry” (aka spyware) and bloat and now the AI stuff nobody asked for….. However, it is true that some systems are affected by the power service and some are not. I don’t know why that is. Maybe it’s just lucky circumstances that the process is bothering a Core isn’t used by the game. The issue is the constant polling and probing this process does which causes cpu latency. And it doesn’t stop when priority processes are running like most other background stuff does. Unfortunately it doesn’t go away with choosing another power plan either. When you are plagued with the issue, I doubt that the ultimate power plan will change anything. The problem (when it affects you) is the process itself, not its settings. That said, there is of course no harm in trying. Due to the somewhat “random” nature of windows problems, the outcome of countermeasures seems to be equally random. My strategy with windows for the longest time has been to keep it as minimalistic and slick as possible. And that worked well for me. So just getting rid of stuff completely is right down my alley. But I can see how others may prefer a different approach.

No, I had an Atari ST with a monochrome monitor like you. That was just the stock photo from wikipedia……

Yeah, thats the obvious downside. No more power saving features. (Which are however first and foremost present and important to save battery on mobile devices). No difference when the system is stressed, but when you let it sit idling around 24/7 it will increase energy consumption. So I recommend turning it off when not used. Fortunately, it boots up a lot quicker then back in the days…..

It’s not only DCS. Windows is just a hot mess, a patchwork particularly not build for slick performance. A lot of games actually perform better under the proton compatibility layer in linux. They kinda found their way with NT and its derivatives (XP, 7….) and then totally lost it again when they introduced spyware windows. Flightsims are just particularly sensitive to the issues that windows has…..

Overreacting much, aren’t we?

No, you can just permanently turn it off. (security updates and fixes usually don’t change any settings and feature updates are basically a new OS version, that should a) postponed as long as possible and b) thoroughly scrutinised)

It is true. Unless artificially limited by a fps limit, you will always be either limited by the GPU or CPU, which will run basically at a 100% (maybe reported differently though, because of architecture like multiple cores or purpose specific cores). That in itself doesn’t cause stuttering. If it would, nobody would ever play free of stutters. I’m not going into the possible reasons for your stutters right now, because there is so many possibilities for it. I’m just telling you, you are fishing in the wrong spot or rather, you maybe are looking at correlation not causation. (well here is a random list of possible culprits: - windows (e.g. power service, AV like defender) - lack of VRAM - IO processes (like drive access) - background processes (monitoring software, RGB crap etc) - driver issues - settings issues …..) you get the idea……

99%(ish) and being GPU limited is totally fine and actually pretty much the norm (at least with decent GPUs and in 2D). When it stutters you have some other problems, but not the “99%”

The server count includes all those 1 on 1 sessions between two fly buddies….. Not all are public servers, just not set to private because the slots are limited anyways. So doesn’t make sense ti average the players on those numbers…. I think it has to do with the time it was released. We didn’t have so many great options back then. Just Persian Gulf, Nevada and Caucasus of course. Compared to those maps it was a big leap forward.

It's not only the power saving, but the thousands of interrupt requests that service generates. It is a prime example of how not gaming optimized Windows is....

you may have a bigger range of detection in pitch but I have never felt the need to replace the passive clip. Just works for me….

If I had a christmas wish free from ED, I would wish for a makeover. Just visuals and maybe sound.

...if only I had a dime for any YT video with "changed forever" in the title...... clickbait should be outlawed..... seriously. Not only for creators but also for media in general..... (let me dream of Utopia, will'ya...)

...I might add, that the Viggen is one of the few DCS Aircraft I own but absolutely never fly (so is the hornet by the way). Don't ask me why. So take my opinion bout it with a grain of salt. I absolutely use the living daylight out of the Mi-8 though.....

No, not really. The Viggen has a very particular non-Nato interface. The Mirage even though french and distinct from US jets is still much closer to them than the Viggen (IMHO!!!). Apart from that, the F1 is a nimble, light fighter with ground attack capabilites, whereas the Viggen is an penetrator kind ground attack first and foremost. I don't have anything against the Viggen, but I think it is the most distinct aircraft we have in DCS - for better or worse.

I had (have) the Index. It is good, but too cumbersome to use (compared to a Q3). Lighthouses, cables - all of that stuff. However it worked very well with Steam. The Frame adresses most if not all of the issues I had with the Index. And the main advantage: It is Valve not Meta. Only disappointment for me is that it doesn't feature (Micro-)OLED displays. But personally I'm even more interested in the new Steam Machine. When the price is reasonable I will probably make it a Living Room TV gaming device. (Substitute for a Playstation that I never use anyway)