| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 0005144 | Spring engine | General | public | 2016-03-06 23:06 | 2016-03-07 13:53 | ||||||||
| Reporter | jamerlan | ||||||||||||
| Assigned To | |||||||||||||
| Priority | normal | Severity | major | Reproducibility | always | ||||||||
| Status | new | Resolution | open | ||||||||||
| Product Version | 101.0 | ||||||||||||
| Target Version | Fixed in Version | ||||||||||||
| Summary | 0005144: hitsphere of closed unit | ||||||||||||
| Description | Bullets are flying through hitsphere and not hitting this closed viper https://youtu.be/PKYlhL_bQ3o?t=1m8s the same for laser weapons I guess I can set the center of the unit lower.. but still this is not a very good solution/work around | ||||||||||||
| Additional Information | BA 9.35 + spring 101 | ||||||||||||
| Tags | No tags attached. | ||||||||||||
| Checked infolog.txt for Errors | |||||||||||||
| Attached Files |
| ||||||||||||
Notes |
|
|
Kloot (developer) 2016-03-07 00:26 Last edited: 2016-03-07 00:26 |
the engine atm does not like units that use piece collision volumes in one state, but not in another (open vs closed corvipe). |
|
jamerlan (reporter) 2016-03-07 13:34 |
Kloot, what do you mean by "not in another"? Unit is using usepiececollisionvolumes = 1 http://imolarpg.dyndns.org/trac/balatest/browser/trunk/units/corvipe.lua#L34 and we have a configuration for pieces: http://imolarpg.dyndns.org/trac/balatest/browser/trunk/luarules/configs/collisionvolumes.lua#L208 so it's still uses "piececollisionvolumes" in closed state. Just for 1 piece: http://imolarpg.dyndns.org/trac/balatest/browser/trunk/luarules/gadgets/unit_dynamic_collision_volume.lua#L106 |
|
Kloot (developer) 2016-03-07 13:53 |
I know, my explanation was simplified. For corvipe, the custom configuration in the closed state is too different from its "true" closed state and causes an optimization test to always fail. A fix is possible but will take some work. |


