Eugel

Same here. Works fine (with an AMD X570 board - after praying to the machine god to bless one of my USB ports) But one question: How do you switch on the G2 ? I find it quite annoying that WMR always automatically starts with WIndows as long as the headset is plugged in. So far, I haven´t found any solution other than to plug/unplug the USB cable every time.

Oh ok, I thought that maybe earlier batches of the G2 had different connectors (as it seemed to me from your picture) that caused a problem and was changed since then.

@Sr. Oh my god, that cable looks terrifying. Was that originally so ? Or did HP change it ? Mine is attached like this:

I recently popped a tire at about 140 knots on takeoff (didn´t check the exact speed, but it was definitely below 160)

For me, 100% of both A-10C II and Huey replays derail after about 10 minutes (since 2.7 - before that it only happened occasionally). To be honest, I hadn´t found out how to fast forward in replays, so that´s not causing it for me. Maybe it´s worse in VR because of all the head movement ...

How can it be perfect if it can´t track the controllers behind your back and won´t work if the room is too dark ? Don´t get me wrong, I was disappointed by the Vive Pro and won´t buy the Pro 2, but light station tracking from the Vive (even first generation) is simply on another level compared to inside-out tracking.

Hm, I´d disagree. The basestations are somewhat unpractical, yes. But the tracking, even from the first generation Vive, is way better than for example a Reverb G2.

Yeah, I posted about it a while back: It got way worse for me with 2.7. Since 2.7 I haven´t had a single replay that wasn´t totally derailed from what actually happened during the mission after 10 minutes. And yes, I also wondered why after every encountered bug they ask for a track file. It´s quite annoying for me. As I play in VR, I like to re-watch my missions with higher graphics settings to take screenshots and also would like to use it for learning purposes (check my landing approach, bomb release, what shot me down ? etc.)

I just repeated my A-10C II target practice mission. No scripts involved, only one unit in the air (me) and mostly static ground targets. The mission duration was 47 minutes. When I watched the replay, the startup was fine, and the first two bombing runs with mk82´s were correct. After that in the actual mission, I made an attack run where I fired 4 Mavericks then turned to the next waypoint and landed safely. In the replay however, I fired only one Maverick, flew over the enemy base and rammed my A-10 into the ground. It´s not just position desync and the replay isn´t resimulating my inputs. My inputs fired 4 Mavericks. It is really like the first 10 minutes are fine and after that it looks like the pilot just died.

As in the left picture the headset is in stand-by mode, your computer will only render the lower resolution desktop mirror image. If you alt-tab out of the game while still wearing your headset, the window will be out of focus, but there will be no performance change.

Die checkt die Position der Knöpfe und Achsen am HOTAS und überträgt sie bei Missionsstart ans Cockpit. Wenn also z.B. der Throttle am Warthog auf MAX steht, gibst Du bei Missionsstart direkt Vollgas. Ich würde da aber trotzdem mal die Belegungen checken. Mit der Synchronisation an würde der eigentlich checken "Aha, keiner der Knöpfe an den Cougars ist gedrückt" und sollte daher an der Stelle eigentlich gar nichts machen.

There is actually a setting in the windows mixed reality options to run the headset at lower resolution (though it doesn´t say 1/2). Check this video (he´s talking about it at around the 5 minute mark): I haven´t tried it and, as was already said, DCS requires you to run Steam VR, and I´m not sure if that setting has any effect there or is overwritten by the resolution settings from Steam VR. And generally, it´s not a good idea to run anything below native resolution. You will most likely take a hit in picture quality.

Bist Du denn sicher dass es an den Cougars liegt ? Ich habe die gleiche Kombo (Warthog Stick/Throttle + Cougar MFDs) und habe sowas bisher noch nicht beobachtet. Ich wüsste jetzt auch nicht wie die Cougars so einen Effekt auslösen könnten, höchstens wenn einer der Knöpfe in der "gedrückt" Stellung festklemmt, aber selbst dann sollte das Flugzeug nicht Gas geben und nach links ziehen. Das klingt ja wirklich nach irgendwelchen Achsen die Input liefern wenn sie es nicht sollen. Hast Du mal im Thrustmaster Control Panel gecheckt ob einer der Knöpfe aufleuchtet ohne dass Du drückst ? Hast Du mal probiert die Cougars einzeln dazu zu schalten um zu sehen ob vielleicht nur einer der beiden falsche Signale schickt ?

Bei mir ist es aus nostalgischen Gründen auch der Apache - Habe meine schönsten Flightsim-Erinnerungen an Janes Longbow 2. Aber ich bin da noch etwas skeptisch, zum Einen weil ich nicht sicher bin ob der sich alleine - ohne menschlichen Co-Piloten, vernünftig fliegen lässt. Und zum Anderen weiß ich nicht ob der sich mit meinem Setup (TM Warthog) gut fliegen lässt da ich nur in VR fliege und auf Belegung der Tastatur verzichten muss. Der Apache Stick ist ja doch etwas komplexer... Aber ich kann mich zum Glück beim "Jagen und Sammeln" ganz gut zurückhalten. Mit A-10 und Huey gibt´s für mich wahrscheinlich für den Rest des Jahres noch genug zu lernen.

