<?xml version="1.0" encoding="utf-8"?>
<root>
  <!-- 
    Microsoft ResX Schema 
    
    Version 2.0
    
    The primary goals of this format is to allow a simple XML format 
    that is mostly human readable. The generation and parsing of the 
    various data types are done through the TypeConverter classes 
    associated with the data types.
    
    Example:
    
    ... ado.net/XML headers & schema ...
    <resheader name="resmimetype">text/microsoft-resx</resheader>
    <resheader name="version">2.0</resheader>
    <resheader name="reader">System.Resources.ResXResourceReader, System.Windows.Forms, ...</resheader>
    <resheader name="writer">System.Resources.ResXResourceWriter, System.Windows.Forms, ...</resheader>
    <data name="Name1"><value>this is my long string</value><comment>this is a comment</comment></data>
    <data name="Color1" type="System.Drawing.Color, System.Drawing">Blue</data>
    <data name="Bitmap1" mimetype="application/x-microsoft.net.object.binary.base64">
        <value>[base64 mime encoded serialized .NET Framework object]</value>
    </data>
    <data name="Icon1" type="System.Drawing.Icon, System.Drawing" mimetype="application/x-microsoft.net.object.bytearray.base64">
        <value>[base64 mime encoded string representing a byte array form of the .NET Framework object]</value>
        <comment>This is a comment</comment>
    </data>
                
    There are any number of "resheader" rows that contain simple 
    name/value pairs.
    
    Each data row contains a name, and value. The row also contains a 
    type or mimetype. Type corresponds to a .NET class that support 
    text/value conversion through the TypeConverter architecture. 
    Classes that don't support this are serialized and stored with the 
    mimetype set.
    
    The mimetype is used for serialized objects, and tells the 
    ResXResourceReader how to depersist the object. This is currently not 
    extensible. For a given mimetype the value must be set accordingly:
    
    Note - application/x-microsoft.net.object.binary.base64 is the format 
    that the ResXResourceWriter will generate, however the reader can 
    read any of the formats listed below.
    
    mimetype: application/x-microsoft.net.object.binary.base64
    value   : The object must be serialized with 
            : System.Runtime.Serialization.Formatters.Binary.BinaryFormatter
            : and then encoded with base64 encoding.
    
    mimetype: application/x-microsoft.net.object.soap.base64
    value   : The object must be serialized with 
            : System.Runtime.Serialization.Formatters.Soap.SoapFormatter
            : and then encoded with base64 encoding.

    mimetype: application/x-microsoft.net.object.bytearray.base64
    value   : The object must be serialized into a byte array 
            : using a System.ComponentModel.TypeConverter
            : and then encoded with base64 encoding.
    -->
  <xsd:schema id="root" xmlns="" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:msdata="urn:schemas-microsoft-com:xml-msdata">
    <xsd:import namespace="http://www.w3.org/XML/1998/namespace" />
    <xsd:element name="root" msdata:IsDataSet="true">
      <xsd:complexType>
        <xsd:choice maxOccurs="unbounded">
          <xsd:element name="metadata">
            <xsd:complexType>
              <xsd:sequence>
                <xsd:element name="value" type="xsd:string" minOccurs="0" />
              </xsd:sequence>
              <xsd:attribute name="name" use="required" type="xsd:string" />
              <xsd:attribute name="type" type="xsd:string" />
              <xsd:attribute name="mimetype" type="xsd:string" />
              <xsd:attribute ref="xml:space" />
            </xsd:complexType>
          </xsd:element>
          <xsd:element name="assembly">
            <xsd:complexType>
              <xsd:attribute name="alias" type="xsd:string" />
              <xsd:attribute name="name" type="xsd:string" />
            </xsd:complexType>
          </xsd:element>
          <xsd:element name="data">
            <xsd:complexType>
              <xsd:sequence>
                <xsd:element name="value" type="xsd:string" minOccurs="0" msdata:Ordinal="1" />
                <xsd:element name="comment" type="xsd:string" minOccurs="0" msdata:Ordinal="2" />
              </xsd:sequence>
              <xsd:attribute name="name" type="xsd:string" use="required" msdata:Ordinal="1" />
              <xsd:attribute name="type" type="xsd:string" msdata:Ordinal="3" />
              <xsd:attribute name="mimetype" type="xsd:string" msdata:Ordinal="4" />
              <xsd:attribute ref="xml:space" />
            </xsd:complexType>
          </xsd:element>
          <xsd:element name="resheader">
            <xsd:complexType>
              <xsd:sequence>
                <xsd:element name="value" type="xsd:string" minOccurs="0" msdata:Ordinal="1" />
              </xsd:sequence>
              <xsd:attribute name="name" type="xsd:string" use="required" />
            </xsd:complexType>
          </xsd:element>
        </xsd:choice>
      </xsd:complexType>
    </xsd:element>
  </xsd:schema>
  <resheader name="resmimetype">
    <value>text/microsoft-resx</value>
  </resheader>
  <resheader name="version">
    <value>2.0</value>
  </resheader>
  <resheader name="reader">
    <value>System.Resources.ResXResourceReader, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</value>
  </resheader>
  <resheader name="writer">
    <value>System.Resources.ResXResourceWriter, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</value>
  </resheader>
  <data name="Record_Car3DMotion" xml:space="preserve">
    <value>汽车 3D 运动</value>
  </data>
  <data name="Record_Car3DMotion_Tooltip" xml:space="preserve">
    <value>记录汽车的 3D 运动（加速度和相对速度）</value>
  </data>
  <data name="Record_CarMapPosition" xml:space="preserve">
    <value>汽车地图位置</value>
  </data>
  <data name="Record_CarMapPosition_Tooltip" xml:space="preserve">
    <value>记录汽车的地图位置（X、Y、Z</value>
  </data>
  <data name="Record_Engine_Temp" xml:space="preserve">
    <value>发动机温度</value>
  </data>
  <data name="Record_Engine_Temp_Tooltip" xml:space="preserve">
    <value>记录发动机温度（如果启用了遥测记录功能）。

