Known Bugs: Difference between revisions

From The DarkMod Wiki
Jump to navigationJump to search
(Updated to reflect TDM 1.03 changes)
 
(11 intermediate revisions by 3 users not shown)
Line 1: Line 1:
Even after the release of v1.0 TDM and the subsequent updates, there are plenty of incomplete features and potential bugs.  Chances are, we're aware of most of them already. Here is a list of common bugs or incomplete features that players may encounter:
Even after the release of v1.0 TDM and the subsequent updates, there are plenty of incomplete features and potential bugs.   
<br>Chances are, we're aware of most of them already. (See our [http://bugs.thedarkmod.com/view_all_bug_page.php Bug Tracker] for a '''<u>really big</u>''' list of them.)
<br>Here is a list of common bugs or incomplete features that players may encounter:


== My Screen is Upside Down! ==
== My Screen is Upside Down! ==
Turn off HDR-Lite Post-Processing from the Settings Menu or preferably disable Catalyst AI in your Catalyst Control Panel.
Turn off HDR-Lite Post-Processing from the Settings Menu or preferably disable Catalyst AI in your Catalyst Control Panel.
With Standalone 2.0 having a new executable name and the new GLSL based shader as of TDM 2.07 and as of the latest AMD drivers,
<br>we have had no reports of this issue since TDM 1.07.


== Physics Bug ==
== Physics Bug ==
Line 9: Line 14:


This is probably the biggest irritation with D3 physics.  The issue is potentially fixable but it's not an easy task.
This is probably the biggest irritation with D3 physics.  The issue is potentially fixable but it's not an easy task.
=== 2.07 Rope Bug ===
<s>In 2.07, if you set FPS to uncapped and your FPS goes below 60FPS then ropes may develop extreme physics issues</s>
which could even harm the player.
This is fixed in 2.08 and newer.


== AI Issues ==
== AI Issues ==


AI currently don't react to certain stimulusThey do not notice doors opening, ropes from rope arrows, or moss from moss arrowsThey don't currently see mines.
Sleeping behaviour is still a bit rough around the edgesAI sometimes fall through the floor when getting up off a bed.  ''(should be fixed in 2.0)''


Occasionally, dead or unconscious AI will jitter and bounce around awkwardly. This is caused either by an attached object (like a key) that a mapper has not set to nonsolid, or the AI having been clipped into a surface when they enter ragdoll state.
AI occasionally try to search at a point beyond a solid wall (usually as a result of a thrown object).  This can cause unusual behaviour, like running into the wall or running away to a different part of the map.  When AI run into a wall, they sometimes clip into the floor (which doesn't cause any problems but looks even worse than just running into the wall normally). ''(happens far less frequently as of 1.08)''


Sleeping behaviour is still a bit rough around the edges.  AI sometimes fall through the floor when getting up off a bed.
AI sometimes go through each other or (even worse) stand overlapping each other.  This is a last resort to avoid AI endlessly treadmilling into each other or not being able to get past.


Players can sometimes KO alerted guards from the front (if they don't have a helmet).  This is a bug.  Alerted guards without helmets should only be KO'd from behind.
== Combat ==


AI occasionally try to search at a point beyond a solid wall (usually as a result of a thrown object).  This can cause unusual behaviour, like running into the wall or running away to a different part of the map.  When AI run into a wall, they sometimes clip into the floor (which doesn't cause any problems but looks even worse than just running into the wall normally).
There is a bug with combat that sometimes results in the AI not drawing his weapon properly. This might show up as an AI attacking with an empty hand (but still parrying and doing damage), or the AI might just run into the player continually, unable to attack at all.  ''(fixed in 2.0)''


== Combat ==
== 2.07 end level crash ==
 
If you have shadow maps enabled some missions will crash just as you reach the mission complete display.
<br>As a workaround:
 
* Save just before ending the mission
* Set shadow method to Stencil
 
This is fixed in 2.08


There is a bug with combat that sometimes results in the AI not drawing his weapon properly. This might show up as an AI attacking with an empty hand (but still parrying and doing damage), or the AI might just run into the player continually, unable to attack at all.


AI sometimes do not flee properly, and instead stand there petrified.


[[Category:Gameplay]]
[[Category:Gameplay]]
[[Category:Gameplay concepts and settings]]

Latest revision as of 03:14, 1 March 2022

Even after the release of v1.0 TDM and the subsequent updates, there are plenty of incomplete features and potential bugs.
Chances are, we're aware of most of them already. (See our Bug Tracker for a really big list of them.)
Here is a list of common bugs or incomplete features that players may encounter:

My Screen is Upside Down!

Turn off HDR-Lite Post-Processing from the Settings Menu or preferably disable Catalyst AI in your Catalyst Control Panel.

With Standalone 2.0 having a new executable name and the new GLSL based shader as of TDM 2.07 and as of the latest AMD drivers,
we have had no reports of this issue since TDM 1.07.

Physics Bug

One significant annoyance with D3 physics is that a moving object cannot propagate impulses from one object to another. In other words, while a moving object (like a door) can push a movable object out of the way, if that movable object hits *another* movable object, it will stop. That means that a door can move a crate out of the way, but if that crate hits a spoon, the crate and door will stop moving. It also means that if you put a spoon on top of a movable crate on an elevator, the elevator will not move up (spoon blocks crate which blocks elevator).

This is probably the biggest irritation with D3 physics. The issue is potentially fixable but it's not an easy task.

2.07 Rope Bug

In 2.07, if you set FPS to uncapped and your FPS goes below 60FPS then ropes may develop extreme physics issues which could even harm the player.

This is fixed in 2.08 and newer.

AI Issues

Sleeping behaviour is still a bit rough around the edges. AI sometimes fall through the floor when getting up off a bed. (should be fixed in 2.0)

AI occasionally try to search at a point beyond a solid wall (usually as a result of a thrown object). This can cause unusual behaviour, like running into the wall or running away to a different part of the map. When AI run into a wall, they sometimes clip into the floor (which doesn't cause any problems but looks even worse than just running into the wall normally). (happens far less frequently as of 1.08)

AI sometimes go through each other or (even worse) stand overlapping each other. This is a last resort to avoid AI endlessly treadmilling into each other or not being able to get past.

Combat

There is a bug with combat that sometimes results in the AI not drawing his weapon properly. This might show up as an AI attacking with an empty hand (but still parrying and doing damage), or the AI might just run into the player continually, unable to attack at all. (fixed in 2.0)

2.07 end level crash

If you have shadow maps enabled some missions will crash just as you reach the mission complete display.
As a workaround:

  • Save just before ending the mission
  • Set shadow method to Stencil

This is fixed in 2.08