View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0000148 | Medieval Engineers | Bug | public | 2022-03-28 20:14 | 2023-02-04 16:49 |
Reporter | equinox | Assigned To | equinox | ||
Priority | normal | Severity | minor | Reproducibility | N/A |
Status | resolved | Resolution | fixed | ||
Target Version | 0.7.3.968CF8 | Fixed in Version | 0.7.3.968CF8 | ||
Summary | 0000148: Trash removal always runs for exactly 0.1ms | ||||
Description | The trash removal system always runs for exactly 0.1ms even if there is only a single grid in it, because it will just keep repeatedly processing that single grid over and over again until it has spent 0.1ms. This 0.1ms should be definition configurable, and it should never process the same grid twice in a single frame. Practically it would probably be reasonable to limit the per frame grids scanned to 1/100th the total grid count. There's no reason to process grids more than once every few seconds. | ||||
Tags | No tags attached. | ||||
Date Modified | Username | Field | Change |
---|---|---|---|
2022-03-28 20:14 | equinox | New Issue | |
2022-04-07 13:58 | equinox | Target Version | 0.7.4 (unreleased) => 0.7.3.968CF8 |
2022-04-08 16:01 | equinox | Assigned To | => equinox |
2022-04-08 16:01 | equinox | Status | new => assigned |
2022-04-08 16:07 | equinox | Status | assigned => in progress |
2022-04-08 17:34 | equinox | Status | in progress => resolved |
2022-04-08 17:34 | equinox | Resolution | open => fixed |
2023-02-04 16:49 | equinox | Fixed in Version | => 0.7.3.968CF8 |