启用和禁用记录选项，以控制记录在遥测记录文件中的数据量。

这些记录选项仅适用于遥测文件，不适用于 UDP 遥测（UDP 遥测总是发送所有信息）</value>
  </data>
  <data name="Record_Springs_Dampers_Rollbars" xml:space="preserve">
    <value>弹簧、减震器、防倾杆</value>
  </data>
  <data name="Record_Springs_Dampers_Rollbars_Tooltip" xml:space="preserve">
    <value>记录弹簧、减震器、支撑杆和防倾杆的运动情况</value>
  </data>
  <data name="Record_Telemetry_DataFile" xml:space="preserve">
    <value>在文件中记录遥测数据</value>
  </data>
  <data name="Record_Telemetry_DataFile_Tooltip" xml:space="preserve">
    <value>在 Plugins\NGP\Telemetry 文件夹中存储和记录实时赛车遥测文件。

录制的 NGP 遥测文件可用于分析赛车在舞台上的表现。遥测数据包含发动机、刹车、弹簧、减震器和轮胎的详细信息。

警告。只有当您真的想分析比赛时才启用此选项，因为记录可能需要几百万字节的磁盘空间</value>
  </data>
  <data name="Record_Telemetry_TickRate" xml:space="preserve">
    <value>更新间隔</value>
  </data>
  <data name="Record_Telemetry_TickRate_Tooltip" xml:space="preserve">
    <value>遥测记录的更新间隔时间（1-1000）。低值为详细遥测，但启用记录时会消耗更多 CPU 和磁盘空间。
	
1 = 详细遥测，但 CPU 和磁盘使用率非常高（适合分析弹簧和阻尼器）
5 = 良好的全面更新间隔（默认值）
10 = 粗略的遥测数据，但占用较少的 CPU 和磁盘空间（适用于温度和轮胎磨损分析）</value>
  </data>
  <data name="Record_TyreBrake_Temp" xml:space="preserve">
    <value>轮胎和制动器温度</value>
  </data>
  <data name="Record_TyreBrake_Temp_Tooltip" xml:space="preserve">
    <value>记录轮胎和刹车温度</value>
  </data>
  <data name="Record_TyreBrake_Wear" xml:space="preserve">
    <value>轮胎和刹车磨损</value>
  </data>
  <data name="Record_TyreBrake_Wear_Tooltip" xml:space="preserve">
    <value>记录轮胎和刹车磨损情况</value>
  </data>
  <data name="UDP_Telemetry" xml:space="preserve">
    <value>UDP 遥测</value>
  </data>
  <data name="UDP_Telemetry_Address_Tooltip" xml:space="preserve">
    <value>UDP 遥测接收器应用程序（例如 SimHub）的监听 IP 地址（默认为 127.0.0.1）</value>
  </data>
  <data name="UDP_Telemetry_Port_Tooltip" xml:space="preserve">
    <value>UDP 遥测接收器应用程序（例如 SimHub）的监听端口号（默认为 6776</value>
  </data>
  <data name="UDP_Telemetry_Tooltip" xml:space="preserve">
    <value>为外部应用程序（例如 SimHub）启用 NGPhysics 遥测服务，以便在比赛期间提取实时遥测数据</value>
  </data>
</root>