Frederic Chardon 63bf4bf868 Solve 2 bugs in projectile movement simulation: ... - properly initialize mSimulationPosition in the constructor. Unlucky thread scheduling can cause processHits to be called before the first simulation run, causing the projectile to vanish to whatever value the variable happens to contains. - don't continue moving the projectile after a hit. The position would continue to be updated to some senseless value.		2021-12-29 15:20:44 +01:00
..
benchmarks	Store mesh source data in recast mesh	2021-12-10 23:55:02 +01:00
bsatool	cleans up BSAFile (#3177)	2021-10-14 14:46:44 +02:00
esmtool	Save repeat and duration	2021-11-20 11:03:07 +01:00
essimporter	Automatically drop workaround when the format is next updated	2021-12-24 23:17:50 +01:00
launcher	Fix navmesh cache progress bar jumps	2021-12-16 21:48:50 +01:00
mwiniimporter	Using auto keyword in most apps	2021-05-18 19:20:59 -05:00
navmeshtool	Fix coverity issues	2021-12-27 16:08:00 +00:00
niftest	Do a bounds check before calling functions defined in cctype	2021-11-14 11:26:15 +01:00
opencs	Merge remote-tracking branch 'upstream/master' into detain-hash-selectively-reluctant	2021-12-09 17:09:52 +00:00
openmw	Solve 2 bugs in projectile movement simulation:	2021-12-29 15:20:44 +01:00
openmw_test_suite	Do not write shapes to navmeshdb when writing is disabled	2021-12-16 22:57:35 +01:00
wizard	Remove 'no relevant classes' moc warning	2021-09-14 11:20:18 +02:00
doc.hpp