Titan Quest Anniversary Edition (475150)

[teldon]

It seems the only thing that needs to be done to get this game working is to set the windows version to xp in winecfg.

[d10sfan]

That worked for me as well.

[FreeSevenSix]

i just installed it without any tinkering and it worked fine (played around 15min)

[fesm0750]

I've Installed it on my system and it ran out of the box. However, the game stutters if I try to rise detail and shadow settings even though the fps counter seems ok (above 30 fps), running on a Intel HD 4000 though.

[liberodark]

#MaxXor is not same for me Titan Quest Anniversary edition not run

[teldon]

I wonder, what graphics card/driver is everyone using? I'm using gtx 1060 6gb with 396.54 drivers

[Mat24]

It works fine in my laptops
laptop 1: Dell Latitide 7480 -> Ubuntu 16.04.3, i7 7600U, HD Graphics 620, 16GB RAM
laptop 2: HP Pavillion G4 -> Ubuntu 18.04, i7 2640m, HD Graphics 3000, 8GB RAM

But, in my gaming desktop, loads the game, plays the intro videos and finally shows a black screen with the game cursor :(

Desktop config
Using proton 3.7-3 (on steam play settings menu)

[HyperEye]

I am running Nvidia 396.54 drivers with a GTX 1070 8GB on Gentoo amd64 (4.17.6). I was getting the black screen when the game got to the menu until I set the windows version to winxp. Now it works fine.

[teldon]

I'm starting to see a bit of a pattern. It may be an issue with an issue with NVidia drivers.

[HyperEye]

A bit more info on this problem. I believe that the windows version fix is incidental. An alternative is to set the video memory size in the registry. When I set it to 2GB or 4GB the game worked regardless of windows version. When I tried setting it to 6GB or 8GB I got the black screen.

[lieff]

Hmm, worked for me with Proton 3.7-5 Beta without any changes.

[mayjs]

On my machine, singleplayer seems to work pretty much without any flaws (played about 30 minutes), but I can't join multiplayer. Can anyone confirm that multiplayer works?

[abienz]

I also had to change my Windows version to XP to get it working past the black screen. Using Nvidia 396.53 on GTX 1070

[fesm0750]

I couldn't play on multiplayer as well.

[kelnmaari]

yep, i cant go in multyplayer too.
game freezing after click "Connect"

[liberodark]

Work on proton 3.7-7 but have little bug and lan work

[Sbte]

To work around invisible characters, the registry key CheckFloatConstants has to be set to true.

[abienz]

I started a new character a few weeks ago and had a relatively bug free play through with intermittent crashes after extended play and some alt-tab issues.

I played all the way through Normal.

Upon starting again in the next difficulty mode Epic I frequently get crashes that I would say the game is unreliable.

Unsure of the cause of the issue or how to report further.

[diraven]

Same thing with multiplayer. Clicking "connect" does nothing other then turning the button gray.

[diraven]

Relevant piece of log: https://gist.github.com/diraven/3decbfbef50054f34bfb43b1edd1a320

[abienz]

Latest updates to Proton and graphics drivers have the game running very well for me even in Epic mode, haven't experienced as many crashes.

On another note I still don't get any text for the place names, or when you press 'Space' to pause for example, you just see the bookend graphics, anyone found a workaround?

[lucifertdark]

Latest updates to Proton and graphics drivers have the game running very well for me even in Epic mode, haven't experienced as many crashes.

On another note I still don't get any text for the place names, or when you press 'Space' to pause for example, you just see the bookend graphics, anyone found a workaround?

Installing Corefonts might fix that.

[abienz]

Latest updates to Proton and graphics drivers have the game running very well for me even in Epic mode, haven't experienced as many crashes.
On another note I still don't get any text for the place names, or when you press 'Space' to pause for example, you just see the bookend graphics, anyone found a workaround?

Installing Corefonts might fix that.

Unfortunately that hasn't made a difference, I checked with the latest Proton beta (3.16-2) also.

[xsgb]

Same thing with multiplayer. Clicking "connect" does nothing other then turning the button gray.

Same here, I did not managed to play in LAN too, other game clients don't see the server and vice/versa. No firewalling enabled on the hosts and on the LAN.

[Steedalion]

To work around invisible characters, the registry key CheckFloatConstants has to be set to true.

This worked for me and the hollow/invisible man problem. According to wine this results in a small performance hit. I think it should be enabled by start for this game.

Also I think this problem occurs with low-end GPUs. I'm using nvs4200m.

More detail here: https://www.gamingonlinux.com/forum/topic/3538/post_id=17811

[moll]

For those interested, WINE v4.2 as Windows 7 or Windows 10 gets passed the black startup screen if you set the video memory, for example, to 2GB through winetricks videomemorysize=2048. Courtesy of someone on https://www.protondb.com/app/475150.

[sonnyp]

The fix for multiplayer described in #567 (comment) broke with Proton 5.13-1 - the game displayed some kind of error when trying to host a multiplayer LAN game.

However it seems that it isn't necessary anymore with Proton 5.13-1 but you'll have to remove the launch option, the .dll file and use "verify integrity of game files" to get rid of it.

EDIT Tested so far with Proton 5.13-1 without tricks:

• Hosting a LAN multiplayer 👍
• Joining Internet multiplayer 👍
• Alt+tab / game looses focus 👎 - game freezes (On Proton 5.0-9 it wouldn't freeze but no way to re-gain focus)

[at46]

@sonnyp any chance you are talking about 5.13-1 instead of 5.3-1? I haven't seen a 5.3-1 version so far only 5.13-1 which appears to be a beta with some regressions #4289
The multiplayer fix from #567 (comment) only seems to be necessary for proton 4.x. Since proton 5.0 at least online-multiplayer worked fine for me without it.

[sonnyp]

@at46

any chance you are talking about 5.13-1

Indeed - I fixed the typos.

The multiplayer fix from #567 (comment) only seems to be necessary for proton 4.x.

Pretty sure the fix was required for LAN on Proton 5.0-9. Could be wrong.

[at46]

Is there anything I can do to be able to see the whole text in the start options window? The window isn't resizable and I haven't found any option to change it's size or the font size. As far as I know the first one (which I normally use) is DX11 and the second one is DX9 but I've no idea what the others (especially the last two) are used for.

[soredake]

Is there anything I can do to be able to see the whole text in the start options window? The window isn't resizable and I haven't found any option to change it's size or the font size. As far as I know the first one (which I normally use) is DX11 and the second one is DX9 but I've no idea what the others (especially the last two) are used for.

https://steamdb.info/app/475150/config/

[at46]

@soredake thanks. I didn't know that steamdb shows the launch options.

[tmespe]

Still crashes on window losing focus as of Proton 6.3.6/Experimental. I was hoping it would be affected by "Improve input handling after focus loss in some games like Project Cars 3, Warhammer: Chaosbane, and Far Cry Primal.", but no go.

[minisori]

I had to use the flag PROTON_FORCE_LARGE_ADDRESS_AWARE=1 to avoid crashes with DX11 version in Proton 6.3-7.
For now seems to work ok even the multiplayer.
Still crashes whit ALT+TAB.

[at46]

I had to use the flag PROTON_FORCE_LARGE_ADDRESS_AWARE=1 to avoid crashes with DX11 version in Proton 6.3-7. For now seems to work ok even the multiplayer.

Isn't PROTON_FORCE_LARGE_ADDRESS_AWARE=1 the default? At least in the readme it is noted that:

Force Wine to enable the LARGE_ADDRESS_AWARE flag for all executables. Enabled by default.

[minisori]

Isn't PROTON_FORCE_LARGE_ADDRESS_AWARE=1 the default? At least in the readme it is noted that:

Force Wine to enable the LARGE_ADDRESS_AWARE flag for all executables. Enabled by default.

Hmm it looks like so.
It doesn't make any sense. I retested and now it doesn't crash with or without it, before it was consistently crashing with DX11 in the first fountain, so i was playing with DX9 until i remembered that some 32b games could have problems with memory and decided to give it a try, not knowing that it was already defaulted.
The only thing that changed between is that i bought the Atlantis DLC.

[Zlopez]

I played only the single player, but it works great (I'm already in second act). Only issue I have is with the freeze happening on ALT+TAB.

[screwylightbulb]

The alt-tab thing seems to be that the game does not refocus.

[Leopard1907]

Issues with this game seems to be purely windowing related at this point.

1-) Toggling Fullscreen breaks the game. To a point that game throws an error that says my gpu is not DX11 supported. Borderless and windowed works fine, borderless is default.

2-) Alt tabbing just breaks this game, after that interacting with game window is not possible and game just stays there like a dead process.

[Leopard1907]

doitsujin/dxvk#2395

Filed an issue about it on upstream DXVK.

With using wine dxgi game can be toggled to fullscreen without issues:

WINEDLLOVERRIDES="dxgi=b" %command%

[Wedge009]

I only just started playing for the first time today. Most things seemed to work just fine without any manual tinkering under Proton 6.3-8. As others have mentioned, losing focus - eg via Alt-Tab window switching - results in the game hanging/freezing. The aforementioned Wine DLL Override didn't work for me.

The other major issue I found is battle sound effects seem to be non-existent. It doesn't appear to be an issue with volume - background music, button clicks, dialogue speech, even the low health warning, I can hear all those. There's just no sound effects in combat, which is rather disconcerting. I confirm I can hear battle sound effects when playing on Windows 7.

[Leopard1907]

@Wedge009 Mentioned winedlloverride is for being able to set game to fullscreen. Not related to alt tabbing.

[Wedge009]

Got it. Sorry for the misunderstanding.

[Leopard1907]

doitsujin/dxvk@b53c305

Fullscreen fix is in master now.

[Wedge009]

Still seems okay with Proton 7.0-1. I forgot to clarify that I resolved my aforementioned volume issue, it wasn't related to Proton just the game's internal mixing.

[subwaystation]

Using either Proton 7.0-1 or 6.3-8, the game will launch to black screen for a second and then crash.
Any ideas how to fix this? Thanks!

[Wedge009]

Is mesa-vulkan-drivers:i386 or distribution-equivalent installed?

[subwaystation]

I am running ArchLinux. https://wiki.archlinux.org/title/Vulkan. Already installed are vulkan-icd-loader, lib32-vulkan-icd-loader, nvidia-utils, and lib32-nvidia-utils. I can run e.g. Dota2 using Vulkan without any problems.

[Wedge009]

I only suggested that because when DXVK became the default over WineD3D with Proton 5.0, nearly everything broke for me with the symptoms you describe. I had 64-bit mesa-vulkan-drivers installed, but not 32-bit. Installing the 32-bit drivers resolved those issues for me. Not sure, but I wonder if DotA2 would run on the 64-bit drivers.

It might not be applicable to you, just offering what I know.

[subwaystation]

Thanks! Maybe it is still related:

ls /usr/share/vulkan/icd.d/
amd_icd32.json  nvidia_icd.json

I don't understand why AMD would pop up here. Reinstalling all packages mentioned above did not change this. So I assume it's fine.

[subwaystation]

I don't know for what reasons, but there was also the AMD 32-bit driver for Vulkan installed. This confused Proton. Uninstalling of the AMD package and Reinstalling all Vulkan and Nvidia packages solved the issue. Thanks for the tips @Wedge009!

[Wedge009]

Glad you got it working! Perhaps AMD packages are installed by default by the distribution since I understand they're usually open-source.

[Cederick]

Works flawlessly on Steam Deck out of the box without any issues. Controller support is working and in-game dialog fields open the keyboard automatically.

I don't know why it still says unsupported and I'd like to request whitelisting and/or retesting of the game.

[Wedge009]

The main problem for me was on a desktop Alt-Tab switching breaks the game when returning to it. But checking just now on vanilla Proton 8.0-3, no command-line options, that problem seems to be resolved now. So I agree, this seems worth white-listing to me.

[Espionage724]

Does anyone notice lines in grass in Act 1 with DX9? It's almost subtle-enough to look intentional with small grass patches, but I played mostly on Windows without the lines.

With Intel UHD 630 I get noticeable lines DX9 with and without DXVK on Wine on Linux, but DX9 was fine on Windows. DX9 give me better performance to meet Vsync.