OpenXcom Forum

Modding => Help => Topic started by: robin on December 23, 2019, 11:22:26 pm

Title: standHeight vs floatHeight
Post by: robin on December 23, 2019, 11:22:26 pm
I have a doubt.
The total height of the unit is standHeight + floatHeight..? yes they are it seems.
Or maybe floatHeghit simply represents the "empty" part of the standHeight value?
For example: with the following I wanted to define a 10-high unit standing at 10 from ground (which means the top of the unit is at height=20):

    standHeight: 10
    floatHeight: 10

Or should i set:
    standHeight: 20
    floatHeight: 10
?
  # setting this is not allowed

Edit:
Alright they are summed. But then the selection arrow on the unit is drawn in the wrong position. It seems to me that floatHeight is not taken into account to calculate the arrow positioning. Which means, in units with large floatHeight and small (relatively) standHeight, such in this case, the arrow is drawn on top of the unit itself. Pretty ugly.

Title: Re: standHeight vs floatHeight
Post by: Docent on December 24, 2019, 11:49:25 am

But then the selection arrow on the unit is drawn in the wrong position. It seems to me that floatHeight is not taken into account to calculate the arrow positioning. Which means, in units with large floatHeight and small (relatively) standHeight, such in this case, the arrow is drawn on top of the unit itself. Pretty ugly.

Maybe this means that heights are not added to each other?
From the descriptions of the Ruleset Reference, I would draw just that conclusion.

upd: And, I understand, it swears if you try to create a unit with a standHeight of 20 and a floatHeight of 10? He says that in total, these two indicators can not be more than 23, 26? Then - yes, it is strange.
upd2: Alien Drone in FMP with standHeight: 11 and a floatHeight: 12 looks normal and no problem with the arrow... maybe if you make standHeight: X and a floatHeight: X+1 - everything will be fine?
Title: Re: standHeight vs floatHeight
Post by: Meridian on December 24, 2019, 01:17:04 pm
Edit:
Alright they are summed. But then the selection arrow on the unit is drawn in the wrong position. It seems to me that floatHeight is not taken into account to calculate the arrow positioning. Which means, in units with large floatHeight and small (relatively) standHeight, such in this case, the arrow is drawn on top of the unit itself. Pretty ugly.

Will be fixed.
Title: Re: standHeight vs floatHeight
Post by: robin on December 24, 2019, 05:29:56 pm
upd2: Alien Drone in FMP with standHeight: 11 and a floatHeight: 12 looks normal and no problem with the arrow... maybe if you make standHeight: X and a floatHeight: X+1 - everything will be fine?
For me it still looks wrong with those values.
Will be fixed.
Thanks.