FragBum

Okay see if dropping PD to 1.0 and adding MSAA @ 2 gives you better performance. Both PD and MSAA by themselves are CPU and GPU intensive. I basically try to keep CPU usage of the core doing most of the work at about 80% it will ramp up and down as well I try to keep GPU usage to around 70% this will also ramp up and down. I do most of my tweaking using task manager. short description might help.

Maps in order of performance for SP Free Flight. NTTR by far the best. 45FPS rare drop in FPS Caucasus Slightly more demanding 45FPS occasional drops in FPS PG More demanding 45FPS regular drops in FPS Normandy The most demanding can usually hold 45FPS most of the time. With VR keeping my settings the same all low level flying in and around built up areas in helicopters. My Settings here PD 1.1 All testing done using FPS in game display and task manager to monitor CPU and GPU usage. Oh and seat of the pants as well. :thumbup: I don't see any significant difference on MP servers except lag events. HTH

That's worth a try good call.

Whilst not super scientific you can get a pretty good idea of what cores and CPU utilisation DCS uses. Simple method look at task manager processes and there is an entry for DCS (when running) that indicates overall CPU process utilisation typically about 15% for me it varies depending on map mission and what I am actually doing. Next display the CPU graph do some flying or what ever and gauge what each core is doing once you get a general feel for what DCS is using use task manager to kill the DCS process and you'll see what cores where used which in my case includes Rift and some other "helper" processes. Then start DCS up again watching task manager. 15% just roughly is 1 core peddling away at near 100% for my 6/12 core i7 as indicated in task managers CPU window. Also DCS has it own built in FPS (and other data) that you can toggle on and off with "L CTRL and Pause/Break" key combination. As I said not exactly scientific but you get the feel for what is going on and in my observation as soon as either the CPU core that is doing most of the work or the GPU hits 100% usage that is when DCS stars to drop frame rate. Now all we need is a 20Ghz 2 core CPU,.. :D

Works an absolute treat especially if you take out the center detent, these are RC shock/spring assembles with the spring removed. There is enough "resistance" to movement to hold the cyclic where I leave it which allows me to use mouse or keyboard if I need to and I don't ever use trim. My prototype cyclic @OP nice to see other solutions at work. :thumbup:

I've run pretty much this setup for nearly 2 years works perfectly for DCS.

Huh! No just windows start menu navigate down to "Eagle Dynamics" then under Eagle Dynamics selection is a selection "Repair DCS" just use the mouse to select it like any other app you would run from the start menu. :) If you really want the command line version I'll give it to you however thats not really necessary ATM. Have you managed to get a copy of the DCS log after DCS crashes?

Exactly. :thumbup:

I know it's not exactly what the op wanted but we kinda got a free helicopter with the minigun version, just saying. :music_whistling: Now where's my free lunch,.. :P :D On a more serious note a free helicopter module would kinda be great like you get the su27 and the 51 but I cant think of any suitable from the current range of existing modules. I do like the idea of a test drive type offer sort of like here have it for a week long enough to just get to like and just enough time to start to get confident with it. The customer would then be more likely to buy it.

Wireless should be okay for LAN but what is you actual connection to the internet ADSL?? what I'm asking is it like copper wire to the house or something else? I'll check but I not sure about disk usage, generally in SP I get about 6 to 8GB RAM and 6 to 8 GB VRAM in MP about 16GB of RAM and 10.something GB of VRAM. Just a thought did the repair utility do anything for you install? Yep you need that fan working. :D

Your RAM capacity seems low for MP Server would consider 16GB. What sort of connection are you using?

The log file is over written each time you start DCS just check it and rename it, if you can compress it and attach it to the post. Some servers will boot you if you have any "mods" as well as booting you for long ping times etc. But you usually get a message telling you why. It would be more helpful if you could tell us what version etc and which server(s) :thumbup:

No it works okay for me ver OB 2.5.lattest, Logging on can be a bit of a dogs breakfast and literally take minutes. Have you checked the C:\users\saved game\your_DCS_version\logs\dcslog that may indicate something. How does it crash? Try running windows start-> Eagle Dynamics->RepairDCSWorkd->your version

With those settings I can run PD @ 1.1 which ramps up the GPU usage I can also run PD at 1.2 ~1.3 on NTTR map only Caucasus PD 1.2 max and PG and Normandy PD 1.0 or 1.1 without too much of a FPS hit. I'm trying to put a second rig together for DCS given the cost it may have to use my 980Ti pretty much equivalent to a 1070.

