为多场景作品添加场景文件到列表是很简单的。
It is easy to add scene files to the list for multi-scene builds.
自定义属性脚本完全地从场景文件中保存和装入。
Scripted custom attributes are properly saved to and loaded from scene files.
转换的FBX导入到您的玛雅包含你的模型场景文件。
Import your converted FBX file into your Maya scene containing your model.
使用FBX场景文件作为系统场景的载体并且对FBX场景文件进行必要的信息提取。
FBX scene file is used as the carriers of the scenes of this system. The system can extract necessary information from FBX file.
如果你想快速编译一个只有一个场景文件的测试程序，只需编译一个空白场景列表的播放器。
If you want to quickly build a test player with only one scene file, just build a player with a blank scene list.
典型的富媒体服务包含一系列场景，由场景文件来定义各种媒体元素在时空上的排列组织情况。
Typical rich media services include a series of scenes, which are used to organize various media elements from the temporal and spatial.
下次打开场景文件的时候，将文件中存储的对象依次取出并赋值给程序的相应对象中，即可恢复场景。
To resume scene, getting all object saved in file orderly and evaluate it to correlative object in program when open scene file next time.
注意：对于变形的属性结构发生了变化，场景文件使用了旧版本的变形可能无法加载在某些情况下正确。
ATTENTION: for the deformer's attribute structure has changed, scene files using the old version of the deformer may not load correctly in some cases.
如果你已经添加了多个场景文件，并希望重新排列它们，只需在列表中拖动它到其它场景上面或下面，直到你需要的顺序。
If you've added more than one scene file and want to rearrange them, simply click and drag the scenes on the list above or below others until you have them in the desired order.
本文的主要工作内容为如下几个方面：一，利用基于网络传播的交互三维建模的新软件标准X3D来构建系统中大坝三维场景文件；
The main works of this paper are as follows: 1. Building the 3D scene through the new networking-based interactive 3D modeling software standard—X3D.
新版的存储功能可保存所有设置为单独的一个场景文件，这就意味着不用在担心模型和贴图的丢失了，简单的按下保存按钮就搞定了。
All objects and settings are now saved in a centralized scene file, no need to worry about saving meshes or materials separately, one nice big save button for everything!
对于这一示例场景，您需要将数据源指定文件绑定到相应的数据库。
For this sample scenario, you want to bind the data source specific files to their corresponding database.
现在已经构建了配置我们的示例场景需要的所有密钥存储文件。
We have now built all of the key store files necessary to configure our sample scenarios.
图7显示了我们刚刚描述的实现场景的目录与文件分层结构。
Figure 7 shows the directory and file hierarchy for the implementation scenario we just described.
我们可以通过添加新文本文件向场景中添加元素，也可能希望添加多重复杂度。
We can add elements to our scenarios by adding new text files, or we may wish to add multiple complications.
考虑一个简单的场景，属性文件的价值就会变得很清楚。
The value of the properties file becomes clear when you consider a simple scenario.
现在我们具备了配置示例场景所示的SSL连接所需要的所有文件。
We now have all the files we need to configure the SSL connections shown in our sample scenarios.
这个示例场景中的处理程序定义文件如 清单3 所示。
The handler definition file in the example scenario is shown in Listing 3.
在这种情况下，可以定义并返回默认的XML文件，当场景中已经确定了“默认”行为时，这项处理将很有用。
In this event, a default XML file can be defined and returned, a useful process when a "default" behavior is defined in a scenario.
在每次场景之后检查文件，可以确保您去决定什么例外属于什么场景。
Checking the file after each scenario ensures that you can determine which exception belongs to which scenario..
造成混乱的另一个典型场景是意外地覆盖现有的文件。
Another typical doomsday scenario is the accidental overwriting of an existing file.
在拥有这些文件后，生成场景的代码与生成名称的代码基本相同。
Once we have these files, the code to generate a scenario looks much the same as the code to generate names.
下载场景1文件。
下载场景3文件。
下载场景4文件。
下载场景2文件。
可以在多个不同的场景中暂停一个响应文件的处理。
You can pause the processing of a response file in different scenarios.
场景1：本地文件系统编校。
通过使用这些功能，您就能够为您希望分析的大部分问题场景生成转储文件。
Using them, you should be able to generate dumps for most problem scenarios you want to diagnose.
这就会把ErrorDetails文件中的数据与场景联系起来，因为日志文件中条目的前面就是场景名。
This relates the data in the ErrorDetails file to the scenario, because the entries in the log file are preceded by the scenario name.
应用推荐