Skip to content

scatter3d: suppressing connecting lines causes WebGL warning #704

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

Closed
scottwittenburg opened this issue Jun 29, 2016 · 5 comments
Closed
Assignees
Labels
bug something broken

Comments

@scottwittenburg
Copy link

I am using plotly.js version 1.12.0. In my browser console, I do:

container = document.querySelector('.plotly-container')
Plotly.newPlot(container, [{x: [1, 2, 3], y: [3, 2, 1], z: [2, 3, 1], type: 'scatter3d'}])

and everything is fine. If I don't want the lines between the points, I do:

Plotly.newPlot(container, [{x: [1, 2, 3], y: [3, 2, 1], z: [2, 3, 1], type: 'scatter3d', mode:'markers+text'}])

and then, while I no longer see the lines between the points, I get many of this warning:

[.CommandBufferContext.Offscreen-MainThread-0x3969ca4b4a00]RENDER WARNING: Render count or primcount is 0.

I'm using Ubuntu 14.04 and the above warnings only seem to appear in Chrome (for me, Version 51.0.2704.106 (64-bit)). When in Firefox, I do not see the warnings.

Thank you!

@etpinard
Copy link
Contributor

Thanks for report. I can confirm this issue on Chrome 51 and Ubuntu 16.04.

The plot still renders fine to my eyes. @scottwittenburg can you confirm?

@etpinard etpinard added the bug something broken label Jun 29, 2016
@scottwittenburg
Copy link
Author

That is correct. The plot renders fine, and the only issue is the console warnings.

@etpinard
Copy link
Contributor

cc @dfcreative

@etpinard
Copy link
Contributor

Oh actually, I was able to replicate the same warning message with:

Plotly.newPlot(gd, [{
  type: 'scatter3d',
  mode: 'text',
  x: [1,2,3],
  y: [2,1,2],
  z: [2,1,3]
}])

I'm thinking this has to do with setting mode: 'text' when text is empty.

@etpinard
Copy link
Contributor

Fixed in #3171

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

No branches or pull requests

3 participants