<?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="321_Countdown_Paused" xml:space="preserve">
    <value>3-2-1 Countdown paused</value>
  </data>
  <data name="321_Countdown_Paused_Tooltip" xml:space="preserve">
    <value>When this option is set then the 3-2-1 countdown is paused until handbrake is pulled to at least 30% level or Pause/Ignition/Esc key is pressed.

Pedal activity is visualized on screen, steering wheel adjusts the speed of camera spinning around the car and ChangeCam RBR key switches between internal and external cam view.

You can verify controls, check the internal cam position and make sure the race seat feels comfortable before the race begins</value>
  </data>
  <data name="Adaptive_FFB_force" xml:space="preserve">
    <value>Adaptive FFB force</value>
  </data>
  <data name="Adaptive_FFB_force_Tooltip" xml:space="preserve">
    <value>Number of buffer cycles NGP plugin uses to generate adaptive FFB effects (0-4).

0 = Very strong adaptive FFB effect (may cause FPS performance issues)
1 = Strong adaptive FFB (default)
2 = Average adaptive FFB
3 = Weak adaptive FFB (improves FPS when adaptive FFB is enabled)
4 = Very weak adaptive FFB (almost the same as disabling the adaptive FFB effect completely)</value>
  </data>
  <data name="Adaptive_FFB_FPS" xml:space="preserve">
    <value>Adaptive FFB FPS</value>
  </data>
  <data name="Adaptive_FFB_FPS_Tooltip" xml:space="preserve">
    <value>Minimum FPS frame rate adaptive FFB effect tries to keep up with (28-240 depending on the display frequency).

58 = Recommended for 60Hz displays (default)
72 = Recommended for 75Hz displays
116 = Recommended for 120Hz displays
140 = Recommended for 144Hz displays
236 = Recommended for 240Hz displays</value>
  </data>
  <data name="Adjust_SteeringWheel_Range" xml:space="preserve">
    <value>Adjust steering wheel range per car</value>
    <comment>An option in Controls page</comment>
  </data>
  <data name="Adjust_SteeringWheel_Range_DetailsBtn" xml:space="preserve">
    <value>Details...</value>
    <comment>A button label in Controls page</comment>
  </data>
  <data name="Adjust_SteeringWheel_Range_DetailsBtn_Tooltip" xml:space="preserve">
    <value>Show detailed list of supported steering wheel models</value>
  </data>
  <data name="Adjust_SteeringWheel_Range_Protocol_Tooltip" xml:space="preserve">
    <value>Alternative protocols how the range is adjusted in a steering wheel controller device.

Default is the recommended value (auto-detected).
Try different Protocol 1-4 selections only if the steering wheel device does not work with default option</value>
    <comment>A tooltip of an option in Controls page</comment>
  </data>
  <data name="Adjust_SteeringWheel_Range_ScanBtn" xml:space="preserve">
    <value>Scan...</value>
    <comment>A button label in Controls page</comment>
  </data>
  <data name="Adjust_SteeringWheel_Range_ScanBtn_Toolt" xml:space="preserve">
    <value>Scan connected USB devices and show the list of connected devices</value>
  </data>
  <data name="Adjust_SteeringWheel_Range_Tooltip" xml:space="preserve">
    <value>By default RSF does not adjust the physical steering wheel rotation range per car. You have to use steering wheel specific configuration tools to do it (outside of RSF and RBR).

If this option is enabled then RSF adjusts the physical steering wheel rotation range using lock-to-lock value set in My Cars page (car specific value).

Several Thrustmaster, Logitech, Fanatec, SimuCube, Simagic, Moza, MMOS, OpenFFBoard models are supported</value>
  </data>
  <data name="Autohide_Mouse_Pointer" xml:space="preserve">
    <value>Autohide mouse pointer</value>
  </data>
  <data name="Autohide_Mouse_Pointer_Tooltip" xml:space="preserve">
    <value>Autohide the mouse pointer after few seconds of mouse inactivity</value>
  </data>
  <data name="Autohide_Mouse_Pointer_Tooltip2" xml:space="preserve">
    <value>When a mouse pointer is autohidden this option sets the minimum mouse movement threshold to show the pointer again.
	
