Nedum

Do I understand that correctly? The FCR will never display anything other than a neutral target in terms of color? For my own understanding: The HSD shows me a target (hostile (red) or friendly (green)) with the help of the AWACS. But the FCR will only ever show me a neutral target, regardless of this and also completely independently of two-factor authentication (IFF+AWACS)? Can someone explain to me logically why the FCR has been given a color mode at all if it is completely useless for identifying targets?

Yes, it is, that's for sure. Feel pleased to hear my truths. Oh, so no one is of this opinion? What about the following quote (see below)? Guessing should in theory more precise than knowing? In what Universe? DLSS subtracts pixels from an image to reduce its size. Image information is lost in the process. This information then has to be guessed when restoring the original resolution, and this has to be done every time the image is resized. The faster the image shifts its content (pixels), the more complicated the guessing process becomes, even more with overlapping fast moving content. Pixel errors and ghosting are the ugly "children" of this "marriage", and they will always be there, not always so ugly, but they are the product of omitting important "genetic material". And as long as we can't look into the future to know what tomorrow will have been, nothing will change. This is physics, not make a wish.

Da das Problem sowohl in DCS als auch in MSFS auftritt, sollte das Problem unabhängig von den Spielen sein. Alle automatischen Knopf-Zuweisungen für den Stick herausnehmen. Nur die Achsen dürfen belegt sein und noch einmal testen. Oft treten solche Probleme auf, wenn mehrere Achsen sich eine Schnittstelle teilen. Versuche alle Eingabegeräte so weit wie möglich vom PC zu entfernen, und teste den Stick solo. Sollte er funktionieren, dann die anderen Geräte nach und nach wieder ankoppeln und immer wieder testen. Nutze keine Verlängerungen oder USB Hubs. Wenn der Stick nicht defekt ist, dann muss er funktionieren, egal was MS da für Standardtreiber installiert. Habe an einem anderen PC den identischen Stick in Benutzung und der funktioniert so wie er soll.

Quote myself, because there is still no solution for the displayed issue. Is there a solution and if, what solution is it, I can't see in the "solution" thread? I can't figure it out, if in this solution-thread is a solution for this special >TGP< issue. Would be nice if one could point me to it.

Thank you for your response. That are my VR Settings and the Visibility Range is set to Extreme. And I think in the past the Forrest Visibility Slider was the one for the LOD distance for the trees alone. Now the Visibility Range alone dictates how far we can see the trees if we set the Tree Visibility to max. And as you can see the trees become invisible very soon. I can't really see a LOD-System working. But please let us not derail this Thread and pm me, if you have another idea.

@Barthek Thank you for your work. I see the screenshots and have to ask: how do you get all the trees in the far distance? I have maxed out all of my sliders inside DCS and my trees are going away at nearly 5 miles. Furthermore, I did many slow repairs and rebuild all the shaders several times, after that I thought it is like it is. Now I see your screenshots and DCS looks so much better in the far distance (more detailed). What's your trick?

Hi, what version of DCS you are using? Steam or Standalone? How do you start DCS? What tools you are using? Did you read this Thread? In most cases (if you don't use Steam-DCS and the Standalone version activates Steam VR) SteamVR was activated as the main OpenXR runtime environment. I don't know for sure, but if you have ever activated SteamVR as an active OpenXR runtime environment, and you deinstall Steam after that without undoing the change, the "trigger" will stay. I hope this will give you a hint.

Thank you for your rude explanation. Sir, yes Sir.

Hello, my question is: How do I measure the right height, if I am flying the preset flight plan? What system/display should I use? I am using the HUD Symbologies to fly the flight route. But If I do so (overlapping the Diamond in the HUD (STP), the Horizon Line and the Flight Path Marker), all displays (HUD (Baro) and DED) showing a different elevation height. But If I do so, I should fly at the right height and the right flight direction, right? The issue is, the HUD display shows a different Baro-Height in comparison with the DED height for my flight plan. We are talking about 1000+ feet of a difference. The pictures blow are from the Instant Action Mission "Cold and Dark". You can see the Baro Data is aligned. DED show a planned elevation of 8000 feet. All HUD Nav Symbols are overlapping for the right direction and the right height, but I am 1,250 feet too low. The higher I have to fly, the bigger the difference will become. Is that a bug, or is there a way to do it the "right way" to negate such a big divergence?

Hi, afaik the F16 can carry 4 HARMs but can only fire the ones of the inner stations. But I can be wrong. ;)

The Pimax Crystal already has a good mic. For a normal Gamer, there is no need to take an extra mic. I would suggest testing the Pimax Crystal mic at first.

Can one explain how the marked solution is a solution for this issue? In the marked solution, we are talking about CZ without a TGP. How can that fix this issue with the TGP?

