[HOW TO] HUD is not visible/does not start

[Azalta]

Hmm, in 17.11.4.0 BETA for Diablo III 2.6.1.47710 (v7.4) does not start.
Clean install, windowed screen, 64bit version game. There log (from status.txt):
2017.11.04 07:45:46.413 initializing overlay
2017.11.04 07:45:46.419 create Direct2D1 Factory
2017.11.04 07:45:46.422 create DirectWrite Factory
2017.11.04 07:45:46.424 create DirectInput
2017.11.04 07:45:46.434 create DirectInput Keyboard
2017.11.04 07:45:46.445 create SwapChain
2017.11.04 07:45:46.474 maximum supported feature level: Level_11_0
2017.11.04 07:45:46.492 create RenderTarget
2017.11.04 07:45:46.564 loading configuration
2017.11.04 07:45:46.565 config.xml
2017.11.04 07:45:47.897 terminate TurboHUD because Diablo 3 is not running
2017.11.04 07:45:47.916 exit

In task manager i see, how it is: the process starts, reaches 25% of the CPU and closes. Any idea ?

[k0ve]

Hmm, in 17.11.4.0 BETA for Diablo III 2.6.1.47710 (v7.4) does not start.
Clean install, windowed screen, 64bit version game. There log (from status.txt):
2017.11.04 07:45:46.413 initializing overlay
2017.11.04 07:45:46.419 create Direct2D1 Factory
2017.11.04 07:45:46.422 create DirectWrite Factory
2017.11.04 07:45:46.424 create DirectInput
2017.11.04 07:45:46.434 create DirectInput Keyboard
2017.11.04 07:45:46.445 create SwapChain
2017.11.04 07:45:46.474 maximum supported feature level: Level_11_0
2017.11.04 07:45:46.492 create RenderTarget
2017.11.04 07:45:46.564 loading configuration
2017.11.04 07:45:46.565 config.xml
2017.11.04 07:45:47.897 terminate TurboHUD because Diablo 3 is not running
2017.11.04 07:45:47.916 exit

In task manager i see, how it is: the process starts, reaches 25% of the CPU and closes. Any idea ?

I'm getting this exact same issue. Game is 100% running and updated to same version.

[BaldheadStoner]

Hmm, in 17.11.4.0 BETA for Diablo III 2.6.1.47710 (v7.4) does not start.
Clean install, windowed screen, 64bit version game. There log (from status.txt):
2017.11.04 07:45:46.413 initializing overlay
2017.11.04 07:45:46.419 create Direct2D1 Factory
2017.11.04 07:45:46.422 create DirectWrite Factory
2017.11.04 07:45:46.424 create DirectInput
2017.11.04 07:45:46.434 create DirectInput Keyboard
2017.11.04 07:45:46.445 create SwapChain
2017.11.04 07:45:46.474 maximum supported feature level: Level_11_0
2017.11.04 07:45:46.492 create RenderTarget
2017.11.04 07:45:46.564 loading configuration
2017.11.04 07:45:46.565 config.xml
2017.11.04 07:45:47.897 terminate TurboHUD because Diablo 3 is not running
2017.11.04 07:45:47.916 exit

In task manager i see, how it is: the process starts, reaches 25% of the CPU and closes. Any idea ?

yeah, same here. so i guess it's not on our side :gusta:

[BaldheadStoner]

Problem is only related to 64-bit. The 32-bit version runs fine!

[Lysyn]

In my case 64 bit version (v7.4) also does not work. (7.3 works ok)

[Vern1701]

I don't run the 64-bit version, but it could be a glitch in the config file itself.

[MaFiot]

I confirm, х64 (7.4) no work.
2017.11.04 10:59:45.457 initializing overlay
2017.11.04 10:59:45.468 create Direct2D1 Factory
2017.11.04 10:59:45.477 create DirectWrite Factory
2017.11.04 10:59:45.481 create DirectInput
2017.11.04 10:59:45.492 create DirectInput Keyboard
2017.11.04 10:59:45.505 create SwapChain
2017.11.04 10:59:46.025 maximum supported feature level: Level_11_0
2017.11.04 10:59:46.509 create RenderTarget
2017.11.04 10:59:46.570 loading configuration
2017.11.04 10:59:46.575 config.xml
2017.11.04 10:59:47.813 terminate TurboHUD because Diablo 3 is not running
2017.11.04 10:59:47.828 exit

[AutiwaOfficial]

I have the same problem both with the 64 bits and the 32 bits version (I click or un-click the 32 bits option in Diablo inbetween).

It didn't worked for me with the previous beta version (but only in the 32 bits case). Now it doesn't work for the 2 versions.

The log when I run the 32 bits version (people already posted the one for 64 bits)

2017.11.04 10:23:22.645	initializing overlay
2017.11.04 10:23:22.656		create Direct2D1 Factory
2017.11.04 10:23:22.666		create DirectWrite Factory
2017.11.04 10:23:22.667		create DirectInput
2017.11.04 10:23:22.678		create DirectInput Keyboard
2017.11.04 10:23:22.687		create SwapChain
2017.11.04 10:23:22.732		maximum supported feature level: Level_10_1
2017.11.04 10:23:22.746	create RenderTarget
2017.11.04 10:23:22.799	loading configuration
2017.11.04 10:23:22.800		config.xml
2017.11.04 10:23:24.217	terminate TurboHUD because Diablo 3 is not running
2017.11.04 10:23:24.252	exit

