Tinkickef

Exactly. Be sure that the 2080TI is a force to be reckoned with. It's just that the VR software is not there yet. Some games show a 50% increase in performance, yet others show very little. Optimisation is the key. VR is still filling its nappies and drinking out of a bottle with a rubber nipple. The software will improve If you had a hypothetical 5380Ti, you would still not see a big performance increase. The old adage for computers applies.... rubbish in, rubbish out.

TBH,if you have a 1080TI, I would advise you to hang fire for a while. It only works for me because I went from a 980TI to the 2080TI and I was always going to buy into the series after the 10s anyway. Always have ASW on and it is smoother than before, but is not earth shattering. It is more stable however as my old 980 was seriously OC. Until Vulkan and the promised VR optimizations come on stream, you will be disappointed. No hardware can compensate for poor optimisation.

Keep one eye on your nozzle position indicators on the engine display. When closed in full military power, both nozzles will show one bar from the top. (Edit... note that you will not see 100% N2 at altitude without AB lighting which is why you watch the nozzles, everything else varies with altitude). When AB lights, you get a progressive opening of the nozzles depending on how much fuel you are pouring into them. AB on the Hornet is progressive and variable, not a one shot deal. I always use the indicators to set full military dry power in the climb. I have even had nozzle actuator malfunctions and had to RTB. The IFEI should be regarded as an instrument that should be cross referenced every few dozen seconds. If you routinely do missions over 750nm with no in-flight refuelling, you should be referencing it as part of your in flight planning and fuel management in any case.

Well I found your post informative Worrazen. I'm one of those who thought TaskManager was telling the truth, load spreading for temp control ect; and based a lot of advice posts on the back of it in the past. After reading your post, I now realise I do not know enough to be offering sound advice to others and should keep quiet. So your post has at least one positive..... it has stopped me from embarrassing myself further. :doh:

Press it again....

Map size is final with countries already set. Map team have moved on to developing another map, however, PG is not finished and new content will continue to be added, just not as fast as previously. I personally think it would be a good idea to allow those players who are avid map builders to add features such as air bases, towns ect with ED controlling the quality of the submissions to be added to updates. Of course ED would have to supply the tools (esp the ability to lay concrete, grass, tarmac and trees ect) and the direction. As I see it, the maps still get regular updates, the hobbyist builders get their stuff on the main map, the quality is tightly supervised, so air bases ect have to be extremely detailed, and ED map team can concentrate on new content. We all enjoy the results and everyone is happy.

So, I have always stuck with classic home. I don't give a monkey's about changing the colour of the sofa in a virtual room. Now they have enforced this update and I'm now getting hourglass and stutters which blows. Anyone got any ideas of re-establishing classic home?

Press Num 5 to recenter your view.

I don't have OVRservice on my rig. I have OVR service launcher and OVRserver#######

My VR pit.... %5Bimg%5Dhttps%3A//i.imgur.com/zyXbfYa.jpg[/img]

Driver 24.21.14.1163 is the one I reverted back to. 25.21.14.1616 is the bad one.

Do NOT switch to the new Nvidia driver that came out a couple of days ago. Seems to lock PD to native value and introduces generally poorer performance in VR. Colours washed out, shimmers with head movement ect. I had to revert back to the original one. Far better.

Ditch MSAA it does very little to zilch in VR. If by AA x16 you mean Anisopteric filtering, you can keep that as it does not have much impact on frame rates. If you mean SSAA ditch it. Have a look at how your logical cores are performing in task manager. Remember that TM shows 2x logical cores (LC) for each physical core (PC), so as in my case if you add each LC on the PC that DCS is using you will get a ballpark figure on that core load. In my case I had one LC showing around 30% and the other 40%, so the physical core DCS was using was loaded at 70%. A useful overhead remaining on that single core, but only 25% overall CPU usage. This where Vulkan will work its magic with multithreading. Bottom line, so long as my missions do not include huge add ons (see below), I have no need to go ahead with my planned 2019 CPU replacement schedule and keep the money in my piggy bank a little longer. As others said, 700 AI units is a LOT of processing and will eat away at any overhead you have. My testing was done on the quick mission generator with the AI red and blue units set at default, so there were probably a few dozen planes, helicopters, vehicles, infantry and anti air units, but certainly not 100s. The main bottleneck for frame rates appears to be within DCS itself, VR is an addition added later, not built in from the start. It works, but it is not very efficient, seems to have a lot of internal latencies which get higher with texture quality. It does not matter what hardware you have for DCS VR use, you will always need to rely heavily on ASW. As such I am never really bothered about frame rates in themselves, it is the experience I am interested in. If the experience is smooth and without stutters with ASW making it so, I am happy as a clam. Vulkan and fresh coding will be our saviour. I hope. I suspect the CPUs are processing a lot of stuff that no longer apply. Must be a nightmare making changes to DCS code as it is so unbelievably complex. We can thank our lucky stars that ED have some of the best flight sim coders in the business, and even they screw up regularly.

Look in on the Aurelious Augustus thread. He is a pro and doing a far better job at testing than my amateur attempt. Also, my tests were in response to specific requests for test data on how the 4790k in particular, handled the 2080TI when I revealed I had one on pre order, so everything was conducted in the worst case, CPU intensive scenarios I could think of, including default quick mission generator AI friends and enemies. I concentrated far more on CPU performance than card performance (excellent card performance in relation to my old 980TI being a given factor), although once Knock Knock showed me how to include frame rates, I did so. Nice to see many of AA's conclusions are the same as mine though. AA's thread is much more professional, generalised, card /headset orientated, and of more worth to the average VR user. Plus he is doing his tests on Caucasus. Time to bow out and let the Pros handle it from now on. :)

