BeastyBaiter

Any stick with that style of centering will have that effect. I always solved it with silicone grease on my old X-52 Pro (used 8 years without issue) and my newer X-55 (3 years). Typically the grease goes about around 6 months to a year before needing to be cleaned and reapplied, depending on how much I play. I've never tried Vaseline but that seems like a bad idea on plastic parts in the long term.

It might be a bit limited at first but I strongly suspect the Hornet will be the single most capable fighter and fixed wing mudmover in the game once released. The reasons are a combination of maneuverability, payload and simply the variety of payload it can carry.

I'm willing to compromise on a lot of things to keep fps up in my Rift, but lighting effects aren't among them.

According to leaks, the 2700x has a factory boost clock of 4.35GHz, there are also some 4.8GHz results up. 5.0 GHz for the top end 3000 series seems very reasonable if the leaks are true.

No, and 20 fps is not playable anyways. Also, DCS 1.5 is dead and has higher system requirements than 2.5.

The Vive is not worth considering. It's worse than both the Rift and Odyssey in every way imaginable save for room scale tracking and yet far more expensive because... reasons. I bought a Rift last summer and about a month ago gave the Odyssey a try. I ended up returning the Odyssey though due to poor image quality compared to the Rift. It is possible I got a dud though since I seem to be the only one who had that issue. Comfort wise, I find the Rift better than the Odyssey for extended periods as a glasses user. The Odyssey is definitely more convenient to put on and takeoff with glasses, but it would irritate my forehead after about 30 minutes (weight + skin can't breath). The Rift can be worn for hours comfortably. Another aspect is the sound quality. The headphones on the Rift are nothing special, but adequate. The Samsung has good drivers in the headphones, but they have far too much foam on them and too little pressure on the ears. The result is there is zero base on them unless you squish them against your ears with a bungee cord or something. Edit: Another big point for the Rift is smoothness. With the Rift, if you can't hold 90 fps, you can use ASW to smooth tracking or simply lock the framerate to 45 fps by hitting ctrl + numpad 2. In my day with the Odyssey, I didn't find any such feature. Result is the fps would bounce all over the place, which did take away from it substantially.

I've been assuming a max of 8x 9K114 Shturm (AT-6) missiles with 2 mounted on each tip pylon (AT only) and another pair on each of the middle pylons. The inner most pair of pylons cannot carry missiles as far as I'm aware. I've seen pics with the quad missile racks instead of the standard pair, but I'm not sure if that's an option on all Hinds or just modified/modern ones.

DCS 2.5 on the Caucuses map is very demanding. I have an OC'd i7-8700k (4.7GHz normally, 5.0 doesn't offer anything I find), 1080 TI and 16GB DDR4 3200 and holding 90 fps on the deck at high detail settings (not preset) is difficult. The game is beautiful, and that beauty comes at a hefty price. One thing to note is PD is a massive FPS killer, as you'd expect. I can get away with 1.5-1.6 PD over Normandy but on the free map, I have to chop it down to 1.3 to have any chance of seeing 90 fps with high object draw distance. The two higher draw distances are out of the question unless I want a locked 45 fps.

The on screen display is only a copy of what you see in the HMD, it does not use any additional RAM, GPU or CPU. As for steamVR itself, steamVR is an interface for programs to interact with the device drivers. The Vive uses it directly while WMR and the Rift use it to access their own interface which in turn controls the device. The advantage of steamVR is that it supports all VR devices, the disadvantage is performance is negligably lower than direct support for WMR and the Rift. If you have a Rift, steamVR is not needed in DCS (but is for IL2:BoX), if you use anything other than a Rift, installing steamVR is required for DCS. You do not need to start steam or steamVR to play DCS after installing it though. DCS will automatically start the steamVR backend whenever launched.

The GPU is the weak link in that system. This is true regardless of if the CPU is overclocked or not when using a normal 2d monitor. In VR, the CPU would be a problem without overclocking. GPU stocks are starting to recover a little, it is now possible to buy a GPU at non-scalper prices if you check the major online retailers daily. They still have elevated pricing though. The MSRP on the GTX 1060 6GB is $300 instead of the previous $250. For you, I'd recommend a 1070 or higher, which sadly are very hard to find still. Another option is grabbing a GTX 980 TI. They aren't absurdly expensive and should do ok.

View range has a massive impact on performance (determines number of objects drawn on screen). As far as I can tell, water quality has zero impact on FPS (not a single FPS difference). Civ traffic can have an impact though. At low altitude, more stuff is drawn and it effectively adds a bunch of very crude AI units. Thus it hits both the CPU and GPU.

Using Nvidia's Gimpworks is never a good idea, and I have an Nvidia card...

$67 a month is truly awful for a 1080 TI, my 1060 6GB cards make more than that. My 1080 TI makes about $5 per day gross with nicehash mining whatever. Or more specifically, it would if I let it run 24 hours a day mining, I also have to use it at times. That number doesn't account for electricity, but it is at 85% power target so it's only drawing around 200W. Mining income did take a pretty big hit when bitcoin bottomed out at around $5900 USD last week, but it's since gone back up to $10k and mining is once again worthwhile with the right miner/pool/gear.

I wonder if it can be swapped IRL without the use of duct tape. In any case, no ideas for solutions other than closing your left eye when aiming. You can adjust the position up and down in game now and it used to be done via config file out of game (probably still works) but this is strictly a vertical adjustment.

System: CPU: i7-8700k 4.7GHz (can do 5.0 no problem but don't for longevity concerns). Cooler: Arctic Liquid freezer 120 AIO push/pull configuration GPU: EVGA GTX 1080 TI SC2 ICX RAM: 16GB DDR4 3200 (Hynix) Mobo: ASRock Z370 Extreme4 Drive: Samsung 960 Evo 500GB OS: Win 10 Home 70-90 fps over cities at tree top level, 90 fps everywhere else on the Caucuses map including in 104th. Settings as follows: Textures: high Terrain: high Traffic: off Visibility Range: high Heat blur: low Shadows: medium Res. of Cockpit Displays: 512 MSAA: Off HDR: N/A Differed Shading: On Grass: 50% Trees: 75% Preload: Max Chimney: 2 AF: 8x Terrain Shadows: Flat Global Cockpit Illumination: On Pixel Density: 1.3

Or you can run 1.3 PD with no MSAA and get 90 fps like me.

Sounds right to me. With an i7-8700k at 4.7GHz and a 1080 TI, a single core runs at 90% or more with the GPU at 90% or more at my settings(mostly high, 1.3 PD).

I don't think the Mi-24P has a data link at all. They were talking about workload on the ka-50, which is a hell of a lot lower than on the A-10C. For the Hind, I expect workload to be much higher than the Ka-50, probably similar to the Gazelle. This is due to the missile targeting system not auto tracking, weaker autopilot and general flight characteristics of the bird. This might be partially offset with an AI autopilot, but I don't have high hopes for such things. Regardless, can't wait to get my hands on it. Out of all the aircraft in development, I look forwards to it the most.

Bitcoin and the other crypto currencies dropping 40% of their value over a week is neither unusual or cause for alarm. That happens all the time. I went to bed last night with Bitcoin worth $5900 and woke up with it at $7300 this morning. It went up another $700 today despite endless bad news in articles and TV. I'm laying 50/50 odds on it gaining or losing $1000 when I sleep tonight. I don't think banks charging extra for credit card purchases of crypto has anything to do with crypto being a competitor. They are doing it cause morons who know nothing about it are hurling themselves into unmanageable debt gambling on it. If I ran a bank, I'd do the same.

Overclocking your 8700k will improve things a fair bit probably. Out of the box it only does 4.3 GHz unless you have process lasso put all 50 or so windows threads onto a single CPU thread. Getting 4.7 GHz for all cores all the time at below stock voltage was trivial on my Mobo. That will bump performance up pretty well. 5.0 GHz is also doable but I find it doesn't make much of a difference in DCS. No delidding is required. I use a simple push/pull 120×49mm AIO, so nothing too crazy is needed for cooling. My system runs the Rift mostly locked at 90 fps on the deck with high-ish settings and 1.3 PD.

The threads in that pic are StarForce copy protection and the sound engine from the looks of it. What needs breaking up is the graphics engine and game logic. Vulkan allows the graphics engine to be split across multiple CPU threads. As for what can be run asynchronously, that's not a real problem. It doesn't matter what order the positions of each unit are updated or the order of AI actions. These are all calculated for a specific instant in time. It does matter what order different types of calculations are done, such as if the positions are updated before or after the draw commands are fed to the GPU. And that brings up the real limit, GPU draw commands. Vulkan allows these to easily be split across multiple threads. Doing so was the primary reason Vulkan was created in the first place.

I gave up and returned it. It's a nice headset with good features, but the image sharpness was far too low compared to the Rift. Guess I'll have to wait till next year for better VR resolution.

Pixel density and super sampling are the same thing.

In an empty mission, my 8700k at 5.0 GHz can just barely keep up with my 1080 ti at low altitude at high-ish settings. The result is mostly 90 fps with the Rift. In this situation, about 20% of the CPU is used and 90-100% of the GPU. The thing is, that 20% CPU usage is 100% on a core + 40% or so on a second + windows scattered around 12 virtual cores. That 100% core is the problem. If AI units are added, it can't keep up and 45 fps follows. I can get around this by dropping settings, flying higher or using less demanding parts of the map. But the problem remains, the game is far too dependent on single thread performance in VR. Vulkan should fix this as it allows for easily using multiple CPU threads to feed the GPU. But really no telling when that update will happen. Additionally, we can expect a new generation of GPU's this year. They will easily exceed the capabilities of even an overclocked 8700k.

Might be VRAM usage. I have an Oculus Rift and in 104th, it uses 10GB of VRAM. In a target range mission, it uses 5.5 GB. I picked up an Odyssey yesterday hoping for better resolution. In the same target range mission it uses 8.5 GB and 104th will not load. The game simply crashes after a few minutes of loading screen. Even with 1.0 PD, it won't load. This is with a 1080 TI, which has 11GB of VRAM.