FragBum

Sure but before the latest update Rift was IMO perfect now it's a fuzzy in all but the center aperture of vision. I have also done the usual delete fxo and shaders dirs not improvement. And guess what the updater will not allow you to revert to the previous version. Just sits and tells me it aup to date I've used the same CMD many times before and it worked but not currently.

Alright now it seems you can't revert to the previous version DCS_Updater Update DCS 2.5.3.23954 When I run it simply says I have 2.5.4 and it is upto date which is a PIA as 2.5.4 is rubbish in Rift Any suggestions??

For Rift users don't be in a hurry it looks rubbish in VR poor fuzzy image quality and a 12GB download to boot it seems you can't revert back to the previous version. The Rift image is only kinda clear right in the center and fuzzy all around the rest of the image.

Udapter broken can not revert to 2.5.3 Alright now it seems you can't revert to the previous version DCS_Updater Update DCS 2.5.3.23954 When I run it simply says I have 2.5.4 and it is upto date which is a PIA as 2.5.4 is rubbish in Rift Any suggestions??

Update DCS 2.5.4.26368 appears to have fixed the issue. Anyone else getting very fuzzy image quality with Rift under 2.5.4. Seems like the tiniest center aperture is kinda okay but the rest of the image is fuzzy like there is no MSAA processing applied to the surrounding peripheral image it kinda makes DCS useless to fly in. Yes I have done the FXO and shaders BS again but no change to image quality.

Wow 2.5.4 sucks, image quality for Rift there is now a tiny center portion that kinda looks ok but the rest of the Rift image is very fuzzy I.E. when rolling eyes to check peripheral vision elements. I'm going to pull the pin on 2.5.4 and roll back until this is sorted. The other thing I see is CPU utilization go up from 16% ish in 2.5.3 to a whopping 28% ish in 2.5.4 for poorer image quality and the same 45FPS.

By not pulling hard on the collective, look at the engine RPM and rotor RPM gauges the generator failure will happen under 2 conditions Rotor under RPM and rotor over RPM You need to keep descent rate well under say 1 mtr/second when your out of ETL when you have some speed over say 100Kph you can be a little more keen on descent initially try to keep this under say 3mtr/second.

Okay just did the update and a quick test in NTTR. Okay seems there is something new going on with CPU usage <now> hitting 28% (ramps up and down) this was around 16% in 2.5.3. What is interesting is we now have a second core hitting 100% utilization here normally only core 11 is hitting high 80 + % but now there are 2 cores. What happened to my peripheral vision in Rift only the tiniest center portion of the Rift image is in any sense clear and the peripheral portion of the display is really fuzzy, sorry guys this ain't good enough I rely on being able to roll my eyes to look at the extents when flying Gazelle at high speed through built up areas it now looks like someone smeared Vaseline around the major portion of the display. This was very acceptable and usable in 2.5.3 but not anymore.:cry: <edit> no this doesn't work currently. This might have been a typo My biggest question is with all the additional CPU utilization what exactly are we getting? I will do some more testing but this reduction in image quality is really pointing to going back to 2.5.3 ATM

Well I'm not sure what you are experiencing, ;)

I know but can we get the multi-core CPU graph perferably just after doing some taxing or if you fly helicopter just after manoeuvring and set down so we can see what the CPU cores are doing. BTW looks like your GPU is not getting enough data from CPU to keep it occupied. Server side has some issues for everyone we call it lag and can be maybe 1 to 5 seconds usually at a most inopportune time. :cry:

Just for comparison quasi the same situation/aircraft with exactly the same settings but in Normandy map, as you can see GPU usage average is much higher than in NTTR map hence the performance issues with that map. The PG map isn't much better. CPU usage does vary between maps but it's the GPU usage that seems to hit the wall mostly.

I have no idea where that comes from my monitor is 2560*1600 but I see mines the same setting?? Yes set nVidia to allow app to set settings as best I can tell most anything in nVidia doesn't do much/anything in VR.

Cool okay can you also show individual core usage like this. I suggest setting PD to 1.0 as a baseline as per previous post you need to get a comfortable 45FP with ASW on then you can explore PD MSAA and AF settings, as I said you should be able to set most everything else to what I have there isn't a great deal of difference between our PC's.

It's not my original idea there are some posts on this mod even on this forum I just adapted the concept to suit. :thumbup: As far as I can tell they are just linear dampers in use for RC service they are paired with springs which can be linear or progressive for the non-linear suspension function. In RC Car circles high end damper kits can have adjustable restrictors even bidirectional adjustment as well as a range of oil grades to allow users to setup their car just the way they want.

Yes it will help give us a better idea of what you have set up. I'd be pretty sure with a 1080 and 4.2GHz CPU you could just about run your settings mostly as mine are with PD @ 1.0 and perhaps MSAA @ 2 and shadows off. with ASW on @ 45fps.

Maybe,.. :D

It stems from logical zero is the first instance of something, like address zero is the first logical address of the first memory "block of data" or byte. Think about 8 bit binary which can represent a maximum value of 255 or 0xFFh however those 8 bits can represent any 1 of 256 combinations. :)

Agree I just don't need the CPU overhead of After Burner/River Tuner it's not that I don't use them. We all know what happens when we saturate CPU or GPU, FPS drop there are other causes but that seems to be the root cause for my system. My CPU core 11 is the one that does most of the work I presume it's logical core 5. :thumbup::D

Visually the Rift looks okay*, of course the resolution of the Rift is 1080 *1200 but is reasonably sharp for DCS about as sharp as the Rift Home. Are you able to post you settings. *More is always better.

Okay that was my bad seems thats how it goes when starting up without focus on the DCS app I was looking at the task manager panel. As soon ay I got focus on the DCS app GPU dropped to 60% and DCS CPU went to ~4.5%.

Not sure about normal. :) However I do get 90FPS in the main menu which makes sense interesting to see CPU for DCS at 5.9% but the main menu is not the game environment. Try to turn shadows off that should lessen the load on your system. Can you post the settings.

For the gimbal I looking at using larger dampers from RC 10 Scale. like these ones here. There are adjustable ones as well.

<edit> seems there was a glitch in the Matrix. As soon as I got focus on the DCS app GPU dropped to 60% and DCS CPU went to ~4.5%. Okay main menu. CPU 5.9 light to low activity all cores 6.4GB RAM GPU 100% 2.4GB VRAM

I'll check although main screen wasn't a metric give us a bit and I'll start up the DCS machine.

Oddly the main menu is the only place I get 90FPS. I guess there will be some difference.but I don't expect it to be huge. On NTTR SP in the above .mentioned free flight I get about 7GB.RAM and 6GB VRAM usage. If I jump onto a.MP server this can hit maybe 12GB RAM AND A TAD over 10GB VRAM but that does vary a bit. For me I find just sitting on the ground in a heli I get about 80% CPU and 70% GPU usage this is my base line from there flying around the usage will ramp up towards 100%.