# Perspective View Shows Bad Quality Randomly

**URL:** <https://forum.inductiveautomation.com/t/perspective-view-shows-bad-quality-randomly/111031>\
**Category:** Ignition\
**Tags:** perspective\
**Created:** [September 26, 2025, 11:58pm UTC](https://forum.inductiveautomation.com/t/perspective-view-shows-bad-quality-randomly/111031 "2025-09-26T23:58:09Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![nminchin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nminchin/32/6911_2.png) [@nminchin](https://forum.inductiveautomation.com/u/nminchin)\
**Post date:** [September 27, 2025, 12:11am UTC](https://forum.inductiveautomation.com/t/perspective-view-shows-bad-quality-randomly/111031/2 "2025-09-27T00:11:19Z")

</div>

This is likely the same issue as in **[this topic](https://forum.inductiveautomation.com/t/flex-repeater-instances-sometimes-initialize-null-values-embedded-view/92867/18)**

It's to do with deep nesting of embedded views, where the deeper you go, the less likely all of your embedded views will receive your passed parameter values due to race conditions beyond our control. It's worse when you are using complex data types for your params (objects [dicts] or arrays). It's unfortunate, but the best way to protect against this is to keep your nesting levels to 2-3 layers deep, and to use simple `value` data types for your params, until the bug is fixed by IA

---

_[View the full topic](https://forum.inductiveautomation.com/t/perspective-view-shows-bad-quality-randomly/111031)._