<?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>Gerakan 3D mobil </value>
  </data>
  <data name="Record_Car3DMotion_Tooltip" xml:space="preserve">
    <value>Catat gerakan 3D mobil (akselerasi dan kecepatan relatif)</value>
  </data>
  <data name="Record_CarMapPosition" xml:space="preserve">
    <value>Posisi map mobil</value>
  </data>
  <data name="Record_CarMapPosition_Tooltip" xml:space="preserve">
    <value>Catat posisi map (X,Y,Z) dari mobil</value>
  </data>
  <data name="Record_Engine_Temp" xml:space="preserve">
    <value>Suhu mesin</value>
  </data>
  <data name="Record_Engine_Temp_Tooltip" xml:space="preserve">
    <value>Catat suhu mesin (jika pencatatan telemetri dihidupkan).

Hidupkan dan matikan opsi pencatatan untuk mengontrol berapa banyak data yang akan dicatat ke dalam file catatan telemetri.

Opsi pencatatan ini hanya diterapkan pada file telemetri dan tidak pada telemetri UDP (telemetri UDP selalu mengirimkan semua informasi)</value>
  </data>
  <data name="Record_Springs_Dampers_Rollbars" xml:space="preserve">
    <value>Spring, damper, rollbar</value>
  </data>
  <data name="Record_Springs_Dampers_Rollbars_Tooltip" xml:space="preserve">
    <value>Catat pergerakan spring, damper, strut dan rollbar</value>
  </data>
  <data name="Record_Telemetry_DataFile" xml:space="preserve">
    <value>Catat data telemetri ke dalam file</value>
  </data>
  <data name="Record_Telemetry_DataFile_Tooltip" xml:space="preserve">
    <value>Menyimpan dan mencatat file telemetri balapan di folder Plugins\NGP\Telemetry. 

File telemetri NGP yang direkam dapat digunakan untuk menganalisa bagaimana mobil berjalan pada stage. Telemetri berisi detail mengenai mesin, rem, spring, damper dan ban.

Peringatan. Menghidupkan opsi ini hanya ketika kamu ingin menganalisa balapan karena pencatatan membutuhkan beberapa megabyte pada penyimpanan</value>
  </data>
  <data name="Record_Telemetry_TickRate" xml:space="preserve">
    <value>Interval update</value>
  </data>
  <data name="Record_Telemetry_TickRate_Tooltip" xml:space="preserve">
    <value>Tik interval update pada pencatatan telemetri (1-1000). Nilai rendah = lebih detail, namun memakan CPU dan ruang penyimpanan lebih ketika pencatatan dihidupkan.
	
1 = Telemetri lebih detail, namun penggunaan CPU dan Disk sangat tinggi (bagus untuk analisa spring dan damper)
5 = Baik secara keseluruhan (default)
10 = Telemetri secara kasar, namun memakan CPU dan ruang penyimpanan lebih sedikit (cukup bagus untuk analisa temperatur dan penggunaan ban)</value>
  </data>
  <data name="Record_TyreBrake_Temp" xml:space="preserve">
    <value>Suhu ban &amp; rem</value>
  </data>
  <data name="Record_TyreBrake_Temp_Tooltip" xml:space="preserve">
    <value>Catat suhu dan dan rem</value>
  </data>
  <data name="Record_TyreBrake_Wear" xml:space="preserve">
    <value>Keausan ban &amp; rem</value>
  </data>
  <data name="Record_TyreBrake_Wear_Tooltip" xml:space="preserve">
    <value>Catat keausan ban dan rem</value>
  </data>
  <data name="UDP_Telemetry" xml:space="preserve">
    <value>Telemetri UDP</value>
  </data>
  <data name="UDP_Telemetry_Address_Tooltip" xml:space="preserve">
    <value>Mendengarkan IP address pada aplikasi penerima telemetri UDP, misalnya SimHub (default 127.0.0.1)</value>
  </data>
  <data name="UDP_Telemetry_Port_Tooltip" xml:space="preserve">
    <value>Mendengarkan nomor port pada aplikasi penerima telemetri UDP, misalnya SimHub (default 6776)</value>
  </data>
  <data name="UDP_Telemetry_Tooltip" xml:space="preserve">
    <value>Menghidupkan layanan telemetri NGPhysics untuk aplikasi eksternal (misal SimHub) untuk mengekstrak data telemetri secara langsung selama balapan</value>
  </data>
</root>