Phantom711

@Tensorial_Architect I do speak „sarcasm“ but it‘s hard to tell from a comment from a guy on a forum that I don‘t know. But I gave you the benefit of doubt…

@Tensorial_Architect You got a pretty beefy system yourself…including that latest 5090. making assumptions on someone else‘s financial background based on the VR headset he chose/chooses, is pretty silly in my opinion. Fair enough, it was probably meant in good fun. Even with (just) a QuestPro and a 4090 it‘s easy to run into ASW occasionally. The 20-30% performance increase of a 5090 might eliminate that. High res VR headsets would benefit even more so. Having a 4090 already, I will skip the 5090, but @EvilBert VR has a valid point there, that the 5090 is still a great upgrade for people with weaker 40-series cards or below.

QVFR definitely works with VD, and has been doing so for a while now. You have to enable eyetracking in VD as well and if you have a custom QVFR settings file, make a setting for [VirtualDesktopXR].

Hi... I usually keep track of such things quite well, but this whole matter is a bit confusing. There are just so many variables... Do we not have to rename some files anymore for this to work? That´s how it was previously, but nobody seems to mention it now anymore? Does that DLSSswapper do it for me? How would he know how the file needs to be named for DCS? Also, there seems to be a new DLSS tweaker to set the desired Preset? So why are people now using NVidia inspector? Do I need both?

Ich würde mal sagen, es ist einfach nur anders. Zum Beispiel braucht man in der Hornet wiederum kein "CZ-Cursor Zero"...

„Target Designate“ und „Undesignate“ sind keine einzelnen Buttons in der F/A-18. Wie Du in Ansätzen schon richtig erkannt hast, kannst Du ein Ziel im Radar mit TDC depress designieren oder dem SCS nach Rechts direkt in Single Target Track gehen. die Buttons haben eben oft verschiedene Funktionen, je nachdem in welchem Mode sich bestimmte Systeme gerade befinden. In der Luft brauchst Du ja kein Nosewheel steering…daher ist das dann auch der „Undesignate“ button. Das ist jetzt aber alles recht oberflächlich erklärt, da das Radar ja mehrere Modes hat. Jein. Du kannst in TWS mit dem „Undesignate“ button durch die Ziele die das Radar sieht durchschalten. Dispense switch: Ja, dieser Switch löst Chaff/Flare aus. Welche und wieviele hängt von Deinem gewählten Programm ab. Ich will nicht unhöflich klingen, aber mir scheint, dass Du vllt von den Flaming Cliffs Modulen kommst und etwas „Arcade“-artige Vorstellungen von bestimmten Funktionen hast. Schau Dir vielleicht mal „Chucks Guide“ für die Hornet an, dann erklären sich manche Sachen vielleicht besser. (Manches in Chucks Guide ist auch schon nicht mehr ganz aktuell).

Did. The. Cable. Test. Ok. In. The. Meta. App. On. Your. PC?

@SnowTiger Are you using the official Meta Cable or at least a quality substitute? Has it tested ok in the Meta App on your PC?

@DCS.Fighter.Masi Probier doch DLAA.

Thanks everyone for sharing their experiences with DLSS4. I have personally not updated yet. I would ask you guys to be a bit more precise in your statements though. So when you report ghosting/smearing, is that with the actual DLSS or also with just DLAA?

Well...even real pilots share that feeling when they fly their million $ military simulators. So one could even argue, that they are at a disadvantage there, because they usually have the actual feel which they then lack when flying the simulator. A contrast, that most DCS players won´t have to cope with. Point is, we (in DCS) simply have to be a bit more disciplined in flying the numbers properly. As I had already pointed out here, I fly in a virtual F/A-18 squadron and broken landing gears really are not an issue. Check your landing weight. Fly "on speed". Fly the ball (IFLOLS). Be wings level on touch down. Following that, it s near impossible to break the landing gear.

@mongo52 Had to read that a couple of times to follow along but I got it now. Thanks for sharing such insights and also by doing so confirming my assumption, that hard landings are recorded by the system.

