2019-12-08 14:11 CET

View Issue Details Jump to Notes ]
IDProjectCategoryView StatusLast Update
0002914Spring engineGeneralpublic2017-08-29 14:00
Reporterabma 
Assigned TojK 
PrioritynormalSeveritymajorReproducibilityhave not tried
StatusresolvedResolutionfixed 
Product Version85.0 
Target VersionFixed in Version 
Summary0002914: map rendering looks horrible at Knockout_v2
Descriptionsee attached screenshot,

the details far away looks pretty, near distance is ugly...
TagsNo tags attached.
Checked infolog.txt for Errors
Attached Files

-Relationships
has duplicate 0005732closedabma ROAM fails on very spiky coastal terrain 
+Relationships

-Notes

~0008134

abma (administrator)

Last edited: 2012-01-12 06:21

i don't know but i would expect this costs also performance?!

uhm... at which value of grounddetail does the terrain look best?

with GroundDetail = ~ 90 it looks best, with higher or lower values it becomes ugly.

~0008137

jK (developer)

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, ...).

~0008139

abma (administrator)

can it prefer points in the middle / bottom of the screen, so the "ugly" stuff is at the borders / far away?
+Notes

-Issue History
Date Modified Username Field Change
2012-01-12 05:27 abma New Issue
2012-01-12 05:27 abma File Added: screen00210.png
2012-01-12 05:28 abma Note Added: 0008134
2012-01-12 05:28 abma Severity minor => major
2012-01-12 05:31 abma Note Edited: 0008134
2012-01-12 05:33 abma Note Edited: 0008134
2012-01-12 06:01 abma Product Version => 85.0
2012-01-12 06:01 abma Summary Rendering looks horrible at Knockout_v2 => map rendering looks horrible at Knockout_v2
2012-01-12 06:20 abma Note Edited: 0008134
2012-01-12 06:21 abma Note Edited: 0008134
2012-01-12 14:18 jK Note Added: 0008137
2012-01-12 15:20 abma Note Added: 0008139
2012-12-16 22:49 jK Status new => resolved
2012-12-16 22:49 jK Resolution open => fixed
2012-12-16 22:49 jK Assigned To => jK
2017-08-29 14:00 abma Relationship added has duplicate 0005732
+Issue History