Yes, please fix this! I’m getting tired of continuously opening a new NSC Shaded Model windows when the current one becomes non-responding. This has been going on for quite some vesions now…

/Hans

Zemax management seems to let some bugs linger, like dangling a carrot in front of us, hoping we’ll continue to pay for updates that fix the bugs.  That’s not how Ken Moore would have handled them.  This new optics code from Quadoa at https://www.quadoa.com/index is beginning to look like a good alternative.

Yeah, Quadoa definitely seems attractive with its modern look and the possibility to simply select en element simply by clicking on it, as opposed to some “spreadsheet-based” optical design software…

Have you tried it yet?

After testing QUADOA for a month, I was thoroughly impressed with its modern feel and responsive GUI, especially when compared to Zemax. The multi-sequential ray tracing feature stood out to me as it allows for defining multiple paths through the same set of optical elements, which is much more convenient than Zemax's multi-configuration feature. Additionally, QUADOA offers excellent import/export options for Zemax and Code V, and the Python interface is easily accessible and user-friendly. I found the support team to be swift and always helpful via email.

Sounds great! Are you sure you’re not affiliated with them in any way? 

:D No, I am certainly not. I would still like to see them succeed and grow their customer base. More competition in the market for optics design software would be beneficial for us users. 

Hi Mike, Hans, Benjamin, and everyone following this thread,

I hope you’re doing well! In regards to this discussion thread, I wanted to reach out personally to make sure we fully understand the issue you've been experiencing with the NSC Shaded Model. It sounds like it’s been causing quite a bit of frustration, and we want to make sure we have all the details to investigate it properly.

Could you provide any additional information about when the issue occurs or any specific actions that seem to trigger the non-responsiveness? In the future, please make sure issues like this are reported to our ACE team or through your channel partner, so it can be tracked and prioritized. We rely on those reports to ensure issues like this get the attention they need.

Last year, we made a commitment to be more transparent about our development efforts, including addressing bugs and improving the overall user experience. Alongside new features, our team has been working hard on fixes—especially those impacting users like yourself. More than half of the resolved items in recent releases have been customer-reported bugs. In short, we are striving to make good on our promises, and customer feedback is key to that effort.

I appreciate your patience, and if there’s anything else you'd like to share about your experience, feel free to reach out directly!
 

I guess it would depend on the complexity of your 3D model to view in the shaded model. I noticed it tends to be slow to update when the 3D object is complex or consists of lots of parts.

I’m glad you posted.  I thought my graphics card was dying, but it’s probably fine.