HiCan you please help me to set the “Field Height” in image simulation feature.I wish to use the image simuation feature in Wide angle sysyem, lets take for example “Wide angle lens 210 degree field.zmx” file in Zemax examples subdirectory \Sequential\Objectives. For a source file I took the file “Demo Picture 640X480.bmp”What should be the Field Height in this case? The digonal field 105 degrees? or the full Horizonatl field in degress? I wish that Horizontal field to much the Height of my detectorWhen I turned on the feature, the deafult Field Height parameter is 148 degress ? Why?I found this link:https://optics.ansys.com/hc/en-us/articles/43071095752467-How-to-set-up-Image-Simulation-toolbut still, I dont understand what Field Height parameter should I use.Thanks,Talimu

Hi all,I think I found a bug in the RMS wavefront error plotting tool - initially saw it in the 2025 R4 version, but I downloaded the latest 2026 R1 and it’s still there.I was working through some analysis and noticed a discrepancy in the RMS wavefront error values reported on the plot vs evaluation in the merit function. As seen in the example below, the merit function operand RWCE was reporting a fairly different value compared to the plot. Initially I assumed this was due to sampling, but the difference persisted (I also tried comparing rectangular array vs Gaussian quadrature). Next, on a whim, I evaluated the RWCH (chief ray reference) operand and noticed it did match the plot value, which I found odd, because the default for the plot is to reference the centroid. Looking closer at the plot, I noticed that although Centroid is selected as the reference in the settings, the title block reports “Reference: Chief Ray”. Likewise, when Chief Ray is selected in the settings, the plot sh

Hello all, I have a model of the objective, from the supplier as well the lens and wavefront data with Zernike values.The Zernike coefficients in the model do not match the values in the measurements which I assume comes from the manufacturing and assembly tolerances.I want to use the optimization function with the lens dimensions as variables, including tilt and decenter and use the optimization process to reach the dimensions and other parameters that yields similar Zernike values as the measurements.I set up the Zernike polynomial operands with the wavelength and other settings. Use the values of the different Zernike coefficients that I want to reach as “targets” in the editor but when running the optimization, I am far off from the values where I want to be. Am I making a mistake in setting up the operands? Or am I underestimating the complexity of what I want to do, and it will not be feasible?Measured valuesMerit function editor setup​​​​Has anyone performed such an analysis bef

I need the L,M,N values for vectors normal to plane surfaces in non-sequential mode.  I have tried many different ways, and just haven’t found the magic decoder ring yet.  How can I get surface normal components for plane faces on objects in non-sequential mode?

Hello,I would like to model the propagation of a polarized light beam through a biaxial crystal.While methods for uniaxial crystals seem to be well established, I am unsure how to approach this problem for biaxial crystals.How do I handle this case?Thank you very much for your help.Best regards,Dirk

An error message is popping up which states: An entry with the same key already exists. I am curious why this error is occurring and what I can do to mitigate.Specifically, this error occurs when I perform a tolerance analysis with a single tolerance operand. I am using the TEZI operands to tolerance the surface form of a conical mirror, and if I only include zernike polynomial 5 (by setting Max# = 5 and Min# = 5). Furthermore, the error only occurs if the tolerance analysis criterion is set to Merit Function and when the RSRE operand is used in the Merit Function. Lastly, I did try to recreate this error on a simplified zemax model made from scratch, and was not able to recreate, which is quite unfortunate. It therefore seems somewhat tied to the specifics on my model. Regardless, I am hoping that understanding where this error comes from may give a hint as to what is happening. Adam