Morphine

Ok, I found the issue. I was reducing saturation of the elevation axis to make the radar tilt more controllable (fine). If I reduce the saturation to 5 then the zoom doesn't work. If I set it at 10, the zoom works.

I observed that the the Radar Elevation Zoom function does not work with the Litening Pod if the HOTAS control is bound to an Axis. It does work if it the HOTAS control is bound to a button press. The HOTAS axis zoom function does work with the ATFLIR pod if bound to an Axis. If the Emergency Jettison is used the center mounted Litening Pod appears to be ejected in the 2D view but the Pod still functions on the jet for targeting, etc. Can anyone confirm these observations? Thx!

In case you don't already use these solutions, I find Open Kneeboard paired with DCS Moving Map as a more than adequate replacement for the spotty implementation of the AMPCD Map. I know it's not great to have to rely on 3rd party stuff, but at this point it's sort of a ED/DCS tradition.

Can we also exempt the HMD from DLSS? Having the HUD fixed really shows the fuzziness of the HMD.

When using DLSSTweaks it says that I'm running DLSS 3 with Preset K in the HUD... Should it be saying I'm running DLSS 4? Thx!

Price? Or is it one of those... "if you have to ask you can't afford it" type of things?

@mbucchia Yes, I mean the new Registry key in 4.3. So this is something DCS needs to fix and not a Varjo issue or both?

@mbucchia BTW, this same bug currently makes the Varjo native DFR unusable with the same problem which is why everyone is still using your Varjo Foveated software. Hopefully DCS fixes this and that will enable us to use the Varjo Native DFR.

There also needs to be an AWACS (or wingman) in the mission providing the additional information regarding the HSD tracks.

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.

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.