Route with Unit of length in feet

The documentation (2012 version) makes it look easy; just use Option.UnitOfLength 0.3048 and Option.UnitOfSpeed 1.609344.  Has anyone out there tried this?  Did the train physics work properly?  Are objects also dimensioned in feet?

I ask because I have a lot of old plans, all dimensioned in feet.

Rogerc

I believe that modifying the units doesn't change the objects as far as I know, only the route file itself.
For instance, using mph instead of km/h makes SpeedLimit.Begin(60); Track.Limit 60 turn out to be 100ish km/h, as it's processed as 60 mph, same with length. 25 m become 82.0209974 ft but you can set the "rail block" to be a nice and round 80 ft. (24.384 m)
Meshes are still in meters unfortunately, no matter how big or how tiny you make your length unit.

We used to use feet and inches in the UK and Ireland all the time. Metrication (use of metric system of weights and measures) began in UK as early as 1965, being phased in gradually. The USA and Burma still use the Imperial (feet and inches) units of measurement. As an older user, familiar with both systems, I find it easier to stick to the metric system for all my BVE building projects, when inches, feet and milles need referencing (mileposts, for example) it's easier to convert these to metric and insert them in the route code.