Sunday 18 February 2018

User friendliness update

Hi.

And now for something completely different.
This update doesn't bring any new functionalities, but instead focuses on making it much easier to distribute and install marker packs.

First off: marker packs can now be distributed as zip files as well. Any zip file inside the POIs folder next to TacO will be parsed, and all xml files inside there will be imported as markers. This should help out a lot for those of you who don't really like messing around decompressing downloaded stuff.

But wait, there's more!
There's a very interesting thing in windows where it's possible to register an application to handle its own protocol, similar to how file extensions can be assigned a default application. This means that when you click on a non-standard link in your browser, it'll look up the appropriate application and ask you if you want the link opened in that application. Steam uses this mechanic to start games when you click on them in the browser, and now TacO can do something similar too: the overlay now supports one click, on-the-fly installation of marker packs straight from a browser, just by following a link. Of course you first need to download and run the new build in order for the protocol to be registered.

In short: tab out of GW2, go to a website, click a link, tab back to the game and enjoy the markers.
Important: you need to run the new build of TacO once before the links will start to work.

So here's the technical stuff: any website hosting markers can now also link to them using the gw2taco://markerpack/* formula, where the * part should be the actual download URL of the zipped up marker pack without the http:// part (TacO will try to download the zip file through http, and https if that fails).
Here's an example link:
gw2taco://markerpack/www.somewebsite.com/subfolder/markerpack.zip
this will tell TacO to download the  http://www.somewebsite.com/subfolder/markerpack.zip file, save it to the POIs folder and load it as a marker pack. Some tests are performed to make sure that the file is actually a zip and that it can be loaded before storing it in the POIs folder.

Oh, and also, I registered the gw2taco.com domain :)

You can download the new build here.

Changelog:
  • GW2 TacO will no longer be fooled by other windows called "Guild Wars 2"
  • Added "toggleCategory" attribute to markers. These markers will toggle the specified category on or off when triggered with the action key.
  • Turning off the tactical display will now also hide trails
  • Zip compressed marker pack support for easier distribution
  • Trail textures will now also be found under the POIs folder (like marker textures are)
  • I caved. http://www.gw2taco.com is now official :)
  • Added gw2taco:// url scheme support for one click, on-the-fly marker pack installation from any website

28 comments:

  1. Antivirus is detecting this version of GW2Taco is suspicious and will not allow me to open GW2Taco. Previous versions were fine, I'm not sure what is up with this version.

    ReplyDelete
    Replies
    1. Im just guessing but I bet is the new Browser Install Feature

      Delete
    2. Maybe, I just reverted back to the old version of GW2Taco. Hope the developer figures what is causing the alert. Been using Taco for about 1 year, first time I ran into the antivirus issue.

      Delete
    3. Happens after each release. Please send it in to your antivirus company to be analyzed thoroughly so it can be put on their white list. Every av program should have a function for that.

      Delete
    4. Yeah, my antivirus told me it was okay after analyzing it for 5 hours. First time it ever alerted me. Thank you.

      Delete
    5. I just downloaded version 034 and my antivirus did not have a problem with it. It only had an issue with version 033.

      Delete
  2. Waouh, this is very impressive.
    For my distribution, it will be excellent, but i will need time to adapte this.
    Your work is very good.

    ReplyDelete
  3. It crashes with trails, trails disappear after a minute then a few minutes later it crashes with a window that states application crashed

    Build version: GW2 TacO 033.1864r
    Exception Type: e06d7363
    Unresolved address: 761608B2
    Unresolved address: 13246FB
    Unresolved address: 131DCCA
    Unresolved address: 12D19F1
    Unresolved address: 12D1F69
    Unresolved address: 1302762
    Unresolved address: 12F162F
    Unresolved address: 12F151B
    Unresolved address: 132146B
    Unresolved address: 746B8654


    Crash occurred at: 2018-02-18 01:37:18
    Build version: GW2 TacO 033.1864r
    Exception Type: e06d7363
    Unresolved address: 761608B2
    Unresolved address: 13246FB
    Unresolved address: 131DCCA
    Unresolved address: 12D19F1
    Unresolved address: 12D1F69
    Unresolved address: 1302762
    Unresolved address: 12F162F
    Unresolved address: 12F151B
    Unresolved address: 132146B
    Unresolved address: 746B8654

    ReplyDelete
    Replies
    1. Does this happen with build #32 as well?

      Delete
    2. On build 32 trails works fine

      Delete
    3. Could you please zip up your complete taco folder and send it over?

      Delete
    4. Sure, but can't find where to send it, hehehe

      Delete
    5. boyc [at] scene [dot] hu :)

      Delete
    6. Hotfix is up, thanks for the report :)

      Delete
    7. Thanks for your hard work :)

      Delete
  4. Build 030 remains the latest build I can get working. 030 works like a dream, I have no idea why the later builds won't start. :(

    ReplyDelete
    Replies
    1. This comment has been removed by the author.

      Delete
    2. It seems to be trying to run the wrong folder. I have placed build 033 into its own folder off \TACO.

      First it tries to do this:
      Faulting application name: GW2TacO.exe, version: 0.0.0.0, time stamp: 0x596bc86b
      Faulting module name: GW2TacO.exe, version: 0.0.0.0, time stamp: 0x596bc86b
      Exception code: 0xc0000409
      Fault offset: 0x000a7714
      Faulting process id: 0x3a44
      Faulting application start time: 0x01d3a8918bf18a93
      Faulting application path: C:\GW2 extra stuff\TACO\GW2TacO.exe
      Faulting module path: C:\GW2 extra stuff\TACO\GW2TacO.exe
      Report Id: b8c1a72f-5104-405b-bc5a-bbcca7ba45e1
      Faulting package full name:
      Faulting package-relative application ID:

      Then it does this:
      Faulting application name: GW2TacO.exe, version: 0.0.0.0, time stamp: 0x59346f71
      Faulting module name: GW2TacO.exe, version: 0.0.0.0, time stamp: 0x59346f71
      Exception code: 0xc0000409
      Fault offset: 0x000a6154
      Faulting process id: 0x1358
      Faulting application start time: 0x01d3a892e1b51bc6
      Faulting application path: C:\GW2 extra stuff\TACO 029\GW2TacO.exe
      Faulting module path: C:\GW2 extra stuff\TACO 029\GW2TacO.exe
      Report Id: c8893c17-e521-4f3f-9786-cbd89b43eede
      Faulting package full name:
      Faulting package-relative application ID:

      Build 030 is fine running from the path C:\GW2 extra stuff\TACO 030\GW2TacO.exe

      And build 029 is fine running from the path C:\GW2 extra stuff\TACO 029\GW2TacO.exe

      I tested both 029 and 030 from their subfolders, but the 032 error was occurring before I tested those two builds.

      My first error today was:
      Faulting application name: GW2TacO.exe, version: 0.0.0.0, time stamp: 0x596bc86b
      Faulting module name: GW2TacO.exe, version: 0.0.0.0, time stamp: 0x596bc86b
      Exception code: 0xc0000409
      Fault offset: 0x000a7714
      Faulting process id: 0x2b18
      Faulting application start time: 0x01d3a890dd3e5c73
      Faulting application path: C:\GW2 extra stuff\TACO\GW2TacO.exe
      Faulting module path: C:\GW2 extra stuff\TACO\GW2TacO.exe
      Report Id: b79f7d6a-d770-4756-831b-b501cb1919d7
      Faulting package full name:
      Faulting package-relative application ID:

      which does not relate to the path of the latest version of TACO that I have been running.

      Delete
    3. Are you using some sort of shortcut to run TacO that changes the working directory?
      Also, remove the spaces from the folder names and try like that. If that fixes this, I'll need to look into it.

      Delete
    4. I've been clicking directly on the .exe in the folder. I've also tried right-clicking and Run as administrator, and that doesn't seem to have an effect. I have the 030 .exe pinned to the taskbar and that works fine. When testing the other builds, I have removed the pin.

      Delete
    5. Do you have TacO and _all_ its files _extracted_ to a separate folder? Or are you trying to double click it inside the zip? The latter will do what you're describing.

      Delete
  5. Sorry, the sentence should read "I tested both 029 and 030 from their subfolders, but the 033 error was occurring before I tested those two builds."

    ReplyDelete
  6. Uhm...man :P I wrote you a mail many times ago xD no reply yet....could you reply ? XD

    ReplyDelete
    Replies
    1. Uhm I don’t recall getting any email from you, Anonymous ;)

      Delete
    2. I will write to you again as soon as as possible tomorrow ^_^

      Delete
  7. Hello Boyz, first off ty for the work you put into this overlay. My problem tho is after a got a update for Windows 10. The overlay crash's right when the gw2 game starts. Can you help? Here is the crash report for you.

    Crash occurred at: 2019-06-26 00:43:39
    Build version: GW2 TacO 034.1866r
    Exception Type: c0000005
    Unresolved address: 755A92F7
    Unresolved address: 75582268
    Unresolved address: 7558739C
    Unresolved address: 75587220
    Unresolved address: 75586360
    Unresolved address: 75C1F4F9
    Unresolved address: 77B040ED
    Unresolved address: 75C2A2C9
    e:\!code\workshop\basecode\core2\windowhandler.cpp (261)
    e:\!code\workshop\basecode\whiteboard\application.cpp (417)


    Crash occurred at: 2019-06-26 00:44:05
    Build version: GW2 TacO 034.1866r
    Exception Type: c0000005
    Unresolved address: 755A92F7
    Unresolved address: 75582268
    Unresolved address: 755874EB
    Unresolved address: 75587220
    Unresolved address: 75586360
    Unresolved address: 75C1F4F9
    Unresolved address: 77B040ED
    Unresolved address: 75C6F70D
    Unresolved address: 75C348EB
    Unresolved address: 75C1709D


    Crash occurred at: 2019-06-26 00:44:05
    Build version: GW2 TacO 034.1866r
    Exception Type: c0000005
    Unresolved address: 755A92F7
    Unresolved address: 75582268
    Unresolved address: 7557F8C6
    Unresolved address: 7557C5D9
    Unresolved address: 7557C3EE
    Unresolved address: 75AD2CDA
    Unresolved address: 75C11EC2
    Unresolved address: 75C12301
    Unresolved address: 75C13005
    Unresolved address: 75C12EE5

    ReplyDelete