<?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>Car 3D motion</value>
  </data>
  <data name="Record_Car3DMotion_Tooltip" xml:space="preserve">
    <value>Record car 3D motion (acceleration and relative velocity)</value>
  </data>
  <data name="Record_CarMapPosition" xml:space="preserve">
    <value>Car map position</value>
  </data>
  <data name="Record_CarMapPosition_Tooltip" xml:space="preserve">
    <value>Record map position (X,Y,Z) of the car</value>
  </data>
  <data name="Record_Engine_Temp" xml:space="preserve">
    <value>Engine Temperatures</value>
    <comment>A specific option for telemetry recording</comment>
  </data>
  <data name="Record_Engine_Temp_Tooltip" xml:space="preserve">
    <value>Record engine temperatures (if telemetry recording is enabled).

Enable and disable recording options to control how much data is logged in telemetry recording files.

These recording options apply only to telemetry files and not for UDP telemetry (UDP telemetry always sends out all information)</value>
  </data>
  <data name="Record_Springs_Dampers_Rollbars" xml:space="preserve">
    <value>Springs, dampers, rollbars</value>
  </data>
  <data name="Record_Springs_Dampers_Rollbars_Tooltip" xml:space="preserve">
    <value>Record spring, damper, strut and rollbar movements</value>
  </data>
  <data name="Record_Telemetry_DataFile" xml:space="preserve">
    <value>Record telemetry data in a file</value>
    <comment>An option in Telemetry page to enable telemetry saving in a file</comment>
  </data>
  <data name="Record_Telemetry_DataFile_Tooltip" xml:space="preserve">
    <value>Stores and records live racing telemetry files in Plugins\NGP\Telemetry folder. 

Recorded NGP telemetry files can be used to analyze how a car behaves on stage. Telemetry contains details about engine, brakes, springs, dampers and tyres.

Warning. Enable this option only when you really want to analyze the race because recordings may require several mega bytes of disk space</value>
  </data>
  <data name="Record_Telemetry_TickRate" xml:space="preserve">
    <value>Update interval</value>
    <comment>An option in Telemetry page</comment>
  </data>
  <data name="Record_Telemetry_TickRate_Tooltip" xml:space="preserve">
    <value>Update interval tics of telemetry recording (1-1000). Low value is detailed telemetry, but consumes more CPU and disk space when recording is enabled.
	
1 = Detailed telemetry, but very high CPU and disk usage (good for spring and damper analyzing)
5 = Good all around update interval (default)
10 = Coarse telemetry, but consumes less CPU and disk space (good enough for temperature and tyre wear analyzing)</value>
  </data>
  <data name="Record_TyreBrake_Temp" xml:space="preserve">
    <value>Tyre &amp; brake temperatures</value>
  </data>
  <data name="Record_TyreBrake_Temp_Tooltip" xml:space="preserve">
    <value>Record tyre and brake temperatures</value>
  </data>
  <data name="Record_TyreBrake_Wear" xml:space="preserve">
    <value>Tyre &amp; brake wear</value>
  </data>
  <data name="Record_TyreBrake_Wear_Tooltip" xml:space="preserve">
    <value>Record tyre and brake wear</value>
  </data>
  <data name="UDP_Telemetry" xml:space="preserve">
    <value>UDP Telemetry</value>
    <comment>An option in Telemetry page</comment>
  </data>
  <data name="UDP_Telemetry_Address_Tooltip" xml:space="preserve">
    <value>Listening IP address of the UDP telemetry receiver app, for example SimHub (default 127.0.0.1)</value>
  </data>
  <data name="UDP_Telemetry_Port_Tooltip" xml:space="preserve">
    <value>Listening port number of the UDP telemetry receiver app, for example SimHub (default 6776)</value>
  </data>
  <data name="UDP_Telemetry_Tooltip" xml:space="preserve">
    <value>Enables NGPhysics telemetry service for external apps (example SimHub) to extract live telemetry data during racing</value>
  </data>
  <data name="Motec_Conversion" xml:space="preserve">
    <value>MoTeC telemetry files</value>
  </data>
  <data name="Motec_Conversion_Tooltip" xml:space="preserve">
    <value>Convert NGP telemetry files (.tsv) automatically to MoTeC application format (.ld).
Requires NGP2MoTeC package installation</value>
  </data>
  <data name="Motec_KeepOnlyMotecFiles" xml:space="preserve">
    <value>Keep only MoTeC files</value>
  </data>
  <data name="Motec_KeepOnlyMotecFiles_Tooltip" xml:space="preserve">
    <value>Keep only MoTeC telemetry file recordings (.ld) and remove NGP telemetry files (.tsv)</value>
  </data>
</root>
