Thank you for your response. However, I believe this is a different issue from what you mentioned.
I have been using FDTD consistently since the 2019 version, and this issue suddenly occurred after upgrading to the 2024R2 version. As mentioned in the subject, this seems to be a bug.
Even when trying to change the position of the source in the example linked below, the problem persists.
https://optics.ansys.com/hc/en-us/articles/360042358574-CMOS-image-sensor-Angular-response-3D
When I attempt to change the z position of the source from the original 3.8 um to 3 um, the edit window does not properly accept the input due to the bug. However, when using scripts to make the change, it works correctly.
I would like to reiterate that this seems to be a bug. Not only am I experiencing this issue, but people around me are also encountering it after the version upgrade.
You are navigating away from the AIS Discovery experience