It seems this bug has been fixed in version 2025 R2.00.

Too bad no Zemax staff member is spontaneously reporting about these bugs or about their resolutions (see also this thread). They seem to me pretty noticeable during standard sw use.

Now that I recently upgraded to 2025 R1.00 and faced a number of bugs, I share your frustration ​@Alberto.Donazzan.

​@Allie would it make sense to have a section of the Community dedicated to bugs? I see there’s a tag already: rBug report] but its not obvious how to search this tag and it lacks organization. It would be nice if we could see if the bug is confirmed (by another user perhaps) and fixed. And if it is, at which version was it fixed?

Take care,

David

Hey Alberto,

The Bug Fixes have moved recently to the Ansys Help portal (it would be nice if OpticStudio included these directly in the software like they do with What’s New).  The issue with the Go to surface and Go to operand dialog boxes were marked as fixed in the 25R2:

https://ansyshelp.ansys.com/account/secured?returnurl=/Views/Secured/Zemax/v252/en/OpticStudio_release_notes/OpticStudio_release_notes/topics/bug_fixes.html

To get to any of the Bug Fix reports, once you’re logged into https://ansyshelp.ansys.com, navigate to Zemax OpticStudio, click on the desired release in the upper left corner of the screen, click on the Release Notes link, then click on Release Notes again and then select Bug Fixes

Hello ​@MichaelH ,

thank you for pointing this out to me.

I am not yet used to the Ansys support platform, which, imho, looks anything other than straightforward to a new user. Anyway, I’ve immediately boomarked your links.

​@MichaelH, I have a side question about the online Help file: do you confirm that to access the online Help file I am forced to log in to the Ansys platform every day (username, password, verification code by email) ?

Or is it just me? I find this quite annoying.

Hi all! Thanks for tagging me in this one, David. 

Regarding your question about creating a section for bug reports in the forums, I don’t think that’ll be possible. I am working on re-aligning our forum content with the Ansys web structures, and there isn’t a good place for bug declarations on the Ansys Learning Forums. That said, I agree that we could use a more formalized approach to high-impact active bugs like a UI one. We will occasionally create a post for big bugs on this forum (which is when I implement the Bug Report label) but we don’t have a systematic approach for determining which bugs are worth bringing to the full community. Some options I’ve seen from other Ansys teams are to include them as a small article within ACSS, or to add the information to AnsysGPT. I’ll look into options and connect with the product team to see what we can do.

In the meantime, the most effective way to submit or check on a bug is via a support case. If you purchased your product directly with Ansys, you can create a case via the Ansys Customer Portal (ACSS). If you purchased your product through a Channel Partner, submit your inquiry to them.

For bugs that were fixed, they are available on the Release Notes via the Ansys Help page, as Michael pointed out. We are working on some in-product UI updates to make it easier to access the Release Notes, so stay tuned for that. 

Finally ​@Alberto.Donazzan - regarding your question about the Help file - if you click a question mark inside of the Zemax software, you will be taken to the private version of the Zemax OpticStudio Help. That does require a login through the Ansys SSO system. We maintain a private version of the help in case there is any proprietary or export-restricted data in the docs. A scrubbed and therefore un-restricted version of the Help file is also available here:  Ansys Help. The un-restricted link does not require a login. You should be able to find most of the same data in the public version as the private one at this time. 

Dear Allie, thank you for taking the time to give us some insights about the bug reporting.

Regarding the Help file, personally I find it quite cumbersome to have an online Help requiring to go through such a tedious login process every day. In my opinion the Help file should be part of the software; it must be, as working with OpticStudio would be impossible without it. Being the Help file an essential part of the software, it should be accessible altogether. Why should I have to demonstrate I am an authorized Ansys customer while my OpticStudio instance is already up and running and therefore my paid licence has already been validated through the Ansys servers?

Both the pdf version and the unrestricted online version cannot hold as substitutes, as the link to in-context question marks is completely lost. Imho, the present situation is affecting usability a lot.

I personally see two solutions:

1. Restore the offline chm file.
2. Subject the access to the Help file to an automated OpticStudio licence verification, within the software. 

Of course, I am aware both the above solutions may have related difficulties or weaknesses. Or even, I might be the only OpticStudio user complaining for the present situation.
Thank you for your support.

Hi ​@Alberto.Donazzan - thanks for the reply! Actually, we have heard this kind of request a few times from other users, so I appreciate you taking the time to articulate why you’d like it yourself.

We cannot reinstate the original CHM file, but there is another option we’re working on. Ansys offers an offline help tool via the Download Center. We are working on getting Zemax’s help files installed into that program. Once set up, you should be able to use it in the same way as the original CHM file. It will provide offline & contextual help. 

The work on the offline help is part of the same initiative as the work to make the Release Notes easier to find. I don’t have a release number for that initiative, yet, but I’ll check back in on this thread when it’s released .

Dear ​@Allie,

I am pleased you’re working on a possible solution. I am looking forward to it. 

Thank you

Thanks ​@Allie I’m also looking forward to this one.

Take care,

David