Nedum

I really try hard to understand what ED try to simulate with this ugly behavior (look at the pictures) if you change the view angle and the whole environment gets darker or brighter. Never saw such a behavior in real life. I really tried hard to find something in RL that could fit with the DCS behavior. ED try to simulate something I've never seen before. And guess what, I couldn't find a single RL comparison that would fit, nor do I find any science explanation for that "art" of simulation. In RL, if I move my had a few degrees up and down or Left and right or all together and glance around, all has still the same brightness or darkness as before. Nothing changed a little bit. There is no difference if I do this in my house or in my garden. So what does ED try to simulate with "that"? And please, ED, give us an option-switch to disable this ugly behavior which is simulating nothing you could find in this kind of universe we are living in.

DLSS will (for a very long time) not be an option for people who like a crystal clear picture. If you own the MSFS2020 you can test it by yourself. It's not an option, not a tiny little bit. There is no GPU on the market, which can give you the performance you need to fire up a Pimax Crystal in DCS with the best visuals. You have to tweak it. And you have to look for your personal best visual settings to run DCS smooth. You have to find a way to optimize your settings to stay lower than a 20 ms frame time with motion smoothing or not higher than 10 ms without motion smoothing to get a smooth game experience. Is that your first experience with DCS and VR?

Hm? Should we guess what settings you use (DCS, PimaxXR, OpenXR Toolkit, etc.)? What build of DCS do you use? Open Beta? Did you a slow repair? What OS do you use? What about your DCS system settings? Could it be, and motion blur is enabled? What about your in game Frame Times? By far, not enough information from your side, to lay you a helping hand.

Not enough information. If you want our help, you should show us what VR hardware you are using. How's the VR-setting. What kind of problems shows the issue report you receive? And many more to show us. Should we guess what you did or didn't to help you to fix your issue? Is that your first VR time? What about your DCS app-settings (shortcut: --force_enable_VR)? Do you use them (look underneath) What VR-HS you are using? And many more questions. Without the missing information from your VR-hardware and the settings, you give us a really hard time to help you. null

Did I see the right numbers for the frame times? 30+ ms sometimes? Something seems to be off with your resolution setting. I myself still waiting for my crystal, but I'd read that many guys run with a resolution around 3300 x 3800 (done in the OpenXR Toolkit, set size to 75%(Performance Tab)). You should try that. Isn't DCS, but you get a feeling how to optimize the crystal.

The guys talking about -> flying underneath <- the clouds, and you show up some Pictures from above the clouds? The shadows underneath the clouds are all a way too dark, if you are flying in those shadows. I don't know if you are a RL aviation guy, but hey, did you ever flow underneath a light cloud layer? You will miss some extreme cockpit reflections which would make your eyes hurt, but it's by far not a tiny little bit as dark as it is in DCS. It's still bright, not as bright as without the clouds, but not dark, not a bit. In DCS, it's in most cases 90% too dark. On a light cloudy day, you can't even see any colors anymore if you fly in a cloud shadow cast. How is that possible? But right next to the "Darkness" the Buildings and the Grass shines like a Christmas tree, because there is no Cloud Shadow. That's miles away from the RL. You do not even need to be an Aviation Guy to show up, that the current Shadows in DCS are a way too dark. At a really sunny day, went behind a house with a full shadow cast and look around, and after that don't tell me that the RL Shadows are only a tiny little bit as dark as the DCS ones, so you can't even see any color anymore. And why are all the trees begin to shine if they are in a shadow, If you look from above? If you are at the same height, they start to get "invisible". That will only show up during the twilight. Before and after that, a Forrest is the darkest part of the environment. Not in DCS. DCS is miles away from showing this in a way that is near the RL behavior. I am so happy ED is on it.

It's working fine. No bigger problems. XRNS Beta 5a, DCS (open beta) the newest version. At first, I had some trouble, till I mentioned I have to restart my PC after I set up XRNS for the first time. I've got a twisted view (from the back and upside down). After that, I can change every position without any problem. No BS or other crashes.

You all use OpenXR? Ah, and I forgot to mention, I am using XRNS Beta 5a and playing only the Open Beta of DCS (newest version). Mods: Better Trees (Caucasus, Syria, Marianas) from @Taz and Caucasus Texture pack V2 from @Barthek. Most people with this problem have a problem with the System configuration (OC). It could be a RAM Problem. Set the RAM Setting back to default and test it again. For AMD Ryzen users: if you are using CPU Curve Optimizer, disable it (later try to lower the setting, till the systems runs fine). Try to get the newest stable BIOS for your main board and install it. Reset all settings to default and test it again (I would suggest you should do so even without a BIOS update). Another thing is the page file. Some of you might have set up the page file for your needing (32GB). Undo that and test it, it could help.

