OpTaliX Version 8.60

2013-06-16 00:04:44

Note that support of the 7.xx editions (blue Hardlock key, 32-bit only) has expired. This 7.98 update version is the last supported version. Users are encouraged to migrate to the new 8.60 version. This migration is free for users with a valid support license.


New Features in version 8.60:

• OpTaliX has been successfully tested under Windows 8 (both 32-bit and 64-bit). Windows 8 is now an officially supported platform.

• Statistical (monte carlo) tolerancing is now available. This option supplements the sensitivity and inverse sensitivity options.

• The tolerance editor is now a modeless dialog. This means that this editor may stay permanently opened, like other editors as surface editor, zoom editor, coating editor, etc. This allows easier and faster interaction between parameter changes and tolerance analyses.

• Ray data from illumination analysis now also can be exported in binary format. Previously, only ASCII format was supported.

• Schott filter glasses added: BG50, BG55, BG60, BG61, BG62, BG63, BG64

• Schott chalcogenide glasses added: IRG22, IRG23, IRG24, IRG25, IRG26. These glasses are primarily intended for use in the infrared wavelength range between 1 and 12 micron.

• Dn/dT data of private glasses can now be defined and saved. The appropriate dialogs have been extended appropriately. See the main menu under Glass Manager -> Create Melt Glass, or from Glass Manager -> Glass Catalogs, then selct the private catalogue.

• The number of processors used in multi-core systems is now maintained between sessions. Previously, the number of processoer was determined automatically and manual settings had to be done for each session individually. This option can now be set from the OpTaliX main menu under File -> Preferences -> Miscellaneous Tab.


Bug Fixes in version 8.60:

• Ray trace on two-dimensional (gridded) wavefront deformations corrected. Previously, the calculated aberrations were incorrect by a factor 2.

• OpTaliX did not run under Win-8 64-bit. This problem is resolved by an updated Safenet/HASP dongle driver.

• Minor tweaks