plko345 plko345
关注数: 24 粉丝数: 101 发帖数: 4,190 关注贴吧数: 37
这是我在知乎上看到的对WOW游戏引擎的评价 原文:你说得很对,我只是拿图像举一个侧面的例子,并且我只针对于游戏中的程序技术来说的!还不包括策划设计! COD用的2001年的引擎这点是可讨论的,应该是2001年的引擎基础,但是绝对很多次大的修改!COD系列说实话我不太熟悉,但我对MMO很熟悉,以MMO引擎举例子。 我们来看WOW的引擎,WOW的最初版本最牛的地方在于场景结构及渲染优化,有几点是我至今认为非常强悍的,也就是在现在的游戏产品中能做到的依然少见,包括: 1.完全的室内外场景结构无缝结合并采用PORTAL链接,说白了在室内,你对着墙是完全看不到室外的,并且室内可以支持超复结构。 2.室内的静态光照预处理是在Vertex Colour级别实现的! 3.完整的时间-地域环境系统 4.效果最为柔和的bloom 但是到后期,WOW引擎明显基础强悍升级: 1.全场景的CSM阴影技术,并且巧妙的室内外阴影分离 2.延迟着色的使用,副产品SSAO 3.更多的post-effect 可以看到这几乎是把一款10年前的引擎一跃修改为主流引擎,而没根本变化的其实只有场景系统了。所以从COD引擎没有大改变是不太可能的,基本上是完整的技术升级。 另外讨论的跑题了,我大概理解你的意思,你的意思是说这个话题不应该只从技术考虑对吧?同时要从产品设计考虑。 我同意你的看法,同时我认为的是连技术都根本达不到。觉得能做和做完成了是有鸿沟的,当然这个鸿沟可跨越,但绝对是场战役!
kate无法在终端下打开文档,有错误信息,求解决办法 root@M:/home/m# kate /etc/apt/sources.list QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. (process:3826): GConf-WARNING **: Client failed to connect to the D-BUS daemon: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. (process:3826): GConf-WARNING **: Client failed to connect to the D-BUS daemon: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. (process:3826): GConf-WARNING **: Client failed to connect to the D-BUS daemon: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. QGtkStyle was unable to detect the current GTK+ theme. Qt: Session management error: Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed kate(3826)/kdeui (kdelibs): Session bus not found To circumvent this problem try the following command (with Linux and bash) export $(dbus-launch) KCrash: Application *kate* crashing... KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit sock_file=/root/.kde/socket-M/kdeinit4__0 Warning: connect() failed: : 没有那个文件或目录 KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi directly (process:3827): GConf-WARNING **: Client failed to connect to the D-BUS daemon: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. (process:3827): GConf-WARNING **: Client failed to connect to the D-BUS daemon: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. (process:3827): GConf-WARNING **: Client failed to connect to the D-BUS daemon: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. QGtkStyle was unable to detect the current GTK+ theme. drkonqi(3827)/kdeui (kdelibs): Session bus not found To circumvent this problem try the following command (with Linux and bash) export $(dbus-launch)
首页 1 2 下一页