Lt_Jaeger

Before I step down this rabbit hole as well, how much gain we are talking here. I'm running a G2 on 3080TI with 5900, tuned with VRperfKit and all that is imaginable. My benchmark is the F-14 cold start in NTTR which lead to a frame time around 17-18ms looking around. I know it is all very dependent on a bunch of things, but can someone provide a rough ballpark number, so I would be able to figure out if it's worth it to start digging into this, please.

PointCtrl simuliert das Mausrad, man muss halt nur 2 Knöpfchen drücken. Als Erstes wird einer der beiden Mausknöpfe gedrückt, um die Rad Drehrichtung festzulegen ( rechts = rückwärts / links = vorwärts), danach der "Mausrad" Knopf und voila, es dreht sich

Nah, AP is currently looked at. The problems are known and should be rectified soon (I hope)

2. You can remove the adapters from the port and got a standard mini(?) USB connector.

That's the way I have set it up: As you can see, it's totally normal for the radios to be greyed out during the Tomcat still dark and cold As soon as power and radios are on, the radios come alive in VAICOM as well You want to make sure you have all the relevant PTTs mapped in VAICOM As soon as everything is mapped you should see the listening resumed listening suss pended lines in VAICOM consistent with your press and release of the relevant PTT For the use of SRS I have also mapped the PTTs in the keybindings Bindings:

Did you set up your PTTs right. If you check in the Vaicom config gui, what does it say which radio you are operating.? Another thing, did it worked before or is it your first try to get it running?

That's right in line how it is supposed to work. As long as the Jet is cold and dark, the Radios are turned off, and you have to use the Intercom to talk to the ground crew. As soon as the Jet comes alive, the other two radios become available, but you have still to use Intercom to talk to the crew. Make sure you assigned the correct PTT buttons (3 needed for the F-14) The menu is also supposed to not pop up. If you still want menus, you have to do the appropriate setting in the VAICOM setup. Other than that, there is the way of the keyword "options" which will open the com menu and you being able to navigate it with "take 1 ... "

Ich glaube ja. War eine Mail die den Eingang bestätigt und darauf hinweist das es dauert.... Meine hing irgendwo im Spam Ordner von gmx

Hört sich doch gut an...also diese Extra-Knöpfe an der Brille kann man frei belegen...ich dachte, die haben die gleiche Funktion, wie die Knöpfe an den Fingern......darum habe ich deren Sinn nicht so ganz verstanden. Ja, die sind zwar "hart verdrahtet", d.h irgend etwas mit STRG + xyz rst oder so, aber die können halt in DCS frei belegt werden. 6 weitere Knöpfe, mit modifier halt mehr. Kann man nie genug von haben.

PointCtrl funktioniert zuverlässig wenn KEINE IR Streustrahlung da ist. Wie TrackIR auch reagiert PointCtrl auf gewisse IR Frequenzen. Wenn man nun direkt vor einem Fenster sitzt, ist es Asche. Ich habe ein Fenster im Rücken und PointCtrl reagiert nur komisch wenn ich mich umdrehe und etwas zu drücken versuche. Das ist eigentlich nur beim scharfmachen des Schleudersitzes in der F-14 der Fall und somit zu vernachlässigen. Die erste Version hatte ein paar Probleme mit der Firmware der Fingerdinger (FCU), aber das ist wohl behoben. Die zusätzlichen Knöpfe.....ich nutze sie z.B. für Salut, die Taschenlampe, active pause, die linke Seite für die Bedienung der NVGs. Muss man sie haben, NEIN, will man sie haben, JA Nett beim de luxe Paket sind auch die magnetischen Ladekabel. Alles schi schi, aber ich finde, es macht das Leben angenehmer. Das haptische Feedback holen sich manche Simmer indem sie eine Sperrholzwand, o.ä. da hinstellen wo das Instrumentenbrett im Jet ist. Ist sicherlich nett, ich brauche es nicht. Wie gesagt, ich bin überzeugt von PointCtrl, allerdings bin ich auch offen für neues. Wenn Leap motion oder die Handschuhe mal vernünftig funktionieren und irgendwo im Bereich des Komplettsets für ca. 250 (inkl Zoll, wenn man Pech hat) liegen, werde ich es mal probieren. Ist halt besser Kram zu haben als zu brauchen

Ich habe das Leap Motion Teil mal probiert und war alles andere als überzeugt, das ist aber schon einige Zeit her und ich denke, es werden seitdem Verbesserungen vorgenommen worden sein. Allerdings benutze ich Point Ctrl und bin sehr zufrieden. Für mich kommt "derzeit" ein fliegen ohne nicht mehr in Frage. Bei kurzen test hops, bei denen ich die FCUs nicht extra anlege, versuche ich trotzdem alles Mögliche im Cockpit zu drücken und wundere mich, warum es nicht geht. Kurz gesagt, der Kram ist sein Geld echt wert und ich hoffe Miles bekommt die Nutzung in MSFS auch hin.

Took a quick look, seems to be very interesting. Will follow for sure

All pretty easy....as soon as you are leveled out, referencing the instruments rather than the HUD, you could use the two knobs HUD Trim and VDI Trim to trim out the respective indications for THAT regime of flight. You will quickly learn not to reference the HUD for indication, but the instruments. As much as I recall it was stated that the HUD itself is not rated for instrument flight, the jet himself is though. That said, VDI is some magnitude more reliable for the indication of the "flight status", so get used to use that thing and disregard the HUD

In the beginning you will grab four the mouse, but that will be gone fast, since PointCTRL is very intuitiv. Now I point at switches even not wearing the FCUs for a quick test hop. But basicly it's like pre flight natural to slip the finger thingys on, as soon as dcs starts. I don't want to be without it any more

I use Num 5 - center view then RCtrl RShift NUM 8-6-2-4 to center the view and RCtrl RSHIFT NUM / and * to move forward or backward. Saving with RCTRL RALT NUM 0

Oops, just read in the discord that you are aware already.

Seems like the Mission 10 is broken. For launching the Alert aircraft and the Ready 5 hooked up, the "Tomcat launch problem" comes into play. No. 1 launches and after that the mission stalls, no. 2 never leaves the deck. I see no possibility to unhook from the cat and "re-taxi" so that no. 2 could launch, so we would sit there in eternity and no 1 is burning all his fuel flying circles around the boat. Maybe you could take a look and just leave alert 5 unhooked in a stop gap measurement? Or is there a different way to launch that no.2 bird?

Had / have the same problem with rotating shafts, especially annoying with my rudder trim hat. Then a lighting struck ... and voilà, no more rotation. For mounting on the shaft (in my panels I had to glue it on top ) it might need some more refinement. Since I have no idea about constructions in Fusion, it doesn't go better as this

Both of these commands work flawlessly for me. Maybe try "scan range two five (2 5)" As for Nellis it beats me. Did you check "import new module" in Vaicom?

For me "tally wildcard" works fine. Due to my old analog brain with very limited memory, I usually add a couple of aliases, as suggested above, so one will be right

The throttle design is bought (I'm too dumb to do something like that myself), I just changed/edited some parts e.g adding a flap lever - which is not seen on the pic- The extra switches in the base are normally not there, but I think one can't have enough.

A new item in my ghetto pit. Already in love...

You got switches and a lamp showing you the status of the autopilot, so I guess there are a bunch of indications

Select stores - brings you in the config menu Select mark eighty twos (82s)

Try: Jester, Nellis - select