Ah yes I'm seeking some quantitive information especially for DCS. A lot of the reviews I've seen show from smallish FPS gains to maybe 10 or 15% gains in some resolutions and the gains can be a mixed bag. The 2080 from what I see is quasi equivalent to a 1080Ti with less RAM and no real benefit. Reason I ask is of corse the freaking price between $2000 and $2400 AUD here for an RTX2080Ti Link to my current DCS settings For NTTR and Caucasus maps pretty much does a constant 45FPS ASW on, PG and Normandy maps well not so good with frame rates dropping from time to time. So I need to tweak to reduce the likely hood of dropping below 45FPS.

I'm on my laptop ATM but just an idea how much fuel do you have in the main tanks? The header tank from memory gives you about 30mins flying after the transfer pump alert.

Not sure what benefit your 2080Ti has over 1080Ti and I would be interested to know, however as for DCS if you look at CPU performance you should see one core pretty much hammering along at near 100% depending on settings etc. As for why DCS has difficulties with VR I suspect it's to do with code efficiency and shaders, given that in DCS ver 2.0..2.3 I could get constant 90FPS with a 980Ti under VR now I struggle to maintain 45FPS with a 1080Ti on PG and Normandy maps. That's progress for ya. :cry:

Yes it's amazing what the brain fills in to make what you perceive visually in VR feel "real" of course you don't get the G's of being in a aircraft which probably would slow down a lot of the jet jockeys with some of the manoeuvres I see. To that end motion platforms and VR would likely be as close as you can get at home. Love that zero G feeling doing vertical stalls. :D

Roger that, we are seeing performance tank with current technology offering only marginal improvement at this time. :thumbup:

I think you'll find with some effort you can adapt to both. :D

My thinking is that there is no best hardware as such especially for VR and yes single core usage is the limiting factor for us currently also and again especially for VR GPU is limiting as well. I'm looking at either an upgrade or new PC but it really is getting to the pointy end of diminishing returns. The PC build also depends on what price your willing to pay for what performance. For example I'd be keen for a i9 9900K but given it's price (including a new mother board) and well "a maybe" I might get 5.2Ghz I can see the $ vaporizing away given that I could expect a several % increase in performance, the down side I loose memory bandwidth over my existing CPU. :(. @Mr_Burns. I'm hearing you there rtx 2080Ti >2000AUS to replace/upgrade the 1080Ti and or psudo equivelent rtx 2080 costs more than a 1080Ti and has less RAM. :cry:

Although when I get wasted on MP it tells me the obvious but not always the cause. Interesting, maybe a netcode issue.

I think it's partly your brain adjusting to some elements of motion physically missing from the visual input you should get used to it, although it's important to not push yourself to the point of getting sick obviously. I also normally don't get motion sick, when I first got my Rift I took the Huey out and it was an awesome experience however after while I gave the Gazelle a go, lets just say after about 10 minutes I had to land it and take a break or it wasn't going to end well. Now it's fine no issue at all. Gotta say the first few times you crash in VR can be interesting. :lol: :music_whistling:

I can fix.that for you if you jump into the WO seat of.a Gazelle on a MP server with me prolly take a only a minute or so. :P:music_whistling: @OP just take it easy at first do not let first impressions put you off there are some aspects.that take a while to adapt to as well some time tweaking your system. :thumbup: <Edit> Keep in mind we're all here to help.

Something to also use with your testing is task manager and look at the different loadings that the various settings incur. I found I preferred MSAA to PD even if that meant dropping other settings to med/low etc. I found PD because it artificially increases the resolution and the artefacts it creates increased the amount of work the MSAA filter had to do, which makes sense but that amount of work increases in a nonlinear fashion. This is just by observing what the effects of MSAA and PD were on GPU and CPU usage. You might be able to improve the VR image by using MSAA at 4 and PD at 1.1 even if that means lowering some others. I also find to keep the VR frame rate at 45 with ASW was also to not push CPU and GPU at 99%+ but rather CPU at around 80% average and GPU at around 70% (that kinda works for me you may need to adapt for your system) However doing that seems to give the system some headroom, those usage amounts vary depending on what you are doing etc. Another observation is drop frames /stuttering or lag seems to occur when either GPU or CPU reaches 100%. GPU is obvious but CPU it should be the same with AMD CPU you'll find one core pretty much doing all the work so CPU usage might say 40% for a 4 core however you need to look at the core which is most active and keep that one from hitting full utilisation as well. If you haven't already discovered all the maps preform slightly different keeping settings constant and observing CPU and GPU usage with the different maps for me NTTR is the least GPU/CPU intensive map. NTTR pretty much always 45FPS Caucasus slightly more demanding slightly more frequent FPS drops and occasional lag PG more regular drops below 45FPS and sometimes lag Normandy somewhat more regular drops in frame rate and lag HTH