[WingmanReloaded] Auto (Flask, Quit, Mine, Spell) & Loot (Manage, Filter, Click)

[qfrag]

Hi. Plugin works correctly only after starting in administrator mode. How risky is this for my account? After all, as I understand it, plugin does not take information from the game’s memory or something like that, it uses publicly available data, such as colors on the screen and a log file.

[Araitz]

its possible to use only auto skills?

[excel]

Not sure what's going on, was working fine last night. Getting the same error after reinstalling fresh?

wingman.PNG

[ZeroneXYZ]

I confirm the same Error.PNG

[Araitz]

Not sure what's going on, was working fine last night. Getting the same error after reinstalling fresh?

wingman.PNG

the same! for me is not working

[Alangasar]

Not sure what's going on, was working fine last night. Getting the same error after reinstalling fresh?

wingman.PNG

Its ok, just uncheck "Are you running Steam" and set path to your client.txt in Configuration tab. Delete client.txt if its too big (more then 128 mb), game will create a new one.

[Toperz]

Still not working after doining everything you wrote

[GTLBaby]

sad labyrinth runners use this

[excel]

So reinstalled everything from scratch and still the same, the one thing i did notice was that there is an active AHK window open that doesn't close with the label NoActive?

[thebbandit]

Looks like something is wrong with the POE ninja API

To fix this issue, modify this in your Settings.ini. If you do not have a settings.ini file then just paste this into a blank file and save these two lines

[Database]
YesNinjaDatabase=0

I will have more time to find out which API has been changed this afternoon

[Alangasar]

So reinstalled everything from scratch and still the same, the one thing i did notice was that there is an active AHK window open that doesn't close with the label NoActive?

I fix this issue by closing and re-opeining script and disabling POENinja feature.

[thebbandit]

another temporary solution would be to remove the line 47 in wingman that says
, "Fragment"

something has changed with the fragments api at PoE.Ninja and I dont know where the new address is. for now, any "normal" quality fragments will not show up with ninja data

[Araitz]

the program is running but nothing is working

[thebbandit]

Looks like the guys at POE.ninja came out with an update to their API that caused the script to crash. I will need to add an error catch for this issue in the future. But for now, its fixed, just needed to do a traceroute on the Network tab of Chrome's debug panel. The adress has been updated to the new api format they are using, and they adjusted the names of some fields in the JSON.

The other thing I have been tinkering with is reducing the amount of screenshots that are occuring, previously we had several different timers and functions all for the different parts of the script. But this was causing for competition for the single thread that can operate at once. Since we are using so much processing power to capture each screenshot I have been determined to do everything possible with that one screenshot before we move to the next frame grab. I did a pretty good check and the last thing to do is moving the quicksilver function back into the main script. I think I have learned adequate methods of determining the time since you last pressed the left mouse button instead of hanging the script with a keywait. The controller portion of the script will remain seperated to allow for its further development later.

Version .09.02 December/30/2019
--------------------------------------------------------------------------------
More adjustments towards removing extra screenshots
    Delve OHB function is now running at max potential without resampling
    Extrenuos checks were removed from the main flask logic
    same for utility firing, all calls to utility are from main game timer

Attack hotkeys have been refactored, and incuded into the main game timer
    this removes competing timers that were unnecessary

Utilities fired on cooldown have also been moved into the main game timer
    Now uses the same screenshot to check for missing buffs
        this lessens the overall processing load of the script
    This also allows me to tie those utilities to the AutoFlasks hotkey
        You can now stop them from firing by pausing AutoFlasks

Bugfix for PoE.Ninja parser crash
    API address has been updated, as well as the fields for currency data

[kastorsigmund]

I rarely post on forums. Forgive the writing style if I don't adhere to whatever forum post nomenclature is popular.

First allow me say thank you for the ongoing work on the script. It makes POE playable by mere humans. It gives a slightly less likely chance of insta-death in end game boss fights.

IMO The performance issue in v9 is not related to CPU architecture.

I have a an intel I7-7700 and a 1070 GPU and 16GB of ram.

With v8 script, the game ran smoothly on a beautiful 32 inch g-sync 2560x1440 @ 144hz / fps. Only dipping down in fps due to massive mtx graphics hell in party runs of high level maps. Even so, rarely below 60fps.

With v9 of the script, fps wildly thrashes between 144 and 20 immediately upon encountering the first monster mob in the game. Perhaps due to the script using a screenshot method? Even with the advantages of g-sync enabled it makes the game unplayable. Capping the framerates to 60fps seems to make a moderate improvement, but still a serious problem.

This league I built a traditional cyclone / impale / massive overleech slayer. I set all 5 flasks to continuously fire while holding q for cyclone. Therefore the script is constantly working.

Total CPU load never goes above 75% Gpu hovers at 50% - win10, poe, script, combined. So it is not like my CPU is being maxed out. The hardware is not too old or inadequate. I don't game on a toaster.

It seems as if the script is somehow thrashing


So I apologize if I find it hard to accept the response of "your hardware is too old, development moves on, live with an outdated version."

From what I have read in this thread, it seems the script pulls pixels from screenshots? Perhaps 144 fps is overfeeding the script causing it to thrash wildly. Is there a way to limit how many screenshots per second the script pulls? My use case scenario is only for the automated flasks triggered on q. I virtually do not utilize the other functionality of the script. Therefore flask active or not active could be polled maybe twice per second and be perfectly adequate for flasks with cd timers of 4 seconds.

EDIT: Just now updated to v.9.02

It seems whatever changes were made in the last update have fixed the fps performance problem for me. Hope it works as well for others.