sir-wilhelm/SmartHunter

Widgets invisible

Closed this issue · 11 comments

Me and a Friend encounter the Problem that we can't see the Widgets anymore. The only notable Thing we do was an Nvidia-GPU Driver Update (Version 445.75).
Before this the Aplication works fine.

The Widgets show absolut nothing but If I press the "ManipulateWidget-Key" I can see the red Marks as usual but without any Content beside the Widget-Name.

I hope there is something you can do. THX

Here an Owl for your Aid: <O,O>

OS: Windows 10 Pro

LOG - Regular Install:

[2020-03-29 16:03:06] Started 1.5.1.0
[2020-03-29 16:03:06] Config.json loaded
[2020-03-29 16:03:06] Warning: de-DE.json differs from autogenerated version.
[2020-03-29 16:03:06] de-DE.json loaded
[2020-03-29 16:03:06] MonsterData.json loaded
[2020-03-29 16:03:06] PlayerData.json loaded
[2020-03-29 16:03:06] Memory.json saved
[2020-03-29 16:03:06] Default.xaml loaded
[2020-03-29 16:03:07] State Machine: None (54 ms) > DeleteOldFiles
[2020-03-29 16:03:07] State Machine: DeleteOldFiles (62 ms) > CheckingForUpdates
[2020-03-29 16:03:07] Searching for updates...
[2020-03-29 16:03:07] This can be disabled by setting ["AutomaticallyCheckAndDownloadUpdates": true,] in Config.json.
[2020-03-29 16:03:08] No updates found.
[2020-03-29 16:03:08] State Machine: CheckingForUpdates (679 ms) > WaitingForProcess
[2020-03-29 16:03:20] State Machine: WaitingForProcess (12056 ms) > ProcessFound
[2020-03-29 16:03:20] State Machine: ProcessFound (58 ms) > FastPatternScanning
[2020-03-29 16:03:20] State Machine: FastPatternScanning (62 ms) > PatternScanning
[2020-03-29 16:03:20] Win32Exception: Nur ein Teil der ReadProcessMemory- oder WriteProcessMemory-Anforderung wurde abgeschlossen
bei System.Diagnostics.NtProcessManager.GetModuleInfos(Int32 processId, Boolean firstModuleOnly)
bei System.Diagnostics.NtProcessManager.GetFirstModuleInfo(Int32 processId)
bei System.Diagnostics.Process.get_MainModule()
bei SmartHunter.Core.MemoryUpdater.<>c__DisplayClass20_0.b__20()
bei SmartHunter.Core.StateMachine`1.Update()
bei SmartHunter.Core.MemoryUpdater.Update(Object sender, EventArgs e)

LOG - Fresh Install:

[2020-03-29 16:06:50] Started 1.5.1.0
[2020-03-29 16:06:50] Config.json saved
[2020-03-29 16:06:50] en-US.json saved
[2020-03-29 16:06:50] MonsterData.json saved
[2020-03-29 16:06:50] PlayerData.json saved
[2020-03-29 16:06:50] Memory.json saved
[2020-03-29 16:06:50] Default.xaml loaded
[2020-03-29 16:06:50] State Machine: None (68 ms) > DeleteOldFiles
[2020-03-29 16:06:50] State Machine: DeleteOldFiles (60 ms) > CheckingForUpdates
[2020-03-29 16:06:50] Searching for updates...
[2020-03-29 16:06:50] This can be disabled by setting ["AutomaticallyCheckAndDownloadUpdates": true,] in Config.json.
[2020-03-29 16:06:51] No updates found.
[2020-03-29 16:06:51] State Machine: CheckingForUpdates (420 ms) > WaitingForProcess
[2020-03-29 16:06:59] State Machine: WaitingForProcess (8634 ms) > ProcessFound
[2020-03-29 16:06:59] State Machine: ProcessFound (52 ms) > FastPatternScanning
[2020-03-29 16:07:00] State Machine: FastPatternScanning (63 ms) > PatternScanning
[2020-03-29 16:07:00] Win32Exception: Nur ein Teil der ReadProcessMemory- oder WriteProcessMemory-Anforderung wurde abgeschlossen
bei System.Diagnostics.NtProcessManager.GetModuleInfos(Int32 processId, Boolean firstModuleOnly)
bei System.Diagnostics.NtProcessManager.GetFirstModuleInfo(Int32 processId)
bei System.Diagnostics.Process.get_MainModule()
bei SmartHunter.Core.MemoryUpdater.<>c__DisplayClass20_0.b__20()
bei SmartHunter.Core.StateMachine`1.Update()
bei SmartHunter.Core.MemoryUpdater.Update(Object sender, EventArgs e)

[2020-03-29 16:07:00] Win32Exception: Only part of the ReadProcessMemory or WriteProcessMemory request was completed
at System.Diagnostics.NtProcessManager.GetModuleInfos (Int32 processId, Boolean firstModuleOnly)
at System.Diagnostics.NtProcessManager.GetFirstModuleInfo (Int32 processId)
at System.Diagnostics.Process.get_MainModule ()
at SmartHunter.Core.MemoryUpdater. <> c__DisplayClass20_0.b__20 ()
at SmartHunter.Core.StateMachine`1.Update ()
at SmartHunter.Core.MemoryUpdater.Update (Object sender, EventArgs e)

looks like it's failing to read the memory. Could you try running it as admin to see if that helps?

looks like it's failing to read the memory. Could you try running it as admin to see if that helps?

I always run the Application as an Administrator.

I'll try and run DDU and update to 445.75 this afternoon. I do not know why it would start failing for you.


Ich werde versuchen, DDU auszuführen und heute Nachmittag auf 445.75 zu aktualisieren. Ich weiß nicht, warum es für Sie scheitern würde.

I don't think this will fix the problem, but could you reboot your computer and try it again?


Ich glaube nicht, dass dies das Problem beheben wird, aber könnten Sie Ihren Computer neu starten und es erneut versuchen?

I don't think this will fix the problem, but could you reboot your computer and try it again?

I encounter the Problem two days ago... I restart My PC several times since then. Same for my Frind since Yesterday.

Ok I Restart My PC again. Still doesn't work but something changed:

Line 6 bevore:

bei SmartHunter.Core.MemoryUpdater.<>c__DisplayClass20_0.b__20()

and after the restart

bei SmartHunter.Core.MemoryUpdater.<>c__DisplayClass20_0.<CreateStateMachine>b__20()

I'm not sure what issue you are running into, after cleaning my video card drivers and installing the latest mine is still able to scan/match the memory of MonsterHunter.exe.

Ok I use DDU to reinstall my GPU Driver and reinstall the whole Game... nothing works.

Afaik there ist no alternativ for SmartHunter, right?

I think HelloWorld works:
https://www.nexusmods.com/monsterhunterworld/mods/142
It has quite a bit of config, but some people have published minimal configs:
https://www.nexusmods.com/monsterhunterworld/mods/2483

sorry I could not help :/

Ok very strange... It works now, but only if I start Smart Hunter AFTER launching the Game... If I start it before as usual... it shows the error mentioned earlier.

But thanks for all your time and help!

I'm glad you found a workaround.