I have used User-defined DLL (Source DLL) by myself with compiling CPP to DLL. It is working well in 2023 R2 but it can’t be loaded in 2024 R1. Is there some difference in loading DLL? Please let me know if there is someone who has experience. Thank you. Best Regards,Munseok

I’m working on a pair of DLL files. The sag of the second DLL depends on the parameters of the first DLL, plus a few other parameters. What’s the best way to share information between these two user-defined surfaces? Do I need to add pickups for every parameter (manually or via script)? Or is there some way to pass the entire 1st surface as a parameter/argument to the 2nd surface?

The program in the following file assigns random values ​​to the specified Zernike terms. This ZPL works in non-sequential mode but not in sequential mode.Where do I need to modify it to make it work in sequential mode?Lens data is attached in another file.

There is minor typo in the current help file for Zemax OpticStudio. I caught it in the PDF for 2024 R1; however, it is present in the online help file from Ansys as well discussing Numeric Functions.In the description of the obselete STDD() tag for ZPL programming, it references SRPO which does not exist. It meant to reference SPRO.Confirmation that SPRO is correct can be found in @Katsumoto Ikeda’s post here. 

This User-Defined Surface DLL provides a realistic model of relief-type diffractive lenses based on zone-decomposition. Using zone-decomposition, diffraction into multiple orders can be accurately considered at once, and this method inherently accounts for wavelength dispersion and diffraction efficiency by modelling the actual shape of the diffractive element.Application examples include the creation of advanced intraocular lens models, where the different orders are designed to provide sharp vision for multiple viewing distances, thereby substituting accommodation of the natural crystalline lens.This application is discussed in detail in the following knowledgebase article:Realistic modeling of relief-type d

This Source DLL models an Astigmatic Gaussian Source.  It is based on rays but the statistical distribution of rays gives a picture of a diffracting Gaussian beam. It is valid for small angles (paraxial approximation) and when propagating in free space. So clipping at apertures and aberrations will give incorrect results.w0x, w0y are the real beam waist radii (defined at the 1/e2 intensity point) in the XZ and YZ planes. They includes M^2. z0x, z0y are the positions of the beam waist in the XZ and YZ planes. z0<0: in propagation direction if the waist is located before source. M^2x, M^2y are the quality factors in the XZ and YZ planes.For more information, see "Representation of a Gaussian beam by rays" by P. P. Crooker, W. B. Colson, and J. Blau - Physics Department, Naval Postgraduate School, Monterey,

Hello Everyone! During the discussions with the Zemax staff, we came across something that might be useful for everyone. This has to do with working in Python with the ZOS-API. As it is generally known, Python does not have IntelliSense in the same sense as Matlab does. The standard workaround (https://my.zemax.com/en-US/Knowledge-Base/kb-article/?ka=KA-01620 ) has been inserting break points and debugging your code to see the functions and the properties. Below is a different way that can enhance the working speed in Python. However, I should note the following. At the moment of writing this, the method works only with Python 3.8 (Tested on Python 3.8.1). The precise reason for why it doesn’t work in, say 3.7, is not clear to me, but maybe Zemax staff can provide some feedback on this? Anyway, in order to get the method to work, I required the following. As an ID

Fellow ZPL programmers,I want to share some of the tools that I use for editing ZPL scripts and code.I use Microsoft Visual Code Studio to edit the ZPL files.I also use an extension from Hiiragi that enables support for ZPL in VS Code. It provides syntax highlighting and some code completion through IntelliSense.For IntelliSense, I would disable the option “Editor>Suggest: Match On Word Start Only”. This allows you to type “MERIT” and pull up all the tags that contain “MERIT”.Option to enable “Fuzzy Search”Example of Code Completion,

This DLL creates a surface identical to the Extended Polynomial surface, but it allows the user to specify if symmetry should be enforced upon the surface, specifically in the x direction, y direction, x & y direction, or no symmetry (identical to the typical Extended Polynomial surface).The source code is not shared.Author: Dominique ‘Nikki’ GalvezDownload SymExtPoly.DLL Here Date Version OpticStudio version 2024/08/15 1.0 24.2

I have a couple scripts I began writing a few software versions ago on Zemax 21.2 and MATLAB 2020b. These were Zemax Zos-API MATLAB scripts that performed a large number of direct unpolarized ray traces. I have noticed that since updating my software to Ansys Zemax Opticstudio 2024 R1.03 and MATLAB R2022b there seems to be a fairly substantial performance hit. Has anyone else noticed this? Have there been changes to the way the ZOS-API functions that I need to implement in my scripts post update? 

https://support.zemax.com/hc/en-us/articles/1500005576822-Rotation-Matrix-and-Tilt-About-X-Y-Z-in-OpticStudio is misleading.OpticStudio uses degrees for Tilt About X/Y/Z, and this graphic suggests using theta_x = tilt about x. Tilt about X is in degrees, but theta_x should be in radians. If you do as the graphic suggests and plug in degrees, you'll get the wrong rotation matrix.Please let me know if I'm wrong here.

Dear community,I am wondering how the zemax calculate the power of ray, which comes out of the DLL surface (RCWA model for a grating). In the DLL, data [30] represents relative energy of the ray. Here I assum it is diffraction efficiency, which is power flow. Besides, the output electric is also required to give in data [40-45]. Based on my test, the zemax detector seems to calculate the energy of the ray from DLL based on its square module of electric field instead of diffraction efficiency. However, when the diffraction efficiency of first order of light is high, e.g. 99.9%. The square module of electric field is usually larger than 1 because the k-vector changes. Therefore, I have normalize the electric field and multiple square root of the diffraction efficiency to achieve the right number on detector, which is contradictory to the law of wave propagation. Besides, If I did this, the detector energy will change again when this ray from DLL interact with next surface, whic

In the API command ReadNextSegment, is pathLength = optical path length or physical path length?ReadNextSegment (out int segmentLevel, out int segmentParent, out int hitObj,out int InsideOf, out double X, out double Y, out double Z, out double L, outdouble M, out double N, out double exr, out double exi, out double eyr, outdouble eyi, out double ezr, out double ezi, out double intensity, out doublepathLength) Where is the documentation on this?Is there a way to select optical or physical with this command?

I have known that using command ‘ZOSAPI.TheSystem.NCE.InsertNewObjectAt(i)’can realize the function ‘Insert Object’, then I tried some commands but still cant find corresponding one for ‘Insert Object After’.The other similar question is similar. I have known that using command ‘Det_Set1.ShowAs = ZOSAPI.Analysis.DetectorViewerShowAsTypes.GreyScale’can realize the function‘ can realize the function of setting ‘Show As’as ‘Grey Scale’, then ‘InverseGreyScale’and ‘CrossSectionRow’ dont work for corresponding functions.

I have set the ‘Scatter To Method’with the commond ‘...ScatterToData.ScatterToMethod = 1’, then I wanna set the Ray data as shown in Fig. 1, but I failed to call the function ‘SetRayData’.According to the Ansys Developer Guideline as shown in Fig. 2/3, it doesnt give more details, I have tried to infer corresponding code but cant work.Fig. 1Fig. 2Fig. 3

If I have a 2D array e.g. 10x2  A(x,y), what’s the syntax to extract one column (or row) in that array so that it’s a 1D array?I’ve tried:col = A(1:10,3)col = A(:,3)

Hi, I am writing a user-defined scattering dll. I know that Zemax allows users to implement the wavelength shift during the scattering simulation (by specifying a certain shifting ratio in the dialog),  However, my application requires more complex way for determining the wavelength shift, so is it possible that I define the wavelength shift directly in the self-written dll file? If yes, how could I do that? Thanks a lot in advance! 

Hi all,I am facing an issue when using the Image Simulation tool via the ZOS-API. The goal is to vary a certain variable in a loop (in this case the object distance), perform each time an image simulation, and save the image with a specific name to a file. However, I notice that the previous images are always overwritten when a new image is saved.This is the simple MATLAB code that I am using in the main body:sampleDir = 'D:\Zemax OpticStudio\';testFile = System.String.Concat(sampleDir, '\Test_ImageTelecentric_Issue.zos');TheSystem.LoadFile(testFile,false);TheSystem = TheApplication.PrimarySystem;TheLDE = TheSystem.LDE;zline = 0;surface = TheLDE.GetSurfaceAt(zline);zvec = [1100,1500]; %variable object distancefor z = zvecsurface.Thickness = z;index = 3; %existing Image Analysis window with correct set

Hello, Currently I have a program in MATLAB ZOS-API that involves a light source that is shining on an array of detector rectangles. The purpose of the for loop is to tilt the X and Y component of the light source then read out the total power from each detector. The problem I am having is how to extract the data efficiently without opening a new detectorviewer each iteration. Currently I am having the for loop run a new ray trace as well as a newanalysis command which I believe is responsible for opening a new detectorviewer each iteration. Ideally the code would just update one detectorviewer or not open one at all to save me computing time. I will attach a snip of my current for loop where I believe the problem resides. I have tried to follow along to this link: Methods for extracting detector data throug

I am rather new in the field of creating Macro. I am trying in a Macro to introduce a Ray tracing. I need to select the ray that I want to display. This function is done with Filter String is the normal use of Zemax. I could i use a filter string in the macro. Is there something special to carry. 

Hi Zemaxers I am trying the python sample code of ZOS-API (as attached below). But it does not work at the first step.https://support.zemax.com/hc/en-us/articles/4403605141267-Generate-the-executable-in-Python-for-ZOS-API-User-Extensions The error shows as belowAttributeError: 'PythonStandaloneApplication' object has no attribute 'TheApplication'(after checking the zemax install root , I guess it has something with 'TheApplication'  attribute) Environmentpython 3.10PyCharm Community Edition 2022.1Ansys Zemax OpticStudio 2024 R1.03pythonnet version 3.0.3

to_surf = TheSystem.LDE.NumberOfSurfaces-1; Ex=0;Ey=1;phaX=0;phaY=90;waveNumber=2;Hx=0;Hy=0;Px=0;Py=1; raytrace = TheSystem.Tools.OpenBatchRayTrace(); [success,errCode,exro,exio,eyro,eyio,ezro,ezio,intensity]=raytrace.SingleRayNormPol(ZOSAPI.Tools.RayTrace.RaysType.Real,Ex,Ey,phaX,phaY, to_surf, waveNumber,Hx,Hy,Px,Py,0,0,0,0,0,0); Open the batch ray trace tool Create polarized real raytracing in which a single ray with normalized pupil coordinates will be added waveNumber=2;Hx=0;Hy=0.5;Px=0;Py=0.5; raytrace = TheSystem.Tools.OpenBatchRayTrace(); [success,X,Y,Z,L,M,N]=raytrace.GetDirectFieldCoordinates(2,ZOSAPI.Tools.RayTrace.RaysType.Real,Hx,Hy,Px,Py) Open the batch ray trace tool Get direct field coordinates with inpu

Within the API, we are able to quickly pull Peak Irradiance, Total Power, and Total Hits by using the property GetDetectorData as described in the forum post 'Methods for extracting detector data through the API.' However, this property will not take into account an applied ZRD file. We can apply a ZRD file to a Detector Viewer window, so is there a way to extract the same information from there?

Hello, I would like to save graphical plot in detector viewer into a picture file by ZOS-API.I looked at some similar questions in community but most of those tell that “get numerical data and draw a plot using the numerical data” or “that feature is in request” 1 year go.So, I am wondering if that feature is implemented already or not.To me, GUI already has that feature and hence it seems that if there is a function in ZOS-API  to call that feature in GUI, it gets the job done.  Does anybody know that? RegardsKazu 

NOTE (added 2/5/2024): A new version of the DLL is now available, so I have deleted the older one supplied with the posting below.  Please see this link for latest version:Ray-tracing model of a perfect lens compliant with Fermat’s principle: the Cardinal Lens ***********************Attached is a user-defined surface DLL that functions as an ideal thin lens obeying the Abbe sine condition.  It is distinctly different than a paraxial lens surface and is particularly well-suited for simulation of high-NA objectives.  The Ideal Lens surface requires two user-supplied parameters, namely the effective focal length and the paraxial magnification at wh