TED

It’s not a big deal but can be slightly distracting if flying in the back seat in mp server for example using George as cpg, when the cautions be seen constantly flashing in the front cockpit. Could it be implemented that he cancels either after a given time or at the same time as the pilot cancels his?

Errr…yes they do. The last 8 different types I have flown in the last 20 years all have had yaw trim. Only a couple of types I’ve been rated in in my career that didn’t have it. Most IFR certified types will have it integrated in the afcs.

I agree. It works very well and is very simple to use. Will be nice however if and when amd have an inbuilt solution that matches or exceeds openfsr and we don’t have to modify game files and folders.

That makes sense. I did a few more tries and could not get it to work. I gave up and went back to using openfsr.

I think people should be a bit reserved in blindly stating "the apache I'd unplayable the vr". It may be for some depending on hardware and settings but for many of us it is perfectly fine. There are so many variables in getting everything to run smoothly, from Windows, wmr, svr, other apps and background processes running. I'd always start with some good pc hygiene and check the system thoroughly outside of dcs. I've been getting excellent performance with g2, 6900xt and 3800xt. Running native resolution in sp and mp. Mp is noticeably lower fps and higher frame times but quite acceptable. Sp is totally smooth even with ihadds, flir, pnvs and anything else running. I even saw improvements in performance with the latest patch.

I don’t know…I’m a bit confused by it. I activated and then lowered steamvr res to 60% and quality looked same as full resolution, so perhaps it is working. I will need to look closer at frame times. I just don’t get any upscale status indication anywhere.

Not actually sure this works with steam vr. I just tested it but didn’t seem to work. I’ll have to look into it more tomorrow. Be great if it does, but I have a feeling steamvr gets in the way. I be very pleased if I’m wrong and someone can get this to work.

I was about to post a similar thread and wondering if it was just me or some placebo induced by my enthusiasm for the new ah64! I was initially quite concerned that the Apache would kill my frames in vr. Imagine my surprise when the complete opposite happened. Not only are my frames better, but I’ve been literally on dcs all day trying to learn the ah64 in various maps with all settings on high, my g2 at 100% resolution and actually pushing 120 in per app. Msaa x2 af x16, mv and motion smooth enabled. I did not experience even one stutter today in several hours of testing. im using a 6900xt, 3800x cpu,. I dont know what ED has done in the engine but it’s working for me. Everything is just going from strength to strength.

Solved. Somehow the audio inputs and outputs had changed in the audio settings menu. This actually happened a few weeks back too and all sound disappeared so something is causing it to change. At least I know now where it is and it’s easy to fix. my suspicion is that I have a usb device somewhere that’s confusing it and causing it to register as an audio output.

Thanks. I tried all these and all other sounds are normal. Only radios. I think it may have to be the painful process of reinstall

I'm pretty sure this is something I've screwed up but hoping someone can help. Suddenly the other week the radio comms stopped working. It's on all modules and all maps. The comms menu works, and the calls are being made as I can see it goes onto the appropriate next menu. However there is no voice ai audio at all. I've gone through all the obvious things. Easy comms on and off. Checked frequencies are all correct. Ptt buttons assigned. It happens both on ground and in air, no difference. Anyone have any other clues about where to look? It basically seems like all the audio scripts are gone.

Ahhh my bad. I assumed as you were posting on this thread you had a 6900. 2 totally different animals. Tuning the nvidia and amd require quite different approaches. I still have both with the 3080 still in my study. With either there is definitely some merit in maxing the resolution then there is very little requirement for msaa. I’m playing with that at the moment and feel it gives a better result. No fsr. No msaa. No af but max resolution. Unfortunately everything you add on top softens the image, especially msaa. For me right now on the g2 with resolution at 100/125 the shimmering is minimal and actually no worse than 90% with msaa. So several different routes to the results depending on what your priorities are. I am extremely happy with it all right now and dcs just looks goddam awesome in the g2 now I u derstand all the tweaking a bit better. This is the best I’ve seen it. I suspect the latest OB patch has improved some things too and the drivers keep adding small improvements so everything is going in a very positive direction. The last month all of my performance and image quality has improved significantly.

