That’s a good point michael…. I think. as for it effecting ray trace speed, there should be no reason for that. If G is a (default) negative 1, then the calculation is local and Zemax knows that. If the G value is some positive integer, then Zemax is flagged that it’s global and there should be no difference between REAY with a G value specified and an RAGY. I don’t understand why inserting another column in the MFE would be a big deal. As for backwards compatibility, it should be fairly easy to handle. Like inserting a surface or something. Just insert the new column in the MFE. Ken once told me that he painted himself into a corner when programming Zemax in a spread sheet type format. He can’t pick up values in a surface larger than the one picking it up, or in a config that’s higher. Like you can’t pick up a value in config 5 from config 2. You can’t pick up a value from surface 20 from surface 4. It’s frustrating. It’s also frustrating to be allowed only one global surface at a ti
Wow, this guy’s really smart. Oh, wait, that’s me.Never mind.But I cringe at all the typos. Sorry about that.Also the wordy explanations of things. I know it’s difficult to follow without images.But that’s to Zemax for giving me the opportunity here. I hadn’t expected this to go public without an edit. Oh well. Proves I’m just human.P
Hi Sven,Thanks for this reply. I hadn't thought of these two solutions, but they make total sense. I will try them.This is my first time on the Community site and I had no idea if I’d get a response or not. Much appreciated.Paul
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.