-
Member
Originally Posted by
HunterHero
Anyone else getting .NET errors?
PoeHUD.Hud.ExternalOverlay.<OnLoad>d__14.MoveNext()
System.Runtime.CompilerServices.AsyncMethodBuilderCore.<>c.<ThrowAsync>b__6_0(Ob ject state)
It worked fine yesterday and I've tried searching through this thread but there doesn't seem to be any concrete solution.
Only ever seems to work when you replace the files, not sure why. Something must be getting corrupted when it happens, maybe the config files?
-
Originally Posted by
xxsevernajaxx
nice, that was quite fast, looking forward to a fix. the suggestion to use lead to gold for anything else but sorcerer boots is a horrible decision by neversink though

(just came to my attention, didn't ever look at that part)
it's fixed now.
Thx to Cosmo777 for helping me out!.
If I did not reply to you, it mean the question you are asking is stupid.
-
Contributor
Originally Posted by
TehCheat
Pretty sure it's getting flagged falsely because it uses a scrambler to change the exe name, which is something a lot of viruses do. If you're still uncomfortable using it, the code is open source (so you and others can see there's nothing malicious) and it's rather easy to compile it in VS2015 thanks to nuget grabbing packages automatically.
I don't think the scrambler is it, I implemented that a LONG time ago and neither my initial version nor I2um1s F# version were flagged, so I think something else is going on.
I think it's much more likely we're being flagged for the keyboard and mouse hook, which I'm guessing are being matched with a rule since they appear in the strings of the executable. Since the virustotal results are inconsistent with Emsisoft flagging us as tinybanker and others flagging us as some cryptolocker variant. I'm guessing it's a combo of RPM, keyboard and mouse hooking and process spawning (with cmd spawning for symlinks).
Then again if recent compiles don't throw virustotal then it's worth investigating.
it's worth mentioning that we don't trigger any yara rule according to malwr.com on the poehud-master branch.
Last edited by HvC; 04-04-2017 at 05:02 PM.
-
Post Thanks / Like - 1 Thanks
TehCheat (1 members gave Thanks to HvC for this useful post)
-
I suggest removing x32 version as that's the only version being flagged. X64 is fine.
Also x32 is old, no one develop it/add new features to it. Do we really have time to support/remove flags for x32?
If we can't do that my second suggestion is remove exe from x32 version.
Let those who still use x32 compile exe by them self.
If I did not reply to you, it mean the question you are asking is stupid.
-
Post Thanks / Like - 1 Thanks
tsm-evo (1 members gave Thanks to GameHelper for this useful post)
-
Contributor
I don't think we should be distributing exe's in the first place, or at least not bundled in the github, we really should get a build system going one of these days.
-
Post Thanks / Like - 2 Thanks
-
Member
And what to do to those who can not afford x64?
-
Member
Originally Posted by
Semen6
And what to do to those who can not afford x64?
Cmon, anyone can get 20-30 dollars~ for a legit win10 key lol. If u have certain sites u get it for free, if u know what I mean.
-
Member
Is not problem 20-30 dollars,problem is much higher,and i will tell you what is the problem in next topic
Last edited by misterhacker; 04-05-2017 at 12:54 AM.
-
Member
Honestly,i hope Badplayer will make same day Autoscript flask for 64bit.
-
Member
Originally Posted by
hurrhurr1
Cmon, anyone can get 20-30 dollars~ for a legit win10 key lol. If u have certain sites u get it for free, if u know what I mean.
Guys,guys,the problems why people still want to using 32bit version PoEHUD is because,there is no version for PoE Autoflask & AutoScript from author Badplayer for x64bit!!!
That was the problem.
For 64bit there is no simple Autoflask,we have only autoflask for 64bit plugins in PoEHUD,and that was the problem,because a lot of people still dont know how to use,how to make properly,that plugins is so confusing,is not simple like Autoflask and Autoscript from author Badplayer.
Trust me,one day,if Badplayer make Autoflask-Autoscript for 64bit,then you will see,95% players will use PoEHUD 64bit...
Thats it.
-
Originally Posted by
misterhacker
Guys,guys,the problems why people still want to using 32bit version PoEHUD is because,there is no version for PoE Autoflask & AutoScript from author Badplayer for x64bit!!!
That was the problem.
For 64bit there is no simple Autoflask,we have only autoflask for 64bit plugins in PoEHUD,and that was the problem,because a lot of people still dont know how to use,how to make properly,that plugins is so confusing,is not simple like Autoflask and Autoscript from author Badplayer.
Trust me,one day,if Badplayer make Autoflask-Autoscript for 64bit,then you will see,95% players will use PoEHUD 64bit...
Thats it.
Makes no sense how its harder, it has settings just like badplayers version..
-
Good news guys, PoeHud Stash Manager coming soon,
This will allow plugin makers to easily get stashes names, locations, items, total stashes and every detail they want. 
stash.jpg
If I did not reply to you, it mean the question you are asking is stupid.
-
Post Thanks / Like - 2 Thanks
toadskin,
dodger (2 members gave Thanks to GameHelper for this useful post)
-
Member
Originally Posted by
hurrhurr1
Cmon, anyone can get 20-30 dollars~ for a legit win10 key lol. If u have certain sites u get it for free, if u know what I mean.
The problem is just in the hardware. For some, it's just not rational to put x64 for one game.
-
Contributor
Originally Posted by
Semen6
The problem is just in the hardware. For some, it's just not rational to put x64 for one game.
There are a lot of games that come out these days that don't support x32 to begin with.
32bit architecture is a dying platform.
-
Member
Originally Posted by
HvC
There are a lot of games that come out these days that don't support x32 to begin with.
32bit architecture is a dying platform.
I know. But this does not mean that we must now exclude an audience that can not afford to upgrade their PC or does not do it because they do not need it.