[MOD] TurboHUD <-- The very first thread TurboHUD had ever

[Saah]

experimenting with "pickit"...

edit: reconsidered

For enchancement it would be good to separate MAIN_STAT_VITA to something like "str_vita" or other separate primary attribute combined with vita. its for the case, when some slots have higher caps, like shoulder and belt for STR etc.

btw in ROS there will be no affixes with combined attributes and possibly also differences with slots, i described above.

[chumii]

- check logs\exceptions.txt
- do a clean install

redownloaded 2.0, exception.txt spams

   bei SharpDX.Result.CheckError()
   bei SharpDX.Direct2D1.RenderTarget.CreateLayer(Nullable`1 size, Layer layer)
   bei ..
(Single ,  )
   bei ..
( ))
2013.11.28 00:40:42.999	overlay paint error (SharpDX.SharpDXException: HRESULT: [0x8899000C], Module: [SharpDX.Direct2D1], ApiCode: [D2DERR_RECREATE_TARGET/RecreateTarget], Message: Ein Präsentationsfehler ist aufgetreten, der möglicherweise behoben werden kann. Der Aufrufende muss den gesamten Frame neu erstellen und rendern und den Präsentationsvorgang wiederholen.

   bei SharpDX.Result.CheckError()
   bei SharpDX.Direct2D1.RenderTarget.CreateLayer(Nullable`1 size, Layer layer)
   bei ..
(Single ,  )
   bei ..
( ))

the message part is sth like "Apresentation error has occurred, whichmay be corrected.The caller must create the entire frame and re-render andr epeat the presentation process."

[KillerJohn]

you have directx 10.1 or newer?
are you sure there is nothing else in the exception log? usually a single exception in the drawing thread could push the rendertarget into an invalid state and from that point, the entire UI is dead... Please upload your exception.txt and give me a link (pastebin for example).

redownloaded 2.0, exception.txt spams

   bei SharpDX.Result.CheckError()
   bei SharpDX.Direct2D1.RenderTarget.CreateLayer(Nullable`1 size, Layer layer)
   bei ..(Single ,  )
   bei ..( ))
2013.11.28 00:40:42.999	overlay paint error (SharpDX.SharpDXException: HRESULT: [0x8899000C], Module: [SharpDX.Direct2D1], ApiCode: [D2DERR_RECREATE_TARGET/RecreateTarget], Message: Ein Präsentationsfehler ist aufgetreten, der möglicherweise behoben werden kann. Der Aufrufende muss den gesamten Frame neu erstellen und rendern und den Präsentationsvorgang wiederholen.

   bei SharpDX.Result.CheckError()
   bei SharpDX.Direct2D1.RenderTarget.CreateLayer(Nullable`1 size, Layer layer)
   bei ..(Single ,  )
   bei ..( ))

the message part is sth like "Apresentation error has occurred, whichmay be corrected.The caller must create the entire frame and re-render andr epeat the presentation process."

[Saah]

For pick-it enchancement also would be good to make "main_stat" and "str", "dex", "int" when put together with "main_stat_vita" in the same "at_least[X, Y1, Y2, Y3, ...]" group do disallow them to be summed both for the "at_least[X, Y1, Y2, Y3, ...]" the X variable
so in example:

at_least[2, main_stat+150, main_stat_vita+180, allres+60, crit+8]

currently item with 150 primary and 30 vita with 0 all_res and 0 crit would count as a "TRUE", althought its intended to always have
all_res OR crit AND either main_stat+150 OR (excluding) main_stat_vita+180, so primary attribute must disallow main_stat_vita to count and vice-versa (main_stat_vita is an option for attributes to pass, but NOT another at_least-check entry.

as far as i know, "at_least" inside another "at_least" like there:

at_least[2, at_least[1, main_stat+150, main_stat_vita+180], allres+60, crit+8]

will not work

so:
1) either make that syntax support
2) or make "primary" COUNTING to always disable "main_stat_vita" from counting possibility and vice-versa, but separate "main_stat_vita" allows another "main_stat_vita" to count, same with primary also allowed with other pure primary to stack, but NOT pure with gibrid

so
at_least[3, main_stat+150, main_stat+180, str+250] >>> CAN BE TRUE
at_least[2, main_stat_vita+150, main_stat_vita+180] >>> CAN BE TRUE
at_least[2, main_stat+150, main_stat_vita+180] >>> CAN NOT BE TRUE

and yes, this strange enchancement can be used with meaning (at least i would use)

EDIT: after some cosideration, sometime pure with gibrid should stack too... so just a syntax support is an ideal option for rings and amulets

________________________________________________________________________________ _________________________________________________

EDIT: another enchancement (insignifficant) idea added to complement

3) allow to point amount of primary attrubute in value or percentage for main_stat_vita, like in example:
main_stat_vita[+180, 120]

second variable (120) points amount of minimum primary attribute needed to present on item

what do you think?

[KillerJohn]

For pick-it enchancement also would be good to...
what do you think?

nice ideas, but HUD development is stopped. read the first post.

- main_stat_vita[+180, 120] is not necessary. you can write main_stat_vita+180 & main_stat+120 instead
- I can see why at_least[2, main_stat+150, main_stat_vita+180, allres+60, crit+8] is not what you need, but you can divide it into two conditions:
at_least[1, main_stat+150, main_stat_vita+180] & at_least[1, allres+60, crit+8]

[Saah]

- I can see why at_least[2, main_stat+150, main_stat_vita+180, allres+60, crit+8] is not what you need, but you can divide it into two conditions:
at_least[1, main_stat+150, main_stat_vita+180] & at_least[1, allres+60, crit+8]

the difference is, that i dont want to have the attributes, but an option to either have any of them or not have them at all and just crit & crit dmg, that is not something syntaxically possible

example:

amulet = at_least[2, main_stat+300, main_stat_vita+450, crit+8.0, critdmg+80, ias+8]

i want to have or 300 primary, OR some less primary, but summed with vita to be 450, or just have crit & crit dmg, currently you may have 300 main and 150 vita to return "true", which is not intended (ideally), ofc if you dont mind to have attributes forced, then there is no problem... but in this example it is not possible

[Saah]

btw these values where compared to my current barb gear spreedsheet dps gains, so values are quite precise (300 str = 8 CHC = 80 CHD)

[chumii]

you have directx 10.1 or newer?
are you sure there is nothing else in the exception log? usually a single exception in the drawing thread could push the rendertarget into an invalid state and from that point, the entire UI is dead... Please upload your exception.txt and give me a link (pastebin for example).

Direct X 11
This is my exceptions.txt

https://gist.github.com/chumiiger/7699852

[KillerJohn]

Direct X 11
This is my exceptions.txt

https://gist.github.com/chumiiger/7699852

Yeah, somebody else reported the same. It seems sometimes DirectX requires to re-create the rendertarget... (I'm not a big DX expert).
I tried to fix it, but currently can't release a new HUD.

[chumii]

Yeah, somebody else reported the same. It seems sometimes DirectX requires to re-create the rendertarget... (I'm not a big DX expert).
I tried to fix it, but currently can't release a new HUD.

so nothing I can do about it?

[KillerJohn]

so nothing I can do about it?

a possible fix is coming in the next days. try to restart D3 and/or your pc when the problem appears

[Saah]

omg, i just now realised, there is no "ideal" formula for pickit item slots without some weight system, so sad, without a weightening system you have to write each possible combination of affix number rolls and that would take a lot of lines for some items, dozens of lines... i will make simple config allowing very low numbers, better check more pick-it marked items, than miss something potencionally good (especially if you play casually and your dps is below 170k)

hmm.. i got an idea how to write it.. gonna test tomorrow..

gonna try huge at_least block repeating affixes with different rolls and high "least" value (more than 6)

[KillerJohn]

omg, i just now realised, there is no "ideal" formula for pickit item slots without some weight system, so sad, without a weightening system you have to write each possible combination of affix number rolls and that would take a lot of lines for some items, dozens of lines... i will make simple config allowing very low numbers, better check more pick-it marked items, than miss something potencionally good (especially if you play casually and your dps is below 170k)

hmm.. i got an idea how to write it.. gonna test tomorrow..

gonna try huge at_least block repeating affixes with different rolls and high "least" value (more than 6)

you are overreacting a bit you can filter out 90% of crap with the default pickit. if you improve it to match your taste, it will filter out even more...

[Saah]

you are overreacting a bit you can filter out 90% of crap with the default pickit. if you improve it to match your taste, it will filter out even more...

nah, i dont wish to filter crap, i just wish to make more universal filter to not skip some even cheap, but in some way usefull items, selling or using items below 200k budget is ok for me (i dont want to miss some potencial upgrades for my low budget toons) its a different purpose

[KillerJohn]

nah, i dont wish to filter crap, i just wish to make more universal filter to not skip some even cheap, but in some way usefull items, selling or using items below 200k budget is ok for me (i dont want to miss some potencial upgrades for my low budget toons) its a different purpose

yeah, people are different. I don't even sell items below 10M. gl for pickit customization, and please post your pickit if you don't minds (through pastebin)