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

Blank screen with no nodes #3

Closed
AnandJayaraman opened this issue Aug 17, 2016 · 6 comments
Closed

Blank screen with no nodes #3

AnandJayaraman opened this issue Aug 17, 2016 · 6 comments

Comments

@AnandJayaraman
Copy link

Hi,

I followed the instructions as specified in the Github site. The server was started using

npm run dev

On going to the localhost link, i see a black screen which has the top pane with VIZCERAL, Feedback, Global, Filters, Display.

There are no nodes displayed.

Is there anything to be done to display the nodes from sample json?

Regards
Anand

@rdgreis
Copy link

rdgreis commented Aug 17, 2016

Same here...

@jrsquared
Copy link
Contributor

@AnandJayaraman @rdgreis
What browser and version are you running?
Are there any errors in the console?

@rdgreis
Copy link

rdgreis commented Aug 18, 2016

@jrsquared
Google Chrome: Version 51.0.2704.103 m (64-bit)
vizceral

@AnandJayaraman it works on firefox. :)

@jrsquared
Copy link
Contributor

@rdgreis @AnandJayaraman

Ah, yeah, that's not vizceral specific. The Error creating WebGL context. means that Chrome is having trouble with WebGL in general. Vizceral requires WebGL. If you believe your system can handle/support WebGL, then you can check mrdoob/three.js#4927 for a few different approaches that have been successful for different people.

If you cannot load https://get.webgl.org/, three.js will not work, and transitively Vizceral will not work. This is then a bug that you should report to Chrome.

A few approaches that have worked:

  • Make sure Use hardware acceleration when available. is checked in your Chrome settings.
  • If it is already checked, try unchecking it, restarting chrome, checking it, and restarting again.
  • Like @rdgreis said, use Firefox ;) Most Vizceral development is done using Chrome, so it's not a general problem with Chrome and Vizceral, but if you are seeing WebGL problems with Chrome, Firefox may not have the same issues.

@jrsquared
Copy link
Contributor

Closing this assuming my previous comment addressed the issue.

@AnandJayaraman
Copy link
Author

Yes, your comment helped but the underlying issue was it wasn't working
because i was using browser in VDI

On Wed, Aug 24, 2016 at 9:02 PM, Justin Reynolds notifications@github.com
wrote:

Closing this assuming my previous comment addressed the issue.


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#3 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAKHOIl8FZK68mHQIDWRZg_PcyoyL2Scks5qjGP5gaJpZM4JmWi_
.

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

No branches or pull requests

3 participants