Jump to content

Viper19ca

Members
  • Posts

    6
  • Joined

  • Last visited

1 Follower

Personal Information

  • Flight Simulators
    DCS, Star Citizen
  • Location
    Canada
  • Interests
    Photography, Outdoors, Gaming

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. This was done on the Afghanistan map. I will.create one on Caucasus in a few days.
  2. Infantry Equipped with JTAC Do Not Move or Embark Created a test mission which involves transporting a FAC team by helicopter. The FAC team consists of 2 dismounted infantry soldiers, 1 armed with an M4 one with the default JTAC loadout. The M4 soldier moves to waypoints and embarks Huey as tasked. The JTAC equipped soldier will not move to any waypoints nor embark on the Huey with its team. I also tried a single JTAC equipped infantry soldier in its own ground unit, same issues. Anyone come across this issue and have a fix? JTAC Test.miz
  3. @omohat, no I haven't tried the other options. Going to wait for the upcoming patch this week, as there is apparently a fix in that patch. Thanks for the recommendations though.
  4. Well I tried to start up DCS last night in VR. It is crashing on start again. Looks like we will need to wait for DCS to find the problem and issue a patch.
  5. POTENTIAL FIX OCULUS QUEST 2 META/Oculus V63 update crashing DCS on startup. My System: Intel i7-13700 RTX 3060 Oculus Quest 2 I may have found a fix for the Oculus desktop and Meta Quest 2 V63 update which has been rolled out to all users. Uninstalled and reinstalled DCS. - (may not be necessary) Rebooted the Oculus Quest 2. Uninstalled and reinstalled Oculus desktop. At first run of the Oculus desktop I did not set the Oculus as the default OpenXR runtime in General settings. (may not be necessary) Then reestablished the wired link. Started DCS via the link successfully in VR. I then closed DCS after a short test flight. Hand controllers did not work well during the flight. Sporadically usable. Shutdown the Oculus Quest 2. Set Oculus desktop as the default OpenXR runtime. Then reestablished the wired link. Started DCS via the link successfully in VR. I then closed DCS after a short test flight. All working wired and wirelessly. Both the HMD and the desktop software are version 63. Seems to me the key was to fully uninstall the Oculus desktop software and reinstall. Hope this helps.
  6. THE FIX FOR CONTROLLERS INTERFERING WITH A REAL LIFE HOTAS !!!!! With the the hand controllers active, go to SETTINGS and clear the Pitch and Roll axis binding from the hand controller. Problem solved. If you are using the virtual stick and throttle this is obviously not a fix for that use case. I am using an Oculus Quest 2 and X56 HOTAS. This is the problem I was experiencing: When in VR, using the left controller in any mode, the controller interferes with the X56 joystick until the controller's internal timer deactivates it. It doesn't interfere with the throttle. Once the controller is deactivated (times out) the stick returns to full function. I have noticed that there is some partial function when the left controller is active. Seems like the saturation of the joystick controls are severely reduced while the left controller is active, they are basically competing with each other. If setting the right controller as the only controller or when both are enabled, and I only use the right controller, there isn't any interference with the joystick or throttle. So the left controller is the only side interfering with the joystick, and only when it is actively being used, until it times out and returns to an inactive state. Makes sense as both the joystick and left controller and bound to the pitch and yaw axis.
×
×
  • Create New...