-
Posts
147 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by mkel2010
-
OpenXR Toolkit 1.3.8 still usable as stand alone (not Steam)
mkel2010 replied to StratosFalcon's topic in Virtual Reality
I too have been interested in OpenXR Toolkit, but this advice on the Github site has stopped me; "AS OF 2024, SUPPORT FOR OPENXR TOOLKIT IS DISCONTINUED. THERE IS NO NEW DEVELOPMENT AND NO TECH SUPPORT OF ANY SORT. THE DEVELOPER DOES NOT RECOMMEND TO INSTALL/USE OPENXR TOOLKIT, AS IT IS KNOWN TO CAUSE ISSUES WITH MANY OF THE NEWER GAMES RELEASED IN SINCE 2024" Any comments on the above statement? -
I just placed an order through the Winwing USA web site. The order had no added Tax. Are you sure you're not on the Global shipping site?
-
Right Hardpoint power on should be: LCtrl -LWin - W. Off is LShift - LWin - W.
-
Quest 3 VR NO LASER POINTER from hand controller in cockpit
mkel2010 replied to NIGHTHAWK1's topic in VR Bugs
@NIGHTHAWK1 I'm curious if you're using a link cable or Virtual desktop? I haven't been able to get hand controls to work well with either method, but Virtual Desktop seems to be a little better. I've been using HTCC but even that has detection issues with pinch control movements. -
As far as I know, Virtual Desktop is through a wireless connection, regardless whether or not a link cable is used. The link cable in this situation will keep the headset charged and that's about it. That said, I came across the video linked below that describes how to hook the Quest 3 directly into a wired router and use Virtual Desktop. I just ordered what I need to try this so it will be next week before I know whether or not it will work.
-
Who makes the stand that you're using?
-
Don't know if you're still having issues, but I was just able to get hand tracking working in DCS while connecting via link cable. First, in order to turn on the Devoloper Runtime Features, Meta - in their infinite wisdom - requires a Developer account. You can get the account either by setting up a business or by submitting ID verification. I chose the latter and it took about 48 hours to get back the approval. Second, I've found an app by the same developer who does Openkneeboard called Hand Tracked Cockpit Clicking (HTCC.) This app gives you a cursor in the cockpit for both hands (as long as you hand is visible to your headset cameras. You can then use finger gestures to flick switches and turn knobs. (It will take some getting used to.) If you go this route, make sure to read - and then re-read - the instructions for setting it up on the web site. If you need help, the developer has been very responsive through the Discord channel. Meta, and by extension DCS, certainly doesn't make this VR stuff plug and play. Link to HTCC: https://htcc.fredemmott.com/
-
What link cable are you using?
-
Is that something you can do with Virtual Desktop, or are you using the direct link? I'd love to know how to do that in Virtual Desktop (if it's even possible.)
-
Using Quest 3 and Virtual Desktop to connect to the PC and DCS. I've noticed that when I load a mission, I don't get any progress bar for the load screen and it seem to take much longer to load than 2D. Is this normal? I have an NVidia RTX 3060, a Core i9-129000K processor and 128GB of RAM. Latency in game seems to average about 70ms just sitting in the cockpit. The Quest 3 is connected to a dedicated router at a solid 2400 megabits per second. Are there settings that I can change to improve the latency?
-
Solved: Issues with New Quest 3 and DCS Hand Controllers
mkel2010 replied to mkel2010's topic in Virtual Reality
I'm referring to the Meta Virtual Desktop App available on the Meta web site for $25. The site you linked to provides the streamer app for Meta's Virtual Desktop to operate and the authors on that web site likely wrote Virtual Desktop, but the app itself is not free. The streaming app from this site runs along side Meta Link on the PC and allow the headset to connect to the PC with Virtual Desktop. -
Solved: Issues with New Quest 3 and DCS Hand Controllers
mkel2010 replied to mkel2010's topic in Virtual Reality
I was finally able to get hand tracking within DCS to work. For anyone else going down this path, it is important to understand that hand tracking ONLY works in Meta's Virtual Desktop app; IT DOES NOT WORK when connecting directly to a computer via link cable or AirLink. Also, apparently it is important to create a Meta Developer account in order to activate Hand Tracking. All that is required for the account is identity verification and takes about 48 hours. -
Solved: Issues with New Quest 3 and DCS Hand Controllers
mkel2010 replied to mkel2010's topic in Virtual Reality
Plenty of YouTube videos show it does, going back at least a year. -
I just got a Quest 3 (first time using VR.) I've connected to my desktop with both a link cable and AirLink. With the LInk cable, I only get the option of controllers or Disabled for Hand Controls and with Airlink I get the Hands option; neither works that I can see. I think Meta has changed their software and removed many settings, but the hand controllers work for everything else. Any suggestions? UPDATE: I figured out how to get hand tracking working in DCS. See my post further down for details.
-
It sounds like the roller on the handle isn't consistently tracking on the upper guide bar. I had a similar problem when I set mine up and it took some fiddling (technical term) to get the upper bar adjusted so the roller tracks through the entire range of motion.
-
How can I find the setcommand for [Cockpit Perform Clickable Action]
mkel2010 replied to liudy116's topic in Mission Editor
In the Saved Games config folder, create a file called autoexec.cfg and put this in it: input = { command_code_tooltips = true, } (No extra lines are needed, just the way the forum formats the code. You should end up with four lines of code.)- 7 replies
-
- 1
-
-
- mission editor
- triggers
-
(and 1 more)
Tagged with:
-
"Sheraton" on the image of the Sheraton Adana is misspelled.
-
You want Simulation not game. After the last update some of my controls didn't function as they were previously bound in game. I had to delete those binds that weren't working correctly and set them up again. Also, be aware there is an Afterburner detent setting in the game settings Special page for the F-16 so you may want to make sure there isn't a setting for that in whatever aircraft you're flying in that section of the settings.
-
Understood. Just to clarify, turn off the Pitch/Roll settings and zero out the dead zones in the Special Settings menu? I've calibrated my stick any number of times. I discovered today that with the stock SAP dead zone settings there was a small, visible amount of forward stick showing on SAP without touching the stick. I was able to get it centered by increasing the SAP dead zone to 5% on the pitch axis (without dcs running) I haven't tried it yet in game.
-
I'm referring to the new Pitch and Roll settings under the Special Menu for the F-16. In reading the release notes, turning these settings off if you don't have a FFB stick is supposed to help with stick response for sticks with springs like the Orion2 base.