| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||
|---|---|---|---|---|---|---|---|---|---|
| 0005732 | Spring engine | General | public | 2017-08-29 07:01 | 2017-08-29 16:16 | ||||
| Reporter | Google_Frog | ||||||||
| Assigned To | abma | ||||||||
| Priority | low | Severity | minor | Reproducibility | always | ||||
| Status | closed | Resolution | not fixable | ||||||
| Product Version | 103.0 +git | ||||||||
| Target Version | Fixed in Version | ||||||||
| Summary | 0005732: ROAM fails on very spiky coastal terrain | ||||||||
| Description | This map has large regions of very spiky terrain that vary between elevation -50 and 50: http://zero-k.info/Maps/DetailName?name=Knockout_v2 The map really affects my framerate with high ground detail and had large patches of broken terrain rendering. The map is at least playable with low ground detail. This is probably not something to fix during a feature freeze and I don't particularly care if this map works. The map thread indicates that the map worked at some point. | ||||||||
| Tags | No tags attached. | ||||||||
| Checked infolog.txt for Errors | |||||||||
| Attached Files |
| ||||||||
 Relationships |
 Notes |
|
|
Kloot (developer) 2017-08-29 12:39 Last edited: 2017-08-29 12:40 |
"The map thread indicates that the map worked at some point." I want prior verification of this, test the map with older (dating back to 91.0) engine builds first. Either way a recent (post-103) regression can be ruled out. |
|
abma (administrator) 2017-08-29 14:27 |
IMHO the screenshot from 0002914 looks the same: "ROAM limitation. It has a limit pool of tessellation triangles, once it reaches it -> stops further tessellation. Also the current ROAM implementation is not linear := you cannot tessellate a groundsquare just 1 depth level and continue later with the further tessellation levels. And making it so is not trivial. Neither is increasing tessellation pool size a real solution (memory bandwidth limiations, 3GB alloc limit, ...). " |
|
Kloot (developer) 2017-08-29 16:16 |
fwiw performance on this map is quite a bit better with the new terrain mesh drawer (/mapmeshdrawer 1) and a detail bias set between 2 and 4. |
| Notes |
| Issue History |
|||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2017-08-29 07:01 | Google_Frog | New Issue | |
| 2017-08-29 07:01 | Google_Frog | File Added: grounDetail180.jpg | |
| 2017-08-29 07:01 | Google_Frog | File Added: groundDetail50.jpg | |
| 2017-08-29 12:39 | Kloot | Note Added: 0018299 | |
| 2017-08-29 12:40 | Kloot | Note Edited: 0018299 | View Revisions |
| 2017-08-29 12:40 | Kloot | Status | new => feedback |
| 2017-08-29 14:00 | abma | Relationship added | duplicate of 0002914 |
| 2017-08-29 14:27 | abma | Assigned To | => abma |
| 2017-08-29 14:27 | abma | Status | feedback => closed |
| 2017-08-29 14:27 | abma | Resolution | open => not fixable |
| 2017-08-29 14:27 | abma | Note Added: 0018301 | |
| 2017-08-29 16:16 | Kloot | Note Added: 0018303 | |
| Issue History |