Open dhdbtkd opened 4 years ago
After finished loading. Set dynamicScreenSpaceErrorDensity is working in Chrome developer tool's console.
I think you may need to turn off foveatedScreenSpaceError
since that interferes. The 3D Tiles inspector should also make this easier to test: viewer.extend(Cesium.viewerCesium3DTilesInspectorMixin);
Although even after turning it off I still can't determine for sure if the dynamic SSE changes are taking effect so I'm leaving this open.
For context you can read a bit about the changes in traversal (the foveated SSE) that kind of supersede dynamic SSE here: https://cesium.com/blog/2019/05/07/faster-3d-tiles/
Hi Omar. Although set foveated SEE to false, dynamic SSE parameter is not applied. I just read your comment's post. You mean foveated SSE is more powerful than dynamic SSE ?? foveated SSE and dynamic SSE are can't be used at the sametime??
Sandcastle example: https://sandcastle.cesium.com/#c=hZLbTgIxEIZfpdkblki6gIcYXYgGNZqYaIToTW9KO0Bjt0Om3TVofHfLLniM2pumM9//z3TaShKrDDwBsQFz8MRG4E1Z8Ps6lrZUfRyhC9I4oFaHvQjH4gpAFEO3hJXRQEdboSKQAR6QrJ40SNoW7rV9LJxwVawWjAUP4Wu5Zts9mzTJdFOkJPtufIXuDjyWpIDPCItTH8Erne51Dw8O2p1GoFdOFkaNYxfgxkup4JwIiR2xQCVESIRfkDNw3oRVJLu82/uLvJAq1Jb9v6hLMPNFuJDW4mxWu/b3P+ZQT5d7BQ74kkxhgqnAc6l1upnPGtxgz4jFBD8nFDqPFrjF+TbM/7nXDmsJ4Vpx/0fQXK/pM+kkuQ8rC8NmvCemWCKF9buknGcBiqWNr+2zaakeo6Xyfi3Ms60o16ZiRg9E8u0jiYQpK72PmVlp7dg8g0iGeRb5LzKLUhs3v6mArFytkUVveN0EOed5Fo8/VQHRTiV9cnwD
Browser: Chrome
Operating System: Win10
I think dynamicScreenSpaceError for 3Dtiles not working. I set dynamicScreenSpaceErrorDensity, Factor but not applied. As you can see console log at I attached sandcastle sample.