The next version adds some more configuration for the “best average” column:
Proper config options for the DPS meters would require refactoring a bunch of code 
The “Other damage” tracker essentially everything else, that is:
With the additional exception of also not including damage dealt to your pets.
It’s most likely not a useful meter to enable, it’s there by means of legacy and just hasn’t been removed.
Thank you and sorry I wasn’t uhh trying to imply or demand you build or code anything. I worded things badly and was just wondering if I wasn’t using the program properly.
Thank you for answering. I think I need to turn the font size up more and see if I can keep a better on the in the moment dps.
For example:
can use file [affix.txt] or [prefix.txt & suffix.txt] to customize the affix name, and can freely modify the desired prefix and suffix name.
GI is fixed and cannot be modified.
The loot filter as saved to disk uses the localization tag to store which affixes are selected.
This simplifies handling when swapping between mods, as affixes not present in the currently active mod can still be loaded (inertly) without special handling.
Version 13 has been uploaded, which adds a customizable loot filter and an option to hide items on the ground while “In combat”.
Just try out.
At this point, I give up 
This is fixed in 13a, in this case it would have been the rule for looting Epic items that was picking up the Legendary items, classic off-by-one bug on my part 
Just exclude the tool from being necked by any anti-virus programmes you have.
Очень не хватает Русского языка!!!
There seems to be an error. Once you connect to that program, the modeling has changed as shown in the character selection. When you connect to Dom mode, the program stops. Another mode (Grimalion) is connected.
Connect in dom mode when connected normally. Character selection window is normal.
Am I the only one doing this?
Yes, it’s the same for me.
The A-posing on the character list is fixed in 13b, still looking into dom crashing.
This has been fixed in 13c.
There are some affixes in dom that don’t have an associated rarity, which wasn’t handled properly by DPYes.
I have an issue with the latest version of this tool.
It is not when I use it, it is when I exit the game.
It suddenly is (Not Responding) that I need to end it with task manager.
Never had this issue on v12 -below.
Thanks again for this phenomenal tool. 
Any chance for ReShade support friend?
When I installed ReShade Graphical Overhaul at Grim Dawn Nexus - Mods and Community DPYes complained about the Direct3D mode and didn’t load 
Do you use any other external mods (e.g., ReShade)?
Also, can you share the output of DebugView (linked in OP) when you attempt to close Grim Dawn?
This is what it should look like:
[13504] GDD: Begin detach.
[13504] GDD: ImguiCleanup
[13504] GDD: Begin cleanup of 24 functions
[13504] GDD: Unhooking 00007FFE16276798(00007FFDD0780120) 00007FFE161679A0
[13504] GDD: Unhooking 00007FFE162767E8(00007FFDD0780180) 00007FFE16168250
[13504] GDD: Unhooking 00007FFE162767F0(00007FFDD07801E0) 00007FFE16168240
[13504] GDD: Unhooking 00007FFE162761D8(00007FFDD0780240) 00007FFE16163090
[13504] GDD: Unhooking 00007FFE162761E0(00007FFDD07802A0) 00007FFE16163060
[13504] GDD: Unhooking 00007FFE162761E8(00007FFDD0780300) 00007FFE161630C0
[13504] GDD: Unhooking 00007FFE16272C10(00007FFDD0780360) 00007FFE16163180
[13504] GDD: Unhooking 00007FFE162761F8(00007FFDD07803C0) 00007FFE16162F00
[13504] GDD: Unhooking 00007FFE16276200(00007FFDD0780420) 00007FFE16163040
[13504] GDD: Unhooking 00007FFE16276208(00007FFDD0780480) 00007FFE16162FE0
[13504] GDD: Unhooking 00007FFE16276228(00007FFDD07804E0) 00007FFE161639E0
[13504] GDD: Unhooking 00007FFE16276230(00007FFDD0780540) 00007FFE161639C0
[13504] GDD: Unhooking 00007FFE162760A8(00007FFDD07805A0) 00007FFE16161040
[13504] GDD: Unhooking 00007FFE162760B0(00007FFDD0780600) 00007FFE16161110
[13504] GDD: Unhooking 00007FFE162760D0(00007FFDD0780660) 00007FFE16161E00
[13504] GDD: Unhooking 00007FFE162760D8(00007FFDD07806C0) 00007FFE16161E30
[13504] GDD: Unhooking 00007FFE16276788(00007FFDD0780720) 00007FFE161671F0
[13504] GDD: Unhooking 00007FFE162767F8(00007FFDD0780780) 00007FFE16168F00
[13504] GDD: Unhooking 00007FFE16276800(00007FFDD07807E0) 00007FFE16168EE0
[13504] GDD: Unhooking 00007FFE16276808(00007FFDD0780840) 00007FFE16168EB0
[13504] GDD: Unhooking 00007FFE16276068(00007FFDD07808A0) 00007FFE16163890
[13504] GDD: Unhooking 00007FFE16276290(00007FFDD0780900) 00007FFE16164820
[13504] GDD: Unhooking 00007FFE162762A0(00007FFDD0780960) 00007FFE161649D0
[13504] GDD: Unhooking 00007FFE16276080(00007FFDD07809C0) 00007FFE16160E00
[13504] GDD: Detach OK.
[13504] GDD: Detach complete
I installed it again from 0 following the instructions in the Nexus page and still the same error
How do i use the DebugView?
I think it only happens when the game is paused for awhile. Still testing other possibilities. But for now, it’s nothing serious. Thanks for looking into this.
DebugView won’t show any relevant info regarding the renderer Grim Dawn attempts to use. DPYes doesn’t make any attempt to influence which renderer Grim Dawn uses.
Are you using the Steam version of the game?
If you launch the game directly through Steam with Play Grim Dawn (x64) as the chosen launch option and then try again with DPYes, does it still try to use direct3d?
Edit: Just to confirm, regarding Step 7, d3d11.dll is not to be confused with Direct3D11.dll which is part of Grim Dawn. Removing Direct3D11.dll will break the direct3d11 renderer.
Inside the location of your Grim Dawn.exe , look for a file named d3d11.dll and delete it*.*** (This file is replaced with dxgi.dll) If you wish to be able to restore it, simply rename it to d3d11.dll.bak**
