Announcement

Collapse
No announcement yet.

Weird issue with singularity 2.03 in "discovery mode"

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Weird issue with singularity 2.03 in "discovery mode"

    Hey there,

    I'm running singularity in what i call "discovery mode", i.e. after entering a system singularity does all the scanning for me... or at least that is how it used to work.

    Now, with that new HUD mode stuff, what happens is this:

    - I jump into a system with the hud in DISCOVERY MODE
    - Singularity switches the HUD to COMBAT MODE and then tries to do the scanning, which of course fails, and all I get are three popups saying "this module can't be used in this hud mode"
    - then, singularity switches back to discovery mode.

    Is it a bug, or my bindings?
    The keyboard part of my bindings is here: https://edrefcard.info/configs/md/mdnblt-keyboard.jpg

    Any ideas?

  • #2
    What happens if you jump with the hud in combat mode?
    1) I reject your reality.... and substitute my own
    2) Not to be used when upset... will void warranty
    3) Stoke me a clipper i will be back for dinner
    4) Never tell Gangrel to do anything... he will probably get it wrong
    WARNING! Swedish wall-of-text hits you for bork-bork-bork damage!

    Comment


    • #3
      try this:

      say lights on and then say it again. If you get a "that has already been done" or words to that effect then the reading of the journal isn't working. Run VA as admin and try again. Once that is working correctly then the hud switching will work correctly as well
      The Singularity profile - One profile to rule them all and at HCS we bound them

      You see, TheThingIs, eventually you'll be allright.

      Comment


      • #4
        Originally posted by TheThingIs View Post
        try this:
        Run VA as admin and try again. Once that is working correctly then the hud switching will work correctly as well
        I just went straight to running VA as admin, and now all works as expected.

        Thanks for the hint!

        Comment

        Working...
        X