I downloaded Evga Precision X1 very late in the testing to see if it would bump up frames (nope still locked to a max of 45fps by Oculus despite asw off)by doing a little overclocking on my Asus Dual. It incorporates the Nvidia scan tool for one button overclocking. I got a score of 70 after all the adjusting and testing (whatever the 70 means) with a target temp of 84 degrees and 110% power. It hit temp before power target even with fan curve set more aggressively, so definitely a case there for fitting a waterblock. Interesting to note that during the scan tests, the results differ wildly. I have seen a score of 30 and a score of 90, so I guess you run it repeatedly until you get the score you want and save that setting. I found it important to reset the card to default before the next scan if I didn't want the results to tank. Don't really want, or have the confidence to manually OC the card at this moment in time. Maybe in two or three years when it starts to struggle.... Can't wait for Vulcan, the promised VR optimizations and Gen two headsets. Should make life easier.

I'd put NTTR as the best performer, followed by PG, then ,Caucasus and lastly Normandy. Normandy needs speedtrees badly as well as a little TLC re water textures which are still not where they once were.

Zhukov is entitled to his opinions and entitled to voice those opinions. I do not agree with him, but it must be remembered that everyone looks to get different things out of any game or sim. Much of what he says is true, if a little over exaggerated. Using VR or monitor in DCS is a compromise. Monitor you compromise immersion for resolution. VR you compromise resolution for immersion. I would wager that most VR users are mainly SP guys that enjoy flying over raw combat, rather than MP types whose sole reason for taking off is combat. Apples and pears, but both are fruit grown on trees.

It will be interesting to hear your results with Vive Pro. Raw resolution via higher pixel count should be much easier to maintain for the same image quality than the software solutions we currently have. Running 2.3PD for a very tiny difference over 1.8 PD is an horrendously expensive way of doing it.

Wags is aware of this thread.

I do not have Il2 BoS. I do have 1946 and CLoD, although I have not used either for 2 years or more. My honest advice between 1080ti TI and 2080 is go for the 1080TI for the reasons you stated. The 2080TI is an astonishing card, but is badly let down by the DCS engine. I finally settled on a PD setting of 2.3 for my every day use!!! and find this fine. When DCS finally goes over to Vulcan and Gen 2 headsets come on stream, that's when the 2080TI will shine.

Textures. Shadows. PD is limited by hardware. Textures and shadows limited by DCS engine.

As with everything...It depends. 2080 has around the same performance as the 1080TI at a higher price point. It depends how much value you put on ray tracing and DLSS, neither of which is valid for DCS at this point in time. If you plan on buying games like Tomb Raider with RT and DLSS, it is probably worth it.

Great news Hannibal. I will bump this thread up to DCS World where it has a better chance of being spotted.

After a few beers, well more beer than is good for me, I have come to a final conclusion. It is a conclusion that is already well known and simply that DCS is so poorly optimised for VR that no hardware can make up for it. No doubt ED will have plans in the pipeline to address this sometime in the future. So to cut to the chase. If you want to run high settings and far higher PD than before, then look closely at 1080TI benchmarks and compare them to my results before committing to 2080TI. You will be relying on ASW pretty much all the time anyway. Current VR hardware cannot utilise the enormous power this card has and is something else to consider. If you have a 1080TI and are considering the 2080TI, my advice would be to hold off for now. If you have a 9 series card, are looking to upgrade and can still afford to eat after buying the 2080TI, then by all means buy it. I have no regrets and see no point in buying obsolete tech, not knocking the 10 series, fine cards, but they are now obsolete. Until DLSS and ray tracing comes onstream, I see little point in buying the vanilla 2080. What the 2080TI will give you is a stable as a rock experience with very very few jitters even at common chokepoints like turning onto the runway. Very smooth even at high settings. I think that overall the card has coped admirably with the torture I have thrown at it. Remember all my testing was done in absolutely worst case scenarios. Flying my usual missions are impressive as Hell. MSAA and SSAA. Frame killers and I cannot say they are worth it. Not sure if they are a placebo or not. SSAA, I may just turn back on to load the card. Pixel Density. This has the most effect on image sharpness, I can see the difference between 1.8 and 2.3, even if it does suffer from diminishing returns and I will bump this back up. No point running the card at 60% chasing frame rates that are simply not there. DCS needs serious optimisation work. You still need to trade image quality for frame rates, I think this bottleneck is within the DCS engine itself. Again individual choice, I prefer quality over quantity, but then for me, combat is secondary to flying. I7 4790K OC to 4.48ghz. Impressive as Hell, it has taken everything I threw at it, chewed it up and spat it out. Hope you found these tests to be as unbiased and as truthful as possible, my intention is to help others make a more informed decision re upgrading. For myself, I am happy overall, maybe a little disappointed in some areas, but those areas are not the fault of the card. The 2080TI is not a panacea for all of ED's ailments. Thanks for looking in.

What I don't understand is that neither the CPU or the card are anyway near being maxed out. The CPU is clearly delivering all the data the card needs and the card is putting it out with ease. There is another bottleneck somewhere. I did suspect RAM, but lookat the VRAM. no peaks or troughs whatsoever and no hourglass, jitter or stutter. Could Rift computing / display engine be slowing it all down? EDIT :doh: Tried same mission again, switched off ASW and this time got a jitter fest at 30fps. Looks like I was suffering from fat finger syndrome.