Correction: For #2, it's called the Chromium continuous build, not the nightly build.

dkogan

01-10-2011, 01:13 PM

Also, for #1, if you see performance problems, it may help to add the flag --enable-accelerated-compositing:

chrome.exe --enable-webgl --enable-accelerated-compositing

fsanchezherrero

01-11-2011, 02:24 PM

Hello.

I am new around here. I tried unsuccesfully the way 1 on an ubuntu 10.04 machine with Google Chrome 9.0.597.45 beta.
There the chrome.exe does not exist, but there is a file called google-chrome, when I launch

./google-chrome --enable-webgl
the browser starts ok but when I try to go to bodybrowser.googlelabs.com it doesn't work and tells me I need a Web browser that supports WebGL.

The link http://www.google.com/landing/chrome/beta/ cannot be reached with either Google Chrome 8.0.552.224 beta or Internet Explorer 8.0.7600.16385.

Firefox is able to reach the page :mrgreen:

SteveBaker

01-12-2011, 08:44 PM

It sounds like the reason you can't get Chrome to support WebGL may be to do with your underlying OpenGL implementation. What graphics card do you have? Can you run other OpenGL applications OK?

awbrody

01-13-2011, 05:43 AM

I would like to try Google body on my intel mac os 10.6
I downloaded Google Chrome beta and navigated to /Applications/Google Chrome/Contents/MacOS

there is no executable file named chrome
the executable is named Google Chrome
If I change the name of the file to Google-Chrome it does not launch Chrome
When I type ./Google Chrome --enable-webgl in the terminal window the space character in Google Chrome terminates the string so
I tried ./."Google Chrome" --enable-webgl
./"Google Chrome --enable-webgl"
and ./Google%20Chrome --enable-webgl
none of these work

szimek

01-14-2011, 09:42 AM

The easiest way to get it working is by installing Chrome from dev channel. Just keep in mind that these are development builds and sometimes they can have some strange bugs. Check this page: https://sites.google.com/a/chromium.org ... ev-channel (https://sites.google.com/a/chromium.org/dev/getting-involved/dev-channel) for install instructions

SteveBaker

01-14-2011, 05:21 PM

I've been seeing lots of problems with both Chrome and Safari on the Mac. Since they are both based on the same "WebKit" display routines, they tend to share the same kinds of bugs.

If you have problems with Chrome, I recommend downloading a copy of Firefox 4 (beta) and trying with that.

WebGL is still a "work in progress" and significant bugs still pop up from time to time.

For example, over the last few days, both Chrome and Safari have been killing off shaders that have any single or double quote characters in their comments(!) - since companies like Google tend to stamp gigantic copyright/legal notices on their shaders, often containing things like:

// This software is provided on an "as is" basis...

...which is exactly the kind of thing that Safari and Chrome were having trouble with. That bug got fixed today...but maybe you don't have the fix yet.

So right now, if something fails in one browser, it's worth trying a different one.

However, these pieces of software are getting stronger and stronger every day - bugs like this are becoming more and more rare.

-- Steve

fsanchezherrero

01-21-2011, 01:32 PM

Thanks for the answers and excuse my delay in answering.

I still haven't been able to have bodybrowser working in linux (ubuntu 10.04 64bit) in my PC (it works ok in my windows XP partition with chromium but it fails in my windows 7 virtual machine in the ubuntu host).

My video card is "RV410 [Radeon X700 (PCIE)]".

I have never tried other webgl applications.

I downloaded the latest chrominium release, but when I try the Body Browser I get this: