Headwarp

I meant 417.71.. brain fart. Might point out that even if I let my display sleep, I never let my system go into hibernation. I'd rather just turn the PC off. Hibernation has some kind of issue in every version of Windows I've ever used >.< I stick to High Performance power plan.

I'm noticing a performance hit myself when low among the trees. trk file provided. I used to get away with 2.0 pixel density with the odyssey with a minimum of 45fps. I had to lower it to 1.6 with the odyssey to stay above 45fps using the latest version of 2.5.4 and this track file. Can't say for sure if this started with the patch on the 16th or the latest nvidia driver, or perhaps even something between steamVR 1.1.4 and 1.2.7 I've adjusted various settings in nv control panel as well as in game, ran a dcs repair. Unsure what gives. FPS is fine until I start looking at the trees or flying inverted above them. Can post screenshot of my settings if needed, but would be nice to know if others are seeing a significant sudden framedrop. fpshittrees.trk

Haven't noticed an issue with my g-sync monitor when I've let the monitor go to sleep. I did have issues with upgrading from 417.35 to 417.76 with an express install that caused performance issues in various titles. FPS was all over the place in one game I was playing. Could have fixed it with DDU, but it instead did a fresh windows install for other reasons anyway. Not saying that your nv driver installation is corrupted, but mine was after an express install. Everything seems normal with 417.76 now.

Newegg has the new WD Blacks listed as having a 5 year warranty, current 970 Evos listed with a 3 year warranty. I might just have to shop for WD when I get to the point of having another $380 to blow for a 500gb and a 1TB.

the FOV of the Pimax5k and 8k headsets might help with the peripheral. Idk. My answer is wingmates, or a trusted GCI. But it definitely feels like you got a pair of thick goggles on when you're trying to look over your shoulder.

That's impressive man.

There are numerous training missions that show the framehit being caused with certain static models in view. There are a few threads talking about that issue. Aside from that the TL;DR Version is at the bottom. What is your pixel density in the occulus tool tray? And what are your pixel density settings in the game? Is your GPU set to "Prefer Maximum Performance" in the nvcontrol panel? And have you set up any custom fan curves for your GPU? They run better when cool. I set mine to run at 100% rpm by 45C using Evga Precision X1. EVGA also has bios updates for the RTX 2080Ti XC Ultra that can be found in the EVGA forums, not sure if it applies to the XC2 or which of the two you have. Really only a concern if you are overclocking the GPU afaik. That being said - getting 90FPS in VR in DCS World over land is a task for hardware of the future at the moment in my opinion.. unless you want to render at a resolution like maybe half that of the rift. With my WMR headset I just let motion reprojection do it's thing and configure my machine to run at no less than 45fps. But don't use missions with static aircraft to tune performance for the time being. That being said at with the odyssey I can get to about 2.0 pixel density and stay above 45fps with my 2080Ti. Letting ASW do it's job should keep things smooth, although it will artifact a bit. DCS renders things much further out than just about any other game you will play. There's another sim out there I won't name that only renders objects like aircraft and vehicles and buildings within like a 12.5KM radius with your aircraft being the center of the cylinder and I just barely am able to run @80-90fps above 1000 meters in that title with 180% SS. You can see buildings and targets 40NM or further out in DCS with view distance set to medium. *Edit* - Just looking at your Task manager your CPU is only running at 4.2ghz? Find a guide on how to OC that chip specific to your mobo. Put that liquid cooler to work. should be able to OC all cores to 4.7 at least with very little effort. I'm good @ 4.9ghz on all cores at 1.275 vcore without delidding, stress testing at 75C average under full load using a corsair h100. DCS World is a DX11 title and single threaded performance is a big deal. You'd probably see a pretty nice increase in performance by increasing your cpu clock speeds. You are very likely cpu limited, and it seems like your CPU is using the AVX offset rather than turboing 2 cores to 4.7. Chip should easily do at least 4.7ghz on all cores with a little know how, with the AVX offset completely disabled even. K series comes unlocked for just that purpose. Just for reference - 2080Ti's paired with a 2560x1440 monitor in DX11 titles are showing cpu limitations even @ 5ghz. At that point you're talking about delidding the cpu. I'm not recommending this, it's just a process that is probably necessary for 5ghz or higher clock speeds. But I'm willing to bet you can hit the 4.7-4.9ghz territory with little concern or effort, and there are likely guides you can find by googling your motherboard model + overclock that will help you with every setting. From there it's simply finding the minimum vcore for stability vs the highest clock frequency you can run without crashing or hardlocking (even briefly) within a certain temperature range while stress testing with your particular piece of the silicon lottery. (I'm talking specifically about the OP's 8700K) It's do at your own risk, but if you only adjust vcore in like .005 increments (Start from 1.3 and if stable work down 1.295) you're unlikely to do any real harm that can't be fixed by clearing cmos and reconfiguring your bios. TL;DR version I'm using an HMD with 1440x1600 resolution per eye with Pixel Density @ 2.0, @4.9ghz, and still can see individual CPU cores hit 99% in DCS World if not using motion reprojection, although I haven't seen my gpu usage drop below 97% in the same scenario. I suspect a gnarly CPU limitation, and your system seems to be using the AVX offset, putting all cores at 4.3ghz. Your 8700K paired with a 240mm liquid cooler can probably handle 4.7-4.9ghz on all cores with the avx offset disabled and less than 1.3vcore, and that could offer a nice performance increase. That 2080Ti is hungry, and DCS World is a DX11 title that benefits from single threaded performance. I'd get used to running at 45fps with ASW on, and a high pixel density for some time to come. The good news is, you'll be able to get away with a relatively high pixel density and msaa x2. More good news - Eagle Dynamics is working on implementing the Vulkan API into DCS World, this should make use of more cores/threads, and offer higher framerates. This one might take a couple years or more though, we have no idea yet. I'm sure there's quite a bit of learning for the team involved with that.

