Skip to content
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

3D Tiles - Specify glTF up-axis in tileset.json #5005

Merged
merged 1 commit into from
Mar 8, 2017
Merged

Conversation

lilleyse
Copy link
Contributor

For #3241
For CesiumGS/3d-tiles#175
Merge after #5004

Adds support for a gltfUpAxis property in tileset.json that may be "X", "Y", or "Z", and passes the axis to Model (building upon #4962). By default the gltfUpAxis is "Y" since the glTF spec states that models are y-up.

@pjcozzi
Copy link
Contributor

pjcozzi commented Feb 15, 2017

@pmconne this is for design models.

@pjcozzi
Copy link
Contributor

pjcozzi commented Feb 15, 2017

Looks OK to me, can you open a PR for the spec? I'm not 100% sure this should be a top-level property (per tile seems like overkill especially since external tilesets could be used), but I wonder if it belongs under asset or if we will end up grouping properties like this in another top-level object property.

@lilleyse
Copy link
Contributor Author

asset seems like a good place. I'll update this and the spec.

@pjcozzi
Copy link
Contributor

pjcozzi commented Feb 18, 2017

@lilleyse let me know when this is ready.

@lilleyse
Copy link
Contributor Author

@pjcozzi Could you look at the spec PR first - CesiumGS/3d-tiles#182

If that seems ok I'll update here.

@pjcozzi
Copy link
Contributor

pjcozzi commented Mar 8, 2017

@lilleyse please bump when ready.

@lilleyse
Copy link
Contributor Author

lilleyse commented Mar 8, 2017

This is ready.

@@ -159,6 +159,8 @@ define([
if (picked instanceof Cesium3DTileFeature) {
that._feature = picked;
that._updateStats(true);
} else {
that._feature = undefined;
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I noticed that features weren't being unselected due to changes in #5081, so this is a fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants