Phantom711

@oz555 I‘m eyeballing the BSB2 as well, but one thing that scares me off is the lighthouse tracking, since up to now I have only used inside-out tracking headsets (G2 and QuestPro mainly with an excursion to the Pimax Crystal). I‘m really worried about how to set up those lighthouses and not lose tracking when looking to my 6 o‘clock during BFM etc… Note that I have a gaming chair with a high back. How does that work out for you? How is your setup in that regard?

@GumidekCZ Not at my PC right now, but does the „Open DTC“ button not appear when you start one of these missions? You can load a DTC file with the respective CMDS settings you like there and then activate it in the MUMI page as advertised. The whole process of loading a custom DTC is not very intuitive though. You need to press on „File“ which totally doesn‘t look like a button at all. And after you pressed „Load“ there is also zero feedback. Guess it‘s not an Apple product… I works though… EDIT: The described process assumes you had created and saved a custom DTC file before.

Use one or the other. Not both. It doesn‘t break anything, I guess, but it might add up onto one another which might not be the desired effect.

I used OBS to record as well and then did the cuts with DaVinci Resolve and recompiled it. I‘m not sure, but I think youtube has a framerate limit or something. You must make your file match the YT requirements. DaVinci Resolve has presets for that. A guy from our squadron did the upload to YT though. This was my video by the way:

Well apparently these options are relevant in that case. Pick a DCS resolution, that you want to record in or higher. I would argue, that 1080 usually provides a good quality already. Remember that recording degrades performance (in terms of FPS) as well. You might want to consider not recording while flying VR but record the replay track instead. That comes with it‘s own caveats but also some advantages…

DCS system resolution: shows the VR image on your monitor in the resolution that you have selected in the DCS settings. Crop to rectangle: the VR image would normally show on the screen witz some corners cut off. With that option selected, it will be….well, as it says…cropped to a rectangle. I think none of that is of any relevance, unless you want to stream or record while flying in VR

It´s just that sometimes people tend to think, that the military gets everything they want/need at a heartbeat, whereas in reality they just go by commercially available products. If you have the insights, that those maps can easily be custom made, I won´t argue with you about it.

Well, that‘s just how it is on an aeronautical chart. Assuming you are talking about CTRs, Restricted Areas and such. I think it‘s still realistic, that these charts would be used. If you happen to be at war with that particular country, then you simply ignore their „Restricted Areas“ of course. Drawings from the DTC would still have a different appeal, so it‘s unlikely to get mixed up. Where are these maps located in the file structure actually?

As far as I know, the poor readability is actually „correct as is“….but I still agree, that the maps should be more available to all theaters and at least some reasonable zoom levels. as for „custom maps“: I agree, that this would be nice as well, but really it would still be a workaround. What we really need in that regard is the ability to make drawings from the ME visible in the HSI/SA page.

@_Hoss Thanks, I think you pretty much answered my question. I will check out the WW manual again but I couldn‘t find the answer there in the first place. That‘s why my post here….

Hi I just ordered myself the Monstertech mount for the Super Taurus. I would like to attach the PTO2 to the vertical part of the mount which essentially seems to be a 4080 aluminum profile. Does anyone know, what kind of screws fit through the PTO parts? Is it M5 or M6? Or something completely different? I want to know because I want to order the nuts that go into the rail online somewhere.

@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?