DorsalVR throws FormatException upon parsing default.yaml

[ShadF0x]

Device: Oculus Quest 2
OS: Windows 10
OpenXR: SteamVR
Player.log: https://pastebin.com/uuWUA1Lj
default.yaml:

%YAML 1.1
---
imports:
- Jaitsu/Jaitsu.yaml
...

with paths in Jaitsu.yaml (from #3) appropriately changed.

Upon opening, DorsalVR acts "dead": grey screen, motion controllers do not show up, Dolphin doesn't launch.

Logs don't really have anything in them save for an exception that I haven't seen in any other existing issue:

FormatException: Input string was not in a correct format.
  at System.Number.ParseSingle (System.String value, System.Globalization.NumberStyles options, System.Globalization.NumberFormatInfo numfmt) [0x00083] in <a1e9f114a6e64f4eacb529fc802ec93d>:0 
  at System.Single.Parse (System.String s, System.Globalization.NumberStyles style, System.Globalization.NumberFormatInfo info) [0x00000] in <a1e9f114a6e64f4eacb529fc802ec93d>:0 
  at System.Single.Parse (System.String s, System.IFormatProvider provider) [0x0000c] in <a1e9f114a6e64f4eacb529fc802ec93d>:0 
  at System.Convert.ToSingle (System.String value) [0x0000f] in <a1e9f114a6e64f4eacb529fc802ec93d>:0 
  at Dorsal.Config.ConfigLoader.GetYamlFloat (YamlDotNet.RepresentationModel.YamlNode node, System.String key, System.Single previousValue) [0x0002e] in <c1939bff818e47efb15506d969299875>:0 
  at Dorsal.Config.ConfigLoader.GetYamlVector3 (YamlDotNet.RepresentationModel.YamlNode node, System.String key, UnityEngine.Vector3 previousValue) [0x00051] in <c1939bff818e47efb15506d969299875>:0 
  at Dorsal.Config.ConfigLoader.ParseSingleDocRoot (YamlDotNet.RepresentationModel.YamlMappingNode docRoot, System.String currentMode, System.Collections.Generic.Dictionary`2[TKey,TValue] modeConfig) [0x005ff] in <c1939bff818e47efb15506d969299875>:0 
  at Dorsal.Config.ConfigLoader.ParseYamlString (System.String yamlString, System.Collections.Generic.Dictionary`2[TKey,TValue] modeConfig) [0x0010b] in <c1939bff818e47efb15506d969299875>:0 
  at Dorsal.Config.ConfigLoader.ParseYamlFile (System.String yamlPath, System.Collections.Generic.Dictionary`2[TKey,TValue] modeConfig) [0x0000a] in <c1939bff818e47efb15506d969299875>:0 
  at Dorsal.Config.ConfigLoader.ParseYamlString (System.String yamlString, System.Collections.Generic.Dictionary`2[TKey,TValue] modeConfig) [0x000ab] in <c1939bff818e47efb15506d969299875>:0 
  at Dorsal.Config.ConfigLoader.ParseYamlFile (System.String yamlPath, System.Collections.Generic.Dictionary`2[TKey,TValue] modeConfig) [0x0000a] in <c1939bff818e47efb15506d969299875>:0 
  at Dorsal.Config.ConfigLoader.ParseYamlString (System.String yamlString, System.Collections.Generic.Dictionary`2[TKey,TValue] modeConfig) [0x000ab] in <c1939bff818e47efb15506d969299875>:0 
  at Dorsal.Config.ConfigLoader.ParseYamlString (System.String yamlString) [0x00016] in <c1939bff818e47efb15506d969299875>:0 
  at Dorsal.Config.ConfigLoader.ParseYamlFile (System.String yamlPath) [0x00019] in <c1939bff818e47efb15506d969299875>:0 
  at SettingsManager.OnEnable () [0x00093] in <c1939bff818e47efb15506d969299875>:0 

[ShadF0x]

Changing "Date, time and regional formatting" in Windows' region settings from what I used to "English (United States)" fixed the issue.

Upon further inspection, a similar issue has already been mentioned in #17.