-
Notifications
You must be signed in to change notification settings - Fork 3.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issues to investigate at the Winter Bug Bash. Feb 8-10, 2017 #4897
Comments
Patrick- How long would it take to finish and merge Andre Nunes work on GPX and or shapefile support? Less than 3 days?
|
I see "VR Fixes" in your issue description. Will there be VR headset(s) at the bug bash? |
Thanks for the input, @krheinwald! I updated the list. #4084 is especially a good call! |
Thanks for the offer, we'll let you know! |
We would love to see more visual improvements -- we get asked about this a lot! The three label/text tasks are probably our most desired fixes right now. After that, possibly #3279, or anything that can improve the graphics quality without hammering performance. |
We would also love to see those three visual improvement tasks taken care of. Blurry billboards (#4235) are a constant issue for us. Thanks! |
@jburr-nc if imagery quality is a large concern for you, I recommend disabling fxaa and setting maximumScreenSpaceError to 1.33. fxaa is make the image much more crisp (And actually improve GPU performance) and the cost of some jagginess in geometry. Setting maximumScreenSpaceError will make Cesium request more map tiles and terrain, but will better map to what you see at zoom levels in traditional 2D maps. viewer.scene.fxaa = false;
viewer.scene.globe.maximumScreenSpaceError = 4/3; |
We are seeing a reduced level of Terrain detail when zoomed in and a stream of errors like Does this have anything to do with recent updates to the way maximum detail level of Terain can be queried? Could not find an issue regarding this on Github so that's why I'm posting here directly. |
|
@laurensdijkstra perhaps ask on the forum; this could be a temporary network issue. |
@pjcozzi it has to do with model instancing — https://groups.google.com/d/msg/cesium-dev/sUcx0GLI4Qc/SlU96ZkdCQAJ |
Gotcha, thanks! |
@jhalbroo See #4897 (comment) above on tuning Cesium for maximum image quality. Let me know how tweaking those settings work out for you. The I believe improvements to |
@jhalbroo @mramato Anti-aliasing will be improved with WebGL 2, but that is not the issue. The problem is that parts of the scene do not need to be anti-aliased (imagery, labels, ...) and others do (lines, geometry, ...). Right now, FXAA is run on the entire scene. If it is enabled, it will degrade the visual quality of parts of the scene that do not need it. If it is not, it will degrade the parts that do. |
Thanks @mramato! I tried out the work-around and it enhanced the image quality. I compared it to Open Layers showing the same basemap and they look comparable now. I'll have to assess the quality when I add vector layers, but this looks promising. |
@pjcozzi can we close this? |
Congratulations on closing the issue! I found these Cesium forum links in the comments above: https://groups.google.com/forum/#!msg/cesium-dev/sUcx0GLI4Qc/SlU96ZkdCQAJ If this issue affects any of these threads, please post a comment like the following:
I am a bot who helps you make Cesium awesome! Thanks again. |
Please add a comment with your request (with links to their issues) for bug fixes and small features.
Need ideas? Review issues labeled 'priority'.
ModelInstanceCollection
, https://groups.google.com/forum/#!msg/cesium-dev/sUcx0GLI4Qc/SlU96ZkdCQAJ, @lilleyseSee the Winter Bug Bash blog post for more info.
The text was updated successfully, but these errors were encountered: