ME Units (Imperial/Metric)

[Flamin_Squirrel]

Hi chaps.

 

When selecting imperial units in the options menu, this doesn't seem to have any effect when using the mission editor - everything is still metric. Just wondering, is this to remain this way?

 

Thanks.

[nomdeplume]

I'm not 100% certain, but I haven't seen any indication of plans to make this change how the ME displays units. So far as I know, it only affects external views and map information within the simulator itself.

[CrashEd]

Getting the same in th ME here too. Hope this gets fixed/changed as it's a pain having to convert meters to feet ;)

[159th_Falcon]

Getting the same in th ME here too. Hope this gets fixed/changed as it's a pain having to convert meters to feet ;)

Meters to feet is easy.

Divide by 3, or if you know the desired altitude in feet. multiply by 3.

Not that hard.

3000 feet is 1000 meters

 

from Knots to KM/h is a bit trickier though, not sure what the conversion factor is.

[CrashEd]

Meters to feet is easy.

Divide by 3, or if you know the desired altitude in feet. multiply by 3.

Not that hard.

3000 feet is 1000 meters

 

from Knots to KM/h is a bit trickier though, not sure what the conversion factor is.

 

Indeed, but my point is that you shouldn't have to if I've selected 'imperial' ;)

 

I know what you're saying though... :)

[Lange_666]

from Knots to KM/h is a bit trickier though, not sure what the conversion factor is.

 

1 knot = 1.85200 kmh

[asparagin]

Agreed that this would be a usefull feature, especially when the platform is american and imperial units are used (even if I don't like it).

[Duke49th]

If set to Imperial, then all units (ME and Ingame) should be shown in imperial. Same for metric.

 

:thumbup:

[Echonomix]

If set to Imperial, then all units (ME and Ingame) should be shown in imperial. Same for metric.

 

:thumbup:

 

Should, but doesn't.

[kylania]

from Knots to KM/h is a bit trickier though, not sure what the conversion factor is.

 

Google is your friend.

[MBot]

from Knots to KM/h is a bit trickier though, not sure what the conversion factor is.

 

The other way around has a nice rule of thumb. km/h x2 -10% = kts

[Duke49th]

Should, but doesn't.

 

Yes...thats why I wrote should.

 

 

But what i recognized yesterday that I set height to 6000 in ME - and ingame the A-10 startet at 6000 feet.

 

But thats not happend to the speed...its still 500km/h when set to 500 in ME.

 

Now I'm really confused if that is a bug or a not completely implemented feature/change...?

Edited November 14, 2010 by Duke49th

[coolts]

converting metric to imperial is not difficult, HOWEVER, the point of this post is surely that if "imperial" units are chosen from the options then the ME should use "imperial" units and not just the game engine. This has been a limitation of the sim engine for ages. (game engine / sim engine - two different entities)

 

the point is that it takes time to convert for everything. its not a dealbreaker but would be very nice to have.

 

if all the underlying sim code is metric, and it probably is, then we dont need that changed surely, just the text input / output boxes in the ME could have conversion multipliers added to them. thats what i would do. (it works in excel :music_whistling:)

Edited November 14, 2010 by coolts

[effte]

Oh, and while we're at it: Barometric pressure in millimeters of mercury? Not inches of mercury, as in the US, or millibars, as in most of the rest of the world, but millimeters of mercury? Is there actually any place in the world using this peculiar unit?

 

Reminds me of a previous job where I ended up using millimeter-pounds as the unit for force couples, due to customer requirements clashing with equipment manufacturer specifications... uuuugh!

[Flamin_Squirrel]

Oh, and while we're at it: Barometric pressure in millimeters of mercury? Not inches of mercury, as in the US, or millibars, as in most of the rest of the world, but millimeters of mercury? Is there actually any place in the world using this peculiar unit?

 

Seems to be what the BlackShark altimiter is set for, so I guess so!

[Bahger]

Feet to meters is not exactly x3. Close enough for a rough approximation but no good for accuracy. Feet to yards is x3.

[effte]

Seems to be what the BlackShark altimiter is set for, so I guess so!

 

Oh, the horror... :D

[Frederf]

Ah good ol' 760mm mercury, chemistry class!

 

I defend the idea of the ME being in metric. What happens when you're making missions for A-10s and Ka-50s in the SAME MISSION? The ME has to be in the most universal units possible because it's going to have to be one thing for many uses.

 

It would be nice for a "converter tooltip" to pop up during some modes though. It's annoying to have to say "I want 200 KIAS" which means I have to convert to KTAS as this altitude, then to ground speed for wind, then to km/hr finally to put into the waypoint field.

[kylania]

I defend the idea of the ME being in metric. What happens when you're making missions for A-10s and Ka-50s in the SAME MISSION? The ME has to be in the most universal units possible because it's going to have to be one thing for many uses.

 

This shouldn't matter at all. If you place a unit on the map and another x distance away, it doesn't matter if that distance is measured in meters or yards it's the same distance away, the same point that it's at.

 

As for speed, again it shouldn't matter at all. Any given speed is equal to whatever mph/kph/kts. The computer should be able to convert all of that in it's sleep, why should we have to as a mission designer? Set to whatever units you feel comfortable and leave the details to the computer.

 

If you want 200 kts KIAS, set that and leave the whatever mph/kph and atmosphereic conversions to the birds. :) There's simply no justifiable reason not to have multiple values in the ME other than "We just didn't get around to it". It's really just a value display issue. There are no technical reasons for it that can't be solved.

[Bahger]

There are two things about the ME that ideally should not be out of synch, but are. In neither case do I believe a practical justification is possible:

 

- The metric units for altitude where altitude in-flight is measured in feet.

- The different numbering of waypoints, where the ME flightplan is always one WP out of synch with the actual flightplan.

 

Neither is a disaster, and the ME is great, but each require a bit of an uneccessary workaround and are somewhat eccentric design decisions that ought to be addressed in the retail build.

[Duke49th]

This shouldn't matter at all. If you place a unit on the map and another x distance away, it doesn't matter if that distance is measured in meters or yards it's the same distance away, the same point that it's at.

 

It's so easy...if you set in option metric, then the ME shows metric. If set to imperial, then the ME show imperial.

 

If you set any waypoint then it is always the same distance. So I can see no problems why we shouldn't get this "feature"...except the fact that someone has to write a few lines of code.