The FoV is still the same as a Quest 2 horizontally, vertical it's still as small as the one from the Aero. There is -> no eye-tracking <- If you know how much performance Foveated rendering will give you back, a VR-HMD without it is a huge back step. The Battery lasts 6 - 8 hours with a USB power hub. Where've you get that from, that the Tracking is so bad? I really would like to hear more about it?

Thank you. I will give it a shot.

Keine Ahnung, ob das Thema noch aktuell ist, aber meistens liegt das Problem in den Sound-Systemeinstellungen (Soundmixer) begraben. Teilweise wurden die Treiber nicht oder nicht richtig installiert, sodass das Headset nicht überall einwandfrei erkannt wird. Also als Erstes klären, ob das Headset so im Soundmixer auftaucht und, dass es ggf. für den DCS Voice Chat freigegeben ist (die App sollte dort auftauchen, sobald diese aktiv ist), bzw. nicht deaktiviert wurde (Lautstärkeregel für die App darf nicht auf 0 gestellt sein).

Bei solchen Fragen, wäre es immer besser zu wissen, was denn schon vorhanden ist. Ich habe schon recht sinnbefreite Aufrüstaktionen erlebt, wo bei ->geringeren<- Geldmitteleinsatz mehr als die doppelte Performance herausgesprungen wäre, hätte man andere Komponenten stärker aufgewertet und andere gar nicht geändert. Beispiel: Vorhanden war jeweils ein Ryzen 5900X und eine 3090. Nr. 1 wurde auf einen AMD Ryzen 7590 und eine 4080 aufgerüstet (vorher AMD Ryzen 5900X und nVidia 3090). Performancegewinn: ungefähr 30% FPS in DCS. Kosten = 2.800 €, weil ja alles neu gemacht werden musste (RAM, Bord, CPU, Netzteil = 1500 € + 1300 für die GPU). Nr. 2 Nur die 3090 wurde gegen eine 4090 ausgetauscht: 75 + % FPS in DCS. Kosten = 1800 € (inklusive neuem NT) für die 4090. Deutlich mehr Leistung und 1000 € gespart. Der Besitzer des ersten Systems wollte sofort alles neu haben, weil DCS ja so CPU intensiv ist und mehr Kerne = mehr Leistung sind. Ja und nein. Als DCS noch rein Single Core war, wäre der IPC des einzelnen Kerns der wichtigere Faktor gewesen. Mit MT ist das (fast) obsolet. Es ergibt derzeit keinen Sinn so extrem aufzurüsten, es sei denn, man hat das Geld übrig. Derzeit ist GPU-Power der (fast) einzig wichtig Faktor und, so wird es auch gezeigt, der einzig limitierende Faktor (falls man nicht auf einem alte 4-Kerner rumeiert). Wenn der OP schon ein relativ gutes System besitzt (6- oder 8-Kerner (inklusive SMT oder HT), mit DDR4 RAM und PCIE 3.0), dann wäre es am sinnvollsten nur die GPU zu upgraden und dann gleich auf eine 4080 oder am besten eine 4090. Die verbrauchen dank Undervolting deutlich ->weniger (bei nur maximal 3% Verlust an der Gesamtleistung)<- und bringen am meisten Leistungsplus (je nach alter GPU mindestens 70%). Dann kommen noch DLSS 3.0 und andere wichtige Feature dazu, die die 3090 nicht mehr hat. Eine 3090 hat zwar viel VRAM und ist für VR schon ein guter Boost, aber sie kann bei weitem nicht mit einer 4080 und schon gar nicht mit einer 4090 mithalten. Zumal alle 40XX GPUs deutlich kühler arbeiten als eine 30XX (meine 4090 verbraucht in VR nicht mehr als 280 Watt (undervoltet), meine 3090 hatte immer 380 + Watt gezogen). Also, falls das jemand liest, der auch aufrüsten möchte, bitte immer die Daten eures alten Systems mitliefern. Manchmal geht dann deutlich mehr, mit viel weniger Geldmittel, als man vorher dachte.

