[Tool] DPYes - Player/pet DPS meter & Misc util

Grim Dawn Utilities and Resources
488

hi again!
the latest version (17e) made dpyes work indeed but broke Evade button :frowning_with_open_mouth: char just jumps in one place instead of moving forward.

2 Likes
489

Yeah, same here.

490

DPYes 17f should fix this.
When the current input mode isn’t keyboard+mouse, DPYes will not interfere with Evade – regardless of the current “Evade to cursor” setting.

1 Like
492

Is it possible to add a feature where in Teleport_list one can choose the color of the entry ?

493

I’m playing on 17f and cannot evade.

494

200A5C~1
200A5C~11920×1080 244 KB

had the same problem, you should tick the “Evade to cursor” and Evade will work again.

3 Likes
495

Thank you!

496

Automatic launch is not working for me. I put the winmm.dll in the x64. The “Standard Install” with running DPYes.exe works though. I am running the latest steam version.

497

Warning: Thread hijack :sweat_smile:

Any chance you could give me a crash course in what I need to know to debug his issue?
I don’t even know what to google, need keywords, a direction… something.

There are numerous reports of users with this issue, yet I’ve never managed to reproduce it myself.

I made IA using IDA Pro, analyzing and hooking. Don’t have any experience debugging third party applications written in C(++). Java/.Net dev here, so not my strong side.

Any help is appreciated.

EDIT: If it was not clear, I’m replying to the windbg post from a month or two ago. Since it seems like you got things under control.

498

I don’t know if this is the cause or even something you’re already doing, but DPYes ran into some crashing issues on character load if it tried to inadvertently check transmutes(illusions) too early. Coincidentally, this is the crash I had open in my prior WinDbg screenshot.
The fix in that case was to wait until GAME::GameEngine::IsGameEngineOnline(pGameEngine)

To start, you’ll need a (mini)crashdump from when the issue occurred, the crashdumps produced by Grim Dawn’s own Crash Reporter should be OK.
You’ll want to be using the exact same version of the Game as the dump is from (build number and Steam/GOG).
Once you have the dump file, you can load it into WinDbg from GD’s x64 dir. This should help WinDbg find GD’s dlls.

Once its loaded,

  • In the Threads tab (bottom right pane in my earlier screenshot), you should be able to double click on the main thread to switch to it
  • Back in the Stack tab you should see stack frames with some symbols from GD’s dlls

Depending on whether the crash actually occurred in your hook code, GD’s dlls or the packed Steam Grim Dawn.exe will affect how easy it is to see where (logically) the crash occurred.

499

Was this with KB+Mouse?

DPYes 17h should fix this bug :sweat:

Auto launch works for me with GD 1.2.1.5

Can you have DebugView (linked in OP) running and try using auto launch?
Messages prefixed with GDL are from the auto launch and GDD from DPYes.dll.
It should start something like:

[5652] GDL: existCurDir=1, existParDir=0, existx64Dir=0
[5652] GDL: Load 2
[5652] GDD: Hello from DPYes 17f
[5652] GDD: DPYes compiled with MSC 194134123
[5652] GDD: Installed MSVC Runtime Version: v14.42.34433.00
[5652] GDD: Installed MSVC Runtime Build: 34433
500

I can confirm this happens with controller as well. Around the release of v17 is when the “Evade To Mouse Cursor” bug happened, and it’s been persistent since. Without that option enabled, even if WASD mode is otherwise disabled, you “dodge” in place rather than moving. “Evade To Mouse Cursor” has to be enabled to dodge normally.

501

Is this still happening for you with 17h?

502

Ah, apologies, I thought I’d already upgraded, but I was still on 17f!

17h does appear to have fixed it, yes. I’m able to dash around while “Evade To Cursor” option is disabled in WASD movement, whether using mouse control or controller.

Don’t be like me, everyone! Upgrade!

503

I ran DBGview.exe and when I ran Grim Dawn from steam I see neither GDD or GDL. I then ran DPYes.exe and I see a whole bunch of GDD. Using KB + mouse.

504

Is Steam set to launch the 64bit version of Grim Dawn?

xEWOZOne91
xEWOZOne91842×601 48.1 KB

505

Thanks!

This is really something I should have dedicated time to learning years ago.
9 years into IAGD and still just doing trial-and-error, to see what does and does not crash :sweat_smile:

Clicking on the threads tab did not yield me much, but the initial stacktrace from the dump pointed me towards ItemAssistantHook_x64!OnDemandSeedInfo::HookedMethod+0x40

I suspect I had a race condition where I hooked GameEngine::Update() but had not yet set the global variable for this, to access the original method pointer, resulting in a crash.
image
image

506

I’ve found this to be unreliable, a lot of IAGD users have this set but GD still launches as 32bit.
Ended up having to recommend adding /x64 as a launch option.

1 Like