Have u updated to latest amd driver yet? In my case I noticed quite a bit of real gains. Make sure u clear out your fxo and metashaders in between adjustments btw too. I am just testing now with no fsr at 100/125/1.0. Surprisingly good results and at that resolution don’t need msaa at all.

Thanks. I just tried some of that too but for now I’m done with openFSR as it just deteriorates the image too much for me. 85% svr res without fsr is considerably better than running 120% svr with 0.77 fsr imo. I was testing a bit with no fsr and 85% svr res, msaa and SSAA on. Generally a more agreeable performance and image for my flying around generally in a10 at 3-400’ caucus, Syria and Nevada. Interestingly I’m able to add mv and motion smoothing if needed with a slight softening of the image but I don’t get any artifacts now. what on earth are you doing at angels 10 in an a10c? . it’s all very personal I guess. My preference is for smooth performance at low level with the best image possible. Basically no shimmers and no stutters and for that I’m prepared to sacrifice a little sharpness and detail.

@nikoelcan u just quickly confirm - u r running 100/130/1.0 for svr res, per app and pd. Then no msaa or af. And you find the image quality OK in terms of sharpness and detail?

Should just add that all these settings are a bit map and aircraft dependent too and may need a bit of time tuning. My approach for now is msaa x2, SSAA x1.5, most dcs settings high or maxed except detail on medium. Mv and motion smooth off. from there I only adjust the resolution depending on the map. Last one I did in caucuses and a10c I was getting up to 80 fps at times. More usually 60-70 so I bumped msaa to x4. Looked fantastic. This was with svr res at 85%. basically any tuning is small adjustments of these. A heavy mission with lots of ai will probably need to drop to msaa x2. I agree on shadows. Although I like to have the cockpit lighting effects and shadows in the cockpit. Terrain shadows - meh. Flat is fine.

I had a bit of time on my hands this week and decided to try some blue sky thinking and a few different approaches to the whole tuning. There has been som excellent contributions to this thread and I cant thank everyone enough for all the participation and great inputs. Following a very interesting post by @winghunter about combinations of MSAA and SSAA, I thought that this sounded like it made sense so gave it a go. I agree also with @Al-Azraq on the subject of openFSR. I have used openFSR for a while and indeed it does seem to give some performance gains in FPS, the image for me just is not that great and its an extra layer of processing. I find also the image is better at 80% resolution without it than 100% with FSR, so i removed it. The great posts by @nikoelhas also had me thinking. Ive been slavishly using MV and motion smoothing and whenever i turned them off I found it unacceptable jerky, but could not quite understand why others were getting good results and I was not. So today I threw out a bit of my previous routine and started over. I started by removing OpenFSR. Clearing out all the shaders, fxo and metashaders. I dropped SVR res to 70%, MV and Motion Smoothing off, DX11 force off. MSAA x4 and SSAA x1.5, AF off. I downloaded and installed the latest AMD driver and software update. I set up a mission from Batumi in the A10C. To my utter astonishment it was vastly better than I had been experiencing before. I was already very pleased with the performance, but like all of us enjoy trying to squeeze out more and tinkering. The first and most noticeable effect was that with the combination of MSAA and SSAA the antialiasing is much better and the straight edges of wires, posts and buildings as well as any terrain outlines were much much smoother. Big plus. My biggest surprise was that having now removed all motion smoothing I was expecting it to be very stuttery. I taxied out and took off with a solid 60fps and almost no stuttering at all. I flew a few profiles through the mountains to the east, along the valleys, over trees, over the mountains and over the city. Low level at around 300 ft for most of it. Even looking out the side was smooth. It was actually as smooth as it had been with motion vector and smoothing on, except the fps was higher, usually between 50 and 60. Not quite believing my results I closed and restarted DCS a couple of times with the exact same results. And now of course absolutely no artifacts from the MV. To be honest I dont really know exactly why this is working so much better than I expected and I had tried most of these things at some point in the past but in isolation. It could be that the latest patch in DCS has improved some of the shaders and engine, as well as the latest AMD driver improving things. Most likely its a combination of several factors. After a few runs I could see that there was easily enough headroom to increase the SVR resolution to 80%, which gave an even better visual image with a bit of an FPS cost at around 5 fps giving be a steady around 45 to 55 at all times, of course a good bit higher when at altitude. It never dropped below 45.