Mal unter uns Gebetsschwestern, wie kommt man auf den Trichter, dass, wenn man nur eine Aussage tätigt, ohne eine Frage zu stellen, man eine hilfreiche Antwort bekommt? Die gemachten Angaben sind in etwa so hilfreich wie die Aussage: "Ich habe gestern getankt, nun springt der Wagen nicht mehr an.". Gut, nun wissen wir 2 Dinge: 1. es wurde getankt 2. der Wagen springt nicht mehr an Man kann sich jetzt denken, anhand von Wahrscheinlichkeiten, dass 2. ein Problem sein muss. Was man aber weiterhin nicht weiß, aufgrund von einem massiven Mangeln an Informationen, weshalb das so ist. Ist es wirklich so schwer vernünftige Fragen zu stellen und vor allen Dingen ein Minimum an Informationen mitzuliefern, anhand denen man eine Analyse des Problems starten kann? Das Grafikartenupdate war ein BIOS Update, oder war es nur ein Update des Grafikkartentreibers? Aber lassen wir das, hat eh keinen Zweck so weiterzumachen. Also muss die Antwort 42 sein.

Did I miss something? You are talking about the Valve Index, right? The Valve Index has a 1440 × 1600 Pixel resolution per eye. The Valve Index is light years back right now, looking at the resolution and the lenses. The glare is the worst I've ever seen. The sweet spot is tiny, compared with any "new" VR-HS. How can one tell that old stuff could in any way compare with any new VR-headset? If one is not an absolute FOV nerd (and even then there a much better VR-HS out there, and cheaper), there is absolutely no reason to go for an Index these days anymore. But I may misunderstand you. My Pimax Crystal never heats up my face. It's cooler than my Quest 3. But congrats to your Varjo X4.

Deshalb auch die fast überschwängliche Benutzung des Konjunktivs meinerseits. In seinem Fall lohnt es sich fast gar nicht innerhalb der Generation aufzurüsten. Danke, für die Erläuterung dazu. Wir beide sehen das ja sehr ähnlich.

Innerhalb einer Serie zu upgraden, bringt dir kaum Vorteile und so gut wie keine FPS Gewinne. Die IPC-Leistung (IPC = Instructions per Cycle) ist entscheidend bei einer Aufrüstung, diese muss erhöht werden, um wirklich Leistungsgewinne und damit mehr FPS erzielen zu können. So gesehen, sind die GHz-Zahlen nebensächlich, solange die IPC ordentlich Zuwachs haben. Eine moderne CPU mit weniger GHz kann deutlich schneller sein als die alte CPU mit viel mehr Takt. Wenn pro Takt mehr IPC erfolgen können, ist man eben schneller. IPC > Takt. Wie einigen schon schrieben oder angedeutet haben, damit bei dir mehr Leistung von der GPU auf den Monitor kommt, brauchst du eher mehr Kerne als mehr GHz oder besser ein komplettes Upgrade des Unterbaus (modernere CPU, MB, RAM). Dann explodieren aber die Kosten. Wenn man aufrüsten möchte und ein komplett neues System haben will und nur spielen möchte, würde ich derzeit als Unterbau AMD mit einem 7800X3D empfehlen. In Spielen ist der 7800X3D im Mittel besser als ein 14900 von Intel und dabei um fast 2/3 sparsamer, und damit auch deutlich kühler und viel günstiger in der Anschaffung.

Dear ED-Team, I am shocked, we still do not have any button to recenter the Cross/Mouse Pointer if we are in VR. This should be a Step 1 for ED to please the VR-People. I can not understand what kind of issue can hinder you to make this dream come true? !!!!Every!!!!! VR-Gamer would pay for such a Button. You (ED) said, you are proud of us, please show it with enabling a Button we can press to recenter the Mouse Pointer/Cross in the center of our view. Show us how proud you are with doing such an easy task in the near time (please no 2 weeks ;)). Thank you

Hi, my personal experience: I had to set down the resolution of my Pimax Crystal. With the standard setting, I've got the message "the current setting of the resolution is too high" (don't know the exact words anymore ;)). After lowering the resolution in the OpenXR Toolkit, the message was gone. Only with DLSS enabled, I could see a difference at near distance. Without DLSS, it was no big difference noticeable. And 10 Meters in the distance, I couldn't see any difference anymore, even DLSS was enabled. I had to low down the resolution a lot to notice a big difference. For low resolution HS like the Quest 2/3 and others, and with DLSS enabled, it can make a big difference, but for high resolution VR-HS, there is nearly no difference to see. The biggest issue for me, the tool does not work with DFR enabled. Big cost of FPS, and the shimmer was back. In my opinion, it's a nice tool for low-end VR, and it's nothing for any game you look far away (more than 33 feet). Nothing beats DFR and high resolution VR.

