Morphine

Bump

I have these same options as well but selecting Tracker works for me (doesn't crash) and utilizes the Leap hands as controllers.

Is it possible to use the Leap "hands" to just control the "laser pointer" without activating the "touch" controls (and clicking buttons using left and right mouse)? It currently looks like you either enable both pointers and touch or neither. I'd like to try to use my left hand as a mouse while clicking buttons using mapped HOTAS buttons. I get too many unintended switch activations with touch enabled.

You can use both simultaneously... don't need to choose.

On the VR tab in the settings click the USE MOUSE setting and the cursor will be controlled entirely by your Mouse.

@Roger01 I understand what you are trying to do with the Head Tracked cursor in VR. I hope there is a solution as it would be more convenient to use.

null

The newer Block F-16's have this functionality but not the version in DCS so I don't expect it to be added.

I know you are probably looking for an easier interface, and it requires manual text editing, but the Autostart is customizable now. Look for a file called "Macro_sequencies.lua" for each aircraft you own in your main DCS directory. You can change various parameters and even add new steps if you like.

@BIGNEWY Bump

Any luck? Maybe this would get more attention over in the VR section or the Core Wish List section.

Lalt+C only turns the cursor visibility on/off... The OP is asking for a keybind to toggle the VR tab "Use Mouse" option in game which would be VERY useful for switching back and forth between headset and mouse control of cursor. Please Mr. ED!

I'd like to suggest the ability to have different Mouse Cursor settings depending on if you are in the UI vs 3D in VR. Currently, it's a one or the other choice for the Mouse Cursor to be controlled by the mouse or the VR headset both in-game and in the menus. I would like to use the mouse when in the menus (UI layer) and the VR headset for mouse in 3D (in cockpit). Alternatively, the ability to enable/disable the mouse (command in the VR Menu) via keystroke and button-press would be very useful. Thanks.

Cockpit Shadows work in VR on NTTR if on the HIGH setting. Flat, Low and Medium all exhibit the problems outlined above.

I would be willing to purchase a new version of a DLC Campaign with a limited number (4?) of multiplayer (client) slots. Would anyone else?

As far as I know the answer is No... the command line argument must be for the dcs.exe.

Although the DCS 2D screen no longer shows all 4 screens running with the Native DCS OpenXR, they are still there. It is why you have the mis-aligned cursors. I.e.: mis-aligned cursors = quad screen rendering.

For Varjo Aero and VR/XR-3 users. Currently the native DCS OpenXR implementation forces the 4-screen Varjo mode ON and there does not appear to be a way to run it in the 2-screen mode (also the DCS VR window no longer shows the 4 screens as before). However, the cursor offset/mis-aligned issue persists in the 4-screen mode thus making OpenXR mostly useless for all Varjo users. As everyone is reporting, you can still use the OpenComposite .dll replacement to use OpenXR and OpenXR Toolkit, etc. @mbucchia Can you add this information to your original post so that all the Varjo users don't try to run ED native OpenXR and will have to default to SteamVR for now or OpenComposite .dll? @BIGNEWY Is there any chance that the offset/mis-aligned cursor issue will be addressed as this has been an issue for over two years even in the previous Native Varjo implementation? Or at a minimum allow users to force a 2-screen OpenXR setting? Thanks.

Will the new Board work in the previous R3 Warthog?

If you had the correct length of M4 bolts could you use those to both mount the throttle and hold the rails in place with the same 4 bolts? Or are the front back tolerances of the rail mounts and the offset of the mounting holes going to cause a problem? This being my first WinWing product, I'm a bit surprised they could screw this up so badly.

Further to the OP post... When using the default shortcuts (updater.exe or dcs.exe) to launch DCS, it now launches in a "Varjo Native" mode if you are using a Varjo headset, which results in 4 screens being rendered. The 4 screen "Native Mode" screens used only by the higher-end Varjo VR-3 and XR-3 headsets which contain 4 physical screens. The more common Varjo Aero only has 2 physical screens and therefore, doesn't use the extra 2 rendered screens. Rendering 4 screens is a massive hit on the fps. Therefore, the result is a very significant degradation of of performance for Varjo Aero users for no reason. Users can currently use the "--force_steam_VR" command line argument after making a new shortcut, but they then lose the updater.exe shortcut auto check and is often causing frustration and performance hit for users. In addition as per the OP post, there is a doubling of the in-game cursors and they are out of alignment. Even worse, the dimmer of the 2 cursors is the actual functional cursor which makes this "Varjo Native" mode useless (even if one wanted to put up with the poor fps). Suggestion: Have DCS launch in the SteamVR mode as previously implemented (so that users don't have to use the "--force_steam_VR" command line) and let the small number of VR-3 & XR-3 users who want the "Varjo Native" mode use the "--force_varjo_VR" command line. Also fix the cursor alignment issue in the Varjo Native mode.

Interesting.... With my VR-3 the regular shortcut opens Varjo VR mode and I have to use --force_steam_VR to get the original Steam VR mode. I did not need to redo the WMR flip.

I found that adding the --force_steam_VR switch worked. "C:\DCS Open Beta\bin\DCS.exe" --force_steam_VR

Fair point!

@BIGNEWY Is it a real world procedure that the Bomb codes would not (could not) be changed unless the engine is off? If we have a running jet and change the loadout, it's a real pain to have to shut down to change the codes. If possible, it seems that if the jet is still on the ground we should be able to change the codes (ie. the ground crew would be able to do it at any point). Thx!