Jump to content

cochise

Members
  • Posts

    33
  • Joined

  • Last visited

Everything posted by cochise

  1. Hey man did you get your 1-4 check your display cable error fixed? This seems to be happening across the board with windows mixed reality. My odyssey is doing the same. Also when you unplug your headset and re-plug it in is there an audible sound like you've plugged in a usb device? Sounds strange but mine becomes recognized but without a sound. Whenever I have got it working there's been that you just plugged in a usb device windows sound. I also had some luck uninstalling my usb serial bus controllers in device manager and then restarting to have them reinstall. After the restart I plugged back in to a 3.1 and it worked....until the next restart! Have you also tried command prompt as admin and then sfc /scannow   ?

    1. AKRocco

      AKRocco

      No I never did get my first headset working. The replacement they sent has worked so it was definitely a faulty headset for me. Unfortunately the 1.4 error is not very specific and there's a hundred different things that could cause it.

       

      I did have an issue with the usbs on the mb itself, they were causing stutters in tracking and audio, and I would constantly hear the connect/disconnect sounds. Didn't matter which usb port I used, 2.0, 3.0, 3.1, type C, they all did it. Fix for me was using a powered USB hub. No idea why it would work better than direct but it does for me.

       

      I haven't tried that command prompt command. I do know that there are a few things that register in the device manager for a headset. For the G2 it comes up as a display, a WMR device and under the usb for tracking. If you haven't already I would take a look in there and see which part isn't coming up.

       

      Hope you get your headset running!

    2. cochise

      cochise

      Ah shame man! Yeah I'm thinking I'll try another headset. Once mine works it works flawlessly no stutters or audio crackles which is why it's so baffling. I'm scared to think it might be the motherboard though but it's a possibility! Thanks for the info.

  2. I was having the same microstutters issue with decent frames ( 45+) in vr and it was killing the Immersion for me. Every 10 to 20 seconds the visuals and sound would stutter. I read strongharm's post about having a new powerful rig with bad performance and went through his steps. I also noticed spikes in my ethernet that coincided with the microstutters occurring. Strangle enough for me it was razer cortex! I have no idea why, as it had helped me so much in the past. Disabled it and back to fluid game play. Obviously I tested turning it back on and with it came the microstutters. Sent from my MAR-LX1M using Tapatalk
  3. Well said[emoji1433]and thank you for the clarification / update. Sent from my MAR-LX1M using Tapatalk
  4. This happened to me after a steam VR beta update. Maybe that is the culprit?:doh:
  5. Still has to be one of the most fun missions I've played. I'm sure now with 2.5 this could be made possible again. The only thing would be the adaptation of the tree weights in the db_units_ground.lua as mentioned previously.
  6. Hi all, specifically the Logitech G940 users here. Right now I'm unable to bind my trim HAT on my Logitech G940 through the external profiler. It works fine with other modules like the SU-25 mapping the default trim keystrokes but no joy with the Harrier. The only difference I can see is that in the SU-25 the trim is listed under "Flight controls" in the controls category where as in the AV8 it's listed under "HOTAS". Anyone with the same issue? P.S using the POV for the trim would kill me! :badmood:
  7. Not sure if this is a re-post but very fitting with the NTTR
  8. I get the same when I have upuaut's mods installed. The trees disappear for some strange reason.
  9. it works for me in multiplayer but once I'm coming back with a slingload it crashes the game
×
×
  • Create New...