Yep. Lots. I still have it actually but its packed away and will sell it when I get time. The 6900 was just way more stable. Some pros and cons and 3080 is a great card too. Bit less tuning required. But when 6900 is tuned on balance for me it's just more powerful and more reliable. Especially when it gets crowded on the server.

Just to confirm, no I don’t use “chill” to lock fps. I wouldn’t recommend it for most cases in dcs. Never tried it actually. But I attempted to lock it with the adrenaline setting that attempts to target and caps fps. I’m not entirely sure it works to be honest but has no negative affects. I use motion vector and force dx11 and suffer very few if any artifacts. Certainly nothing that I notice. I’ve upped the power on the gpu though and min freq as well as overclock To 2650. I got rid of fpsvr as I actually found this to be inducing judder . Im getting i g good smooth performance even looking out the side in a harrier at low level. On some mp servers I do need to drop the resolution a bit in svr below 100%, but others it manages just fine. I’ve found in general it’s better to leave most of the adrenaline settings alone except overclock, power and maybe fan timings.

Out of curiosity last night I downloaded xplane again, having not used it for quite some time. In that time xplane has implemented Vulkan API and multicore. I have to say I was really impressed at the performance using my reverb g2. I was able to run all settings on max, and all at full native resolution in the g2. It actually all looked really very good. This makes me rather optimistic for the improvements we are likely to see in dcs when it rolls out. I understand the cautious approach and I expect there are other complexities in dcs that do not exist in xplane, however I feel this might be one of the most significant improvements to dcs we will have seen for a very long time. I’m already getting pretty good performance in dcs but would definitely love to squeeze out more. Additionally this will undoubtedly unleash other development possibilities for the general architecture of the whole system. Exciting times indeed for dcs and I’m very much looking forward to this.

Indeed certainly one can gain a lot from running at 60hz. I also tried this and for sure it ran very smoothly, however I was very aware of the slight flicker which I find very distracting. It’s very possible this is also somewhat system dependent as it doesn’t seem to bother everyone. If I could live with that flicker or remove it I would certainly run at 60.

I’ve been trying various settings and also replicated exactly @nikoelsettings. I suspect every system is different but for me without the motion vector and motion smoothing there is just too much micro stutter. It may even be a bit module dependent but I need to force dx11 and have mv and smoothing on, then everything is really smooth, even in a gazelle at 50ft through valleys and trees or over cities. Most of the rest of the settings however are the same or very similar to Nikoel. Svr 100%, per app 120%. I’m using fsr with upscale of 0,9, radius 0.8 and sharpness 0.85. msaa x2 works fine without any real hit in single player but it’s not really necessary with the resolution dialed up. I think a lot of this is a bit subjective but I just hate even tiny stutters and without the smoothing it’s still noticeable for me.

I wonder if there is some issue between oculus and amd? I am using reverb, wmr and have no problems at all using motion vector and motion smoothing with my amd card. These claims that motion vector is broken for amd are simply untrue. My only other thought is somehow u need to force dx11. In wmr this can be done pretty easily but not sure about oculus. You can check your default dx and or reinstall it from the bin folder in dcs. Check out thuds guide on doing this. Make sure for dcs you are bit allowing dx12 to creep in. This makes a big difference.

Make sure you have deleted absolutely all nvidia software and drivers. Use ddu or something similar.

So I tried your approach to this with mv and motion smoothing off and force dx11 off. For me it's just doesn't work for some reason. Too many small stutters. The force dx11 in wmr seems critical. I've no idea why. With it checked off the image is better but more stuttering. So I've had to tune for that too. Motion vector and smoothing is just too beneficial and it doesn't work properly if dx11 isn't forced on. However I bumped svr res to 132% textures high, but msaa off and it's actually an improvement. I needed to drop resolution to 100% or less to use msaa reliably. However msaa softens the image. Without it but at highest resolution it performs better and the image is generally better (subjectively). Lots of good stuff coming out of all these threads. Id love to know what the dx11 effect is though and why it seems to have such a big effect on dcs with amd cards. If I could get mv to work without forcing dx11 it would be perfect. Perhaps someone cleverer than me can speculate.