Uploaded June 2016 | Updated September 2026, 1 week ago
This issue has been resolved. It turned out that the Liquid Crystal profile in our software was corrupted. So, we were running the "default SLA" profile. What we did to resolve it, was to grab another CW zip package and replace the corrupted profile. Next, we selected the Liquid Crystal profile.
This issue has been resolved. It turned out that the Liquid Crystal profile in our software was corrupted. So, we were running the "default SLA" profile. What we did to resolve it, was to grab another CW zip package and replace the corrupted profile. Next, we selected the Liquid Crystal profile.










