Phantom711

@stalkereye Hier auch nochmal was zum Thema Microstutters. Je nachdem, wie gut Du des Englisch mächtig bist....

When you create a track, simply put the RDR to silent (SIL), that should proove the point unambiguously.

@DCSFonzie @BIGNEWY I need to recheck, but I think I noticed this problem as well on a mission last week or so. But I think what the OP and I observed, was that Link (Offboard) tracks were not shown on the AZ/EL page. As far as I can tell, your picture shows an Onboard track though. EDIT: The offboard tracks showed on the SA page and RDR page as far as I recall.

@stalkereye Sorry, manche Optimierungen hab ich schon fast vergessen, obwohl ich sie selbst anwende. Das mit dem deaktivierten Kern hatte ich auch eine Weile genutzt, aber ich dachte, das wäre eher ein intel Phänomen. Ich mache das auch inzwischen nicht mehr, aber ich habe mir das "High Performance"-Energieprofil in Windows so abgeändert, dass es immer auf allen Kernen läuft und die Kerne NIE in Ruhezustand gehen. Ich glaub, dazu brauchte man noch irgendwelche Zeilen, die man ins Command Prompt eingibt, damit die entsprechenden Optionen überhaupt auftauchen.

Ich hab jetzt erst Dein Video angeschaut, das hatte ich vorher nicht so wahrgenommen. Jedenfalls sieht mir das nach „Microstutters“ aus. Ein bekanntes Problem bei DCS. Hast Du das OpenXR Toolkit? Das wird zwar eigentlich nicht mehr unterstützt, funktioniert aber meist trotzdem noch. In diesem Toolkit kannst Du den sogenannten „Turbo Mode“ anschalten. Das könnte helfen. Ansonsten googel einfach mal „DCS VR microstutters“ und schau, was Du da noch so findest.

@EX_AI What you could try, is to set your FPS limit higher…or to the maximum actually. I just read in another thread, that FPS limits interfere with the turbo mode of QVFR.

Ok, that´s probably also a way of looking at it. What triggers me about it, is the fact, that the switch is OFF-ON-BYPASS instead of BYPASS-OFF-ON. See what I mean...? Anyways, it´s not a big deal...

There are 2 things that I find kind of implausible with regards to the behaviour of systems in the Hornet, here is the first one. The Dispensor switch has 3 positions: OFF-ON-BYPASS What I find not very plausible is, that when I turn it ON, let it do all its self-tests and then turn it to BYPASS, because....well I come to that later.... But let´s say, I turn it back to ON subsequently, it goes through its selftest again and then remains in STBY mode. Now why do I find that unplausible?: The bYPASS position is a position beyond the ON position, so I would consider it a submode of it being ON. Apparrently you can release Chaff/Flare, so it must be on somehow. Why do I find it annoying?: Let´s think about what the usecase of the BYPASS position might be... There are 2 that come to my mind. The first one is an "items check" during the Fence-in in order to check if C/F dispense correctly. It is kinda´hideous that after that you have to go through all the button presses on the EW page in order to set your desired progarm...let aloe the waiting time for the self-tests. The other use case would probably be training sorties, where you don´t want to dispense that many C/F on every press, but chust want to do it for the purpose of training, but therefor rather more often per sortie. Do I have proof, that my claim is correct, and switching fom BYPASS to ON should not trigger the self-test and simply return to it´s last state? No. I simply think it would make more sense. CMDS Logic.trk

Yes, but you also reported poor image quality, hence my suggestion to try with DLSS off or at least set to Quality. In order to rule out DLSS as the cause of your perceived loss in image quality. What headset are you using actually? You also alluded to the fact that you are using VD? Right now I don‘t have a solution to your problem. QVFR works fine to me with a QuestPro. I don‘t fly helicopters though…

As far as I know QV can have a negative impact in scenarios that are more CPU intense. other than that, I would suggest not to use DLSS or at least not at the „performance“ setting since it will have a negative impact on image quality.

Definitely a nice addition for those who seek more realism and immersion. Your A/G ROE with regards to attack headings is very specific. You could generalize it a bit more, like „Every attempt should be made IOT avoid or minimize collateral damage, to include appropriate selection of employed ordnance, fuze settings and attack direction.“

Die Pixel Density in DCS unter den VR Optionen. Das ist letztlich auch supersampling. Am besten man belässt es dort erstmal auf 1.0, damit man nicht durcheinander kommt. Nee, dreh das mal weiter hoch. Nur mal so zum Vergleich, wie läuft es denn in 2D? Nur um mal abzugrenzen, ob es an CPU oder GPU liegt. Und wenn Du „in der Brille“ den Link startest, dann startest Du auch definitiv den „Cabled Link“ und nicht „Airlink“, ja?

Optisch am Besten sieht für mich DLAA ohne DLSS aus. Nur mal so nebenbei. vllt fangen wir erst nochmal von vorn an mit Meta Link mit Kabel. Welchen Auflösungsfaktor nutzt Du? Hast Du ihn vllt an mehreren Stellen eingestellt, so dass Du versehentlich crazy hoch supersamplest? Also zum Beispiel in DCS den PD noch über 1.0 eingestellt? Oh…und wenn Du auch VD genutzt hast, hast Du danach die MetaLink App auf dem PC wieder als OpenXR runtime zugewiesen?

Also wie jetzt genau? Hast Du den ganz normalen MetaLink über Kabel schon probiert oder nutzt Du das Kabel nur zur Stromversorgung? Ist es ein Meta Originalkabel? Hast Du das Kabel in der App getestet? Wenn Du VD nutzt, ist das dann ein Dedicated WLAN router, den Du dafür nutzt? Es hängt natürlich alles vom Szenario ab, aber ich würde mal behaupten, dass Du mit Deinem Setup kein ständiges Ruckeln beim Rollen(?) haben solltest?

Sure…I was just confused… I don‘t think they will restock that adapter ever again though. They are established on the market now. It was probably a consideration back then, to make their bases more appealing to people who already had a Warthog stick and just wanted a base.

@MAXsenna Yes…that‘s why I specifically said „if the OP ever considers a new base as well“. Also that said adapter has not been available for quite some time.

I‘ve had both sticks and I must say, the Hornet grip felt lower quality with regards to the buttons/switches compared to the Viper/Warthog grip. My Weapon Select always got slightly stuck in the forward position. Not a big deal, but worth noting. I also got my hands on a Winwing Hornet Stick which feels much better. If you ever also want to get a new base you can consider Winwing as well.

Hey @markturner1960 Can you describe what is working or what isn‘t? Is the QuadViews boxed not there at all or is it just not moving with your eye-tracking in game?

The way that skywalker described it, is exactly how it felt to me as well. If you use the Quest handtracking, looking at your hands you can see every single finger move exactly like you move them. There is just no reliable reaction on the game side. He also didn‘t claim to know how to fix the problem on the game‘s side. So maybe try it for yourself before accusing others of „confirmation bias“…!

I know that this is not the answer to your question, but you might want to reconsider your approach here: Either use 72Hz mode or use 120Hz and lock to half framerate (without smartsmoothing). I would think that both options offer you a better experience than what you are doing currently. But thats up to you. As for the Super: I guess you won‘t be able to make use of the full resolution of the Super, but yes, DFR will help.

@Qcumber Hey, I got a very good deal on a used Crystal (OG) last week which I could not let pass. I haven‘t used it extensively, so can only give you a first impression comparison. The additional clarity is very noticeable on the MFDs/DDIs in the cockpit and also noticeable on objects in the distance. Downsides compared to the QP are the weight and formfactor. But the one thing that makes the biggest difference are the lenses. The pancake lenses of the QP with the edge to edge clarity are a class of their own. Even though the „sweet spot“ in the Crystal is huge compared to a G2, I still noticed the blurriness when dogfighting, where the opponent might very well be at the outer edge of your FOV… What I missed as well first, was that gap at the bottom, but I flipped up those nose-flaps and I can now take a peek through there a little. I could probably modify (cut) the foam as well in order to increase the gap. I didn‘t do any scientific or systematic tests by any means with regards to performance, but it‘s my impression that I can run the same DCS settings with the mentioned added clarity at 72Hz just like the QP. Mind you, that I have the Crystal OG so I still benefit from QVFR. And on a 4090 that is… my verdict so far: To be honest, I‘m still not completely sold on the Crystal. I will keep it for now though and try it for a few MP flights in my virtual squadron. From my point of view, I would never want to opt for the CL and lose DFR.

Warthog Throttle doesn‘t have a toggle to dial the RDR scan up or zoom the TGP in/out respectively. Don‘t know if the F-15EX has something for it…but probably it has.

Depends on what part you are referring to exactly. The Orion 2 Throttle base is plastic for the most part, but the throttle grips themselves are made of metal. The Hornet stick is metal as well. (And I would guess, the Viper stick is as well).

@Cupra benenne doch Deine Wunschseiten einfach mit 00 am Anfang, dann sollte sie eigtl immer ganz vorn sein.

Just to be clear: Even though the HOTAS MAX has a vibration module, this is not to be considered FFB (Force Feddback) really. The stick will not get easier or harder to move…it just vibrates a little. (No personal experience with it though) Yes. On the top right of the website you can chose to order from the “EU store“. It seems to be really just a contractor with a warehouse. So don‘t expect to get anyone on the phone there. But it‘s way cheaper that way.