2025-07-22 17:20 CEST
  

View Issue Details [ Jump to Notes ] [ Issue History ] [ Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0004217Spring engineAIpublic2013-12-16 17:182017-04-16 22:56
Reportermsafwan 
Assigned ToKloot 
PrioritynormalSeverityminorReproducibilityalways
StatusclosedResolutionwon't fix 
Product Version95.0.1+git 
Target VersionFixed in Version 
Summary0004217: Unit always squish thru tiny opening that it couldn't fit.
DescriptionI made a TANK movedef that have footprint=10 (big!), and this unit keep thinking it could go thru a hole tinier than he is.

This unit go directly toward the hole (always thinking it can fit thru), and when it approach it: it start vibrating, squishing thru, and then stuck at the middle.
Steps To ReproduceI don't think I'm allowed to make critical change to critical ZK file to show this case, so I made a video here that show a tank with footprint=10:

http://www.youtube.com/watch?v=j5j4LMlpK-Y
Additional InformationI suspect this is why unit keep being stuck near cliff in previous Spring version because it goes to area which it doesn't fit.
Tagspathfinding, pathing, stuck, unstuck mechanism go extreme
Checked infolog.txt for Errors
Attached Files

-Relationships
duplicate of 0005520closedKloot 103.0.1-747 Simple unit stuck on terrain example 
related to 0003614closedKloot Units get stuck in specific parts 
+Relationships

-Notes

~0012409

Kloot (developer)

2013-12-16 17:32

 for the billionth time:

the pathfinder does NOT care about footprint size in its terrain traversability checks

it is collision detection that HAS to keep units away from intraversable squares but conflicts with the pathfinder while doing so

if units are given extreme-sized footprints they WILL get stuck, period

~0012410

msafwan (reporter)

2013-12-16 17:40

 Okay.

Do you mean we can do something to fix this or all unit will always squish thru tiny hole? what can we do?

~0012411

Kloot (developer)

2013-12-16 18:13

 all units will always squeeze into even the tiniest hole because pathfinder tells them to go through there.

game devs can do nothing, there are only two possible engine solutions:

1) make pathfinder care about unit footprint size --> already tried and tested, FAR too demanding on cpu
2) remove terrain collision handling again --> much worse for general gameplay than this bug is

conclusion: wontfix

~0012414

msafwan (reporter)

2013-12-17 04:20

Last edited: 2013-12-17 06:23

View 9 revisions

 Thank you Kloot, for the explanation.

I have an idea!:
3) Fake slope size near cliff (or buildings) to fool terrain traversability check to not go there!

Like this: http://i515.photobucket.com/albums/t355/xponen/unpassabilityfakesize.png

I am surprise it already work for static building like factory.

EDIT: okay, seem NOT work. I tried building LLT on the wall to fool the pathmap (F2 map), it ignore the red area. :(

~0012440

Kloot (developer)

2013-12-19 23:05

 there will be a MoveDef key to turn terrain collision handling off in 96
+Notes

-Issue History
Date Modified Username Field Change
2013-12-16 17:18 msafwan New Issue
2013-12-16 17:18 msafwan Tag Attached: pathing
2013-12-16 17:19 msafwan Tag Attached: pathfinding
2013-12-16 17:19 msafwan Tag Attached: stuck
2013-12-16 17:21 msafwan Tag Attached: unstuck mechanism go extreme
2013-12-16 17:32 Kloot Note Added: 0012409
2013-12-16 17:32 Kloot Status new => closed
2013-12-16 17:32 Kloot Resolution open => won't fix
2013-12-16 17:40 msafwan Note Added: 0012410
2013-12-16 17:40 msafwan Status closed => feedback
2013-12-16 17:40 msafwan Resolution won't fix => reopened
2013-12-16 18:13 Kloot Note Added: 0012411
2013-12-16 18:14 Kloot Status feedback => closed
2013-12-16 18:14 Kloot Resolution reopened => won't fix
2013-12-17 04:20 msafwan Note Added: 0012414
2013-12-17 04:20 msafwan Status closed => feedback
2013-12-17 04:20 msafwan Resolution won't fix => reopened
2013-12-17 04:20 msafwan Note Edited: 0012414 View Revisions
2013-12-17 04:29 msafwan Note Edited: 0012414 View Revisions
2013-12-17 04:30 msafwan Note Edited: 0012414 View Revisions
2013-12-17 04:46 msafwan Note Edited: 0012414 View Revisions
2013-12-17 04:49 msafwan Note Edited: 0012414 View Revisions
2013-12-17 04:50 msafwan Note Edited: 0012414 View Revisions
2013-12-17 06:23 msafwan Note Edited: 0012414 View Revisions
2013-12-17 06:23 msafwan Note Edited: 0012414 View Revisions
2013-12-19 23:04 Kloot Relationship added related to 0003614
2013-12-19 23:05 Kloot Note Added: 0012440
2013-12-19 23:05 Kloot Status feedback => closed
2013-12-19 23:05 Kloot Assigned To => Kloot
2013-12-19 23:05 Kloot Resolution reopened => won't fix
2017-04-16 22:56 Kloot Relationship added duplicate of 0005520
+Issue History