Hi Sandrine,

Thanks for your reply. Somehow, when I try to run the macro and then load the cfg file, the ray density setting didn’t change. For example, if I do the following:

• set FOO_RAYDENSITY to 2,
• save the macro,
• run the macro.

I can see the corresponding cfg file is updated. However, when I click the load button, the Ray Density remains at 200.

Am I missing any step?

Hi Sandrine,

Thanks for the reminder. I found the CFG file associated with the file and deleted it. Now the Ray Density is updated every time I click the load button.

Meanwhile, I have the following findings:

1. if I set FOO_RAYDENSITY a value above 39, the Ray Density displayed in footprint diagram settings is not updated.
2. If I set FOO_RAYDENSITY a value above 39, the actual number of rays traced continue to increase.

For example, I see significantly denser rays plotted if I set FOO_RAYDENSITY to 200, and it takes noticeably longer time to generate the plot compared to a setting of 39. I think it is indeed tracing a grid of 2011 x 2011 rays. Meanwhile, the dropdown menu still shows 15 (FOO_RAYDENSITY = 2), which is the previous setting I tested.

It seems that using the macro or ZOS-API, I can continue to increase the ray density. That brings back the original question: What’s the upper limit of the FOO_RAYDENSITY setting? Maybe there isn’t a limit as long as the computer can run?

Hi Yuan! I got a confirmation from the developers and the Footprint calculation code does not have a limit on the maximum ray density. The interface has a limit because a combo box is used to enter the value. But through the API or ZPL any value can be entered. So be careful when you select a value as a high value can lead to very long calculations.