Hey Lads and Gents, can you please stop this Off-talking? You are not funny and you derail this thread. Thank you all

Hi, we need much more information about your system (CPU, GPU, max RAM) and your personal DCS system settings. You are using V-Sync, which, If it can't hit the target FPS (60 FPS in your case) will add stutter. But without knowing your system (CPU, GPU, RAM) and DCS system settings, it's hard to give some hints. My first hint would be: disable V-Sync and look if and how that will affect your issue. 8 GB VRAM is on the low end for DCS (depends on your DCS settings). I would try to set all the in game settings to low and, if that helps to rise the settings step by step, to find the troublemaker.

It has nothing to do with the System. The technic dictates what we all will get and can see! But who I am to forbid one to believe in their "DLSS-God"? If one "can't" see the obvious, I am the last person who wants to fight with a believer. I know it better, for sure, and that's enough for me. If one wants to learn more about DLSS and DLAA, please ask, but I will never tell one what one want to hear, I will tell one the truth, nothing more and nothing less. The truth is: DLSS is nothing for fast path games and DLSS will !!never!! reach the image quality of the original image. That's a rule of the used technic behind DLSS. That's the truth. And as I said before, that has nothing to do with the system one is using.

Hi, If I understand you right, you still use Open Composite. Can you explain why? Open Composite isn't necessary anymore since DCS uses OpenXR by default.

Hi, I don't need any AA with my Crystal to get a 4K Monitor like picture. I have to use Eye Tracking for this. You can use DLSS or only DLAA if a little shimmer at the edge of your vision is bad for you. With DLSS you will get much more blur as with DLAA only, but you will get with both ghosting at !!every!! fast moving object. You don't have to add any kind of supersampling with one of those VR-HS, and the picture will look a way better as with a quest pro.

It has !!nothing to do with "the setup". If one thinks DLSS adds no blur, the person has bad eyes. DLSS will !!always!! add blur. That's how DLSS works to gain more FPS. I bet $1.000 I can show every guy who tries to tell there is no difference, that there is a huge difference in the image quality and that there will be always blur. It has nothing to do with VR, 2D, the setup or the used hardware. The technic behind DLSS can never be as good as the original. That DLSS could be as good as the original DLSS would have to be a time machine so DLSS knows !!before!! the image would be rendered what will happen in the future and that, for sure, will never ever happen. If one tells us there is no noticeable difference between DLSS and the original picture, there could be two reasons for: 1. the person can't see it, because he needs glasses or new ones, 2. the person do not want to see it. DLSS will always add blur to the image. Now and in the future.

The BSB is very small, and it feels like you are not even wearing any VR headset, that's the big plus. The Pimax Crystal is a very heavy VR-HS, but I myself had never any problem with that. You feel the weight with rapid head movements, It's not an issue for me in DCS. The BSB has the better colors and a better black, but the Pimax is close, very close. The Pimax has the better lenses, far better. The Pimax is brighter and a big plus is Eye Tracking, which the BSB doesn't have. The BSB has no battery, in my eyes a big plus. I can play 6+ hours with the Pimax, with the BSB as long as I want. The Pimax Crystal would be the best SIM VR-HS without the wireless module. As a pure PC VR-HS, I guess it would be $300 cheaper and not so heavy. Pimax will sell the wide FoV lenses in a few days/weeks, which will give you 10° more horizontal FoV. I would never buy any new VR-HS for Sim-Gaming without Eye-Tracking anymore. That's a game changer for me. No need of AA anymore. The Picture is so clear and sharp and on top you will get more FPS. The edge to edge clarity is mind-blowing. If you wear glasses, you should buy the 15 mm foam face cover for the Pimax. My personal experience with the Quest 3: The Quest 3 is !!not!! an upgrade if one is coming from the G2 and wants a sharper picture. The advantage of the edge to edge "clarity" which the Quest 3 has, can't hide the back step of sharpness if you are coming from a G2. If one tells you the Quest 3 is as sharp as the G2, don't believe it. The Quest 3 is a good VR-HS, and it's excellent for what it was build for (wireless gaming) but it was not built for PC-SIM-Gaming. Can you play DCS with a Quest 3, and can you have fun? By 100%! Has the Quest 3 a better edge to edge clarity as the G2? Yes! Has the Quest 3 the same sharpness as the G2? No, the Quest 3 is not as sharp as the G2 (sweet spot). If one want to upgrade from a G2, and want a better image quality (sharper, clearer, more details), the Quest 3 is NOT the way to go. For a real upgrade (coming from the G2) there are VARIO, BSB and PIMAX the way to go.