Different method for retrieving process path. #47
Conversation
Previous method occasionally breaks completely (PUBG, process path returned is null) And will also ocassionally get capitalization wrong, breaking process name matching (could/should make this case insensitive anyways?) (Hitman 2016, should be HITMAN.exe, but returns hitman.exe)
|
Does vibranceGUI work with PUBG in this commit? |
|
What about x64 processes? Remember: vibranceGUI is running as a x86 executable, which might cause conflicts. |
|
Yes, this works with PUBG now (it worked before with manually finding the executable, but this allows the process list to work correctly.) PUBG, and Hitman are x64 processes, so it does work correctly with them. |
|
Good catch, thanks |
|
Oh it looks like there are some incompatibilities though? |
|
Oh, sorry. Maybe this is something that was changed in later versions of Windows? I don't have anything running an earlier version to readily check. |
|
I believe QueryFullProcessImageName should work for retrieving the process name from x86, however it's only available from Vista onwards if that's a concern. Sorry about this. |
|
Can you try if this executable works for you (finding PUBG and other x64 programs?) |
|
Yes, it does work correctly for me. |
Previous method occasionally breaks completely (PUBG, process path returned is null)
And will also ocassionally get capitalization wrong, breaking process name matching (could/should make this case insensitive anyways?) (Hitman 2016, should be HITMAN.exe, but returns hitman.exe)
This is on latest Windows 10, by the way.