@Mootmoot I´m german, so living in the metric system as well in everyday life. Simply consider aviation like a closed system with it´s own units of measure. Reeally, there is usually no need to convert from imperial to metric. Here are some conversions within that eco-system, that are usefull: 1 minute on a meridian is 1 NM 1 NM =~6000ft 1NM / h = 1 knot Mach number x10 is equals NM / min -> 0.8M = 8NM / min (without wind of course) There´s probably more, but this is what comes to my mind now.

Ja, gibt es. Wenn Du es realistisch magst, die US Navy nutzt nur den ATFLIR an der Station 4 (also rechts seitlich am Rumpf). Den LITENING benutzen das USMC und die meisten fremden Nutzer. Der LITENING kann auch unter dem Rumpf mittig (Station 5) genutzt werden. Dort ist weniger vom eigenen Flugzeug im Weg, was die Sicht stören würde.

Deutsch - ED Forums Komm erstmal ins Deutsche Subforum und frag da einfach nochmal, hier ist der englischsprachige Teil.

Ok…why and when would you ever need to convert those numbers in DCS? Just set DCS to the imperial system all together and you are good to go to just live in a world of NM, knots and feet. This is the standard for the most part in the western aviation world. Yes…even in France.

And? How would you handle the whole matter in a sim then? I‘ve probably slammed it down with 1000FPM and it was still intact. So there is definitely some tolerance included already. Of course in real life a damaged landing gear might not look as crooked and funny as in DCS, but this is simply to portray that fact to the player. The point is, that, by the numbers, you have overstressed it. I don‘t know, but something like a hard landing might even automatically be recorded by the system.

Dank Dir für den Hinweis. Ist zwar vom CVW-17, aber natürlich falsche Ära und genau genommen falsches Flugzeug. Und ich vermute mal, keiner von uns will so tun, als ob er PAIL wäre… Oder meinst Du einfach nur wegen des CVW-17 Insignia auf dem Helm? Sieht schon gut aus der Helm…

@EightyDuce Ok. Wasn‘t aware of that. I was just mentioning it because people explicitly mentioning the 512GB here when it has absolutely no meaning/benefit for DCS.

On the VR options page in DCS. Make sure you have a tickmark set at VR Mirror - Use DCS System Resolution. Also check „Crop to rectangle“ if you don‘t want to see the black HMD mask on the monitor.

Again, you guys don‘t need the 512GB version unless you also plan on playing several stand-alone games. Unless I‘m missing something here, it‘s called „Quad Views Foveated Rendering“ aka QVFR. Just sayin‘ because the OP might want to find these programs. Here‘s the link: https://github.com/mbucchia/Quad-Views-Foveated/wiki What it does in a nutshell: It increases performance at the cost of visual clarity at the outer edges of the VR image. Trust me, witH DCS in VR, the Quest3 will absolutely bring your 4090 to it‘s knees at times. It‘s wishful thinking you could just casually run one of these very high resolution headsets. I‘m not saying it won‘t work at all, it‘s just not as easy as you are portraying it.

@Boelcke Einrichten/Kalibrieren reicht. Es sei denn, Du möchtest die Beleuchtung der Throttlebase mit der Cockpitbeleuchtung in DCS synchron halten.

@CybrSlydr If you want better graphics quality, try DLAA without DLSS. But of course DLSS might be a good compromise with regards to performance.

@CybrSlydr From the timestamps on your posts…even if you live right next to that BestBuy and you didn‘t do anything else after buying the Q3…at best, you fiddled around with it for 7 hours. And then you returned it without even considering to ask people in this forum? Does BestBuy have an 8 hour maximum return policy? Do you really think that hundreds or even thousands of DCS VR players simply enjoy blurry cockpit instruments/displays with their Q3? I really don‘t want to sound mean… I‘d say it‘s definitely possible to get a nice and crisp image with a Q3. It‘s very likely that you missed some important setting.

Es geht ja um den Performance-Gewinn…und nicht darum, dass Eyetracking für sich selbst genommen ein irgendwie tolles Feature wäre. Ansonsten könntest Du ja auch sagen, warum ne Pimax…hattest ja mit der G2 auch keine so hohe Auflösung.