Jump to content

bflo

Members
  • Posts

    134
  • Joined

  • Last visited

Recent Profile Visitors

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

  1. Yep SSS UP, & TDC Depress worked. AV-8B is the most fun to fly, but at least for me, the most confusing to deploy weapons Thanks for your comment.
  2. Haven't played Av8 for a very long time, & can't get mav to launch. Any help please. av8 mav test.trk
  3. Thanks, what I'm getting at is, I don't plan to ever use it without the cable, so no matter the condition of the battery, it will work?
  4. Does the headset need to be charged up if your using with link cable ?
  5. Been there done that Skate, except the usb testing, which I'll do. I don't have a lot of confidence in asus downloads. I'm not having any problems, everything is running just fine, but thanks for your comments.
  6. Well now after extensive testing, trying this & that, it seems to resolved itself. In the last few days I did a win 11 fresh install, plus all fight sim stuff, & more, hopefully everything has jelled. Thank you for you help!
  7. Posted 10 hours ago I guess if you press OK in the error message something will appear there. Nothing happens when I click on the debug window, just a blinking cursor. This is really strange, the pad works fine testing vibrations, & FS works perfect.
  8. Debug window stays blank. This is a new DCS install, I ran it with SSA (beta & stable) several times. I did a DCS long repair. Got the error as soon play starts, & nothing in debug window.
  9. Hi Andre, If I understand that, I'll give it a try latter today. But I know the error box shows as soon as the game starts.
  10. I have 23H2 np. I wish I knew what latter in the year means for 24H2, tomorrow, July, Dec?
  11. I'm getting the error also. Tried your export.lua from Andre, but didn't help. So I uninstalled NLR HFS, & still got the error. I had no problem with this in FS 2020 though.
  12. Looks like only a wifi driver, it didn't do anything else. All I know is what I see in device manager, with one unknown, after running the chip set inf.
  13. I went back to intel & found a chipset inf, & it fixed all but the unknown, so I'm happy. Thanks for pointing me in that direction.
×
×
  • Create New...