destination: number (elmos, or radians)
speed: number (elmos, or radians per second)
In my animation I have this:
Code: Select all
Turn( lll, x_axis, -5, 5 )
Thanks in advance.
Moderators: MR.D, Moderators
Code: Select all
Turn( lll, x_axis, -5, 5 )
usfags doing it wrong again!!1Forboding Angel wrote:Uhh, when you select a building to place and it has that grid below it? one of those little squares is an elmo.
Double wrong.when looking at a metalmap texture, 1 pixel = 8 elmos ;p
Uhh, when you select a building to place and it has that grid below it? one of those little squares is an elmo.
yes it is incorrect.AF wrote:1 footprint unit == 1 elmo == 8 or 16 pixels.
This is incorrect.
1 elmo = 0.37 meterSinbadEV wrote:Historically we adopted the "elmo" as a unit of measure because it didn't mean anything... the reason is to avoid games being tied to a specific interpretation of scale...
[Citation Needed]zwzsg wrote:1 elmo = 0.37 meter
That only applies to games using the same scale as TA... in Kernel panic I imagine 1 elmo is closer to a nanometer and in spring 1944 (or whatever) it would be closer to 1 metre.knorke wrote:link in the link first posted
AF wrote:Garh its all todo with the basic unit measurements of spring, e.g. heightmap squares and the smallest unit footprints.
Because the units OTA had didnt map onto the 1pixel scale of spring, 1 footprint unit == 1 elmo == 8 or 16 pixels. There's a #define in the engine which has this value, and is used everywhere in the engine.
For convenience the SYs aligned building placement to rounded elmo values, although this is merely a UI thing as any AI can ignore that and place where it likes
This is incorrect.