Kirin

Hey Miles, been spending quite some time in VR over the holidays. Gotta say - cannot fly without PointCTRL anymore. I really appreciate the work you put into this and I can only imagine how much better things will get over time. Did you get your Reverb btw? Anyways, I wish you and your loved ones a great time as well! Kirin out

Yep, definately insufficient lightning - ever since I put up a big lamp behind my cockpit everything is fine. If you use Point CTRL just be sure to get a non IR emitting bulb.

Greetings aces I had the same problem with VA not recognizing any commands anymore. I renamed the Export.lua and let DCS build a new one then added the SRS line manually. Works fine again. Using all the latest patches for DCS Open Beta, SRS and VA.

I wasn't able to properly calibrate in Portrait Mode as the 5 point calibration put the crosses outside of my horizontal FOV. Also the Monitor view calibration is funky cannot get to the outer edges of the game window - neither horizontal nor vertical. Going Portrait is probably not a viable solution at this point. @new Firmware: the indication cursor movement is much better

I think the problem with custom resolutions might be that the actual resolution does not change - afaik the graphical information will be downscaled to your native resolution anyway. It's the same with DSR SuperSampling I tried.

Yep. The cursor even moved beyond my vertical FOV in the headset. Sorry, didn't read correctly. Will test horizontal movement tonite.

Holy moly. That actually works. But it's really hard to navigate Windows 90 degress off...:)

As suspected the "dead zone" stays the same.

I just noticed I can increase it to 3620x2036... I guess it's just supersampling. Gonna try out what effect that has on the cursor movement.

Monitor native res: 2560x1440

@Reverb: For the testing I disabled the cursor confinement to the game window. The mouse cursor seems to be staying at the same relative position of confinments in VR, e.g. the maximum borders I can reach with the blue cross cursor. As you said the blue cross cursor cannot reach the top and bottom 20% of the vertical limit. So if I go to the top of that virtual confinment and exit the side of the gaming window the cursor will be at the top of the desktop window. So it actually jumps away from the vertical center. When I leave the gaming window at the center of that virtual confinment it will stay at the center of the desktop. A similar effect is also seen in the title screen where the virtual cursor confinment is the actual options window. I can move the mouse to the top of that options window but not beyond it altthough the vertical FOV covers more, e.g. I see the hangar above and below the window. If I exit the options window while having the cursor at the top of it it will appear at the top of the desktop screen. I hope this makes sense. @voice assist: It's a real help and makes the calibrating process so much easier as you don't have to remember all the clues the different cursor movement give you. Especially as new ones get introduced or changed. It worked really well. Can't wait to have the full functionality with explanations for edge calibration and zoom.

Hey Miles I am using an HP Reverb, my monitors native resolution is 2560x1440.

I love huge updates! I love pointctrl in general. Works beautifully with the JF-17 in VR. Can't wait to try the new voice assisst setup. Still having trouble reaching switches in the far back and the bottom of the screen. Still, cannot go back flying without it. Thanks again MilesD you revolutionized the experience!

I just ordered a H950P from https://huionshop.de/ - shipping to Switzerland is ok with 18 EUR. Looking forward to try this out!

Bones, do you see the little color indicator in the top left of the HMD for the status of Reprojection? It's green when reprojection is off light/dark blue when it's on and red when the FPS is below the reprojection minimum. If not, reprojection is probably not in use.

Found the problem. I did not correctly add the additional AIRIO commands as layed out on page 36/37 of the manual. Works like a charm now. Off to some F-14 training!

I just recently got back into DCS. Got a new rig - installed everything a new and wanted to try out the F-14 along with VAICOM PRO. I used VP in the past very successfully. Setup was painless and the basic functions work. Voice Attack does recognize the module. Extented Command Set is enabled. AIRIO is enabled. But I cannot get Jester to answer to my calls... see screenshot... Help is needed!

From the experience I have from the Vive, the Odyssey and the Reverb - the Reverb wins handsdown. The clarity is unmatched, it's lighter and I didnt have any of the technical issues that have been reported.

Finally built the new system and got around to have a go with PointCTRL. Pretty awesome. Still have to fine tune the calibration. The crammed 190 cockpit was not the best place to start I guess... :D Can't wait to test further. Great work and many thanks to you Miles. Kirin out

Had a first testflight on the Reverb. Holy Lack of Screendoor Effect!! Didn't change any settings. So PD 1.0, Steam SS at 100%. And the clarity is astonishing. The throttle indicator on the MC2000 is crystal clear and readable now as before on the Odyssey I had to guess the numbers. In FreeFlight Nevada the performance is great. Will dig into the nitty gritty details later this week trying to optimize quality vs performance. Sidenote - is the manual activiation for WMR motion smoothing still mandatory?

Secoda, mind to share your game and SteamVR settings and the results you get?

The XPlane 11 benchmarks are interesting. Can't wait for the real DCS and especially DCS VR benchmarks. Where are our fellow pilots?

Do we know where Vulkan API integration is on the roadmap?

Can't wait for some testpilots actually give us some real info. Holding back atm.

One thing the Gamers Nexus review points out is that Frametime, albeit being a little higher than with Intels flagship, are more consistent, e.g. less spikey on the Ryzen - that could be beneficial in VR.