Tried on a Mac Air in both Chrome 14 / FF 8 and all you see is a giant blue haze with a white outline of the X-Wing.
WebGL X-Wing
31–40 of 56 posts
Re: WebGL X-Wing
#32Earlier quoted context omitted.
The thing is that chipset can play half life 2 just about alright.
The Source engine is much more mature and much better optimized than what's in WebGL implementations right now. Valve and other game makers have strong incentive to make their games run as well as possible on a wide variety of hardware. The WebGL implementations just haven't had the same kind of investment in time and expertise.
Writing a game engine is quite different to writing a set of bindings (which is basically all WebGL is). There isn't much scope for optimization so I wouldn't hold out hope for WebGL apps running much faster in future browsers.
Re: WebGL X-Wing
#33All these webgl demos cause my late 2008 macbook to grind to an absolute halt in a way that no other program seems to manage. You can almost hear the thing whimpering. Even the stuff like the volume control buttons on the keyboard stopped responding, and they normally take priority over everything else (handled by the kernel perhaps?)
[deleted]
Re: WebGL X-Wing
#34All these webgl demos cause my late 2008 macbook to grind to an absolute halt in a way that no other program seems to manage. You can almost hear the thing whimpering. Even the stuff like the volume control buttons on the keyboard stopped responding, and they normally take priority over everything else (handled by the kernel perhaps?)
Late 2008 MacBook? You have an Intel GMA GPU, expect strange, inconsistent, or simply useless performance in 3D rendering. It's probable the browser makers have paid little attention to performance on such chips.
I use a late 2008 Macbook and it has a Nvidia 9400M.
Re: WebGL X-Wing
#35Earlier quoted context omitted.
The Source engine is much more mature and much better optimized than what's in WebGL implementations right now. Valve and other game makers have strong incentive to make their games run as well as possible on a wide variety of hardware. The WebGL implementations just haven't had the same kind of investment in time and expertise.
Writing a game engine is quite different to writing a set of bindings (which is basically all WebGL is). There isn't much scope for optimization so I wouldn't hold out hope for WebGL apps running much faster in future browsers.
Hm, sorry, I was under the impression the WebGL implementations were being done rather differently than they apparently are. I hadn't thought the calls were getting passed through directly due to security concerns.
Chrome, at least, appears to be a straight binding with extensive validation... That... kinda makes my nervous.
Re: WebGL X-Wing
#36Tried on a Mac Air in both Chrome 14 / FF 8 and all you see is a giant blue haze with a white outline of the X-Wing.
Same situation. Strange...
Re: WebGL X-Wing
#37If the intent is to make me pay attention to WebGL, it just may have succeeded.
If, on the other hand, the intent is to prove that I suck at video games, then it's a resounding success.
Re: WebGL X-Wing
#38Re: WebGL X-Wing
#39Earlier quoted context omitted.
Late 2008 MacBook? You have an Intel GMA GPU, expect strange, inconsistent, or simply useless performance in 3D rendering. It's probable the browser makers have paid little attention to performance on such chips.
I use a late 2008 Macbook and it has a Nvidia 9400M.
Ah, I was only looking at the white model. You're right, there was a unibody model with a 9400M at that time, too.
Re: WebGL X-Wing
#40If the intent is to make me pay attention to WebGL, it just may have succeeded. If, on the other hand, the intent is to prove that I suck at video games, then it's a resounding success.
My 3 year old thought it was cute every time I crashed, so it was also a resounding success at amusing him.