unity多人_导航Unity的多人Netcode过渡

unity多人

This blog was last updated, 27th April 2020.

该博客的最新更新时间为2020年4月27日。

As many of you know, we put UNet into maintenance mode because we believe there is a better way forward with our new connected games stack. Since this announcement, we have learned that many of our developers need guidance about the best path for their game during this transition period. In this post we’ve consolidated key questions you’ll need to answer and highlighted how you can make critical decisions about your networking stack. 

众所周知,我们将 UNet置于维护模式 是因为我们相信使用 新的联网游戏堆栈 有更好的方法 。 自从发布此公告以来,我们了解到,在过渡期间,我们的许多开发人员都需要有关其最佳游戏途径的指导。 在本文中,我们综合了您需要回答的关键问题,并重点介绍了如何对网络堆栈做出关键决策。

As you see at the bottom of the flowchart, you have many options, ranging from continuing to use UNet as-is, to targeting our new DOTS based Netcode (efficient, high-level netcode) and Unity Transport Package (lower-level networking stack). Which option you choose depends on the specific needs of your game. In this blog, we’ll walk you through each question and how you should think about them.

如流程图底部所示,您有许多选择,从继续按原样使用UNet到针对我们基于新DOTS的Netcode(高效,高级网络代码)和Unity Transport Package(低级网络堆栈) )。 选择哪个选项取决于游戏的特定需求。 在此博客中,我们将引导您完成每个问题以及您如何考虑它们。

规模 (Scale)

When we talk about the scale of a multiplayer game, we most frequently refer to the maximum number of players in a single session or connected to a single server. In this case, peer-to-peer (P2P) topologies typically struggle when you attempt to sync m

  • 1
    点赞
  • 3
    收藏
    觉得还不错? 一键收藏
  • 0
    评论

“相关推荐”对你有帮助么?

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值