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

Ellipsoid grid lines don't work well on flat ellipsoids #899

Closed
emackey opened this issue Jun 26, 2013 · 9 comments · Fixed by #1067
Closed

Ellipsoid grid lines don't work well on flat ellipsoids #899

emackey opened this issue Jun 26, 2013 · 9 comments · Fixed by #1067

Comments

@emackey
Copy link
Contributor

emackey commented Jun 26, 2013

If one axis of an ellipsoid is too short relative to others, the grid lines fall apart on most cards.

Is there a good solution to this? Should we set a minimum axis ratio, or maybe fall back to non-derivative lines on such ellipsoids?

tooflatellipsoids

@emackey
Copy link
Contributor Author

emackey commented Aug 23, 2013

So pull #1067 offers a substantial improvement, but not a complete fix.

better_flat_ellipsoids

On the bright side, it looks like the new ellipsoidOutlineGeometry will work at any amount of flatness, at the expense of some of the raymarching goodness.

Possibly there could be logic someplace to look at the max/min ratio of ellipsoid radii and make an intelligent guess as to which to use? Would the server have to do this, looking ahead at radii over time, or could the dynamicScene layer figure this out on the fly?

@mramato
Copy link
Contributor

mramato commented Aug 23, 2013

I was under the impression that we would switch completely over to ellipsoidGeometry; since the ray-marched version doesn't support 2D/CV. If there's a good reason to keep both, we can definitely add logic in the Visualizer to determine which one to ultimately use. The visualizers are going to be completely refactored in the next month but we don't necessarily need to wait until then for that.

@emackey
Copy link
Contributor Author

emackey commented Aug 23, 2013

That could be OK.

@emackey emackey reopened this Aug 28, 2013
@emackey
Copy link
Contributor Author

emackey commented Aug 28, 2013

Looks like GitHub auto-closed this issue since we mentioned it a number of times. It's still an issue.

@pjcozzi
Copy link
Contributor

pjcozzi commented Oct 23, 2013

I was under the impression that we would switch completely over to ellipsoidGeometry; since the ray-marched version doesn't support 2D/CV. If there's a good reason to keep both, we can definitely add logic in the Visualizer to determine which one to ultimately use. The visualizers are going to be completely refactored in the next month but we don't necessarily need to wait until then for that.

What's the plan (or already done)? I'm OK with either, but interest in this is increasing.

@mramato
Copy link
Contributor

mramato commented Oct 23, 2013

In the dynamicScene-geometry branch, ellipsoid have been ported over to Geometry and Appearances (along with a bunch of other stuff). There's still a bit of work to be done before I open a PR for it, but it's close. I just need to carve out a couple of days to do it. I'm going to shoot for end of next week.

@pjcozzi
Copy link
Contributor

pjcozzi commented Oct 23, 2013

Excellent!

@pjcozzi
Copy link
Contributor

pjcozzi commented Feb 28, 2014

Can we close this?

@emackey
Copy link
Contributor Author

emackey commented Feb 28, 2014

Yep it's fixed now.

@emackey emackey closed this as completed Feb 28, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants