RuskyV

If you wanted to set or select cpu cores you can do so by adding this command to the end of the target shortcut. - -affinity=FF (the double dash at the front of the command has no spaces and is gapped for illustration, minus key twice) Where FF is the core count (8 cores for FF) in Hex, you can work out what code you need by visiting here and selecting all the cores you want to try, https://bitsum.com/tools/cpu-affinity-calculator/ This is an alternative to downloading additional software if it helps.

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.

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.

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….

It’s crazy to think this has never been looked at…. Very frustrating.

It would be nice to be able to have the cursor cross used in the cockpit and have it align with the radio menu and other context menus that pop up. I fly in VR and it is a really big faff to move the cross cursor in an area other than the menu in order for the white dot to show up so I can finally click on options. multi crew name selection window……what a pain that is!

Pretty much, it’s more of a compromise really when wanting to use other modules with my setup. The only thing I occasionally adjust is the pressure to help prevent any wild oscillations, this is important as different modules react differently to stick movements, some fast some slow. Getting the right balance per module is key to not induce any unwanted over correction resulting in a reactive feeling rather than being pro-active if that makes any sense.

I tune my cyclic axis to make flying while FTR held easier, this has the side benefit of making the helicopter more stable when the SAS is doing its thing without FTR pressed. Might help get a better feel for what we have now, possibly a little more manageable while improvements are being made.

Measuring force instead of positioning has a distinct advantage when it comes to muscle memory, when I want to roll or pitch I know how much I need to lean on that force. For me personally it allows more accuracy and is easy from module to module to get used to, helicopters are amazing with a force sensitive stick as you can adjust the pressure in lbs to achieve the desired amount of accuracy with minimal use of curves and saturation per axis. an analogy would be using the brake pedal in your car, you know how hard to push it in order to stop at a given speed, if this was purely used on a position basis you wouldn’t get any consistency in braking. I love it and would by another one at the drop of a hat if anything should go wrong with mine.

Ok an update on the above. The new realsimulator device tool now has a precision `option` mode (something new to me) that can be configured as a percentage of the total force available. This is activated by the first detent trigger and can be used for many things. This is not an ED issue at all but a rather nifty feature of the R3 lightning that can be used for precision movement of the joystick. Thanks for all the help

I’m wondering if the real simulator software has something to do with it, I’ll check and report back. at least this narrows it down somewhat and it’s not an issue with the FM.

I’ve noticed that when pulling the first stage weapon trigger as the pilot, the cyclic control seems to loose a lot of authority in both pitch and roll. Having the control indicator called up I noticed that the movement was reduced by quite a bit, this can be tested without arming the helicopter or selecting weapons. A simple pull of the trigger and controls almost freeze. is this behaviour intentional?

If your so full of knowledge why don’t you try being a little more constructive in actually helping these guys, who reads a manual from cover to cover before jumping in and having fun anyway..

I think it’s the parking brake….