Skip to main content

ZOF and SAB files are used to speed up model loading when using large CAD (e.g. STEP) files. According to the user manual, the original STEP files should be shared with the model, and ZOS will automatically pick up the ZOF/SAB file, if present, to speed up loading. Makes sense.



However, in the ZMX file, the ZOF / SAB file is referenced. For ZOF files, it doesn't hurt: if ZOF file is missing, ZOS will still use the STEP file.



However, if the newer SAB file is used, and my colleague is not using one of the recent ZOS releases (common in corporate environment), their ZOS doesn't know what to do with the SAB extension and doesn't understand that it should read the STEP file instead.



Since saving the filename in ZMX with this extension shouldn't, by design, have any impact on the loading speed, the proposal is to use the original file extension (STP in this case) always. It is a future-proof solution.



Am I correct in this thinking, and can we have such feature please?



P.S. Is there a common way to tag feature requests on this forum? It would be nice to be able to search for existing feature requests (until we have a proper feature request tool that it ;))

Hi Kotja,



Saving the ZOF/SAB saves a lot of time on program load as the raytraceable object itself is saved, not the CAD file used to define it. Any clever coding to load the STP if the SAB wasn't available would only be available to someone who is using the latest code, so the best solution is to get your colleague on the latest ZOS so he/she can use the new CAD libraries the dev team lovingly installed :-)



Mark


Reply