How does the web player, full screen compare to the performance of a stand alone build? If I’m running Indie and would like to test it out on a PC, will the web player utilize most of my PC’s hardware? How does that performance compare to a stand alone build specific for the PC?
Thanks.
In web player windowed mode, the FPS is limited to about 40 (depending on the browser used). When in fullscreen, it’s not limited that way.
That is about the only performance difference, otherwise standalone and web player use (almost) exactly the same engine underneath.
Hi Aras,
Is that speculation or are you definite? What do you mean by almost? I’m curious about which parts of the engine will not work/render.
Thanks!
The rendering engine is the same, except with a standalone the user can switch the resolution and quality settings when it’s launched. You must set the resolution of the webplayer before you build (Edit>Project Settings>Player), and when you switch a webplayer to fullscreen, it scales that rez across the whole screen.
Also, plugins and file I/O on the local machine aren’t supported in the webplayer for security reasons.
Thanks guys.
By “almost the same” I mean the are minor platform differences. E.g. in standalone, we create the rendering window ourselves, while in the browser that’s a sub-window inside the browser. Or the WWW class performs downloads using separate library in standalone; and it goes trough the browser in web player. And so on.
Functionality and performance wise, both standalone and web player are using the same code. (and I omitted “almost” here :))
Just to avoid further questions 
.ORG
Aras does not speculate 
Unless he wants to have speculation, then he usually puts it into the alpha channel
AC :roll: