instigatorxb

I've been going through the MAD AH-64 Campaign using a Pimax Crystal. Before the August 14 update (2.9.7.59074), I was able to use the Crystal's controller for the EUFD and keypad button presses. Those no longer work (button presses on the MFDs still work fine with the Pimax controller). I can still adjust the brightness knobs. I can also affect the up/down EUFD switches on the left of the EUFD, just not the buttons on the right side of the EUFD. My fall back is to reach for the mouse for those key presses. [Update] After more testing, it seems the controller inputs used to "press" buttons in the Apache are different than what they had been prior to the patch mentioned and I believe the previous one. In the Apache, I'm able to use the Pimax controller to "press" with 1) the trigger, 2) pressing forward on the stick and/or 3) pulling back on the stick. For example: The master arm/ground override buttons, I push forward on the Pimax controller stick. For the MFD buttons, I can use the Pimax controller trigger The left side toggle up/down buttons on the EUFD, I can use the controller trigger The right side EUFD buttons and left keypad, I have to pull backwards on the controller stick (I used to be able to use just the Pimax trigger for these) Very inconsistent implementation of the controller inputs. I've noticed a couple oddities like this in the F-4 as well (push forward on the Pimax controller stick to reset the master caution whereas the other buttons I can use the trigger.

I've just submitted a crash report for a DCS crash when quiting a custom F-4 mission (subsequent AH-64 missions don't crash). Second time this has happened since latest update. DCS extremely rarely ever crashed on me prior to this update.

+1 for the option to disable mouse tracking from the VR headset. This issue primarily affects my use of the Jester UI in the Heatblur F-4. I have controls to navigate the Jester UI but they are not helpful when head movements seem to take precedence in action selection.

Today's patch (July 22) appears to have fixed this issue. All I did was update and jump into the cockpit real quick. But it looks fine.

Today's patch (July 22) appears to have fixed this issue. All I did was update and jump into the cockpit real quick.

I had to turn on "Enable Virtual Reality Headset" from the launch app settings. Just found the "Enable Virtual Reality Headset" slider doesn't stay set on exit/restart either.

So sad. Had an extremely tough work week and had purchased/downloaded the Afghanistan map yesterday in hopes of jumping in and checking it out tonight. Pimax Crystal user, jumping to another game for the time being. <heavy sigh> Just found the "Enable Virtual Reality Headset" slider doesn't stay set on exit/restart either. Probably better to chew on smaller code updates per patch.

I've been using a G2 in DCS since the G2 came out. Just received my Crystal yesterday. You aren't wrong to wait IMHO. I fired up DCS last night with the Crystal and I wasn't happy with the drop in smoothness (running with a 4090, 7950x). However, I was VERY impressed with the increased clarity and having that over a wider area. I could glance back at the FA18 left panel and clearly read the OBOGS switch lettering for example (in general, everything is noticeably more clear). I spent some time last night and this morning tweaking and following posts from mbucchia and others here and on Discord to see what the current state of smoothness settings is. I will try a few tips I've come across over this short period of time and see how that goes. I'll also wait impatiently for the DFR update, and whatever else can improve performance :-). [UPDATE] After some some tweaking last night, I've been able to get to a happy place with performance/smoothness in DCS. I made several changes at once but it was basically: - https://community.openmr.com/t/fixing-pimaxs-smoothing-or-lack-therof-motion-compulsive-smoothing/40851/10 Relatedly: motion smoothing is still functional with PimaxXR + Piclient 1.13, except that currently you must have both the “divide frame rate…” (formerly known as compulsive smoothing) toggle on and the “prefere framerate over latency” toggle enabled (as well as motion smoothing in PiPlay set to on). - And, pimax_cli.exe -int dbg_asw_enable 1 pimax_cli.exe -int dbg_force_framerate_divide_by 2 Late last night, my gut was telling me I should not have forked out $1600 USD for this and I should have stuck with the G2 to have a good/smooth/fun flying experience until Pimax releases its performance goodness. I still have the G2, but I paid too much for the Crystal to just shelve it. I won't return the Crystal, I'll stick it out based on the positive reviews from the beta testing.