Image.addLayerPaintStamp not respecting w and h grid unit scaling.

[SilentRuin]

The addLayerPaintStamp does not respect the w=5, h=1 dimentions as it does when manually doing the layer paint stamp of the asset through the right hand map controls. I can see no reason why this function is not respecting this scaling - it should be the exact same functionality.

      Image.addLayerPaintStamp(sPath, nLayerID, { asset=sAttackAsset, w=5, h=1, x=x, y=y});

this was 25ft long 5ft wide asset layer and is about that dimension in raw assets - places fine from map layer controls but not in lua call of this function.

[POST EDIT]
Actually it does seem to work - just not all the time. Seems wierd but maybe I should hold off on this. Sometimes it does not respect them - other times it does - different numbers? Not sure but I supposed I retract it not working. Its "sort of" working.

[superteddy57]

Moon is currently away on vacation, but I will pass it along to him to review when he gets back.

[SilentRuin]

Verified flaky on when it actually applies the scaling. It "seems" to work most times but for sure fails to at others. Looks like a timing issue. I doubt I can duplicate it reliably you will have to look at the code and see if something appears obvious.

[SilentRuin]

I thought making that call an OOB (as pointless as that sounds) would maybe get rid of the flakyness, but that just made it fail 100% of the time to do scaling. Maybe that can help them debug it as kicking it off as OOB makes it never respect scaling.

[SilentRuin]

Further testing with OOB shows it is basically just as random flaky on scaling as calling directly. I'll stick with OOB as players need to trigger this. Gist is something timing is wrong. Sometimes it works constantly but more often than not after immediately coming up it randomly fails to scale.

[SilentRuin]

Even more testing and I find that Cloud (which I never use) can have players literally not only lose scaling but lose the layer updates completely. I stick to LAN and only have player get scaling loss issues about 50-80% of the time.

[SilentRuin]

This is interesting. A .PNG asset always works - scale is always correct. Only the webm (VP8) have the random scaling failures or general failure to appear. That should narrow it down for you. As to duplicate I'd have to give you an extension that calls the layer with all the magic.

[SilentRuin]

This video at the time linked in shows how .png assets always get scaled correctly and webm (VP8) is hit or miss. No pattern I've recognized.

https://youtu.be/LoN6PGeeVhg?t=147

[SilentRuin]

Inteface.getAssets is undocumented.

[pindercarl]

This video at the time linked in shows how .png assets always get scaled correctly and webm (VP8) is hit or miss. No pattern I've recognized.

https://youtu.be/LoN6PGeeVhg?t=147

I'll chat with John when he gets back from vacation. The dimensions of a Webm file aren't known until the first frame is loaded. All of the image functions have a callback to set the scale after the image is loaded. The API functions looks to be setting the scale first.