Eastfist

Because Google has been trying to phase out dependency on Adobe’s Flash technology in favor of the free, open-source HTML5 standard player, YouTube (owned by Google) has been up to some shady tactics. The transition to HTML5 isn’t seamless as they may think or trying to force. Theoretically, browsers that do support HTML5 should automatically choose the correct format, but users usually find themselves with broken media experience.

This is an example of typical YouTube video url:

https://www.youtube.com/watch?v=VF5jXrZfuCA

Notice the query string for the video itself is:

?v=VF5jXrZfuCA

So this is what you can try to get the Flash player working again:

Append this query string to your YouTube video:

?nohtml5=False

So it would be something like this:

https://www.youtube.com/watch?v=VF5jXrZfuCA?nohtml5=False

It seems the monkeys at YouTube play around with too many query strings and they all do the same thing, or some are just meant to leave you stranded.

There may be YouTube video urls with:

?noFlash = true
?flash = flash

Or whatever query string, that will revert the dependency back to flash. But in most cases it may break the functionality because those monkeys aren’t agreeing on a single query string, but rather multiple implemenations or deliberately creating deadends.

Either way, give this a try and see if it works out for you. It does for me (for now, I guess). Good luck!

UPDATE!! Now it’s ready, amigos.

Z-order rendering is “fixed”, but not optimized, it’s at a satisfactory design point for me. Culling works. Performance is satisfactory, running at 60 frames per second on my quad-core PC, and a very impressive 30 frames per second on my duo-core PC. Hopefully, most people have duo-core and faster PCs these days, but it’s worth noting when I do compile list of system requirements.

So what does this all mean? It means I will more than likely be able to “emulate” at least Super Nintendo quality video games with my game engine and that’s what I originally intended.

It all takes time.

(more…)

You may notice that Google Chrome does not update your website’s favicon when you do because it stores a copy locally on your computer. So deleting your browser cache doesn’t do anything. Instead, you have to go to: C:\Documents and Settings\%USERNAME%\Local Settings\Application Data\Google\Chrome\User Data\Default on your Windows machine, in this case Windows Vista, and delete the Favicons file. Of course, make sure Google Chrome isn’t currently running when you do. If you’re not confident about the change, then you can move the file or rename it. But Google Chrome will automatically generate a new file anyway.

So when you revisit your site, Google Chrome will re-cache your updated favicon. Noice.