CALYPSO 2024 - Patch 7.8.0605 Released on ZEISS Portal

[[Lu...]]

Hello All,

Figured I'd start a post announcing the release of the latest CALYPSO 2024 Patch. At times, the release of Service Packs and Patches can fly under the radar. What better way to get the word out than on the CALYPSO forums!

Patch 7.8.0605 was released on the ZEISS Portal as of 9/17/2024. Here is the latest change from the release notes:

Full release notes can be found on the ZEISS Portal in the Download Center.

I also wanted to post a list of other recent releases that may have gone unnoticed over the last couple of weeks/months:

If this type of post is something you would like to see more of in the future, please let us know. 😃

[[Je...]]

Please sign in to view this quote.

.

Thank you, Lucas! We appreciate the work put into patches and post-release support. We also appreciate that you took the time to keep users informed.

.

[[Lu...]]

Here is a link to the patch - https://portal.zeiss.com/download-cente ... 39627[P]/#

[[Ch...]]

Thanks for the update.

I'm subscribed to receive updates from the portal - I use to to get dame day notifications, now it seems delayed by about 3 days or so.

Cheers !!

[[Da...]]

Is the installation risky? Message from the portal:
Installing only according to consultation with SW-Support!

[[Wo...]]

I'm not sure if risky, but there will probably be some undiscovered bugs.

For example, for me, after installing .03 patch there was an issue with switching units between inches and metric in Measurement Plan Editor features. Had to roll back to the previous version.

[[Za...]]

Please sign in to view this quote.

Installing Service Packs are safe for install for everyone all upon release. However, you should only install a patch if instructed to do so by a Zeiss employee.

[[No...]]

Please sign in to view this quote.

That's standard legalese that comes with all patch releases.
The reason is that service packs are thoroughly tested before release, while patches are not.

[[Je...]]

Please sign in to view this quote.

This was identified and fixed with Patch #.05