Dunx

I see the following on Steam trial... JF-17 F-16 FW 190 F/A-18C Spitfire F-5E BF 109 P-51D A-10C Not sure why the others are missing, and not sure why they are only two weeks instead of the whole month. I believe Steam imposes rules that prevent ED from repeating sales and trials.

Possibly after 27th May?...

DCS OB 2.5.6.47224 Carrier in MP is worse now (ping<40, players<10) Lots of desync and deck sliding, ship was not turning.

+1 Thank you, good luck, and don't panic!

This may be version/config/mod specific. I just test MPRS in single player (open beta, no mods) and comms are working correctly.

There is a 82.34% chance that this may be fabricated.

The "UI Layer > recenter VR Headset" option appears to do the same as "View Center" option (aircraft specific and general dropdowns). This adjusts forward, backward, left, right, up and down. It doesn't adjust head angle/tilt, at least on my system/version/aircraft.

I too have been looking for a "tilt" feature, for my HP Reverb. Flying the F-16C in VR just doesn't work for me. I'm pretty sure it is due to head position.

I'm hoping VAICOM Pro will do this.

I use the F/A-18C free flight missions to test graphics settings and noticed this message for the Persianl Gulf map. The mission itself has changed (different starting point) and so I assume it was edited using the latest (unreleased) version of the mission editor. Exciting times :)

+1, some VR love would be nice

I don't think Santa should be considered because, well, he really doesn't exist (?)

After looking at the picture and looking at DCS again, I have to agree... ... maybe the OP could provide a side-by-side comparison with the same angle, zoom, lighting, etc.

I've not had DCS restart on exit for 5 days now, no idea what fixed it for me, sorry. Dunksey

Agree, after touch down, quick throttle up and back to get ground idle, extend air brakes, slow to 100, apply wheel brakes and full back on stick... Really annoys me that identically loaded AI 18's can land and exit Batumi at second left exit, I've never managed it!!!

-1 ? I cleared out the "Logs" folder to begin testing but now DCS is behaving correctly. Tested DCS in desktop and VR modes, exiting via main-menu and via in-flight exit options. I'll keep testing.

C:\Program Files (x86)\Steam\steamapps\common\MixedRealityVRDriver\resources\settings\default.vrsettings

+1 DCS Steam Edition OB (latest), SteamVR (beta), WMR for SteamVR (beta). Also happened with non-beta versions before I made the switch.

I purchased the F-16 this morning, my main is F/A-18C, and I only fly in VR (HP Reverb, 60Hz). I flew the Free Flight instant mission a couple of times (about 40 mins in total) and about 10 mins of cold and dark (before I got distracted by NATOPS, erm, work). I'd say the VR experience was comparable to the F/A-18C (so far). I'll know more tonight. Which map and/or mission where you using? I will try the same sort in both F/A-18C and F-16.

Thank you ED, I picked up the F-16 this morning. Staggered sales though... hahaha... wonder how many in my demographic are wondering if we'll "get to the chopper" :lol: Dunx.

Sorry, I'm not familiar with the A10C and MVR, I assumed you needed to trigger a key press for each position of the physical switch. The physical three-position "Flap" switch on the Warthog Throttle is mapped to two separate buttons in RS Mapper. Each button can trigger a key when pressed and another key when released... Flap Up = Button 22 Press Flap Center = Button 22 Release / Button 23 Release Flap Down = Button 23 Press I know this can be done in TARGET but I had horrible problems with it due to device combining.

I use RS Mapper to achieve this... https://forums.eagle.ru/showthread.php?t=205492 You can assign a keypress to each toggle-switch position.

Oooo, I had my stick fail on me a couple of times this week. Once while I was in formation and my stick stopped responding, throttle was fine. Second time was even before starting DCS, stick didn't show up in devices. I don't use TARGIT, just RS Mapper. First time I rebooted and it came back, second I closed everything and moved from one USB port to another. I always blame my motherboard and the very poor quality USB implementation.

Wrong thread?

I have similar problems during flight and especially when switching from F10 to cockpit view. I think it is a tracking issue because I can simulate the same kind of flicker by covering both cameras with my hands. I don't think the camera sensors on the Reverb are suitable.