RuskyV

If head restriction ends up being implemented further down the road, I think it also good to add in some sort of "neck saver" or a non linear option that allows people to look to the 6 o'clock position a little easier.

Which I quite gratefully chose to support by purchasing the map last June, I just hope this is not going to be a trend setting theme moving forward with future maps. Cheers,

@Baldrick33Thanks for explaining that one Not that the money is a great cost given the currant offer, however I'm a little perplexed at charging us for essentially an update or refresh of a map, Syria had a whole bunch of updates including a load more airbases with an expansion to the west with no extra cost to the customer so I wonder what's changed this time round?

I was just about to buy it for 9.99 when it said I already have a serial and own the map? If I already own the map then am I just paying for texture updates? This is a little confusing to say the least.. When I actually decided to added it to my cart and attempt go through with the transaction it was flashing at me again saying I already own it, as it was warning me so much I actually backed out of the transaction in fear of paying for something I already had spent 34.99 middle of last year. Confused

I bet this would help with stuttering that’s been seen by people, hope ED have a good look at this as I think it could really help a lot of people. Thanks Taz.

This will definitely help, however it’s a patch put over a problem that needs to be sorted. A good portion of this community have mid to high tier systems capable of running a lot of modern games, those spending a lot of time playing those other games must be a little perplexed to be then lowering settings to get a game to run.

Every time you update make sure you clear out you metashader2 cache, as well as you FXO files in you saved games. Run a slow repair and try again.

Something of a trick you can do that can boost fps is to set the desktop resolution in the bottom of the open profile window to its lowest setting. Once in the headset you won’t notice it and you should gain a few fps, sometime quite a few

If you have an Nvidia card give the low latency set to ultra option a go, but don’t set it globally, only set a profile using the DCS.exe. You can try switching between DCS and your headset (if add as a profile) to see if that makes a difference. I would also go and set the FPS limiters to manual and then push the slider all the way right on both settings, there is rumours that if set to off the greyed out areas showing the FPS can be defaulted to a very low amount. You are essentially un capping the fps by maxing out the slider. Your headset native frequency is worth paying attention to. 144hz = 90fps minimum 90hz = 40-45fps minimum 45hz = 27-30fps minimum 30hz = 27fps fixed 18hz = 27fps fixed (for some reason DCS seems to act as if 27 is a fixed number and won’t go below) Frame time can be a real issue if you hit way outside these numbers which in turn causes stuttering. If you know your system can only hit a certain level of fps then you need to adjust your headset frequency to match as close to these numbers as possible. FPS governs frequency, frequency governs frame time, frame time governs smoothness (hitching) hope this helps.

Object textures always caused memory problems. Just sit in the encyclopaedia and flick through every unit and module including liveries and your ram will be out of memory before you reach the end. I think for multiplayer servers, the owners often use all available liveries for modules they add so players can customise. I theorise that this is part of the problem as not only is the module loading but often players will sit and flick through multiple liveries, this eventually has to be communicated to all other players. When that player comes into range of others the livery then loads for others, however if that same player then changes livery and comes back into contact with those same players multiple times I wonder if you can quickly end up with a similar scenario as with the encyclopaedia? Limiting liveries server side could help clients in theory…

@cboy i Had the same issue as you a while back.

Hi @Candiru89 im glad I could help you, even thought it was probably only a little bit

I think this is a bug with motion blur, try disabling and testing without.

Are you running any kind of overclock on your GPU? If so try running without an any overclock and test again.

Under the Nvidia control panel try adjusting "low latency" to ultra. Don’t set it globally, use a profile for DCS. If set globally then it will mess with your VR software and you will run into issues.

I had the same issue with my 12700KF, I’m using process lasso to de-selected the e-cores from the DCS.exe. This forced it onto the physical cores.

Take a screen shot of your in game settings.

Something I noticed after the beta update is that the GPU now runs a little hotter (10-15`c more) What was happening to me was those temps were getting into the 80s +. As soon as this happened it started to down clock the GPU even thought the fan speed was only at 50% the firmware decided to use clock cycles to cool the card instead of ramping the fans to cool the card. In game I can watch frame times pick up a lot of activity and then stuttering happens, it could be that you are at a threshold hold point and the slightest increase in activity pushes the card to underclock. DCS is very sensitive to overclocking, I know this as I started to get random crashing with just a mild overclock on my GPU. It’s perfectly conceivable that the same could be said for underclocking. The reason I think Nvidia do this (although not certain) is that it’s better to build in protection to underclock and reduce voltage (cooling the card) than it is to rely on all those different fan and cooling solutions applied across all different brands of cards. -Download any of the well known GPU tools that allow you to either set a manual override (or a fan profile) that will cool the card and keep it below 85`c might cure your problem, and if it doesn’t then it’s one thing less to worry about. 85`c seems to be a soft limit set in the firmware for Nvidia cards. Watch Red kite’s video on MT and look at the differences in GPU use and temperature across versions, you will see a 10-15`c difference, DCS now works the GPU harder. good luck, hope this helps or solves the issue.

Hi @Recurve First start with cleaning out both your FXO and Metashaders2 by deleting the contents, you will find this in DCS saved games. Next clear out your DirectX shader cache (right click your OS drive and properties > tools> Disk clean-up. You can also clean out the Nvidia cache located here C:\Users\YOURUSER\AppData\Local\NVIDIA (There's DX and GL cache folders) With all shader locations deleted your game will take some time loading while it recompiles new shaders, load up the game and check to see if you are seeing any improvements.

The only time I trim reset is after landing, this is just to give myself a fresh starting point for the cyclic . Other than that activating in flight is often a one way ticket..

Maybe they are looking at fixing splash damage first then, pure speculation on my part though..

A fix that easy should have been done months ago, there must be more to it than that if ED have not fixed it yet surely?

How i mitigate this problem: collective full down. (Cycle up and down if needed) start both engines almost simultaneously as soon as they both ignite crack the power lever slightly and wait for both engines to fire up. Advance power levers as normal.

I would love to see more functionality for the apache but an underlying platform that performs well and opens new doors for future models and technology is also important, as frustrating as it can be to want something specific done for the apache, there has to be some appreciation for the efforts made in these other areas too. Is development slow at times? sure it is, but there are good reasons for it.

Work in progress….