#1039 GW2 Overlay stopped working in snapshot a few releases back.

Current_snapshot
invalid
nobody
None
unspecified
5
2013-09-23
2013-09-21
Jerry Kilpatrick
No

Discussion

  • Starting a 3 or 4 snapshots back my overlay in GW2 stopped working. It had been working fine for untold snapshot releases before that.

    It is possible I have done something wrong but I hadn't touched the config for quite some time.

    I run windows 7. I use the latest snapshot.

    Any ideas? Can anyone confirm this?

    Thanks!

     
  • Philip Cass
    Philip Cass
    2013-09-22

    Working for me on 1.2.4-165 on windowed, windowed fullscreen, and fullscreen, so it's not a global problem. Can't be more helpful than that, sorry :(

     
  • Kissaki
    Kissaki
    2013-09-22

    I’m on Win7 x64, Mumble 1.2.4-165.
    It works fine in windowed, windowed fullscreen and fullscreen.

    Make sure you start Mumble before GW2,
    run neither in admin mode,
    and have the overlay enabled in Mumbles settings.
    If you want to get (us) some debug information, run DebugView alongside when starting GW2.

     
    • Well, definitely a me problem then. I've never used DebugView so I've attached 2 files. 1 where I started DebugView, started mumble, then started gw2. A second where I started mumble, started DebugView, then started gw2. I wasn't quite clear what exactly you wanted.

      I am running neither in admin mode, mumble always starts first, overlay is enabled, and gw2.exe is in the whitelist. I even tried resetting to the defaults for the overlay settings.

      Is this still appropriate to have a ticket open on this? I would certainly like to fix my problem but I realize this is likely something on my side and not a bug with the software.

       
      Last edit: Jerry Kilpatrick 2013-09-23
      • Kissaki
        Kissaki
        2013-09-23

        Create a discussion topic, or ask on IRC.

         
  • Kissaki
    Kissaki
    2013-09-22

    • status: open --> awaiting-reply
     
  • Kissaki
    Kissaki
    2013-09-23

    • status: awaiting-reply --> invalid