Hippo

Thanks for responding so quickly. Windows desktop resolution = 3840 x2160 Oculus App VR rendering resolution = 5408 x 2736 (1.3x) @ 72 Hz Resolution in DCS config screen = 3440 x 1440 (this might seem strange, but I recently upgraded my monitor and didn't bother to change this - my old monitor res). I've just tried again, after a black screen with the Oculus hourglass for a long time it did get to the main interface and was working correctly, so maybe I just needed to be more patient. I don't think so though. Normally it loads up pretty quickly and I don't get this (or similar) issues. Here's the log for this time. dcs.log

I've been seeing this for around four months or so. When I start DCS, sometimes the system will become almost completely unresponsive. There are variations on exactly what happens: sometimes I'll see the interface screen, sometimes a black screen, but I always see the Oculus hourglass spinning continuously. It looks as if the sim is running at less than 1 fps. I am eventually able to get the keyboard or oculus controller to respond and kill the task, and try to run it again until it works correctly. I would say I see this around 25% of the times I start DCS. I have attached a log file, as this has just happened. Spec in sig. dcs.log

Yes, I get it on Quest Pro. It's been a thing since release. IIRC the dev has said it's something that can only be corrected by ED making changes in DCS. Perhaps @mbucchia can confirm? Since DLAA has made a significant difference with reducing shimmering, it really would be nice to get this working perfectly. Is it worth requesting changes from ED, and how to request? What would they have to do? Personally it doesn't bother me that much as it's rarely very distracting. Much more noticeable in the F-18 than the AH-64 where I can't see it at all.

Thanks. I didn't go out of my way to check moving aircraft. Sad if so as it was all looking so promising. EDIT: Have now checked and indeed am seeing artificating / ghosting. But imho nothing so bad as to not be worth using DLAA + FSR (so far).

I have seen the recommendation to change the following settings in ODT from their defaults of zero, but for the life of me I can't see any difference when I do. Can someone tell me what improvements I should be seeing in DCS when I do this? (endode resolution width, and encode bitrate) I am using Quest Pro over a link cable. Thanks.

Agreed. After further testing, I feel this is truly a game changer. By setting the focus region at 0.25 I am getting AA at a quality very similar to MSAAx4 for free. Yet it is almost impossible for me to tell that DFR is doing its thing (I can see the "square" if I look for it and depending on what I'm looking at, but it's something I can easily live with). I'm possibly seeing some texture DLAA shimmering in the focus region that wasn't there with MSAA (further testing required to confirm). but again, minor enough that I can easily live with it. P.S. Night vision goggles now work properly, and it is possible to see the cockpit "outside" of them. Xmas has come early. Thanks to all concerned.

I've had no issues like that. But then I'm running a Quest Pro, the stanalone version of DCS (i.e. not Steam), and am using a link cable with the Oculus software (i.e. not VD).

DLAA + DFR (i.e. mbucchia quad views foveated) is working wonders for me on Quest Pro. DLAA appears to completely elimate shimmering in the peripheral area meaning the focus region can be substantially reduced for huge performance improvements and a much better overall experience. This is DFR working as I always imagined. For me TAA offers the best visual quality. Especially when looking at taxi way lines and the like. Whilst TAA greatly reduces shimmering, I find it just makes everything blurry, and can produce dreadful ghosting (e.g. in F-18 try quickly looking left and right past canopy frame). DLAA much better but much greater perf hit, same as MSAAx4. But see above if you're using DFR. Having said that, I am running a pretty high-end system. For something more mid-range TAA could be a godsend, it greatly improves the terrain by eliminating shimmering at almost no perf cost, and I think that the terrain blurring looks ok. However, I don't like blurring of the cockpit. Swings and roundabouts.

Sorry, after further testing I was mistaken, and afaict there is no difference. However, I'd swear that since I first tried this when mbucchia released for Quest Pro, either my tolerance or something else has changed. I am able to set a 0.25 focus region (for a massive performance improvement) and whilst I am aware of shimmers in the periphery I can happily live with them - there is no way I felt this was the case when I first tried this out on release. As to 2.9 DLSS, DLAA, TLA, I'm afraid it's all very much 'meh' for me, with any perfomance improvements simply not worth the visual artifacting/ degradation. As always, there's no such thing as a free lunch (though quad views foveated is getting very close). EDIT: Arrrrgh. Someone help pls. I think I'm going nuts. I'm seeing different results between restarting sessions. I think a restart might be necessary between changing MSAA x 4 -> DLAA. I'm not even sure if DLAA is the cause, but I have definitely had sessions where I can detect no shimmering in the periphery, and sessions where I can. DFR is definitely working as it is very perceptible in the menus and I am aware of the "square". If the effect is real, this is a very big deal. To check: in the F-18 engine gauge shimmers are very noticeable when the engine gauge is in the periphery, but I have had sessions where it doesn't shimmer at all. EDIT Again: Almost certainly down to DLAA. Shimmers in the periphery eliminated vs MSAAx4. Needs a mission restart (at least), i.e. changing the setting in-mission doesn't appear to do it. In normal usage (i.e. not using DFR) I can discern no difference in quality or performance between MSAAx4 and DLAA.

My very quick first impression with 2.9 is that DLAA (TAA too, but at the cost of too much blurring) noticeably reduces shimmering (I usually use MSAA x4 as I can't bear jaggies and shimmers), and that it seems to make any DFR peripheral area shimmering much less noticeable than before. Placebo or does anyone else feel the same? Might it be feasible to decrease the size of the focus area further? I will test when I have more time, but wondering if anyone else has already played around with this?

IDK what that is, is it 2880 x 2880 per eye?

What render resolution are you running?

I, like you, have a Quest Pro and am very happy. I haven't tried the Crystal but would be very wary of changing at this time. Main reason: this guy puts it very well. Just do the math and be very sceptical of YTs reporting butter smooth frame rates. Second reason, in spite of multiple YT videos singing its praises, is that Pimax QC and customer service are very suspect. I find this guy tells it like it is although I suspect his particular experience in this case might have been sub-optimal.

Quest 2 with elite strap, vr cover facial interface and link (or 3rd party) cable. 2nd hand (ebay).

Grrrr. Only bought mine recently at £999. Still within the 30 day return period. Would it be very naughty to return it and then buy it again at the lower price?

After multiple reattempts (around eight) I have not been able to reproduce the issue, and the wingman has always behaved correctly, whether I was connected or not. I was actually running two "mods" (sorry for getting this wrong before) when I experienced the issue and which I removed for testing, so, unlikely as it may seem it could possibly be due to them. They are https://github.com/mbucchia/Meta-Foveated @mbucchia https://www.digitalcombatsimulator.com/en/files/3321955/

Thanks again. I tried the mission again earlier and, wouldn't you know it, the issue didn't happen. This time I was taking fuel when the wingman disconnected, and now strongly suspect that it might only happen when I'm not connected; still, I don't see why 1. he banks right and doesn't just fall back, and 2. he flies into me. The next time it happens I will post a track in ED's bugs forum. Personally, I rather enjoy AAR, and like seeing it in (some) missions.

Will do. The only thing I'm currently running that is non-standard is mbucchia's dynamic foveated rendering extension for Quest Pro. Next time I try it, I'll make sure I'm un-modded. For a workaround I can just wait for the wingman to finish and then refuel on the port boom. I should add that I was having some difficulty staying on the starboard boom, so it's possible that the wingman flew into me as I was attempting a reconnect - not sure if that might affect things. Thanks.

Second attempt at this mission. First refueler (Texaco). When wingman finishes fuelling he banks right and crashes into me whilst I'm still taking fuel. Any ideas? Great campaign BTW. I've come from SH2, and this is even better than that. Thanks. EDIT: just searched this forum properly and it seems others have seen this issue, which is likely a bug. I will get around it somehow. No need to reply unless there is anything new to add to this, or unless you think it shouldn't be happening.

Same here. Also happening with Quest Pro.

So with my settings (horizontally) 0.4 - (0.4 * 0.4) = 0.24, and so only the central 24% of my fov is at full resolution? I am somewhat concerned / embarrassed to admit that I can't actually tell.* Should I be worried about my eyesight? Is the drop in resolution in the transition band linear? Is there any advantage to having peripheral_multiplier=0.5, i.e. exactly half? * I can notice shimmering quite clearly if I'm in a screen with lots of text, but not in the cockpit. In the F-18 I only really notice shimmering in the IFEI.

I decided to give this another go, and am currently happy with the following settings which give me a good perf (20-25% reduction in cpu util) : visuals. peripheral_multiplier=0.5 focus_multiplier=1.0 horizontal_focus_section=0.4 vertical_focus_section=0.3 vertical_focus_bias=0.28 turbo_mode=0 smoothen_focus_view_edges=0.4 sharpen_focus_view=0.0 On a previous attempt with... peripheral_multiplier=0.4 focus_multiplier=1.0 horizontal_focus_section=0.5 vertical_focus_section=0.5 vertical_focus_bias=0.25 turbo_mode=0 smoothen_focus_view_edges=0.2 sharpen_focus_view=0.0 ... I found that the performance improvement was much less and the peripheral area was too distracting, Which I find odd, since the peripheral area was smaller. Could it be down to peripheral_multiplier and smoothen_focus_view_edges? Or is it some placebo / me having a bad day / dodgy eyesight? I'm just wondering what works for other people, and which settings they find most critical. Could someone please expand on the definition of smoothen_focus_view_edges? What is the value multiplied against? Is the transition band split equally between the focus and peripheral areas, or is containted within just one of them? EDIT: My comparison isn't really valid, as I had also changed my settings 2xMSAA -> 4xMSAA. Also tested with a different mission. Both of these changes considerably affected the relative changes in performance and my visual perception of shimmering. Overall, I am very impressed with the results I get with the second set of settings: when I'm absorbed in a mission and not consciously looking for the DFR I'm almost never aware of it.

Nope.

I don't know, but if you look at where the dip happens, you'll see the GPU util suddenly spike. It's at this point that ASW kicks in and drops to 36 fps. At least that's what I think is happening. I would've thought either CPU or GPU can cause ASW to kick in. In the mission the GPU is already running at 80%. I could take some of the load off (-> MSAA 2x or OFF) for a bit more headroom and see if the same sort of thing still happens. EDIT: Retried with 2xMSAA and did not get that dip, and DID pick the 1st* F-16 this time. Still seeing the odd spike in frame time, but in the sim I just see a constant 72 fps. *I was mistaken yesterday when I said I picked the first F-16 in the list, I somehow missed the two at the top of the list and had picked the first in the group of four. The drop in fps at the end is after I switched back to the desktop in Dash. The DCS frame rate counter does say CPU bound, but I don't know how reliable that is. ab2023_07_02_08_26_58_837.hml

Well, yes, I'm using ASW. If the GPU tops out, it's immediately down to 36 fps. This does happen sometimes. I would have to try to fly this mission over a longer time to get a better feel for overall performance. With the missions I fly I can (mostly) stay at 72 fps whilst having a bit of overhead. But there will always be times where it gets too much. In this case it could've been caused by me looking around causing loading from memory / disk? I don't know. The mission I linked to earlier (flying low over Dubai), I could hold 72fps throughout before I went 2 -> 4xMSAA, and now the GPU can't cope and I have to settle for 36 fps. Turning ASW off and having fps fluctuate continually does not agree with me.