-
Notifications
You must be signed in to change notification settings - Fork 327
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
Blinking screen in 3D mode #465
Comments
Thanks for reporting this @slavas62. Is it also blinking in 1.26? |
In version 1.26 all ok. |
I tested version 1.26 with the vector example. I can see this blinking when clicking the "add/remove one vector layer" and "add/remove one feature" buttons. |
Well, if anything I find a message. |
Just to add to this, see referenced issue #477 |
FYI, there is a chance this blinking was a Cesium issue which we just fixed in CesiumGS/cesium#5632 It will be part of Cesium 1.36 on August 1st. |
Thank you @mramato, I confirm Cesium master fixes the blinking of the OL-Cesium vectors example. To everyone: next month version of OL-Cesium will be tested against Cesium 1.36. If you need an updated Cesium in the meanwhile you can simply compile it. |
Everything works correctly. Thank you all. -- С уважением,Вячеслав Серебряков 03.08.2017, 15:25, "gberaudo" <[email protected]>:Closed #465 via #481.—You are receiving this because you modified the open/close state.Reply to this email directly, view it on GitHub, or mute the thread.
|
Ok, so this issue has been fixed, however the runtime performance is terrible. Run it in 2d mode and everything renders quick and snappy, switch to 3d and everything drops through the floor ??? |
@HeavenlyHost, the solution was to update Cesium: there is no change in |
In the latest version 1.27 in 3D mode, changing the coordinates of the point vector object (feature.getGeometry().setCoordinates([...]) or layer.getSource().addFeature(feature)) causes the entire screen to blink. How it can be fixed.
In 2D mode all ok.
Thanks in advance.
The text was updated successfully, but these errors were encountered: