-
Notifications
You must be signed in to change notification settings - Fork 54
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
[CityTiler] Weird vertices #78
Comments
If you export the tileset as OBJ during the creation (with |
No I don't. Do you think it comes from the gltf writer ? |
Since it doesn't come from the CityGML file nor the triangles created from the CityGML, it may come from:
|
I think we can cross the viewer since the visualisation is the same in iTowns and Cesium which don't have the same parser and since it only happens for tilesets created with py3dtilers from what I've tested. |
I can see that those weird lines also appears in the Cesium 3D Tiles inspector example: There is an issue open on Cesium Github about this. |
Yes, I wonder if its linked to the batch. Since we create many batched features in a single glTF mesh, maybe the wireframe debug tool creates a thread between all the vertices of the mesh without using the batchIDs to seperate the features. |
Yes that's a good lead. However, it's weird that it only does it on some tilesets. It may also be combined with the fact that when in wireframe mode it interprets the geometry buffer (representing batched geometries) directly as lines instead of triangles and since all geometries are batched, it draws a line between all points instead of creating triangles. |
The 3D Tiles created with the CityTiler have weird vertices: it seems that all buildings are connected with a vertex, while they are not in the original CityGML:
I reproduced it on different input CityGML and the visualisation is the same in iTowns and Cesium. It happens whether the transformation is ran with or without textures. I reproduce this issue before and and after #71 so it does not seem related to this PR and neither to issue #77. Note that it has no visual impact when not in wireframe mode.
The text was updated successfully, but these errors were encountered: