Jump to content

mkel2010

Members
 View Profile  See their activity

  • Posts

    188

  • Joined

  • Last visited

 Content Type 

Everything posted by mkel2010

  1. mkel2010
    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.
  2. mkel2010
    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.
  3. mkel2010
    Plenty of YouTube videos show it does, going back at least a year.
  4. mkel2010
    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.
  5. mkel2010
    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.
  6. mkel2010
    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. mkel2010
    "Sheraton" on the image of the Sheraton Adana is misspelled.
  8. mkel2010
    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.
  9. mkel2010
    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.
  10. mkel2010
    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.
  11. mkel2010
    I have the Orion2 base and F16 Grip. After the last update, I turned off the F-16 FFB settings - which was supposed to help for those without the FFB base. I've noticed since doing that that whenever I start an airborne mission in the F-16 without autopilot engaged, the F-16 pitches down 2 -3 degrees while hands off on the stick. What adjustments, either in SAP or the game, need to be changed to prevent or at least lessen this behavior?
  12. mkel2010
    Yes, I did. I'm pretty sure I had originally set up the MAN RANGE as an axis but after the last update it got changed to a switch, hence did not work. Changed back to an axis and it works again. I've had other buttons, in particular the Weapon Release button not respond on the controls page even though it was properly bound to the right button. Had to delete it and re-bind it to get it to even respond on the controls page. I've also had issues with the MFD TGP screen flickering while in use, again something new with this update.
  13. mkel2010
    I've resolved the Man Range issue. I had previously set the binding to buttons. While this worked previously, it stopped working after the last update. Instead, it is now set to the controller's RZ axis in the axis settings. I had to increase the polling time for the RZ Axis in SimApp Pro to get DCS to recognize it as an axis. It's also worth noting that I somehow ended up with two Input folders for the F-16 in Saved Games. Folder names were F-16 and F-16C_50 (the second one is the correct one.) Still haven't figured out the Expand FOV button issue for the TGP.
  14. mkel2010
    I've resolved the Man Range issue. I had previously set the binding to buttons. While this worked previously, it stopped working after the last update. Instead, it is now set to the controller's RZ axis in the axis settings. Still haven't figured out the Expand FOV button issue for the TGP.
  15. mkel2010
    Has anyone using the Winwing F-16 Throttle and Joystick noticed issues with some key binds not being recognized in game, but do respond in Sim App Pro? Details posted in this thread:
  16. mkel2010
    Since the last update I've found at least three throttle and joystick key binds that the game doesn't recognize. I'm using the Winwing Orion 2 F-16 Throttle and Joystick. The key binds for the Man Range (throttle) and Expand FOV (joystick) don't seem to function since the update. Both are working on the devices, as I can see them respond when activated in SimApp Pro. The Man Range dial itself doesn't respond in the controls panel, but I was able to bind the function to another dial on the Throttle base. I've done a full repair on DCS which had no effect. I've tried with an with and without any mods and still have the issue. I'm not sure what other trouble shooting I can do or what files to upload that might heip diagnose the problem. Any suggestions?
  17. mkel2010
    Thank you.
  18. mkel2010
    @ouky1991 Is it possible to get your mod and the F-16 Yellow MFD Overhaul mod to work together? https://www.digitalcombatsimulator.com/en/files/3328823/
  19. mkel2010
    Is there any way to save the language settings from one session to another? I'm also finding it necessary to select English several times for the change to take effect on the main menu. Windows 11 version.
  20. mkel2010
    What you're looking for is available with the DCS Community Keybinds mod I talked about in your post on the Ejection Lever:
  21. mkel2010
    I looked at the PDF listing I created for the keyboard binds in the F-16 and the Ejection Safety Lever is not bound by default. in my setup, the key is defined under the Systems, Custom category. The "Custom" piece comes from adding the DCS Input Command Injector by Quaggles along with the DCS Community Keybinds mods (both found on Github.) With these mods installed, you can then bind the key to either the keyboard, joystick or throttle.
  22. mkel2010
    I can see the missions fine in Windows Explorer, but they didn't show up in DCS until I removed the periods. (I just checked and I can see them with the leading period in DCS now - not sure why I couldn't see them before.)
  23. mkel2010
    @=617= Evil I really like your missions, but I'm confused about your reason for using a leading period in the filename for the Basic missions. The leading period makes the files invisible in Windows systems. It's a bit of a pain to go through and strip them all out to be able to use the miz files.
  24. mkel2010
    Are you plugging into a built in port on the motherboard or an add-in card? If it's not the power settings, I'd check the drivers and then start looking at the USB hardware.
  25. mkel2010
    Sounds like Windows is powering off your USB devices based on a power setting in the OS. Take a look at this article: https://www.howtogeek.com/296918/how-to-stop-windows-from-powering-off-your-usb-devices/
×
×
  • Create New...