is this UI sluggishness normal?

[Aram Avetisyan]

Now that almost 80perc. of my materials feature Randomizer and Triplanar, often both in row, that is not nice news. I did want better representation in viewport (just by taking any bitmap in chain), but if it's causing  performance issues now : /

Please check my reply here: https://forum.corona-renderer.com/index.php?topic=41834.msg221045#msg221045

I am sure it was scene/object/material specific, so no worries.
I have bunch of scenes and in 99.9% of them all materials are set with Triplanar, MappingRandomizer combination, many of them with CoronaColorCorrect. The mentioned combination is present for sure. None of them has ever caused slowdowns.

I even, just to be sure, dared to open one of the current production scenes of mine and applied to all objects the mentioned material with bad combination. Guess what - the viewport 40-50fps (heavy scene), with bad combination material became faster.

So, really nothing to worry about. I really believe this was scene specific, as tested and confirmed.

[Juraj]

thanks Aram, good to hear!

[brr]

Now that almost 80perc. of my materials feature Randomizer and Triplanar, often both in row, that is not nice news. I did want better representation in viewport (just by taking any bitmap in chain), but if it's causing  performance issues now : /

Please check my reply here: https://forum.corona-renderer.com/index.php?topic=41834.msg221045#msg221045

I am sure it was scene/object/material specific, so no worries.
I have bunch of scenes and in 99.9% of them all material are set with Triplanar, MappingRandomizer combination, many of them with CoronaColorCorrect. The mentioned combination is preset for sure. None of them has ever caused slowdowns.

I even, just to be sure, dared to open one of the current production scenes of mine and applied to all objects the mentioned material with bad combination. Guess what - the viewport 40-50fps (heavy scene), with bad combination material is became faster.

So really nothing to worry about. I really believe this was scene specific, as tested and confirmed.

Glad to hear that this is a specific case. At the same time, I feel "lucky" because this scene was a part of my work project that I created in Corona 9. Then, I installed Corona 11 and immediately hit this bug.  :-/
Anyway, I hope you can resolve it.

UPDATE: just tested with Corona 11 Hotfix2 and it seems like my bug has been resolved :)
Thanks, Corona-Renderer Team!