Hoirtel

Fair enough, yes my rig is well trimmed for too. However in a similar set up (on SA map) I get 7.X present and over 100fps. SA map seems to run really well.

Your CPU times for Present are high. I think this means background apps are draining CPU. Someone correct me if I am wrong.

Various different methods, but essential minimise all keyboard use. Most don't like hand controllers and use the mouse, it works quite well. Also a good hotas with extra switches helps and then there are also button boxes which provide extra places to go for essential bindings. I do have a keyboard I use, but only for esc and F keys when in game. I have bits of duct tape on the F1, F6 and F10 key to help, plus my keyboard has them in groups of 4. As for using key combos... not really feasible but then I could never remember them anyway.

Best thing to do is find something close in user files and then adapt it. Starting from template takes a long time!

If you are using Intel worth trying hyper threading switched off. I always run like this, no need for it with DCS. I actually used to get small stutters all the time on any map with it on, but I've not had it enabled now for a long time so might be ok. I get great performance so not too bothered about changing it.

Don't worry. You don't need it. I have had the half pink screen once after installing it for MSFS. I leave it disabled now and not had the problem since.

I'm thinking that once we start to learn this aircraft we will basically be able jump in either seat? That will be excellent in MP as it will be so easy. Much easier than the apache even as there is potentially no extra buttons to bind.

Do you have the open xr tool kit for use with MSFS?

Reducing resolution, msaa and textures will mainly reduce load on your GPU so you will probably have to bring these down quite far to help your CPU (as you may have found) try reducing CPU settings such as shadows, heat blur and civ traffic. Also chimney smoke. Really take a look at those background apps in windows. Especially those things that startup. I have Adobe Photoshop and disabling all adobe apps and updaters really helped me claim some stability in DCS. Adobe runs and updates just fine without it. With a well trimmed PC I find most MP servers very close to SP performance.

Sort of newsletter related... Did I spy a community mod in an official ED video..... Whaaaat! Is the A4 coming officially? Forever free? Would make a great aircraft to bundle with the download...

Yeah I see this too. When I test in 2D I notice that the goes up and down by a huge margin. Say from 40fps to over 80, then drops. Over and over in just a few seconds. Happens on any mission I have with the simpler missions having higher upper and lower numbers. Seems odd.

Not familiar with the real plane or later versions but the functionality in the harrier isn't too bad. No autothrottle but once you are at alt you can set and it will chug along nicely.

I've just been testing manual microswitch and this performed as expected for me. However as I previously only switched the yaw AP channel on for cruise I still prefer to fly with it off altogether most of the time I'm not a huge fan of holding the button down all the time. However when I do use it I'm enjoying the extra control, maybe I just need more practice. Don't feel the need to retest pedals in motion mode as this performed the same way as manual without pressing the button. I'm not that slow on the pedals... Any faster, or pumping, isnt how I've learnt to fly. Even in combat or on the range. Just for interest how often is this channel used realistically? All the time? I always use pitch and roll channels although I can fly without. Hardly ever use alt unless cruising and even then I generally don't need it. Might be doing it wrong though. Thanks to @admikiand @AeriaGloriafor the posts. Been an interesting thread.

I tested slow and fast movement and always felt it fighting me. Surely "disable when pedals are in motion" should show as minor dampening like roll and pitch does when am actually moving the pedals. I am referring to the channel indicators shown on the top right (white lines). Any turn it seemed to just try and hold my previous heading. As I have non centering pedals I have disabled pedal trim, or so I hope as the new setup means you have to choose a pedal trim option, then select it off when you choose which button to trim from. Bit odd. I didn't have the microswitch button bound when I tried it however. Didn't think I needed it. More testing needed probably!

Think I said to you before, with progressive pedal input, the control indicator progressively moved in the opposite direction. I was eventually in full deflection one way and control indicator showed full opposite. Heli turned like an oil tanker. The correct special option was checked before starting. I have only tried it that once. I may go back and try again after I have had a bit of time with manual.

I've increased the saturation on my roll axis so that it is linear but only needs around half the throw to reach full saturation. This makes the viper feel much more how I expect, tiny flick to roll. I haven't done this with pitch but I don't use a curve either.

Hmm. I have dampened crosswinds and I'm sure it didn't work for me.

Isn't there a DCS disable hotplug option? Also similar to above, I would disable all USB power saving settings. Think this could be done in the bios, but certainly in windows power settings.

It was. I can't google apparently. Lol

Thanks, yeah I had changed the cyclic to central mode, but just wasn't trimming to where I expected. I'll try instant next time I fly, along with manual microswitch.

Phantom first flight 27th May 1960, Phantom F4E first flight 3rd June 1969. Just saying...

That's my experience. In straight flight I press left pedal to initiate a turn left, yaw AP indicator goes all the way to the right and turning is slow and hard work. That with slow progressive pedal input, indicator slowly progressive moves in the opposite direction. I think manual will be what I am after but not keen on holding down a button while I am always manoeuvring. Maybe it won't be that bad. (dampened xwinds, no spring) I also use central trim mode on cyclic (sprung joystick) and although I am a fan of this in the apache, but it just doesn't seem to work the same. It seems to be working like instant trim except not really trimming to where I expect. I always end up using the hat to correct it. Sometimes by a lot. I will try instant trim again and see. probably something I've missed.

You'll get it eventually. But fly manually for a while first.

I just had a flight with my dampened xwinds, no spring, no pedal trim and microswitched enabled/disabled by movement. I could see the yaw channel fighting me, I swear it wasn't disengaging. I still prefer to switch the yaw channel off and on. I think I will probably like the manual microswitch control, next thing to try. Guess I gotta bind that to the stick though.

Interesting podcast, half of it relates to the question. https://omegataupodcast.net/333-flying-and-simulating-the-f-14-tomcat/