Wyverex

Hi, thanks for the feedback! There is no LeapMotion support in IvyVR as of now. That might be added later. Although it will always suffer from missing haptic feedback which is actually a huge deal. But I can see the desire for using LeapMotion. So, the reason why `L DEVICE` and `R DEVICE` are showing is because you presently need to use VR controllers with IvyVR. There are default bindings for a broad range of controllers included. Also, the presence of `MODULE` indicates that IvyVR isn't talking to DCS properly. This could be related to you using the Steam version of DCS which I've never used before. Where is the user data located in the Steam version? In Standalone, it's in `Users\<Username>\Saved Games\DCS.openbeta`. I probably need to update the installer to put in the correct path for Steam. For now you should be able to fix that issue by copying the `Scripts` folder from that directory into the directory that Steam uses for its user data. It contains a LUA script that IvyVR uses to communicate with DCS.

I've updated IvyVR to 2.1.0: - Fixed IvyVR not starting up on various systems. Unfortunately I didn't know about this until very recently. Please let me know if you still can't start it! - Pimax Crystal controllers should work correctly. There's a bug in the PimaxXR runtime which I had to work around until it's fixed properly in the runtime

Previously it only worked using OpenVR (which implied using SteamVR). Now it only works using OpenXR (and as an Index user that means you're still using SteamVR, just using its OpenXR runtime)

Good news, IvyVR 2.0.0 now supports OpenXR natively! SteamVR is no longer required unless your headset requires it. Since my Pimax Crystal is still currently shipping, I could only test this on my Index yet (which does require SteamVR). However, it should work on all OpenXR runtimes and on a large variety of controllers. Give it a try and please let me know if anything goes wrong! The website has been updated, you can download the new version here: https://ivyvr.net/download/ Some other nice benefits in this new version: Recentering now works using the same key as DCS uses (Ctrl+F12). Currently this is hardcoded but I'll add keybinding configuration later if there's any demand for it Better performance and reduced input lag. IvyVR now runs in lockstep with the DCS frame loop which feels more responsive Hint textures are only as big as they need to be

I actually started out with a similar concept. I bought one of these 3D touch pads and wanted to use that to control the mouse with finger gestures: https://www.microchip.com/en-us/development-tool/DM160225 But then I found out that you could render overlays into any VR game using OpenVR and that changed everything for me!

Quick update since I've been silent for a while. I've changed my mind and instead of first supporting the remaining aircraft, I've started the OpenXR port. Progress is good and it looks like everything will work just fine (with probably a few snags we'll have to live with). But it's still a lot of work, so it might take a few weeks until I can release it. Then IvyVR should work with just about any VR headset out there and will no longer require SteamVR to run (except if your headset requires it).

Possibly! However, I want this to work on as wide a range of headsets and controllers as possible. The point is that you don't have to invest in special hardware just to get a feature that you should already have access to using your motion controllers. I agree that picking up your controllers whenever you need them is still a bit cumbersome. I've gotten quite used to rest them in my lap and picking them up when I need to but my endgame would currently be something like this: https://www.instructables.com/Etextile-VR-Gloves-for-Vive-Tracker/ It would be very easy to support in IvyVR. But before I start a project like that, I want to get OpenXR working first.

For the most part, your controllers and your HOTAS don't get in each others' way, especially if your stick is located where it should be in the cockpit. I have my stick mounted to the right side of my chair, so for most aircraft it could obstruct access to the right console. In practice I haven't found that to be an issue though. I also have a lateral offset configured (due to my armrests), which helps further with clearance. Sure, sometimes, you need to adjust your position a bit to reach a certain switch but I didn't find that to be a problem so far!

