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.
That worked for me as well.
i just installed it without any tinkering and it worked fine (played around 15min)
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.
I wonder, what graphics card/driver is everyone using? I'm using gtx 1060 6gb with 396.54 drivers
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)
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.
I'm starting to see a bit of a pattern. It may be an issue with an issue with NVidia drivers.
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.
Hmm, worked for me with Proton 3.7-5 Beta without any changes.
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?
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
I couldn't play on multiplayer as well.
yep, i cant go in multyplayer too.
game freezing after click "Connect"
Work on proton 3.7-7 but have little bug and lan work
To work around invisible characters, the registry key CheckFloatConstants
has to be set to true.
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.
Same thing with multiplayer. Clicking "connect" does nothing other then turning the button gray.
Relevant piece of log: https://gist.github.com/diraven/3decbfbef50054f34bfb43b1edd1a320
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?
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.
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.
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.
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
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.
@HonkingGoose here is a log of launching the game and trying to join a multiplayer game. Game did not find any servers. I could not see any mentions about steam2.dll in the logs.
Unable to reproduce the Steam2.dll messages in proton-4.2-4. I have a log that complains that Steam2.dll is missing from proton-4.2-3b, but I suppose this is no longer relevant for this issue since it is gone
steam-475150_proton-4.2-3b.log
steam-475150_proton-4.2-4.log
systemreport.log
.
Apologies for resurrecting such an old thread but has anyone been able to get Titan Quest AE multiplayer to work? I tried it on my laptop, running Linux Mint 19.1, recently and observed the same as @diraven.
@philipjohnbarlow, I played through the GOG DRM-free version and that played fine against the Windows version. Did occasionally crash on the Linux side, but not too often to prevent enjoyment. :P
If you're having connection problems, check out if you're not using multiple network cards on the Windows side. I remember Titan Quest getting confused and sending its connection UDP packets out from the wrong interface, thereby failing to connect.
Here is the fix for multiplayer:
Change launch options for the game to this:
WINEDLLOVERRIDES="ws2_32=n" %command%
Done!
p.s. This dll is for the Proton 4.11-6, but it will probably work with older/newer versions too.
Here is the fix for multiplayer:
Download attached ws2_32.dll.zip archive, extract it
Put ws2_32.dll into the game directory
Change launch options for the game to this:WINEDLLOVERRIDES="ws2_32=n" %command%
Done!
ws2_32.dll.zip
p.s. This dll is for the Proton 4.11-6, but it will probably work with older/newer versions too.
Brilliant, I'll give this a go later.
Here is the fix for multiplayer:
1. Download attached ws2_32.dll.zip archive, extract it 2. Put ws2_32.dll into the game directory 3. Change launch options for the game to this:
WINEDLLOVERRIDES="ws2_32=n" %command%
1. Done!
p.s. This dll is for the Proton 4.11-6, but it will probably work with older/newer versions too.
it is working great, thanks !!!
WINEDLLOVERRIDES="ws2_32=n" PROTON_USE_D9VK=1 %command%
@Kron4ek thanks for posting the multiplayer solutions. Works fine for me.
In addition I recommend to limit the fps to avoid lags (see also: https://www.pcgamingwiki.com/wiki/Titan_Quest_Anniversary_Edition#Large_bursts_of_lag_in_multiplayer)
I'm constantly crashing after killing a few mobs in the Nerthus Sanctuary from the Atlantis DLC. It's the only place in the game where it happens, most of the times after 7-8 mobs killed. I tried to play at normal speed, lowered the graphics settings but to no avail.
Game works fine with proton 5.0-2.
Titan Quest Anniversary Edition crashes immediately without error message.
Issue transferred from https://github.com/ValveSoftware/Proton/issues/3596.
@Logicisart posted on 2020-03-03T16:27:25:
Game crashes immediately after I press "start" without further notice. Has been working fine a few months ago.
Just press "start" and the game attempts to launch, only to crash right back to steam.
Hello @Logicisart, these look like the lines of interest from your log:
info: Required Vulkan extension VK_KHR_surface not supported
terminate called after throwing an instance of 'dxvk::DxvkError'
This tells us the Vulkan render stack didn't initialize properly for some reason.
Please copy your system information from Steam (Steam
-> Help
-> System Information
) and put it in a gist, then include a link to the gist in this issue report.
Hello @kisak-valve , thank you for your suggestion. If I'm not mistaken, this link should provide you with all the content from the system information report:
https://gist.github.com/Logicisart/c62b771f695faf0fbb0b7050c3e23fc6
Thank you for editing. Don't know what went wrong with my link.
If I'm reading the s-r-t-info correctly, you have no vulkan drivers installed, so it gave us vulkaninfo.c:812: failed with VK_ERROR_INCOMPATIBLE_DRIVER
.
Please check that you have mesa-vulkan-drivers
and mesa-vulkan-drivers:i386
installed with something like apt policy mesa-vulkan-drivers mesa-vulkan-drivers:i386
and install them if they're not already.
Thank you for editing. Don't know what went wrong with my link.
If I'm reading the s-r-t-info correctly, you have no vulkan drivers installed, so it gave us
vulkaninfo.c:812: failed with VK_ERROR_INCOMPATIBLE_DRIVER
.Please check that you have
mesa-vulkan-drivers
andmesa-vulkan-drivers:i386
installed with something likeapt policy mesa-vulkan-drivers mesa-vulkan-drivers:i386
and install them if they're not already.
These drivers weren't installed, for whatever reason. Did install them, and after a reboot everything works just fine. Thank you for you help, and have a nice day!
@Abilbel got Atlantis now and was able to play through it without any crashes with proton 5.0-9.
The fix for multiplayer described in https://github.com/ValveSoftware/Proton/issues/567#issuecomment-536495333 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:
5.0-9
it wouldn't freeze but no way to re-gain focus)@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 https://github.com/ValveSoftware/Proton/issues/4289
The multiplayer fix from https://github.com/ValveSoftware/Proton/issues/567#issuecomment-536495333 only seems to be necessary for proton 4.x. Since proton 5.0
at least online-multiplayer worked fine for me without it.
@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.
Most helpful comment
Here is the fix for multiplayer:
Change launch options for the game to this:
WINEDLLOVERRIDES="ws2_32=n" %command%
Done!
ws2_32.dll.zip
p.s. This dll is for the Proton 4.11-6, but it will probably work with older/newer versions too.