服务器双面3D渲染 [英] Server Sided 3D rendering

问题描述

我的问题都与这个非常有趣的文章： <一href="http://www.techcrunch.com/2008/07/09/otoy-developing-server-side-3d-rendering-technology/">http://www.techcrunch.com/2008/07/09/otoy-developing-server-side-3d-rendering-technology/

他们说了什么： 在这篇文章中就声称，这家公司可以做出令人惊叹的服务器片面的3D渲染（所有显示使用Flash，AJAX的Java或Active X的在浏览器中输出它也声称，禁食方法在Safari上运行Ajax的同时，到220fps）。

What they say: In this article it is claimed that this company can do amazing server sided 3D rendering all the while displaying the output in the browser using Flash, Ajax, Java or Active X. It is also claimed that the fasted method is Ajax running on safari (up to 220fps).

我做了什么： 我开始思索一下思路是这样和我之前甚至愚弄与周围呈现给浏览器的三种方法。需要明确的是我从来没有实现的3D渲染，而是使用托管在谷歌已经提供的图像，或随机生成的像素。

What I have done: I have pondered about ideas like this before and I have even fooled around with three methods of rendering to the browser. To be clear I never implemented a 3D render but rather used already available images hosted at google, or randomly generate pixels.

我的前两次尝试都参与hackishly企图拉​​拢使用div标签或画布标记在浏览器中的每个像素。我用PHP来做到这一点使得它在首位放缓，但经过数万循环......千万像素将需要数年的其他语言，无论如何，花了像7秒时PHP。 （随机像素颜色并没有显著增加执行时间。

My first two attempts were involved hackishly trying to draw each pixel in the browser using div tags or the canvas tag. I used php to do so making it slow in the first place but looping through tens of thousands...millions of pixels would take years in any other language anyway, it took like 7 seconds in php. (the random pixel colors did not significantly increase execution time.

我的第三次尝试包括使用多个图像进行大画面，我设置了总共使用了托管在谷歌10缩略图的测试，其中PHP脚本遍历所有10随机显示48总的图像在网页上。每次preSS一个按钮，阿贾克斯将在PHP脚本中调用重新安排的图像。与您的缓存在本地运行的这种清零大约需要两秒钟显示所有图像（缓存0.5秒后）。

My third attempt involved using multiple images to make the big picture, and I set up a test using a total of ten thumbnails hosted on google where the php script loops through all 10 to randomly display 48 total images on the web page. Every time you press a button the Ajax will call on the php script to re-arrange the images. Running this locally with your cache cleared takes about two seconds to display all the images (0.5 seconds after caching).

的跆拳道到底如何做那些巢穴做到这一点？ 因为我第一次亲身体验和滑动常规的逻辑，什么该公司声称已完成总学士学位。为此，他们说的每一件事，然后通过在互联网上的输出必须采取至少0.5秒的帧，甚至更好的编码和更快的语言。我不认为你甚至可以重写单个像素的220倍的互联网在一秒钟。

The WTF how the hell do those lairs do that? Because of my first hand experience and plain conventional logic, what this company claims has to be complete total BS. To do every thing they say and then pass the output over the internet has to take at least 0.5 seconds a frame even with better coding and a faster language. I don't think you could even rewrite a single pixel 220 times over the internet in one second.

因此，也许不是有巢穴，他们怎么办呢？ 我一定要知道之前我胸围毛细管！怎么使用Ajax他们通过数据如此之快的浏览器，甚至没有考虑在服务器端的3D处理。难道它只是一个快速的服务器不断推出的图像（S）？我所想要的是每秒30帧，并期待在茨艾伦抽搐hogign所有的NETZ。

So maybe there not lairs, how did they do it? I must know before I bust a capillary! How did they pass data so fast to the browser using Ajax, not even considering the 3d processing on the server side. Is it just one fast server constantly pushing out an image(s)? All I ever wanted was 30 fps and look at thos jerks hogign all the netz.

推荐答案

诀窍是，他们转换的实时三维渲染图像视频流。所以基本上浏览器客户端仅仅是一个视频播放器，例如来自YouTube的没有太大的不同。

Trick is that they convert real-time 3d rendered images to streaming video. So basically browser client is just a video player, not much different from for example YouTube.

在服务器端，3D应用是propably原生应用程序，利用现代GPU的中 - 最喜欢的电脑游戏。它只是监听来自客户端，而不是像物理键盘的输入设备的输入。但如前所述，延时将会是问题。

On server side, 3d application is propably native application that takes advantage of modern GPU's - like most PC games. It just listens input from client instead of physical input devices like keyboard. But as noted, latency will be problem.

和马力： http://www.techreport.com/discussions.x/16205

这篇关于服务器双面3D渲染的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！