0 = Autohide feature disabled.
Bigger value = The mouse pointer must be moved more to make it visible again.</value>
    <comment>A tooltip shown on the "autohide mouse pointer" slider</comment>
  </data>
  <data name="Automatic_gearbox" xml:space="preserve">
    <value>Automatic gearbox</value>
  </data>
  <data name="Automatic_gearbox_Tooltip" xml:space="preserve">
    <value>Enable this option to use an automatic gearbox</value>
  </data>
  <data name="ControlMappings_ClickToBind_Tooltip" xml:space="preserve">
    <value>Click to bind a control...</value>
    <comment>A tooltip of "rebind" button in the control mappings screen</comment>
  </data>
  <data name="ControlMappings_PressKeyToBind" xml:space="preserve">
    <value>&lt;Press a keyboard or mouse key&gt;</value>
    <comment>A message shown when binding a control key</comment>
  </data>
  <data name="ControlMappings_RBRVR" xml:space="preserve">
    <value>Control Mappings - Virtual Reality (RBRVR)</value>
    <comment>A label in the control mappings screen (RBRVR related control remaps)</comment>
  </data>
  <data name="ControlMappings_ResetBackToDefault_Tooltip" xml:space="preserve">
    <value>Uncheck to reset the control back to default</value>
    <comment>A tooltip of "reset back to default" button in the control mappings screen</comment>
  </data>
  <data name="FFB_Sens_Gravel" xml:space="preserve">
    <value>FFB sensitivity range on gravel</value>
    <comment>An ffb sensitivty option in Controls and MyCars pages (gravel option)</comment>
  </data>
  <data name="FFB_Sens_Snow" xml:space="preserve">
    <value>snow</value>
    <comment>FFB sens of snow option in Controls and MyCars page</comment>
  </data>
  <data name="FFB_Sens_Tarmac" xml:space="preserve">
    <value>tarmac</value>
    <comment>FFB sens of tarmac option in Controls and MyCars page</comment>
  </data>
  <data name="FFB_Sens_Tooltip" xml:space="preserve">
    <value>FFB sensitivity range on gravel/tarmac/snow.

Lower value = Sharp, but not very sensitive FFB effects (some effects are clipped)
Higher value = More precice FFB effects, but may feel too soft in budget wheels.

The value is usually between 100 and 600. In theory higher value means better FFB effects, 
but the value depends on the hardware capabilities. Start with high value and test FFB effects. 

If FFB feels bad then lower the value by 50 until you are comfortable how the FFB feels. 

You may have to tweak FFB settings in a vendor specific steering wheel driver tools also</value>
    <comment>A tooltip of Forcefeedback sensitivy options (a different FFB sens on gravel/tarmac/snow)</comment>
  </data>
  <data name="Footer_Tip1" xml:space="preserve">
    <value>Tip. Assign controls while the game is in RBR menus and not while the car is on stage.
Press ESC key in RallySimFans menu and choose Options/Controls to assign controls. 
Set steering wheel range temporarily as 180° if RBR doesn't detect the wheel.</value>
    <comment>A footer tip text in Controls page</comment>
  </data>
  <data name="Force_feedback_settings" xml:space="preserve">
    <value>Force feedback settings</value>
    <comment>A title in Controls page</comment>
  </data>
  <data name="Inverted_Brake" xml:space="preserve">
    <value>Brake pedal inverted</value>
  </data>
  <data name="Inverted_Clutch" xml:space="preserve">
    <value>Clutch pedal inverted</value>
  </data>
  <data name="Inverted_Handbrake" xml:space="preserve">
    <value>Handbrake inverted</value>
  </data>
  <data name="Inverted_Throttle" xml:space="preserve">
    <value>Throttle pedal inverted</value>
    <comment>An option in Controls page</comment>
  </data>
  <data name="Inverted_Tooltip" xml:space="preserve">
    <value>Some pedals or controls send 100-&gt;0 values when pressed down instead of traditional 0-&gt;100 values. If an in-game control is at 100% even when you don't press the control then enable this option</value>
  </data>
  <data name="Pause_FreezeFrame" xml:space="preserve">
    <value>Pause Freeze Frame mode</value>
    <comment>An option name</comment>
  </data>
  <data name="Pause_FreezeFrame_1_FreezePause" xml:space="preserve">
    <value>Freeze-Pause</value>
  </data>
  <data name="Pause_FreezeFrame_2_FreezeOnly" xml:space="preserve">
    <value>Freeze only</value>
  </data>
  <data name="Pause_FreezeFrame_Tooltip" xml:space="preserve">
    <value>By default PAUSE control (see Options/Controls menu in RBR) shows the in-game pause menu while racing or replaying.
Set this option to use Freeze Frame in Pause control: Two state Freeze-Pause menu or Freeze only
	
Freeze-Pause:
The first press = Freezes the game, but keeps camera controls available
The second press = The normal in-game Pause menu

Freeze only:
The first press = Freezes the game, but keeps camera controls available
The second press = Back to racing or replaying

TIP. Press F9 key in external cam view to toggle between normal cam and freeCam (move around the cam with a mouse).
Hold Left button = Move the cam up/down/left/right
Hold Right button = Turn around the cam
Mouse wheel = Move the cam forward/backward
Hold Mouse wheel = Zoom in/out (alternative control: CTRL key + Mouse wheel)</value>
  </data>
  <data name="Prevent_Repeated_ShiftEvents" xml:space="preserve">
    <value>Prevent repeated shift events</value>
  </data>
  <data name="Prevent_Repeated_ShiftEvents_MSecs" xml:space="preserve">
    <value> msecs</value>
    <comment>Milliseconds, unit of measure in Prevent Repeated Shift Events slider option (note the extra space char prefix)</comment>
  </data>
  <data name="Prevent_Repeated_ShiftEvents_Tooltip" xml:space="preserve">
    <value>Some shifters may send multiple gear up or down events to RBR even when you intended to change just one gear.
Use this option to eliminate duplicated shift events within certain threshold (milliseconds).

0 = Disabled
1 - 1000 = Threshold in milliseconds to ignore repeated shift events</value>
  </data>
  <data name="Prevent_Repeated_ShiftEvents_Tooltip2" xml:space="preserve">
    <value>Threshold in milliseconds to prevent duplicated repeated up or down shift events.</value>
    <comment>A tooltip shown on the "repeated shift events" slider</comment>
  </data>
  <data name="Split_XBox_Triggers" xml:space="preserve">
    <value>Split xbox gamepad triggers</value>
    <comment>An option in Controls page (combind Throttle+Brake xbox trigger is splitted as two separate axis)</comment>
  </data>
  <data name="Split_XBox_Triggers_Tooltip" xml:space="preserve">
    <value>By default RBR uses xbox gamepad LS and RS triggers as combined Throttle-Brake control. The combined control is very bad in a rally car, because it prevents independent use of throttle and brake. Enable this option to split combined xbox gamepad triggers as separate controls.

See https://github.com/mika-n/NGPCarMenu/issues/15 for more info</value>
  </data>
  <data name="SteeringWheel_FFB_Compatibilty_Mode" xml:space="preserve">
    <value>Steering wheel FFB compatibility mode</value>
  </data>
  <data name="SteeringWheel_FFB_Compatibilty_Mode_ActivateBtn" xml:space="preserve">
    <value>Activate</value>
  </data>
  <data name="SteeringWheel_FFB_Compatibilty_Mode_ActivateBtn_Tooltip" xml:space="preserve">
    <value>Activate the wheel compatibility registry fix</value>
  </data>
  <data name="SteeringWheel_FFB_Compatibilty_Mode_DeActivateBtn" xml:space="preserve">
    <value>Deactivate</value>
  </data>
  <data name="SteeringWheel_FFB_Compatibilty_Mode_DeActivateBtn_Tooltip" xml:space="preserve">
    <value>Deactivate (remove) the wheel compatibility registry fix</value>
  </data>
  <data name="SteeringWheel_FFB_Compatibilty_Mode_OpenRegFile_Tooltip" xml:space="preserve">
    <value>Open the registry file in Notepad for a review</value>
    <comment>A tooltip text of [i] link in Controls page to open FFB registry fix file in Notepad</comment>
  </data>
  <data name="SteeringWheel_FFB_Compatibilty_Mode_Tooltip" xml:space="preserve">
    <value>Some steering wheels may require a compatibility registry options before FFB effects work in RBR.
	
Activate if FFB effects don't work in RBR.
Deactivate if some other game doesn't work when this is activated.

Moza, Simagic, VRS, Cammus, MS-Sidewinder may require this being activated</value>
  </data>
  <data name="SteeringWheel_FFB_Compatibilty_Mode_Tooltip2" xml:space="preserve">
    <value>Steering wheel model.

See rsf_launcher\RSFControlConfig\registry folder for more details</value>
  </data>
  <data name="Steering_wheel_settings" xml:space="preserve">
    <value>Steering wheel settings</value>
    <comment>A title in Controls page</comment>
  </data>
  <data name="Use_Adaptive_FFB" xml:space="preserve">
    <value>Use adaptive FFB effects</value>
  </data>
  <data name="Use_Adaptive_FFB_Tooltip" xml:space="preserve">
    <value>When this option is set then RBR uses more precise and stronger FFB effects (NGP plugin).
AdaptiveFFB works best when VSync is enabled in graphics settings.

Warning. Adaptive FFB effects may cause FPS performance issues in some PCs</value>
  </data>
  <data name="Use_FFB_effects" xml:space="preserve">
    <value>Use FFB effects</value>
    <comment>An option name in Controls page</comment>
  </data>
  <data name="Use_FFB_effects_Tooltip" xml:space="preserve">
    <value>RBR sends FFB effects on the device set in steering control when this option is enabled.
Review also steering wheel vendor specific application to tweak FFB sensitivity settings</value>
  </data>
  <data name="FFB_Deadzone" xml:space="preserve">
    <value>FFB Deadzone range</value>
    <comment>FFB Deadzone percentage from center-to-lock. FFB effects below FFB_DeadzoneThreshold within this range are clipped. See Readme.NGP.txt for more info</comment>
  </data>
  <data name="FFB_Deadzone_Tooltip" xml:space="preserve">
    <value>[decimal] Force feedback deadzone percentage of center-to-lock steering wheel turning range.

FFB effects below the FFB Deadzone Threshold percentage of maximum FFB force are clipped
if the steering wheel is turned within this ffb deadzone range.

0 = No FFB deadzone (default)
1..100 = Percentage of center-to-lock steering wheel range where ffb deadzone threshold is applied</value>
  </data>
  <data name="FFB_DeadzoneThreshold" xml:space="preserve">
    <value>force threshold</value>
    <comment>Force feedback threshold as a percentage of the maximum force</comment>
  </data>
  <data name="FFB_DeadzoneThreshold_Tooltip" xml:space="preserve">
    <value>[decimal] Any FFB effect below this FFB deadzone threshold percentage from the maximum FFB force is
clipped if the steering wheel is turned within the range set in FFB Deadzone percentage. 
For example, 5% threshold value would ignore FFB effect forces below 5% of the maximum ffb force.

0 = No FFB threshold (default)
1..100 = FFB deadzone threshold percentage of the maximum FFB force</value>
  </data>
  <data name="InputRate_ParallelThread" xml:space="preserve">
    <value>Parallel controller input rate</value>
    <comment>The rate NGP plugin keeps polling controller inputs (Hz)</comment>
  </data>
  <data name="InputRate_ParallelThread_Tooltip" xml:space="preserve">
    <value>The rate NGP plugin polls controller inputs in a parallel thread (Hz). The use of parallel thread may improve RBR performance. Maximum rate 1000 Hz.

If a steering wheel and FFB effects don't work then try to lower the rate or disable the parallel thread.

0 = Parallel thread disabled.
1..1000 = Parallel thread enabled and the rate for polling controller inputs (default 1000)</value>
  </data>
  <data name="FFBRate_ParallelThread" xml:space="preserve">
    <value>Parallel FFB effects</value>
    <comment>The rate NGP plugin sends FFB effects to a steering wheel (Hz)</comment>
  </data>
  <data name="FFBRate_ParallelThread_Tooltip" xml:space="preserve">
    <value>The rate NGP plugin sends FFB effects to a steering wheel in a parallel thread (Hz). The use of parallel thread may improve RBR performance. Maximum rate 1000 Hz.

If a steering wheel and FFB effects don't work then try to lower the rate or disable the parallel thread. Some PCs and steering wheels may get stuck if the FFB effect rate is too fast.

0 = Parallel thread disabled.
1..1000 = Parallel thread enabled and the rate for sending FFB effects to a steering wheel (default 1000)</value>
  </data>
  <data name="321_Countdown_Paused_ReleaseKey_Handbrake" xml:space="preserve">
    <value>Handbrake</value>
  </data>
  <data name="321_Countdown_Paused_ReleaseKey_Pause" xml:space="preserve">
    <value>Pause</value>
  </data>
  <data name="321_Countdown_Paused_ReleaseKey_Ignition" xml:space="preserve">
    <value>Ignition</value>
  </data>
  <data name="321_Countdown_Paused_ReleaseKey_Esc" xml:space="preserve">
    <value>ESC</value>
  </data>
  <data name="321_Countdown_Paused_ReleaseKey_Tooltip" xml:space="preserve">
    <value>When 3-2-1 countdown is paused then these key presses continues the countdown</value>
  </data>
</root>