I've always wanted to feel more immersed when playing DCS, especially after I switched to VR (~2.5 years ago). Back then, we still had laser pointers to interact with switches and that just didn't feel good enough. I wanted to reach out and do it instead of just pointing at a switch from a distance. That's what motion controllers were always meant for, so I wanted to make use of that. While hand controller support has gotten much better now, it still leaves a lot to be desired. It still doesn't feel good enough. That's where IvyVR comes in. It's an external program that projects two crosshairs into your cockpit and allows you to perform natural gestures on all available switches. Best watch the video to see how it works: I had a first working prototype beginning of 2021 but then life got in the way, I stopped playing DCS etc. Now, IvyVR is finally ready for release. I hope you enjoy it as much as I do! I couldn't imagine ever going back to using the mouse in VR. Note that IvyVR is not meant to replace your HOTAS, I still use mine and wouldn't give it away. But you can't possibly bind every cockpit function to HOTAS buttons and, frankly, I wouldn't even want to. There is an added level of immersion in physically reaching out to do something, even though VR currently can't give you the full haptic feedback of flicking a switch. Download here: https://ivyvr.net Now fully on OpenXR, you only need SteamVR if your headset requires it! I'm committed to make IvyVR work on as wide of a range of headsets and controllers as possible, so if you have a combination that doesn't work, please let me know in this thread.

I love this campaign! I played the first two Maple flag training campaigns and they were already great but this is an entirely different league. Thanks so much for creating this! I tend to agree with the sentiment about the DIVERT page. Given that the missions already go into so much detail about even fairly obscure things like the IFFCC Test menu, I'm actually surprised that the DIVERT page isn't mentioned at all when going for the landing in Silverbow. That orbit time would be the perfect opportunity. I actually totally forgot about that page while flying the mission and I was wondering how to know once I'm 5 miles out of the airfield. Feels like an inconsistency. I was considering manually going through all the WPs to find the correct one in time. In the end I just winged it and it was ok.

I had the same happening to me today. Biff flew back all the way to Moapa, turned and then followed the FP to land. Things that I might have done to cause this: - I landed on 21R and took a while to clear the runway - I stopped between 21L and 21R because I wasn't sure how far to go. After a while I continued further beyond 21L until I saw the UI message to wait there During my landing approach, Biff also stayed beside me for a long time and wildly oscillated up and down. I don't think he was orbiting around the truck stop. Then I didn't observe him any further until I was on the ground. I guess he started back on his FP then.

Thanks guys! There's some very helpful stuff in here. I'm already banking towards the TGP and I've noticed that the sidewinders you sometimes get in the mission exacerbate the problem. I think my main problem is that I'm too low and too close. There's always a sense of urgency after a dive and coming back up again that probably causes me to not separate far and high enough to set myself up for success on the next run. I'd love to do that more. Unfortunately, with limited resolution in VR, looking out the window doesn't give you much in terms of SA when it comes to ground targets. Even when diving in, I only see targets very late. So I'm actually very dependent on having a good TGP fix and then diving towards the SPI marker to get on target. I hope that changes when upgrading from my Index to a Crystal later this year. The HMCS and and TMS right long have actually been a life saver for me, I couldn't live without that anymore. But I haven't really used Mark points a lot yet. Should probably start to as they sound really useful if employed like you describe. I think I'll have to load up a practice mission and just try to keep a target in sight for as long as possible to get a better feel for what I'm doing.

I've recently started playing the amazing The Enemy Within 3.0 campaign and I keep running into the same issue, over and over. I anchor over a target area using ALT Hold to search for targets and half of the time I spend looking at a masked TGP. So I disengage hold mode and start maneuvering to keep the targets in sight. Sooner or later that makes me oscillate wildly while being heads down dealing with the TGP. The worst part is when trying to track moving targets, like three trucks that I have to destroy before they reach a target. They are hard to spot anyway (especially in VR) and I constantly lose sight of them while my TGP is masked. This is extremely stressful. I waste so much time searching for them again after the TGP is unmasked. This gets even harder in the mountaineous areas in the campaign where I have to watch out not to fly into the mountains and on top of that I regularly mask targets simply by having a mountain or trees in between. At this point I'm sure I'm doing something fundamentally wrong. Keeping your targets in sight is surely a basic skill that everything else builds upon. What are your techniques to ensure you minimize TGP masking time (I doubt you can prevent it entirely, especially during bombing runs since you have to reverse at some point). For example, is there a sweet spot for both the bank angle and distance to target area while anchoring?

No matter how I run DCS these days, ST, ST + force_steam_VR, MT, I can never get the Steam VR dashboard to show while in a mission. It works fine in the menu but not in game. The image just freezes. Does anyone else have this?

When you download the ALVR v20 nightly for the streamer, there is also a generic alvr_client_android.apk included. Download that on your Pico and use that as the client. I did that yesterday and I had good performance