On Friday, January 24, 2014 5:51:17 PM UTC-8, jj wrote:
>
> You need to have a web server to run the file in Chrome - running from a 
> local directory does not work. Try emrun ( 
> https://github.com/kripken/emscripten/wiki/Running-html-files-with-emrun) or 
> "python -m SimpleHTTPServer" to host an ad hoc web server to run the 
> file in.
>
>
Thanks, the python command works well.

But it turned out that by default, WebGL is disabled on linux/chrome for 
Intel graphics.
With chrome://flags I could override the Render list.

It turns out that even though Chrome's FPS is a bit better in full screen, 
every now and then the browser freezes for a second or so.
I guess that is the reason why they disabled WebGL.


As for the fillrate requirements, it is possible that a browser requires 
> additional fullscreen compositing passes over the native build, which 
> causes the extra overhead. Or some other performance issue. Try making the 
> canvas pixel size the same in fullscreen to the one with windowed mode to 
> see if that has an effect, and then conversely make the canvas full page 
> width in windowed mode without fullscreen. That should rule out if there's 
> anything wrong with the fullscreen mode transition/support itself.
>
 
Good idea.
When running a large windowed instance, the slow down is just as much as 
the full screen option.

  Bram

 

>    Jukka
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"emscripten-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to