You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have been using the v2 ArtEngine recently and discovered an issue with a fairly complex setup that requires multiple edge-cases (in our case we have a pose that inherits from separate skin and armour palettes).
The issue appears to be related to this break; in the ImageLayersAttributesGenerator which stops the loop from continuing and being able to find 2nd/Nth matching constraints.
I commented out the value in my local version to test and have confirmed that removing it means both of our edge-cases are matched, however this is less efficient as its potentially looping through unnecessarily for items that only have single edge-cases, so I'm not sure whether you want to accept the performance hit of the unnecessary looping or try and refactor it.
Cheers, Rhys.
The text was updated successfully, but these errors were encountered:
Hi,
I have been using the v2 ArtEngine recently and discovered an issue with a fairly complex setup that requires multiple edge-cases (in our case we have a pose that inherits from separate skin and armour palettes).
The issue appears to be related to this
break;
in the ImageLayersAttributesGenerator which stops the loop from continuing and being able to find 2nd/Nth matching constraints.I commented out the value in my local version to test and have confirmed that removing it means both of our edge-cases are matched, however this is less efficient as its potentially looping through unnecessarily for items that only have single edge-cases, so I'm not sure whether you want to accept the performance hit of the unnecessary looping or try and refactor it.
Cheers, Rhys.
The text was updated successfully, but these errors were encountered: