#UNITY WEB PLAYER FIREFOX FULL#
I am hoping what happens here is Unity really focuses alot of web resources on WebGL and replaces the Unity Player export with that in full force. More fragmentation, more porting and re-implementation, bigger teams, bigger budgets, and less indie development that results in financial success.Ĭlick to expand.Boom goes the dynamite. Titles are likely to become more platform-specific, where only the really successful ones can afford to make themselves available on all platforms.
But now, and for the foreseeable future, it seems like a bit of a dark-age for broad-audience game development. I'm sure that in time these things will work themselves out, one way or another.
#UNITY WEB PLAYER FIREFOX PROFESSIONAL#
That's harder for me right now than it has been in nearly 20 years of professional game development. All I've ever wanted to do was harness as much of my user's hardware as possible to provide the best quality gaming experience to as wide an audience as possible. This whole situation makes me really sad. that's the "security problems" that Google cites when they tell us PPAPI is good for users. Getting high-performance 3D games to run well requires low-level access to the OS and 3D hardware. If Unity attempts to provide a PPAPI implementation, they will encounter a great deal of technical problems just like Adobe is experiencing. As one great post pointed out, that would at-best buy me some time. But that said, I can't justify moving a multi-million dollar web-gaming platform over to Unity in the hopes that it will solve my cross-browser plugin problems, because from my perspective Unity is next in line for the same wrecking-ball that's clobbering Flash games right now. I found this thread because I'm looking for any possible way out of what feels like a room with the walls closing in. Adobe has reduced their technical investment in the Flash Platform, and Google has no compelling reason to support a PPAPI plugin that's trying to use 3D hardware. To solve the problem would require extreme effort from both Adobe and Google, as well as a great deal of collaboration, none of which seems likely to happen. As a result the Flash Player that runs against PPAPI gives incredibly bad performance. PPAPI adds a fat layer of overhead, redirection, and complication. The issue boils down to this: NPAPI is a wide-open protocol that allows the plugin to do pretty much whatever it wants with the OS. Check out this thread for some of the flavor: As a guy who's still doing web games in Flash I can tell you that Adobe and Google are having some serious issues getting this worked out. elbows and zombiegorilla in particular have some really insightful things to say.įrom my perspective this is a significant and potentially game-changing problem. There are some wonderful posts in this thread. The demo was cool, the new stuff is very cool, it will be interesting to see how it evolves. Don't be fooled, a lot of GDC demos are vertical slice/smoke and mirrors, it is about marketing/building hype, when it ships, it is real. Two companies, creative developers and couple of years of work lead to them being able to compile an existing limited demo in a few days. They didn't just decide one day to start and 4 days later had a complete project. And don't forget the Citadel demo had been already been ported to flash two years before. They already stated they they (and mozilla) had been working on it for several months, and it was even a couple of months after they showed it off at GDC before they actually put it up on the web.
I am not saying what they did wasn't cool, but the "4 days" part is largely PR. But the focus was the rendering, and that was impressive. It was at best a vertical slice, no physics, minimal logic.
Click to expand.The "entire engine" wasn't ported for that demo, it was a tech proof of concept using "UE3 tools and technologies".
0 kommentar(er)