Well I still consider this a bug when the replay function does not "re-play" what actually happened during the mission. And for me it got worse with 2.7 I´m not talking about long or heavy missions, even with just a single aircraft, all replays longer than ~10 minutes are pointless.

Define "Full resolution"... Do you mean 50% in Steam resolution settings ? The 50% setting is still above the G2´s native resolution (50% = 2232x2188). To me it looks perfectly fine. Everything above native resolution will improve the picture quality. The higher, the better. The slider goes to 500%, which is 7068x6920 per eye. But as long as you don´t reduce the render resolution below the native resolution, it will be fine. The G2 at 50% looks way better than my former Vive Pro at 100%.

It seems to me that the G2 simply does not like USB 3.1 3.2 ports and the X570 boards only have 3.1 3.2 ports at the back (or at least mine does). My case has a front plate with two USB 3.0 ports and both work fine with the G2. I had the same on my old Intel board, the G2 would not work with the 3.1 3.2 ports. Concerning the performance... you have to consider that the default 100% render resolution in Steam VR for the G2 is set to 19.5 million pixels, or close to a 10K resolution. So it´s not that by some "voodoo" the G2 needs more power than other headsets, if you set other headsets to such resolutions, it will be the same. Edit: meant to say 3.2 instead of 3.1

Die Dinger sind nicht toll, aber auch nicht sooo schlecht. Was bei den TFRP wichtig ist, pack da eine gewisse Totzone und eine Kurve rein. Sonst zucken die schon nach links oder rechts wenn man nur die Füße drauf ablegt.

Pretty much that for me as well. Seeing passengers actually getting on board and sitting in the back would be amazing. With the release of the Hind this year, I think it would also be a good time to implement this. Would be interesting to see how they fit 14 guys in the back... Then some overhauled cockpit textures and maybe some newer navigation instruments (I hate ADF navigation) I´d gladly pay a few additional bucks for that.

Hm, maybe I was unlucky with my Vive Pro then. Or my expectations were too high. The headset rattled and squeaked quite a bit, the audio was bad, the IPD knob sometimes didn´t react at all, sometimes the IPD would change by itself when I put the headset on and the foam started to disintegrate. On top of that, the stepup in resolution from the original Vive was nice, but apart from that, there were no improvements. The screendoor effect was as bad and the light rays I felt were even worse than in the old Vive. And motion smoothing caused so much distortion that it was simply unusable for me.

Thank you very much. Removing the "CAS" action did the trick.

The mission editor is driving me crazy a bit and it looks like I need some help. So, the mission setup is this: Friendly infantry is trapped in the town and has to be extracted by helicopters. To spice things up a bit, I placed a group of BTRs in town and a flight of two A-10 that should attack these with their guns. I really don´t see what I did wrong here. I set their ROE to "designate only" at WP 0, but even if I remove this, it doesn´t change anything. At WP 1, they get advanced waypoint action "attack group" GTR Group. But for some reason, this is what happens: The A-10s spawn after their trigger, then the flight lead ignores his waypoint and target completey and goes for the enemy group in the upper right. The second A-10 at least flies to waypoint one, but then goes up to about 6000 feet without attacking anything. They do have full ammunition. The first A-10 does his attack runs on the enemies in the upper right. I´m sure there is something pretty basic I´m missing here, but I don´t see it

I am generally happy to see VR being further developed. But after the terrible Vive Pro I´m not sure if I´ll ever buy a Vive again.

You know, there is a special subforum if you want to further discuss the technology: https://forums.eagle.ru/forum/63-military-and-aviation/ You might not get as many negative answers there.

Du hast Dich zwar schon entschieden, aber hier noch meine 2 Cent dazu: Ich hatte vorher die (damals noch) Saitek Pedale und bin zu den TM TFRP Pedalen gewechselt. Ich kann mich der Einschätzung "Beide Mist" tatsächlich anschließen. Die Saitek/Logitech Pedale sind ziemliche Plastik-Bomber, recht klapprig und laut, und bei meinen sind nach einiger Zeit beide Toe-Brakes gebrochen. Ich habe sie aber noch hier und habe gerade mal den Vergleich gemacht. Ja, man kann den Widerstand mit dem Rad in der Mitte einstellen, aber auf der schwächsten Stufe finde ich den Anfangswiderstand immer noch etwas stärker als bei den TRFP. Sie springen nur etwas präziser wieder in die Anfangsstellung zurück, ein Problem das ich mit den TRFPs habe. Außerdem macht es mich bei denen wahnsinnig wie dicht die Pedale zusammen sind. Wenn es Dir vorrangig um den Anfangswiderstand geht, tun Dir die Saitek/Logitech Pedale keinen Gefallen.