Jump to content

Tavilha

Members
  • Posts

    9
  • Joined

  • Last visited

Everything posted by Tavilha

  1. Thanks! I’ll give this a try and report back here
  2. As title states. AI aircraft deactivated via trigger or some time after landing and parking is equivalent to the conditions “unit dead” and/or “unit damaged” condition in the mission editor. This makes configuring triggers for a retaliation scenario, for example, unpredictable or not viable. In this case (see image attached), when the aircraft disapear after some time of being idle after parking (I also tried deactivating via trigger), the trigger is activated as if the units were damaged or killed.
  3. As title states. No movement after launch with either of the following options: - as triggered action fire at point with a positive shoot and scoot value; - added waypoint after triggered action fire at point; - as waypoint advanced task, with another waypoint afterwards. Thanks.
  4. I'm buiding a night escort mission and I'm baffled by not being able to turn the AI strike package's nav lights on around the RV area. The perfect feature for this would be a response to a communication (via F10 menu for example), asking the friendly aircraft to momentarily turn the nav lights on for visual confirmation. So yes, +1 on my part for the "wishlist"
  5. Thank you for your quick reply and the solution. Ran a repair with the exe you sent, rebooted and voilà.
  6. Restarted, ran DCS repair. No dice. Suggestions?
  7. I'm on cable link and this didn't work for me either. Are you using cable link or Virtual Desktop? Anyway, I started messing around with the hand tracking again and found something that's working for me. Under UI Layer in the controls setting, I set up a show/hide button for each hand, so that I don't lower the landing gear midflight or press any other buttons unwantingly, and set up a left and mouse button on my joystick. Still not perfect, but beats the hell out of letting go of the joystick to use the mouse. I can try and post a short video showcasing this tomorrow.
  8. Same issue on Quest3. If I use controllers in the VR options, they simply disappear. Furthermore, they used to be detected as Oculus Touch in the controls configuration page and now they're gone. If I switch to hand trackers, they show up and work as before. It's still unusable though, so the controllers must be fixed ASAP...
×
×
  • Create New...