Couldn't read more about your VR-Setting as Quest 2 at 72hz 1.2x resolution, so I asked about the other stuff. You are running the Stable or the Open Beta? The reason why I am asking, your system suddenly going from CPU- to GPU-bound and is losing performance, which sounds really strange. It should be the opposite, you should gain performance. That was a problem for some people getting the first DCS-MT build. Some people found out there was an issue with HT (intel)/SMT (AMD). They had to disable it. And for some people it shows up later, after a few updates, even so they were running the DCS-MT build from the start. Perhaps that could be the "problem"?

What about all of your VR settings? Link cable or not? Is ASW active? Do you use tools? If yes, what tools, release version and what settings? Sometimes a tool-setting, never interact with DCS settings before, does suddenly stuff (because now it interacts with DCS) it never did before. And, as always, do you use mods and did you a slow repair?

It looks like, you are CPU bound. I can't see an issue with the VRAM. Did you all the stuff with the slow repair, no mods and so on?

Nope, not at all. I run NS as a normal user. Can play hours with it enabled. I start NS right before I fire up DCS.

Hi, thank you for your work. Where do I have to copy the trk-file to? And where do I start it from?

Sounds for me, you have set the max refresh rate of your Headset (G2) to 60 Hz. That would explain all your issues. Please don't limit the FPS in VR using extra tools, expect OpenXR Toolkit. Set the refresh rate of your HS to 90 Hz, and after that use "MR" from the WMR settings (you can do that using the OpenXR Toolkit).

Thank you for the explanation. I do not have a Pimax Crystal right now, but I am interested in one. That's the reason why I have to ask so many questions. Even with "MR" I have to put down some of the quality settings in DCS with my G2, and it looks like If I would own a Pimax Crystal I would have to put down much more of those settings. So I ask myself: "Is that perhaps a downgrade (Crystal) if I have to play with all the quality settings down to get a smooth experience, without a feature like "MR"?"

What I can tell from many reviews I have readying: Yes it can be an upgrade, but as a G2 user, there are some points that hit me hard: Glare is back, even at bright scenes (Hello? 2023 already! ;)) = - Tiny vertical FoV (90° with a standard IPD of 64 mm) = - The same if not less horizontal FoV as the G2 = o Edge to edge clarity is not as good as the Pico 4 or the Crystal, but better as the G2 = + Uncomfortable if it's warm in the room (vacuum effect) = - No sound = - No tracking and controllers (you have to buy it, if you are not an owner of that HW already) = - - This HS is for you only, no other user is able to use that HS = o Glare is a No-Go for me. A smaller vertical FoV than my G2 is a No-Go for me. If I upgrade from my G2, it has to be more than the form factor, a better Field of View and an OLED panel and for sure, it should never be a step back from my current experience. Smaller FoV and Glare again, really? I would have to spend more than 2200,- € to get that HS working. For that price, there are too many "go-backs" for me. But I am pretty sure some people will get happy with it.

Hello @mbucchia, thank you for your fast response. The Motion-Reprojection of the OpenXR Toolkit depends on WMR? I've to ask, because my G2 is a WMR-HMD and can use the MR feature the OpenXR Toolkit offers out of the box. What about SteamVR "MR". Does it work? The "motion smoothing" Pimax offers seem not to work very well (if at all, as I can read in the reviews).

Try to enable Motion Reprojection (OpenXR Tools). If you can't hold steady 90 FPS, you will get stutter if you look around and especially if you look to the side.

Can the Pimax Crystal use Motion-Reprojection with the OpenXR Toolkit? If not, what do you guys using to get a smooth and stutter free movement, if you move your head?

Inside/outside-Tracking mag keine komplett gleichfarbigen Wände, die kontrastfrei sind. Das, was du beschreibst, scheint sich genau darauf zu beziehen und seitdem du ein Cockpit gebaut hast, ist das Monotone verschwunden. Die Kameras können die Umgebung deutlich besser unterscheiden als vorher die (vermutlich) nur "monoton" einfarbige Tapete. Eventuell ist das ja der Grund, weshalb der "Fehler" jetzt nicht mehr auftritt. Falls auch andere das Problem haben, einfach ein paar Poster an die "kahlen" Wände kleben, das wirkt Wunder.

There are so many things which can hit the DCS performance really hard, so you have to be much more precise what settings you are using. A big part of this story are Shadows. If you use the left shadow setting alone (terrain shadows flat), it will hit a little more as the terrain shadows alone (shadows flat). As soon as you use both together, they will hit the performance really hard. Grass will hit the performance hard too. Water at high is a bigger performance eater as view distance set to ultra. And so on. Long story short: If you want to compare the performance, the settings you mentioned are by far not enough to do so.