Falcon BMS Forum
    • Register
    • Login
    • Search
    • Categories
    • Unread
    • Recent
    • Unsolved
    • Popular
    • Website
    • Wiki
    • Discord

    TARGET stops doing its job

    Warthog
    4
    6
    330
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • BeakerVBA
      BeakerVBA last edited by

      Hi guys,

      I’m stepping back into BMS after a few months away, and the only change to my entire setup is a new graphics card. Everything else is identical. However, now, my TARGET virtual joystick stops working after I launch BMS, but only AFTER I launch BMS. Weird! If I run the script without BMS and fiddle with the device analyzer it looks great, everything is fine. Once I run BMS though, the virtual joystick might hang on for a few minutes but will inevitably stop working eventually. Result is that while I’m trying to reassign axes (everything else is a manual keyfile,) the virtual joystick axes are available selections but don’t actually move. My rudder pedals, however, are just fine.

      Any thoughts? Thought I had finally licked the whole keyfile and DX button thing, and now this. 😞

      1 Reply Last reply Reply Quote 0
      • F
        Frederf last edited by

        What kind of script? I’ve made some scripts that break after being manipulated too much (reassigning axes on the fly with EXEC()s). They work for a while then halt. Does the script stop working if you only run BMS and immediately exit or is this after some time?

        BeakerVBA 1 Reply Last reply Reply Quote 0
        • BeakerVBA
          BeakerVBA @Frederf last edited by

          It’s a modification of Morphine’s profile that was working well previously. I’ll try replacing it with a backed-up copy. The script appears to be fine until I start BMS, then shortly after (duration appears variable) it will fail.

          Edit:

          Appears another Windows restart fixed things. I’ll report back if that changes. (And I’m sure it will! ;)) Thanks for the help, Frederf. Have a Falcon day!

          Turkeydriver 1 Reply Last reply Reply Quote 0
          • Turkeydriver
            Turkeydriver @BeakerVBA last edited by

            This happened to me every time I used a profile after I upgraded from Win7 to Win10. A reinstall fixed it with no issues.

            BeakerVBA 1 Reply Last reply Reply Quote 0
            • BeakerVBA
              BeakerVBA @Turkeydriver last edited by

              Thanks, that’s good gouge! That was next, even though I didn’t make a Windows upgrade of course. If it happens again I’ll do that.

              1 Reply Last reply Reply Quote 0
              • WeakLink
                WeakLink last edited by

                I’ve had that problem, the joystick and throttle would go to sleep, Thrustmaster wrote back and said" the warthog needs to be plugged in to a powered USB hub or better yet direct to the computer. It seems to work best plugged into the computer and I run my rudders of the power HUB no problems since. Hope that helps.

                1 Reply Last reply Reply Quote 0
                • First post
                  Last post

                39
                Online

                10.7k
                Users

                21.1k
                Topics

                349.2k
                Posts

                Benchmark Sims - All rights reserved ©