-
Notifications
You must be signed in to change notification settings - Fork 64
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
Shader errors on some platforms (was: warning message when using graphjs) #59
Comments
This is working for me with the latest master branch and R version in both command line R and RStudio (details below).
Can you provide details on R.version and threejs version? Thanks. |
Thanks for looking into this. I was running a previous version of threejs. I changed to version 0.3.0 and it now completes but shows no graph in the RStudio window. I'm guessing it is my environment but struggling to debug what is wrong. here are the versions I am running
packageDescription("threejs") |
OK, I can replicate this on Windows, thanks. Working on a fix... |
Ugh. Found the problem. I'm using EcmaScript 6 and in particular the spread operator (https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe erence/Operators/Spread_operator) which apparently is not supported by RStudio yet on all platforms (it seems to work for me on Linux!). (See, for instance, https://github.com/bwlewis/rthreejs/blob/master/inst/htmlwidgets/scatterplotThree.js#L439 and elsewhere in the code). @jjallaire you may find this bug interesting! Working on re-writing this now... |
I see another serious problem rendering on RStudio on Windows--I'm getting GLSL shader errors like:
This might be one of those dumb OpenGL/DirectX problems in Windows. Working on that... |
Wow. Thanks for putting all the effort in on this. I'm looking forward to showing my colleagues (network medicine project) a network visualization using threejs. I'll make sure to mention your efforts |
Also, if you "pop out" the plot into a browser window (with the little "show in new window" button) it should work. The issue is inside the WebGL interface in RStudio. |
pop out did work! Awesome. I was using zoom from RStudio which of course gave the same blank screen. I can make progress with that as a work around for now. |
These shader errors only occur in RStudio as far as I can tell. @jjallaire or @ramnathv if you know someone interested in helping on this, let me know. Things (mostly) work in RStudio on Linux:
but not at all on Windows:
|
I don't offhand. We're hoping to update our version of QtWebKit but we are waiting on Qt 5.9 (or perhaps 5.10). Should be around the end of this year. |
a little more information. pop out works when default browser is chrome. when default browser is microsoft edge same blank page as in RStudio viewer. |
ok, curious--it works for me with edge on win 10.
i am backing through threejs versions tonight to see if that will fix it.
…On May 24, 2017 4:48 PM, "jzicker" ***@***.***> wrote:
a little more information. pop out works when default browser is chrome.
when default browser is microsoft edge same blank page as in RStudio viewer.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#59 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAIsnm4Vwa4pdmZPUACJYT_EORZ9YHybks5r9JeqgaJpZM4Ngh_a>
.
|
I can't fix this--errors are happening with even default threejs shaders. The issues are in the various implementations of WebGL used by the target. For instance the QtWebKit version used by RStudio right now on Windows will not work. Thus, RStudio on Windows won't be supported directly until that is updated. The work around for now is to pop out the plot, or perhaps better, to run RStudio server instead of the desktop application. I will leave this open with a "help wanted" tag in case someone with more WebGL knowledge than me can fix! |
attempting example of graphjs and get this warning
This was for previous version of threejs. I installed 0.3 and now the viewer in RStudio shows nothing. I tried the same in R and got the same results in the browser
The text was updated successfully, but these errors were encountered: