PoEHUD Overlay Updated

[Coyl]

May be little help: freeze in this cycle

            while (queue.Count > 0)
            {
                int nextAddr = queue.Dequeue();
                if (hashSet.Contains(nextAddr))
                    continue;

                hashSet.Add(nextAddr);
                if (nextAddr != num && nextAddr != 0)
                {
                    int key = M.ReadInt(nextAddr + 0x14, 0x14);
                    if (!list.ContainsKey(key))
                    {
                        int address = M.ReadInt(nextAddr + 0x14);
                        var entity = GetObject<Entity>(address);
                        list.Add(key, entity);
                    }
                    queue.Enqueue(M.ReadInt(nextAddr));
                    queue.Enqueue(M.ReadInt(nextAddr + 8));
                }
            }

Unfortunely may be infinity cycle because queue.Count never less or equal 0.

The cycle is not infinite, because queue.Deque removes an item from the queue.
This looks like tree traversal, and the freeze appears to happen when the tree gets rebalanced by poe process. And there appears something like race condition.

Do you know any solution to that? My only idea is to spend less time in this cycle - to reduce the risk that tree will be rebalanced while hud reads it.

[enaf3n]

The cycle is not infinite, because queue.Deque removes an item from the queue.

Correct me if I'm wrong, but it appears as many as two objects can be potentially added to the queue after the Dequeue() operation.

So it does appear that the loop could be infinite.

And there appears something like race condition.

Yes, that is the case. Such is one of the pitfalls of external memory reading.

[TehCheat]

My temporary solution is to limit it to 10k entities. Once it hits 10k, it quits the loop. Not ideal, but will prevent endless loops. I'll adjust this if I need to.

So I found the itemonground stuff, so tooltips/mods work with that now. Also fixed child offsets, they were wrong in a couple places. I think this was breaking some of the tooltip hover and it seems to be working now. I did notice it's not always showing up. I debugged it a bit and it seems to be looping through things, calling render in each plugin, etc., but just isn't showing up. Not sure what that's all about.

Source

Zip

Exe

[tenaciouzd]

The version I use doesn't seem to miss anything. If it says a chest is there, I end up seeing the chest. If there is no chest, I won't run into one. I thought the logic and offsets relating to preload stuff was identical between the main fork and the personal version I run, but I need to double check it.

I think whats happening is it detects 1 version of a chest only, I ran solaris when it said there was 3 chests, but there was actually 5 in 1 run through. So if its multiple perandus chest, it actually only reports 1 at top right, when could be more like 3x perandus chest 1x jewelers 1x trove, but just 3 total show at top because theres only 3 diff versions. Its not saying if there is multiple version of the same type chest. I'm 100% positive this is what hes refering to and whats not working. I can 100% say that i have never seen the same type of perandus chest listed twice, only different versions.

[Coyl]

Correct me if I'm wrong, but it appears as many as two objects can be potentially added to the queue after the Dequeue() operation.

So it does appear that the loop could be infinite.

Note that there's a check for the address of current tree node being iterated over: if pointer is zero or is among the ones already visited, the cycle continues without adding 2 objects.

Yes, that is the case. Such is one of the pitfalls of external memory reading.

We should spend less time in that cycle: for instance, call ReadProcessMemory less times (there are 5 calls in this loop, while that number can be reduced to two.)

[Coyl]

And, by the way, there's a great method to read some blocks of poe memory into hud and then deal with them as if they were local objects.

See the patch file:patch.diff.txt (remove the .txt extension and apply to your working copy of git)

This is what I meant by reducing number of api calls in that tree traversing task

[XaocDIO]

The cycle is not infinite, because queue.Deque removes an item from the queue.
This looks like tree traversal, and the freeze appears to happen when the tree gets rebalanced by poe process. And there appears something like race condition.

Do you know any solution to that? My only idea is to spend less time in this cycle - to reduce the risk that tree will be rebalanced while hud reads it.

I made log for infinity cycle and found that often start when key=0.
Sample log file:
Test.rar

[kookiekrak]

btw new update broke offsets i think.

how do you guys usually update them? I'd love to help but i'm not sure where to start

[Hakkotsu]

Just to give a clear statement that preload is not working correctly

[kookiekrak]

found the area change offset for steam:

9C74C8 atleast it fixes my preload alerts. dunno how to do the rest


world item offsets for chests/poi are broken

[Techneeq]

Do we know if this is currently safe to use? The download link in the OP has 404'd but if I just google poehud and go to the first github page the disclaimer is still there. Even with the disclaimer there, is there anything to worry about and are there any reports of bans? Because looking through these last few replies I don't see anything bad.

[Hakkotsu]

Do we know if this is currently safe to use? The download link in the OP has 404'd but if I just google poehud and go to the first github page the disclaimer is still there. Even with the disclaimer there, is there anything to worry about and are there any reports of bans? Because looking through these last few replies I don't see anything bad.

Its not safe. You can use it on your own risk and with high chance of probability eventually will be banned, like the rest of us.
Seriously, there is no detection prevention methods in PoeHuD, so it's just a matter of time when GGG will run /ban_poehud_users

[IronBank]

Its not safe. You can use it on your own risk and with high chance of probability eventually will be banned, like the rest of us.
Seriously, there is no detection prevention methods in PoeHuD, so it's just a matter of time when GGG will run /ban_poehud_users

The question is how do they detect hud users and if you stop using it will you get banned later on.

[elkond]

unless hud does something else than advertised (reading memory and displaying that info in an overlay), the only way to detect it would be to scan active process list, which if you're a citizen of EU means that GGG can't detect hud in any way whatsoever as this would be against the law.

[Silent_Warrior]

eeh... ban or not ban... guys, if you're so beware of banhammerino, just not use any cheat/hack and stay safe. But if you want use it - there always be a couple of risk, so spam about "will i get banned" in every topic page is not good. Sry, i didn't want to harm anyone.