FragBum

Unless that has changed you get the head movement from the recorded track and what ever head movement you put in during the playback the other gotcha again unless it's actually been fixed is that you will likely fly directly into a building or other object because track playback doesn't work still. I could be wrong as I haven't used in a long time and just leave it in the ever expanding looong list of stuff not fixed in DCS. ;)

Yep I like smashing them as well,.. :D

I know your not using VR but I found in Rift VR any amount of AF caused issues with image clarity. Maybe worth turning it off and check.

Unless it's changed you need to install the drivers when you install windows at least that is the case with Intel 750 series. Stutters or drop frames are very much linked to CPU or GPU bottlenecks as far as I can tell. There isn't much drive or virtual memory activity going on in usual game play. :)

His ED account login "username", I presume so it can be applied to that ED user.

Agree save $220 on SSD. Yes nvme is faster but once DCS is running (it boots up quicker now on 2.5.4) and it doesn't seem to make any significant difference in game. You'd likely gain more in a CPU/GPU maybe even memory bump. :thumbup:

From here,.. I would strongly disagree with this as an option, it presumes that you do not scan the whole screen presented on the HMD by moving your eyes as you would in real life. :(

Sounds great will probably wait out for this to upgrade from Rift. Really good to hear peripheral image quality is good however a question and I do use peripheral image view a lot typically in Gazelle looking back and up through the roof panels even to the point of moving my eyes further to identify objects that I would in real life be looking at them directly but in Rift I'm looking at the edge of the screen with degraded image quality. This lower image quality seems to be partly from Rift lens aberration and partly from 2.5.4 processing. So just how clear is the image in wide FoV at the edges, usable in the above scenario? I'm okay if the very edges are slightly degraded. Currently I still think 2.5.3 had better image quality across the the whole Rift image.

I have sat people down beside me with the Rift and flown the Huey by the monitor screen works okay but can get interesting as you need.fo get them to look ahead from time to time. The Gazelle is somewhat more challenging under those conditions.:music_whistling: I'm currently working on a second PC for this reason and also have others fly on as well.

Well more on performance and CPU usage. (Now that I have image quality back to about what is was like prior to 2.5.4) After tweaking last night I checked Caucasus map and there is a small but possibly significant difference here in the NTTR screen shot one core seems to be pegged at 100% but in the Caucasus map this doesn't happen. as per Average usage for test mission Caucasus map. This is from my first post but looks representative for NTTR test mission, notice middle row 4th column core seems pegged at 100% Interestingly NTTR was the least CPU/GPU intensive map prior to OB 2.5.4 whilst that in itself isn't an issue as the map still preforms well I just wonder if that core should be pegged at 100%? Anyone else seeing this increase in CPU usage it appears quite significant?

Yes I'm seeing FPS still 45FPS I do prefer ASW on. I simply can't run PD at 1.5 I hit CPU and GPU limits with the accompanying drop frames. As for CPU usage you should find there is more CPU activity under 2.5.4 prior to 2.5.4 I would only hit about 16% CPU usage I am now seeing up to 30% CPU usage NTTR map. Ah that sweet spot from what I can see it's seems to be straight ahead at center of view and effects different ranges of view depending on how much processing you dial also the width of it varies. The width can be very narrow maybe 1 degree at a few hundred mtrs to several degrees at 20mtrs. The area that is well processed seems to vary with the level of processing as far as I can tell. There is also a portion of lens aberration within the Rift as well. Try this as in the video. Park your self in front of a mesh fence move your head left to right but keep your eyes focused on the the portion of the fence straight ahead of you even though you head is looking left or right. You should see a difference or change in detail level of the mesh. TBH I don't think the peripheral image is as clear as it was 2.5.3 was, indeed no where near it but I guess that will be fixed one day. I had the system tweaked well under 2.5.3 Rift image was near as good as screen display with the limitations of Rift of course and smooth constant 45FPS. however with 2.5.4 I have had to turn off Anisotropic Filtering it just looked horrible at anything past maybe 100mtrs. I tweaked PD to 1.1 with MSAA at 4 to keep CPU and GPU from hitting 100% running any more PD and Rift became a stop frame video effect. Oh as a side note we don't want any VRS (Vortex Ring State) that's bad for helicopters. :P :D

Okay we really need more info if you can post your system spes Can you post your DCS log file. Also is your video driver upto date nvidia version 417? Apart from you there doesn't seem to be anyone else experiencing your issue, if you are on DCS world OB 2.5.4 there have been significant changes effecting graphics I have had to tweak my settings to allow the full benefit of 2.5.4 Also be aware 3rd party mods need to be disabled as there have been compatibility issues with OB 2.5.4 As some lights come on when battery switch is turned on that's the only thing I can think of but without any information about your system or DCS log we really can't help.

Okay does it happen with autostart or start hot?

I have solved the image quality in Rift! basically what I did. Anisotropic filtering was causing the issue as the near field image looked good the mid to far field looked rubbish, full of aliasing artifacts. So I began tweaking and removed all MSAA processing but the issue was still persistent. I then removed my modest 1.1 PD setting still no change. Dropped the AF setting from 8 to none, bingo. Okay no where near as sharp over all so I ramped MSAA back up to *4 better still not great then I ramped PD up interestingly I can now run PD at 1.3 and avoid FPS drops in NTTR where as prior to 2.4.5 update I could not with or without AF and it looks amazing! Not only looking awesome now and I thought I had it looking and preforming great in 2.5.3 I am seeing increases in CPU usage corresponding with improved image quality in (Rift) VR with improved responsiveness in the SIM. Stay tuned and input welcomed.

Resolved Okay I have a work around which gives unexpected results. Anisotropic filtering was causing the issue as the near field image looked good the mid to far field looked rubbish, full of aliasing artifacts. So I began tweaking and removed all MSAA processing but the issue was still persistent. I then removed my modest 1.1 PD setting still no change. Dropped the AF setting from 8 to none, bingo. Okay no where near as sharp over all so I ramped MSAA back up to *4 better still not great then I ramped PD up interestingly I can now run PD at 1.3 and avoid FPS drops in NTTR where as prior to 2.4.5 update I could not with or without AF and it looks amazing! Sorted!update DCS 2.5.4.26368 :thumbup:

Yes is a blast isn't it.:thumbup: :D

There are other threads indicating there is a possible bug with Huey crash DCS may also crash. 2.5.4 OB

I would also suggest adding some limiting and some gain to bring the audio well into the limiter. But don't overdo the compression radio systems run voice processing and limiting to improve intelligibility and signal to noise levels and bring lower levels up to a prescribed threshold level. Nominal audio BW 300Hz to 3000Hz SSB maybe to 4000HZ AM/FM Don't forget DSP can easily brick wall audio response which will tend to sound harsh even grating to most people especially using HiFi audio systems so maybe allow a bit of slope on either end of the bandpass filter for the bandwidth filtering. Instead of "clicks" in your DAW make an envelope and use that to modulate bandwidth filtered noise to replicate carrier/signal loss at the end of transmission and the squelch kicking in in the receiver. You could use a shorter envelope for the break squelch at the beginning of transmission as well. I take it mixing "white noise" back in is to give the effect of system noise, this usually should be somewhat down in level compared to the voice over level in radios systems unless your representing marginal signal conditions. Foxtrot Bravo out, schhht. :)

No issue at all in VR, have you tried deleting your fxo and metashader folders and let DCS rebuild them. These are located. C:\users\youraccount\saved games\DCSworkdopenbeta\ DCS will take a while to rebuild these when it's started.

Take care all. :thumbup:

Actually that seems about correct given core and clock speed there is currently only so much CPU DCS can utilize as well that can only feed your GPU so much. Perhaps look for the bottle neck and adjust settings to suit and it may play better. :thumbup:

So it's not in your module manager? Maybe raise a ticket or there is usually online chat on the eagle Dynamic's site might help.

Have you ran repair utility?

Just for giggles. Using the skids, well actually not really they are just in view and only form part of the visual input. Link to Video <edit> You should follow procedure and run through this scan all the time. :) Power. Is the power set correct for the specific flight mode? Performance. Is the performance correct i.e. is the speed and climb/descend rate correct for the power set? Instruments. Is there anything contra indicative temps, oil pressure etc scan all of em? Attitude. Is the aircraft attitude correct for the manoeuvre and reflects what the instruments indicate?

Absolutely! VR gets you so much closer to a flying experience in a SIM and gives you an incredible sense of situation especially for close in work in helicopters.