View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0005163 | Spring engine | General | public | 2016-03-11 12:46 | 2016-03-11 15:50 |
| Reporter | Beherith | Assigned To | Kloot | ||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | 101.0+git | ||||
| Fixed in Version | 101.0+git | ||||
| Summary | 0005163: Features that have been moved by impulse never stop moving | ||||
| Description | If a feature has been moved by impulse (e.g. firing a corlevlr at armap_heap), it will never stop moving, as it will always have a small amount of jitter in it. On a related note, how can one fully disable features receiving any amount of impulse mod-side, so that not even map features get any? | ||||
| Steps To Reproduce | With bar:test, load up a map with nice trees (e.g. FolsomDamDeluxe), and fire a corlevlr at it. Because the position of the tree is used as a random seed for the tree shader, it i will shake wildly. It can also be seen by spawning an armap_heap and firing at it with a leveler (corlevlr), after the feature settles from the large initial impulse, there will still be some residual in-place jitter. | ||||
| Additional Information | Videos can be provided on request. Engine version 101.0.1-118 | ||||
| Tags | No tags attached. | ||||
| Checked infolog.txt for Errors | |||||
|
|
I don't see any jittering, instead the (custom) trees jump up. That part is expected behavior: any non-rezzable feature by default can move (e.g. from impulse) in the y-dimension in 101, while in 100 such features were locked in place after initialization. armap_dead doesn't visually move at all. To kill impulse you have two options: 1) use the FeaturePreDamaged callin (already present http://imolarpg.dyndns.org/trac/balatest/browser/branches/BAR/luarules/gadgets/gfx_tree_feller.lua), second return arg is impulse multiplier 2) Spring.SetFeatureMoveCtrl (see changelog) edit: the jittering was probably fixed by 0883e9e24cd (prevents horizontal speed buildup for non-rezzable features, which never move horizontally), so no change required afaict. feel free to reopen if you still see it with later builds. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2016-03-11 12:46 | Beherith | New Issue | |
| 2016-03-11 13:48 | Kloot | Note Added: 0016045 | |
| 2016-03-11 13:50 | Kloot | Note Edited: 0016045 | |
| 2016-03-11 13:51 | Kloot | Note Edited: 0016045 | |
| 2016-03-11 13:57 | Kloot | Note Edited: 0016045 | |
| 2016-03-11 15:50 | Kloot | Note Edited: 0016045 | |
| 2016-03-11 15:50 | Kloot | Status | new => closed |
| 2016-03-11 15:50 | Kloot | Assigned To | => Kloot |
| 2016-03-11 15:50 | Kloot | Resolution | open => fixed |
| 2016-03-11 15:50 | Kloot | Fixed in Version | => 101.0+git |