[KillerJohn]

it is ok for.me. can't reproduce the issue. Make a clean install without plugins, because from now you can use only v7.4 plugins.

[AutiwaOfficial]

I did it several times already. I delete the complete folder, unzip the new version, then launch TurboHUD in administrator and it quit right after it. I just did it again to be sure. I deleted everything, then checked that Diablo had the 32 bits option.

I launch Diablo III, then launch Turbo in administrator, and here is the log:

2017.11.04 10:53:25.544	initializing overlay
2017.11.04 10:53:25.555		create Direct2D1 Factory
2017.11.04 10:53:25.560		create DirectWrite Factory
2017.11.04 10:53:25.561		create DirectInput
2017.11.04 10:53:25.573		create DirectInput Keyboard
2017.11.04 10:53:25.584		create SwapChain
2017.11.04 10:53:25.640		maximum supported feature level: Level_10_1
2017.11.04 10:53:25.676	create RenderTarget
2017.11.04 10:53:25.728	loading configuration
2017.11.04 10:53:25.728		config.xml
2017.11.04 10:53:27.075	terminate TurboHUD because Diablo 3 is not running
2017.11.04 10:53:27.087	exit

But the fact that it's working for you is disturbing. I wonder what I might do differently. It worked before and my way of using TH is the same for at least a year (with another account to launch Diablo and everything, the steps advised in this forum)

[MrOne]

If you are sure Diablo3 is in 32bit ... are u also sure u download 32bit TH?
In my case 17.11.4.1 BETA work in 32bit.

[AutiwaOfficial]

If you are sure Diablo3 is in 32bit ... are u also sure u download 32bit TH?
In my case 17.11.4.1 BETA work in 32bit.

You're right. Even though I clicked on the option "Launch Diablo III in 32 bits", right after launching it, I see "v 2.6.1.****** (64 bits)". I don't really know why the "32 bits" option is completely ignored (I know it worked before because I always used the 32 bits version, up until last week.

And the 64 bits version now works so I don't care anymore about understanding "my" issue, since I tried 32b only because 64b wasn't working.

Thanks for your help and trying to reproduce the bug.

[drkenrich]

After lots of tries, several weeks, and waiting with bated breath, I finally go TurboHUD to work with D3. Unfortunately, nothing seems to be what it is.

first, I have an Intel Quad Core i7-4790 with 16GB memory with Windows 8.1. for both Diablo 3 and TurboHUD I've made sure I set ALL .exe files to Run as Admin. I've made sure the D3 game options box 32 bit is clear. I've literally tried everything I can find, read and follow in both Battle.net and TurboHUD forums and outside if it's with Windows 8.1 or anything else I could find. I've reinstalled the game. I've even tried to run ALL 7 POSSIBLE .exe programs in the various directories checking the Task Manager each time. They all say (32 bit).

I began with the previous version a couple of months ago and kept getting wierd problems. Then everything went down and I waited for the new update I downloaded today, Nov. 4, 2017. To be on the safe side I downloaded both 32- and 64-bit versions of both the STABLE and BETA versions Total of 4).

Before I started I checked with the Update logs.
I'm running 64-bit Windows 8.1 with enough memory to handle most everything.
Windows automatically installs Net Framework. I checked and it's Version 4.7.0.
DirectX is version 11.
Everything is run off the MB so there are no issues with video cards, drivers, etc.

The following didn't work at all -
TurboHUD 17.10.23.0 (v7.3) STABLE for Diablo III 2.6.0.46568 (DX11, 32 bit)
TurboHUD 17.10.23.0 (v7.3) STABLE for Diablo III 2.6.0.46568 (DX11, 64 bit)
TurboHUD 17.11.4.1 (v7.4) BETA for Diablo III 2.6.1.47710 (32 bit).

Only TurboHUD 17.11.4.1 (v7.4) BETA for Diablo III 2.6.1.47710 (64 bit) worked.

Funny thing, though. According to the Diablo 3 game options I have NOT clicked on 32-bit so I'm assuming it's running in 64-bit. However, when I check Task Manager each Battle.net entry says (32 bit) behind it. So it seems I'm running the game in 32-bit. However, only the TurboHUD 64-bit versions seems to work. Huh? Also, as per the TurboHUD directions I ran it in Windowed. I tried Windowed (full screen) and it didn't work. When I again had it working in Windowed then switched to Fullscreen it stopped and left the building.

Now that I do have it working there is still a problem. I'm getting seasick. The action on the screen is so jittery and slowed that it's really disorienting. I'm serious, I feel seasick! I think (and hope) it's due to all the extra overlay information from TurboHUD. If that's the case, and the key thing I want is the area map in the upper right corner, how can I set only that and remove to rest to speed it up? Or else does it have something to do with the Windowed setup?

Hopefully this might help others with similar problems and help me get to a smooth running D3 WITH the enhanced area map.

[AlexLuthor]

Hi, when I start HUD (32 or 64), it turns my screen solid black but I can see HUD.

Pressing F4 will make my "regular" in game screen back but will hide the HUD as intended.

So I can play without HUD or I can't play with HUD because my whole screen is black

Any ideas ? (logs don't show any error)

[MrOne]

What OS? I ask because it can be problem with Aero. Aero should be enabled.