Jump to content

docvego

Members
  • Posts

    8
  • Joined

  • Last visited

  1. Overlordbot is an amazing project and having these APIs accessible is a great idea and worth the effort.
  2. Order #2179 was delivered yesterday to North East USA. I just finished the installation, like everyone else has said, it took about 15 minutes. Install and calibration was a breeze. Thanks so much for such a great kit! High quality controller, great tracking and excellent instructions.
  3. Order #2179 just shipped today!
  4. I'm hitting a similar issue with this mission as well. I'm able to go through to JTAC sequence, LASE ON, etc, without any issue. However when it comes to the 2nd target, I can't get the JTAC to go past "Read back correct". After he says "Readback correct" my Comm Menu is still at the 9 Line Read back stage and won't progress. Had the same problem on two runs of the mission. Tried signing off from JTAC and signing back in as well and still gets stuck in various jtac states. Anyone seeing a similar issue? Playing Open Beta 2.5.5.32533
  5. Cross your fingers, things seem a LOT more stable now. The things that may have done the trick: Uninstalled existing nVidia driver (had tried both 430.64 and 430.86) using DDU (Display Driver Uninstaller by wagnardsoft) Installed nvidia driver version 430.39 Switched from using the 2070 RTX's HDMI port to using a DVI to HDMI port adapter. (this one https://www.amazon.com/gp/product/B00EDT0072/ ) Windows mixed Reality was very cranky at first about the port adapter (kept giving a 1-4 error), took few reboots and unplugs and re-plugs to finally accept it. Also, I don't think it was mentioned previously but I also picked up powered PCI-Express Expansion card: https://www.amazon.com/Inateck-Superspeed-Ports-PCI-Expansion/dp/B00FPIMICA I've had it for close to a week, and it didn't make much of a difference. So in the end this might be a combo of USB Power, touchy drivers and a touchy HDMI Port. I shall do my due diligence and spend the weekend flying to see if it's as solid as it now seems.
  6. Firmware updated to 1.02 (had tried a few times yesterday and it kept getting stuck at 10%), it was successful the first time today. I'm running 16GB of RAM. Tried reinstalling SteamVR & the WMR SteamVR addon & verifying the local install after that, so far.. same problem.
  7. I've got a Samsung Odyssey+ Headset, 1.01 firmware. For at least a few weeks I've had an issue with sporadic crashing of Windows Mixed Reality throwing a 14-2 error while I'm playing. The game itself seems to keep running fine for a few seconds after the crash and then exit out after it and SteamVR can't find the headset anymore. Hitting "Try Again" in WMR will re-init the headset. Launch the game again and the sad cycle continues. While I've gone probably as long as a hour without the crash, more recently it seems to hit more often in as short as just a few minutes. I've even had the crash happen while just poking around in the main menu. I've tried a few different Nvidia drivers, reinstalling WMR, buying a separate USB PCI-E card, disabling the power save on all USB Ports, disabling power save stuff in SteamVR, and every USB plug on my computer. Sifting through Event Logs, SteamVR Logs, Windows Diagnostics and the logs for DCS don't show any obvious errors. So far I haven't been able to replicate the error playing any other games. AMD Ryzen 7 2700X AUSTek ROG STRIX X470-F GeForce RTX 2070 At this point I'm out of ideas. Anyone encounter anything like this and have any suggestions?
×
×
  • Create New...