oCMANo

What'd be the main reason to update to a OLED set when that comes out? Is it just the darker blacks and better colors?

Updated and able to get 120 fps now with Anti Aliasing off. Seems to help spotting with it off. Items are more recognizable at a distance and not all 'muddy' due to the smoothing.

Main download page going to get updated? https://pimax.com/pages/downloads-manuals Still shows v1.33.02.01

Updated the original post for the new Pimax Play version 1.33.01.01 that has the OpenXR built in. You will need to remove a couple of the stand alone apps, but keep QuadViews Companion.

Yeah will do that. Probably will have to get a multimeter.

Have a strange issue with the Virpil Gearbox 2 with the Landing Gear lever. Up position reports button 41 just fine. Middle is button 40, just fine. Going down should report just 42 is active. However lately, down is doing a double button active with 42 AND 41. If I go down about 50% it'll just pickup button 42, but fully down it does both. A little worried it's a physical problem and not something with software, but anyone have ideas? As a work around just put a piece of tape to stop the down at 50% so it's just active on 42, but would like to get this fixed if possible.

The Discord reports seem to get more traction. Might be worth putting it over there if it's not already.

You'll be able to disable it. In fact you should already go through all the Privacy settings and turn a bunch off now. Recall is just the latest thing that tracks activity, there's stuff there already like Activity History.

@Calvin.Pimax for whatever reason this update didn't show up in the client when you were on a older version Settings > Current Version and run the Check for Updates. That would report I was already on the 'latest version'. Had to download from the link to get the update. Might need to make sure the Check for Updates is actually working in client?

That's the reason I wouldn't go down to 18%-20%, but 25% seemed to be a good middle ground. Anywhere between 25-30% is likely a good compromise for FPS vs focus.

Found this chart and adjusted QuadViews. If your eye normally only has full focus in about 18 degrees, then tried lowering the vertical and horizontal focus size to 25% down from 33%. Got about a 8-12fps increase and didn't notice any vision degradation when in eye tracking. Playing mostly in the 4YA WW2 server and don't really have any issues spotting planes (of course using VR Spyglass Zoom for distant spotting). Recommend trying anywhere between 18%-30% for focus size, 25% seemed to be my sweet spot.

My corsair mouse polling was at 1000dpi and I was getting the stutters while using menus and the mouse in game. Lowering to 500dpi in the iCUE software seems to have alleviated the issue, but it was something new after the last patch. Prior to that everything at 1000dpi had been fine.

Darn, was hoping there was some relief in this patch. Looks like someone confirmed it's still a open issue:

The multiplayer fixes for the servers/client with role selection and performance hits when bombers are flying/dropping bombs in a future update?

Awesome! I'll keep an eye out on the store. Thanks!

Super critical bug that only seems to happen in the Anton. Issue: Internal view, look at side of airplane from inside of the cockpit leaning out. The Board number on the side only shows 00. In external view F2, shows the correct board number. In multiplayer, the board number, internal view while leaning out of the airplane while flying shows the first digit of the 00 sliding through 1-9. Very strange. Cannot reproduce on other aircraft.

Yeah I also have this issue with the current version. Doesn't seem to be a issue in any other planes atm, that I can find though.

Repro: From the Launcher, let it load up. Once loaded trying to launch the Game in VR. Issue: Greeted by the message: Authorization is valid for 2d 23h 59m The following DLCs are now authorized and will be disabled: Afghanistan Normandy Was working fine earlier in the same day.null

Issue: From doing a singleplayer Mission with Super Carrier and trying Airboss, then switching to multiplayer the Airboss background sounds keep playing. Repro: Start a Super Carrier mission. Use Right Alt + F9 to go into Airboss station. Quit mission. Go into multiplayer. Connect to server and load into airplane. Should still sound like your on the Aircraft Carrier in the Airboss station.

Don't think you need to do anything other than replace the nvngx.dll in \Eagle Dynamics\DCS World OpenBeta\bin-mt directory. If someone knows otherwise let me know, but on the techpowerup page all it says was to replace the DLL in the game bin folder.

To workaround and be able to play with a decent FPS, I did the below. With my settings, I just: Disabled 'Allow use of the eye tracker' in PimaxXR Runtime Lowered the DCS resolution down to 1440p from 4K Updated the DLAA/DLSS nvngx.dll with the latest version (https://www.techpowerup.com/download/nvidia-dlss-dll/), and switched from MSAA 4X to DLSS Balanced. In QuadViews raised the Focus Size from Horizontal and Vertical up from 25 to 30, and is quite playable now at 65-80 fps. Hopefully they fix the issue soon. Would like to go back to full resolution with the eye tracking, but hasn't been the end of the world.

Does it shutdown while your playing or only when it's started, but no game is playing? Mine will shutdown the screens after about 5 minutes, but stays connected, if I don't start any games.

Yup have a open ticket and attached logs. Was suggested I disable the USB Hibernation in windows 11 so did the following. Open command Prompt as admin Ran command: powercfg -h off Restarted and tried playing. No change, eye tracking still failed after about 20 minutes. Also was suggested bypassing the Pimax powered USB Hub and plugging the USB 3.0 cable into the Motherboard directly. Connected the Pimax USB 3.0 cable to the USB 3.1 Gen2 port and left the Pimax USB 2.0 cable in the Pimax Powered hub to keep the headset charged. Also went into Device Manager > Universal Serial Bus Controllers and any Hub items > Properties > Power Management and unchecked the 'Allow Computer to turn off this device to save Power' After that played a bit and didn't have eye tracking stop. So far so good, but won't close the ticket quite yet until I have a chance to have a few successful sessions with eye tracking staying active. 06/23/2024 With the settings and the cables connected as described above, the eye tracking stays active. Not sure what in particular solved it, but the combination of the Power Settings and plugging the USB 3.1 directly into the MoBo seems to have solved it.

On a whim, decided to try 4K again with some tweaked Quad Views settings. Honestly was shocked I could maintain the 65-90fps! All that said, still getting where Eye Tracking seems to stop working and I have to go out of game and restart the headset. Hopefully it gets more reliable with some updates.