![]() ![]() On a real PC, you easily reach 200 FPS or more. The correct rendering with Firefox / Win7 is:Īfter this first test, I launched Shader Toy in oder to have some framerate numbers. Obviously, someone, among Tegra 2 or Firefox for Android, does not like raymarching. No enough precision! I guess you have to forget live coding at the train station unless you have the keyboard dock… □ But without arrow keys, it’s really hard to position the mouse cursor on a particular line of code, like changing the values of a vec4. Okay let’s try to modify the pixel shader : Sounds cool, but if you look a closer bit, the rendering is pixelated, and the framerate is very very low (few FPS): Okay, let’s forget that point and let’s see the cool stuff, I mean WebGL. I installed Firefox (I really don’t appreciate all these OSes that require your account (here gmail) just to install an app like firefox or the flash player!). With online WebGL tools like Shader Toy or GLSL Sandbox, you can now code your pixel shaders nearly from everywhere…įirst thing, you must install a browser that supports WebGL because the default one does not support it: The operating system is Android 3.2.1 (kernel 2.6.36.3 #1).Īctually what I wanted to test is the 3D side and especially WebGL. I quickly played with ASUS’s Eee Pad Transformer TF101, the one based on NVIDIA’s Tegra 2 processor (dual core CPU).
0 Comments
Leave a Reply. |