I can get them to mostly cooperate but it takes a lot of ‘state changes’. And depends on the loadout - to keep them from making suicide strafing attacks you take away their [gun] ammo. Not ideal but seems to work.
Seriously watched the entire video, only to find out it has nothing to do with DLSS/AA or TAA.
Going back to MSAA removes ghosting because it’s not Temporal AA like TAA, DLAA/SS.
The ghosting from what I can see through DLSS Dev Docs from nVidia is due to objects not having motion vectors attached in the GPU Rendering Pipeline,
The issue is, you can’t put MV’s on EVERYTHING,
DLSS Ghosting is well known in every game it uses, for for the DCS Community to beg and beg for DLSS and then complain about the caveats that come with it, is kind of funny.
Clearly trying to get clicks and views without knowing what any of those settings do.
4 Likes
I learned how to shoot pistols with my grandfather’s service 1911s (there was a reason he started carrying two at some point), so I’m still very partial to the type myself- but can recognize the flaws.
Time to see how this is going to run with my old 1070, while I price and source a 3070 or -80 in the near future.
5 Likes
Provided you’re not trying to run VR, the old battle horse is doing fine on 1080p and Medium settings.
A fellow 1070 owner.
2 Likes
Yeah, wasn’t sure how applicable it was. Not an expert on DLxx. DLSS, when it first came out sounded…to me…like it wasn’t ‘all that’. I guess it can help but perhaps it’s more like a band aid, not a cure.
Mission makers need realistic ORBATs. No ground forces are 50% ADA.
They need to be scaled appropriately as well. If a real mission planner would send X planes against Y ground forces, we shouldn’t have a mission that is 10% X against 75% Y or 75% X against 10% Y.
If you are going against a main HQ, or a major strategic target like a bomber airfield or whatever, it should be better protected and need more attacking forces than some random armor staging area with a dozen tanks.
3 Likes
Just did a flight with the Apache in the Marianas map and I’m gleefully happy with the results. I’m still experimenting with settings and trying to find my sweet spot in VR and monitor environments.
I’m not noticing any of the issues many are talking about so I guess I’m either lucky or Mr. Magoo oblivious. 
Once I’m properly dialed in, I’ll post my settings and specs in the event they may help someone. I do suspect others will get there well before me because I get easily distracted.
2 Likes
That would be nice, thanks.
2 Likes
What were you getting on 72Hz? I’m pretty much stuck at 36fps around the supercarrier, down to 28-30 around Marianas trees or on the Channel cities.
2 Likes
Thanks for posting your settings. I used them as a guideline on where to start (2080Ti) and I only had to back off a few of your settings to get a really nice mix of visuals and frame-rate. I’m still testing though…so I’ll post my settings up when I think I’m feeling good about them. But yeah…great help to get me to a good start point…
5 Likes
With the settings I posted and my quest at 72hz I was pegged at 36fps on every map down low and above about 5000ft it switched to 72fps. The exception to this was the marianas map which seems very spiky in frame rate that varies wildly between about 28 and 36 with some stutters, especially when looking towards the heavily forested area. Now I have upped my quest to 90hz and I am getting a stable 45fps again on all map’s except Mariana …
but the strange thing I have noticed is that I am CPU bound for most of the time and not GPU bound which is what I expected especially with my cpu never going above about 50% usage on two cores
3 Likes
Now I know why my framerates have been so high most of the time in VR (pre 2.9 - I’m updating today, so thanks for the settings). I have my stuff set way lower than any of you guys - and I mean waaaay lower!
Really excited for my new kit - and I can’t wait to get some fandabidozi graphics in my pico 
Has Caucasus improved any? It always looks rubbish to me since DCS 2. I took a flight in 1.5.8 t’other day and I actually preferred it, it’s so bad in 2.x - especially the trees.
1 Like
I can’t seem to get my system to stick with CPU-bound or GPU-bound. If I’m out on the carrier in the water or up in the sky I’m GPU-bound, but once I get near cities or the Marianas islands it switches to CPU-bound.
Check out Barthek’s Caucasus redone mod. The buildings still look like crap but everything else looks pretty good.
3 Likes
Mine is mostly CPU bound and that’s good, because that means the CPU is making the thing adhere to a fraction of my VR headsets’ framerate. So at a steady 45 CPU bound means there’s some overhead. Which is good.
2 Likes
I was cpu limited in 2.8. I’ve just updated this morning, so I’ll do some tests with my current rig over the weekend, then next weekend if all goes well, I’ll do the same tests with the new kit and see how much bigger my smile is!
3 Likes
While I’d considered some of the textures mod for that terrain, I finally came to the conclusion that unless it’s a specific campaign I want to fly I am DONE with that theater! It’s been so many years I’d rather spend the next decade on literally any OTHER terrain.
2 Likes
Well 2.9 won’t change your mind - not based on my experience this afternoon.
I decided to do a couple of flights to see. No mods.
Pico4 running SteamVR+OpenXR with Steam SS at 150% (3116x3116).
I used my usual settings for 2.7 and 2.8 that were always very good for my set-up.
Firstly, I had to close the sim via the task manager because it was stuck in the loading cycle, at about 20% average CPU use. This always seems to happen if I start SteamVR before the sim, which I did this time to check my settings.
After forcing it closed I exited SteamVR and restarted DCS and sure enough it went just fine - booting to the hangar screen in about 90 seconds. My CPU load during the sim load was 100%.
This is what fpsVR showed me in the hangar UI:
I chose a mission from Cyprus/Akrotiri and off it went… note the 100% load on core 1
I’ve never seen this before during loading:
but it was an indicator of things to come. Once I got in the cockpit at Akrotiri it was awful. I had reset my refresh rate to 72Hz, having seen a discussion on the ED forum saying it worked much better than using 90Hz (which I normally do) and having 45fps via ASW. The framerate at the base was 36. The cockpit was moving around a bit with my head movement - like it does when your system isn’t quite up to what is being demanded of it.
fpsVR at this point:
I never saw frametimes in the teens since I got the 4080. So this was bad news. The CPU is being worked hard on the 6th core.
I didn’t attempt start-up and returned to the main UI. btw the UI screen was also moving around in the hangar scene with my head movement in VR - but only a little.
I then loaded up the A-10C in a Caucasus mission. It wasn’t quite as bad - there was some minor movement of the cockpit. Framerate was 36fps and again the 6th core was working hard. I took off with a wingman and suddenly things smoothed out quite a bit. Framerates rose to +/-72fps and the framerates sunk to what I normally see - low single digits (not in this screenshot yet).
External view is normally better, but in this instance not quite…
It’s hard to see in this shot - but the HUD was not as clear as it usually is.
plus the Caucasus scenery - vegetation and buildings - was the worst I’ve seen in a long time.
Settings:
I’ll do some playing around with settings etc and see what, if anything, can be done. If it stays like this after my new kit comes, I’ll be going back to stable and waiting for movement on 2.9
edit: as you can see the settings are low (except terrain and textures) which may explain the poor scenery a bit, but I would have expected better performance than 2.8
1 Like
Do you need SteamVR with the oculus quest?
I have an HP Reverb G2 and I simply use Windows Mixed Reality with OpenXR, performs quite a bit better than SteamVR…
3 Likes
As I reported yesterday, 2.9 MT took a dump on me. 2.8 MT was fine. Dug around the ED forums and this post seems to work for most, if not everyone. It has cured my 2.9 MT problems. TLDR: Parked CPU Cores is the culprit.
Download the UnparkCPU app in POST # 3 . Run the app and unpark all cores.
I’ve got the i9 13900KS which has 32 cores. Before I ran the app, 22 cores were parked! Now, all are unparked and DCS under 2.9 MT works flawlessly with DLSS.
HP G2 VR is hitting max fps of 90.
Disclaimer: Your mileage will vary.
My DCS settings for reference. Fps is hitting my max screen refresh (240 fps— Samsung NEO G9 Monitor)
6 Likes