Project

General

Profile

News

Titan Quest - Update 2.3

Added by Reinhard Pollice 6 months ago

This is the first major update for TQ since the Atlantis release. We will keep watching feedback and react accordingly.

Changelog

  • General stability fixes
  • Fixed garden colossus animations
  • Added missing leg armor textures
  • Fixed weapon projectiles
  • Removed loot drop from Sarcophagus (First Disciple)
  • Removed grey collision walls rendered visibly
  • Updated some textures and models
  • Fixed collision in Gaulos
  • Tweaked Atlas boat captain area
  • Added POI in Atlas cave
  • Added torches outside cave in Atlas
  • Tartarus music volume adjusted
  • Bugfix: quest counters are now cleared between game sessions
  • Side quest fixes: The lost wanderer, The Letter and Foraging quests had an issue where player characters that had completed the Ragnarök expansion didn't get correct quest log updates. This is now fixed but characters who have already started or completed these quest might have some residual effects of this issue. As of 2019-05-09 all player characters are backed up on the first game launch to \Users#user#\Documents\My Games\Titan Quest Backup. Players who want to reset these quest could revert their characters, note that this will reset all progress since the backup was made though.
  • Satyr side quest proxy now spawns three enemies instead of one.
  • Fixed missing collision in Aetolion Polis
  • Blocked off alley in Gadir
  • Changed lights in Necropolis to nightlights
  • Fixed Floating Tartarus-portal in Gadir
  • Fixed hole in the wall in Passage of soul
  • Fixed so the player can't reach deep water in Coastal Asomata
  • Bugfix: fixed crash due to setting debug information on invalid indexbuffer for meshes

How to report bugs

Added by Reinhard Pollice 6 months ago

To report a new bug click the plus sign to the left of the tabs and select new issue or use this link: https://redmine.thqnordic.com/projects/titan-quest-atlantis-community/issues/new
Fill in the following and leave the rest as default.

Subject: Summary of the bug. This is used when the bug is shown in a list so it should be short.
Description: This is the important section of the bug report. See next section below.
Version: Here you write the version of the game when you reported the bug. The version is found in the lower right of the main menu in Titan Quest.
Bug Classification: The bug classification is used to describe how severe impact the bug has on the gameplay. A is the most severe.
* A: Critical. The game crash or something that stops the progression in the game.
* B: Major. Has a large negative impact on the experience of playing the game.
* C: Minor. Smaller impact but it is noticeable.
* D: Cosmetic. Minor detail, a texture that is wrong or a misplaced object that don't directly affect the gameplay.

How write a good bug description
For a good bug description you need to write down what did happen, what did you expect to happen and steps to reproduce. The first part is often easy and the second part is not always needed as it is often obvious from the first. The hard part is the steps to reproduce the bug. This can sometime require more details then one expect. Do not be surprised if you get some feedback requests on some bugs before you get the level of information right. There are many masteries, skill and items in Titan Quest and not everyone play the game the same way. What you might think is the obvious way to do something might not be the way someone else do it. Follow this checklist early on until you get used to reporting bugs and learn what is needed depending on the bug.

  • What did happen
  • What did you expect to happen
  • Steps to reproduce the bug
  • Where in the world where you. Difficulty level/Act1/Area.
  • Character level and what masteries do you have.
    (1-2/2)

    Also available in: Atom