使用场景场景包含游戏环境和菜单。可以将每个唯一的场景文件视为一个唯一的关卡。在每个场景中,您放置环境、障碍物和装饰,本质上是分段设计和构建您的游戏。 更多信息
参见 术语表视图上下文菜单直接在场景中访问常见的场景视图您正在创建的世界中的交互式视图。您可以使用场景视图选择和放置场景、角色、摄像机、灯光以及所有其他类型的游戏对象。 更多信息
参见 术语表操作,而不是从菜单工具栏Unity 编辑器顶部的按钮和基本控件行,允许您以各种方式与编辑器交互(例如缩放、平移)。 更多信息
参见 术语表中访问。
场景视图上下文菜单中显示的菜单选项取决于您当前的选择和工具覆盖层中启用的工具上下文。如果您已选择一个游戏对象Unity 场景中的基本对象,可以表示角色、道具、场景、摄像机、路径点等等。游戏对象的函数由附加到它的组件定义。 更多信息
参见 术语表,则场景视图上下文菜单将显示该游戏对象以及任何相关的附加组件的选项。
要显示上下文菜单,请在场景视图中右键单击。
注意:您可以在快捷键管理器中选择不同的快捷键来显示场景视图上下文菜单。
场景视图中的默认工具上下文为游戏对象。启用游戏对象工具上下文时,当您选择一个游戏对象时,场景视图上下文菜单默认显示以下菜单项
如果游戏对象附加了其他组件,则与这些组件相关的操作将显示在场景视图上下文菜单的末尾。
如果您的项目包含多个工具上下文,则可以使用工具覆盖层中的第一个按钮选择一个工具上下文。如果您启用了不是游戏对象的工具上下文,则场景视图上下文菜单将显示与该工具上下文中您的选择相关的选项。例如,如果您的项目包含样条曲线包并且您启用了样条曲线工具上下文,则场景视图上下文菜单将显示创建和编辑样条曲线的选项。
Did you find this page useful? Please give it a rating:
Thanks for rating this page!
What kind of problem would you like to report?
Thanks for letting us know! This page has been marked for review based on your feedback.
If you have time, you can provide more information to help us fix the problem faster.
Provide more information
You've told us this page needs code samples. If you'd like to help us further, you could provide a code sample, or tell us about what kind of code sample you'd like to see:
You've told us there are code samples on this page which don't work. If you know how to fix it, or have something better we could use instead, please let us know:
You've told us there is information missing from this page. Please tell us more about what's missing:
You've told us there is incorrect information on this page. If you know what we should change to make it correct, please tell us:
You've told us this page has unclear or confusing information. Please tell us more about what you found unclear or confusing, or let us know how we could make it clearer:
You've told us there is a spelling or grammar error on this page. Please tell us what's wrong:
You've told us this page has a problem. Please tell us more about what's wrong:
Thank you for helping to make the Unity documentation better!
Your feedback has been submitted as a ticket for our documentation team to review.
We are not able to reply to every ticket submitted.