[jamesaustin]

This is a classic problem of trying to be helpful and it's confusing people until they understand the details.

The engine uses HTML5 and WebGL. When the required APIs aren't present it falls back onto a plugin. This is supposed to be helpful for developers because it means the games will work on pretty much all browsers include IE.

But it confuses people because some people think a plugin is required.

So what's better -

1. Not providing the fall back and telling users they need to switch browsers? Good for helping people to understand it doesn't require a plugin, but not great for developers who want everyone to be able to play their game, or

2. Providing the fallback.

Additionally, it's worth noting that the games and engine don't have to provide any plugin support. It is actually the game site application code that is doing the detection and trying to be helpful.

The Turbulenz Engine is an HTML5 / WebGL framework.

[WA]

Yes you're right. Thing is, I used Safari 6 to check it out which has WebGL disabled by default. The site offered a download immediately instead of hinting that I might have to enable WebGL.

The fallback is quite a good idea, but it should've detected that I do have a modern browser which simply might be misconfigured for the game experience.

[jamesaustin]

Yep, you're right. We could definitely do a better job of detection. But at the moment we're looking for the 'feature' rather than the browser.

[ensignavenger]

An alternate approach would be to prompt the user, telling them that using an updated browser with WebGL support (Obviously worded better for the non-technical) would not require a plugin, but give them the option to download a plugin if that is what they want to do.

[jamesaustin]

Yep, you're also right. We should improve the case you describe. Thanks for the feedback.