They took some personal time for the holidays, we got the first patch of the year for open beta last week and they've been addressing some bugs that popped up. The devs didn't guarantee a patch for stable every other week.. they outlined their gameplan. If you'd rather not wait out the bug hunting for content updates a bit sooner, convert your client to the open beta version. :)

Glad the WD Black's exist, keeping samsung prices in check. Last I checked on newegg current 970 evo prices matched the WD Black pre-orders. Also glad samsung is responding with the Plus.. while still having to compete with the WD Black prices.

the TWCM throttle + a ch products f-16 stick should be pretty awesome compared to your current setup. I have to say moving to a warthog way back when, having all the hatswitches and buttons certainly makes life easier in DCS World. I mean, especially the A-10C.. it's really quite an experience given how much is controlled by the hotas in that aircraft.... but it's made all aircraft easier to bind controls for.

I hear swivel chairs are nice for checking six in VR. I'm in obutto pit and the chair doesn't swivel, so I tend to have to lean as I turn my head to look behind me. I tend not to fly without friends these days lol.

My general philosophy of shopping for hardware is to get the best that's within your budget. Don't starve your kids. Not being a family man, I may or may not have resorted to ramen noodles for cheap food to get hardware sooner than later. :music_whistling: Also, spreading part purchases out over time can reduce the impact of the total cost of a system if you've got something that will let you get by for the time being. My initial investment into my current rig was $1300 spread out over about 3 or more months, first I bought the CPU ($420 at the time), next month I bought the case, then the ram, then the mobo taking the gpu, and drives from my old build. Somewhere in there I squeezed in my liquid cooler. With all the hardware currently listed it's taken me over a year to get to this point and I'm more like $2700+ USD just for what's in the PC case not including the two SATA III SSD's from my old build and I don't anticipate a need for major hardware upgrades until at least 2023 hopefully. With the cost of the new WD Blacks driving the cost of NVME prices down to what I paid for sataII/sataIII ssd's when they were newish technology, I'm probably going to readdress my storage configuration, but not because of necessity. I also tend to use a little math to justify to myself the cost of hardware, that even with everything I use to fly in DCS or enjoy other games, it's less expensive and allows for more time spent with it than having a night life, or being an RC plane hobbyist, or beefing up a car (hopefully for track racing of course). If you got the dough for the 2080 over the 2070 I'd say go for it. It will likely last you longer.

There was a time I was sticking with TrackIR because I was waiting for higher resolution VR HMD's. Then the Vive Pro was released, and I also learned about the Samsung Odyssey. After plugging my Odyssey in the first time and flying in a sim, my mind was blown. I had no idea what I'd been missing out on.. and in fact - going for a higher resolution HMD gave me further cause to want to upgrade my gpu which at the time was a 980Ti. VR really puts you in the perspective of being in the cockpit, and you can really feel/see the effect of having depth perception. In WWII aircraft my aim improved, but mostly what put the poop eating grin on my face was looking left or right and seeing a life sized wing in either direction. If you have the hardware for VR - it is by far the best simming experience. Graphics quality wont be what you get on your monitor, but the experience is just better. If you don't have the hardware for VR, but have the money to build a rig - worth it imo. It's just really hard to explain how awesome it is without putting on a headset.

Things to know about WMR - you will have to use SteamVR to play DCS in VR using WMR, and you will need the Windows Mixed Reality for Steam app from the steam store (it's free). After you setup your center position in WMR, you also should probably set up your center position in SteamVR, as well as take note of the application resolution sliders on the video and application tab of the steamVR settings and google and understand what they do. Imo set global slider to 100% and use the application slider to adjust resolution per VR application, crank it up as long as you can maintain no less than 45fps. You may have to add dcs.exe from your install directory to steam library as a "non-steam game", and then to your VR library for dcs.exe to show up in the SteamVR settings on the application page. After installing the WMR for SteamVR app, when you launch SteamVR directly it will bypass the cliffhouse loading in. You can also turn off the mirror display in WMR. DCS has it's own monitor display, and lowering the resolution in game for the picture on the monitor may benefit performance overall. When you get both WMR and SteamVR set up for a seated position and centered, you should be pretty close to centered in any cockpit you get into. But you'll probably have to move around and press numpad 5 to get yourself perfectly aligned, or adjust your head position in non VR mode like described above. Also in steam/steamapps/common/mixedrealitydriver/resource/settings there's a file there, open it with notepad and delete the two // before the motion reprojection "auto" line so motion reprojection will kick on when you can't maintain 80-90 fps (which is generally all the time in DCS World)

I personally don't know all the science behind it. But in experience with DX12 titles that behave similarly to what we can expect from vulkan the end result is CPU load being shared across all physical and logical cores of the CPU equally. 50% cpu usage is 50% on all threads. I'm not saying there isn't a limit to how much hardware can benefit the DCS Engine using the vulkan api. @3440x1440 @4.9ghz on an 8700k with 2080Ti in one recently released dx12 title will average about 50-75% cpu usage. In another title I know of, which I believe uses AVX 2 instructions along with dx12 will use 65-99% of my cpu at the same resolution. What you will end up seeing once you exceed a certain amount of "horsepower" so to speak is less overall cpu usage. Without being a part of the development team which I admit I'm nowhere near qualified for and With my limited knowledge on how it all actually works it's impossible to say for certain what kind of cpu usage to expect, but should it utilize even 50% of my cpu at minimum, 7th gen or older i5 chips will be pegged at 100% at all times. The value of an i7 finds a place in gaming. The gist of it is that single core performance will not be the golden measurement in Vulkan and DX12 titles. But just to clear up where I might have been misleading in my previous post, there probably is going to be a point at where x amount of cores @ y clockfreq exceeds any cpu bottleneck you might run into, and some of that is dependant on what is being asked of the CPU and the order of which operations must be completed. There's no telling when we'll see vulkan actually implemented, so my advice to the OP is still buy what you can afford. If you got the dough for overkill, I have to say, I have a lot of love for overkill. My i5 2500k was overkill when I built it. It took me 6 generations to replace it. But if right now is your concern, and you'd like to save some money and revisit the idea maybe a little sooner than you would had you gone for overkill, all you're really looking for is the best single threaded performance as long as DCS runs on DX11, given that you're looking at a quad core or better. With 7th-9th gen intels holding some of the highest clock frequencies achievable.

You will require steamVR but it works with the stand alone version of DCS. You can add non-steam games to your steam library as well, which I find necessary to do with dcs.exe in order to use the steamVR application resolution slider for DCS. That and you have to enable motion reprojection via editng a file with notepad, but once you do it will turn on or off depending on your framerate. In DCS it's an always on thing, as WMR seems to need at least 80-85 fps to have smooth game play without it, and as we just aren't there with hardware, it makes things smooth @ 45fps.

If it reduces the visible pixels, that's a win in my book. My only real complaint with the odyssey is seeing pixels. It would be easier to spot blurry aircraft in the distance if not for them at higher resolutions, as they can blend in with the pixels. If OP's in the U.S. you can probably find one at a best buy or something and try it out for 14 days and return it for a full refund it if it's not your thing. with a savings of $800 i'd say it's worth a shot.. probably going to go for the odyssey+ myself in the future.. my odyssey is just not old enough to justify it yet.

I'm quite aware that the Odyssey, the Odyssey+ and the Vive Pro screens are the same resolution, but the Odyssey+ supposedly has a perceived PPI of 1233. Whatever they did with the screen/lens configuration to achieve it, the result is less visible pixels i.e. screen door effect. The perceived PPI is what the eye will be able to see, so I'm not sure where you felt a need to correct me, especially given as the information comes from the samsung odyssey+ product page. https://www.samsung.com/us/computing/hmd/windows-mixed-reality/hmd-odyssey-windows-mixed-reality-headset-xe800zba-hc1us/ @$400 vs $1200 it's a no brainer in my book, and it's already been as low as $299 USD during a sale. The vive pro has the lighthouses and better controller tracking for sure. For simming purposes WMR works fine. If you got the dough other things to consider are the potential for wireless connectivity.

If you only use your VR headset for simming the Odyssey+ is probably a good runner up. The tracking issues are limited to the controllers. As long as you have a light on in your PC room the headtracking is superb. Odyssey+ declares a PPI of 1233 using its anti-sde screens. Vive Pro 615 PPI. The biggest difference may be the controller tracking.. which many say is "good enough." It's a matter of keeping your controllers in sight most of the time as there are no external sensors to track them. (I wish there were ext. sensors) Bluetooth allows for a second or two out of line of sight, but when out of view they can lose track. WMR headsets would be hard to compete with if they offered a set of optional external tracking cameras or something. I keep meaning to try some standing VR titles, but I really only use my HMD for simming and the odyssey has been great for that. My only regret in buying the Odyssey, is not waiting a few months for the Odyssey+ to come out.

I don't know about drops to 30fps as my settings allow for never dropping below 45 fps in VR. In that regard, motion reprojection does a really good job of keeping gameplay fluid, although it comes with it's own nuisances.. like aircraft's wings "flapping" like some kind of bird on *insert stimulant here* or other anomalies. 90fps vr would be great. But I think chances are slim we're going to convince ED to go back to the old rendering method at this point. We can only hope for improved fps as ED continues to optimize the VR experience. Honestly if we could just find an alternative to MSAA, we'd be much closer.

Let's specifiy "in it's current state" how about it? Eventually there will be Vulkan.. the more cores the merrier. That and even at 60fps you can see a lack of fluid motion in the trees and world around you, at least using a monitor. Kind of amazing what another 15-25 fps can do in that regard. Not everyone is content with 50 fps. Although 45fps and motion reprojection is another story in VR. Also running at 4.9ghz averaging 75C under full load with 8700K that I haven't delidded.. why settle for 4.4ghz with that "lack of heat"? Put a liquid cooler on that thing and get more performance imo. That being said 8600k is a good chip. I'm not downing anybody. But this is all a case of YMMV and how big is your wallet. In the case of VR - it amounts to improved image quality while achieving that 45 fps for motion reprojection. Just one last edit to talk about "Future proofing." My 8700k was top of the line when I bought it, and 9th gen came out a year later. Buy the best that your budget allows for, and the system will last you a longer time before you're thinking about the next upgrade. 9600K, 9700K, or the much pricier 9900K, as well as apparently the ryzen 2700x, or the upcoming ryzen 3 series are all solid choices. Increased core counts will likely handle vulkan better, whenever that may come.

Lenovo explorer without controllers could be had for like $99USD+tax/shipping. Have an aussie friend on a budget that picked one up. I don't think he flies using his monitor anymore unless he's in a hotel with a laptop and an xbox controller because it took the least amount of space in his luggage.

Hope you get a working replacement quickly. Just fyi - latest windows updates causing me no issues, if it helps ease your mind that it was just a hardware fault. Based on things I was reading on NV forums while waiting to purchase my 2080Ti, I made sure to run two separate cables form my modular PSU for the two 8 pins on my gpu. I can't say for certain this is why my 2080Ti has been running like a champ, just that - there was enough hearsay out there to make me forego the single cable with two 8pin connections. It shouldn't make a difference.. and that doesn't shift the blame to you if using a single cable solution. But I've seen such advice given more than once. Hope your retailer gets you sorted soon, if I'm assuming correctly how EU laws work regarding warranty.

They're refering to DCS 2.x alpha where the deferred rendering method was first introduced. I think it was implemented in 2.1? You still had the option of disabling deferred rendering at that point. By 2.2 the devs decided deferred rendering was the way to move forward and removed the option to disable it from the game to save themselves added development time. The downside has been that MSAA is much less friendly with deferred shading, where at least in older versions of DCS between af and high MSAA levels you had sharply defined objects where now, the overall picture can look better in many ways but aliasing is much more present depending on your comfort with performance and variables like resolution.

The 2060 from what I've seen benches very closely to the 1080, while the 2070 benches about halfway between the 1080 and the 1080Ti. If we're expecting 1080 performance from the next AMD gpu's, they're going to have to price them competitively with the 2060 afaict. They're also going to need to respond to DLSS.. which you can only experience in one title @ 4k afaik at the moment, however, my experience with DLSS is that it's pretty awesome. My fear is - DLSS might be too difficult/time consuming for NV and their supercomputer for VR support.. otherwise, it offers comparible image quality to msaa without the hit to framerates. I'm hoping that they can figure something out for VR though. Frankly, I'm very interested in seeing where development of the NGX SDK goes over the next half a decade and more. DLSS is just feature #1. I'd really love to see Eagle Dynamics make use of the tech, even though their stance on things like this is pretty firm. That's a topic for another thread.. but I can't help but feel NGX would be a great thing in the simming world. Using DLSS in place of msaa would solve a lot of complaints in this forum, and when we get to the point where the NGX SDK is able to handle AI programming, possibly to a level like nothing we've ever seen, as the hardware is responsible for driving vehicles in the real world, I just can't help but think that could make for some amazing single player experiences, or even make co-op missions that much more fun. I'm going to stop..i could keep going on and on about how awesome that would be paired with the upcoming dynamic campaign generator, but both are in the distant future, and I'd probably just be getting my own hopes up. I have a hunch that future nvidia gpu's will see an increase in RT and Tensor core count, as the NGX SDK allows for more functionality within the rendering pipeline with future development.