VR Flight Guy in PJ Pants

Sorry, stand corrected.

Sorry I meant smoke from chimneys, ships, etc.

No smoke either...

Thank you for your reply. Oh, it would be Quest Pro. Due to the testing methodology, eyes were fixed to the front, if it was what you were asking. Also, forgot to mention, I used QVF 1.10 and the setting used: # Common settings for all headsets (unless overriden below). smoothen_focus_view_edges=0.2 sharpen_focus_view=0.7 turbo_mode=1 # Fixed Foveated rendering settings for fallback when eye tracker is not available. horizontal_fixed_section=0.5 vertical_fixed_section=0.45 [Oculus] peripheral_multiplier=0.3 focus_multiplier=1.1 horizontal_focus_section=0.3 vertical_focus_section=0.3

About performance gain, I don't think I have made any benchmark comparison yet, so here are a few charts for your reference:

Let's assume that ED only publishes only monthly (ref. Normandy 2, Sinai, F-15E), even if there is something in the pipeline, say F-4U, F-4E, Kola, CH-47, etc (Disclaimer: I have no insider information whatsoever, but I just pick what I thought would be available "soon", and the list here is very likely to be wrong) So, there ain't much time slot to post new product in the remainder of year 2023. Of course, once again, I can be very wrong. Just for your thoughts.

Waiting for the screen shot of the radar screen.

Not only in terms of fps, frame rate has also improved too.

Watch this and makes me worried regarding ECM Sorry if it was the wrong thread regarding this.

Dunno why this happens as I experience this with MiG-29 and F-14. It also happen quite consistently when I check six.

Suggestion: would the update log in the web front page be the link to the corresponding asset page? Appreciation: keep up the great work!

I am not sure but LAW now can be set to another value rather than on or off. I need to verify though...

Dunno, LAW warning still on for both F/A-18C and F-14A and B. Absolutely zero idea.

I did run a A-A test earlier, still not accurate. I read it is still a WIP so I am not pushing.

I see,I guess it was just my system. Actually when actual playing, I did not set any target frame rate. I am not using OpenXR toolkit altogether cause I am using the Foveated Rendering via Quad Views.

Quickie: how does OpenXR Turbo Mode perform? It is great!

For this time, wait for Q3 pun intended.

I think I am skipping the latest hotfix.

Compare the baseline against "Force 45fps; ASW enabled" Please kindly comment.

Saved game, your DCS folder and then Tracks. For my setup, it would be E:\Saved Games\DCS.openbeta\Tracks As usual, your insights and comments are welcome. I am always looking for ways to make it better.

After some playing around and tests, I have established a baseline so that it can be used for comparisons in the future. The benchmark baseline is not used to tune settings. That the baseline serves as the basis when there is one thing changed, let's say, the next OB version, I can check how the performance differs, if any, when everything else remains the same. This is a somewhat not-so-scientific A/B test. Because there are a number of factors that are beyond control: Windows changes, NVIDIA drivers changes, VR drivers changes, and equipment getting old, etc. The scenario or the track file is designed so that there are reasonable amount of actions happening around at the same time, because this is DCS World, not MSFS, not just simply flying. The jet plane used because it is faster and is more demanding in terms of frame rate and frame time (which measures the smoothness) than helicopter. And the graphics settings in DCS attempt to push it towards the limit. At the end of the day, I am sick and tired of people using one single screenshot and claims, without any setup details and context, that certain thing(s) give great performance, and if yours does not work like that, the fault is yours.Turns out, performance is something a very dynamic and complicated thing and it is not what some people think. Hope this clarifies a few things. And the details of the benchmark are in the video. Mission and track files are enclosed. Benchmark - FA-18C - Flyover Beirut 1.7.miz benchmark - fa18c - flyover beruit 1.7.trk

Echoing above, this is mine. Make a "baseline" for comparison. I make a track, run it through. For testing, change one setting/version at a time, run like an A/B test. Example:

Didn’t find MiG-23MLD had damage model issue… Load time is much better now. Running benchmark

Why is everything seem retracted? Was I playing Twilight Struggle?

Shame there is no reproduction to turn on to.