Seeking beta testers for Coreform Cubit 2025.8 release candidate

Looking for beta testers!

We’re pleased to announce a release candidate for the next version of Coreform Cubit, which we anticipate releasing in August. This next release has several major infrastructure changes that we’re rigorously testing. Due to the significance of these changes (detailed below) we’d like to allow the Coreform community an opportunity to test the release to ensure we’ve not missed anything critical to your workflows.


Getting the release candidate

Here are the latest links for downloading the release candidates for your operating system. I’ll be updating these links as we push out more bug-fixes, as you report bugs it will be helpful if you include the full version number (e.g., 2025.7-rc+61215) in addition to your operating system:

As a reminder, while we only officially support Windows 10/11, Ubuntu 20/22, and Rocky 8 this simply means those are the versions for which we have full CI/CD pipelines. The Ubuntu and Rocky packages will probably work for most Debian or RedHat (respectively) Linux flavors over the last five years – see the README in the HPC download link for possible system packages that you might need to install if you’re running a minimalistic Linux such as Arch Linux.

If you need licenses, see the bottom of this message for instructions!


Major features preview & testing guidance

GUI library upgrade: Qt5 → Qt6

This is probably the largest, most complicated upgrade in this release candidtate. Some of you are probably aware that the Coreform Cubit GUI is based on the Qt Framework, the latest version of which is Qt 6.9. Coreform Cubit has been on Qt 5 for quite some time, but Qt 5 is in its “End of Support” stage. We’re excited about this upgrade as it will allow us to provide a slew of new capabilities to users in later releases and provides improved support for modern desktops.

How to test:

We encourage testers to really hammer on the GUI to see if you notice any critical issues that slipped through the cracks!

New, scalable, icons

Many of our users have high-density pixel (HiDP) displays which exposed all the ugly pixels in our PNG-based icons. While largely a cosmetic issue, by redesigning these icons as scalable vector graphics (SVG) we feel that the new icons result in a cleaner user interface and are more user friendly for those with HiDP monitors and laptops.

Old

New

How to test:

  • We encourage testers to really hammer on the GUI to see if:
    • We’re missing any of your favorite icons!
    • Any of the icons don’t feel “hooked up” to supposed functionality

New cloud-based floating license

Lastly, we’ve been hard at work to provide a more user-friendly licensing infrastructure. Specifically, we’re rolling out a cloud-based floating license to better support small teams looking to minimize their dependency on internal IT resources. Note: we will still support on-premise floating licenses in addition to these cloud-based floating licenses.

How to test:

Existing user and want to test on your current machine

  1. Install Coreform Cubit release candidate using the installers provided above.
  2. Create a backup of your existing licenses, either move your licenses somewhere safe or compress to a ZIP file and then delete the license files. Your licenses are probably located in the following directories (backup any and all occurrences):
    • Windows:
      • C:\Users\<user>\AppData\Local\Coreform\licenses
      • C:\Program Files\Coreform Cubit <XXXX.X>\bin\licenses
    • Linux:
      • ~/.config/Coreform/licenses
  3. Launch Coreform Cubit release candidate (installed via links above)
  4. Choose the Coreform Hosted option when prompted to activate a license:
  5. Fill out your email address and password that you currently use to login to our current license portal. If you’ve forgotten your password, you can reset your license by clicking on the Forgot your password? link, which will take you to our new license portal (see section below).

Existing user, but want to test on a new machine

Follow the instructions above, but skip step 1.

New user

  • Commercial user
    • Request a trial license from this link.
    • A Coreform representative will reach out to you to complete your account setup.
    • Follow the steps above, skipping step 1.
  • Academic / Student / Hobbyist

New license portal

We’ll also be moving user accounts over to a new licensing portal, in alignment with our goal of simplifying license management for your team.

How to test:

  • Try logging into your account on the new portal using your existing user credentials. New users can create an account following the New user steps from the previous section.

The first thing I see is that from 2025.1 to 2025.7, the surfaces, and edges are not identified the same. When running a journal file, it errors out at some point. For example, this journal file runs perfectly in 2025.1:

import acis "C:<prefix to file>/test_cubit/03_knuckle/knuckle.sat" nofreesurfaces heal attributes_on separate_bodies
webcut volume 1 with sheet extended from surface 17
webcut volume 2 with plane normal to curve 34 close_to vertex 30
webcut volume 3 with plane normal to curve 34 close_to vertex 31
webcut volume 2 4 with general plane yz move to location at vertex 20
remove surface 15 extend
imprint all
merge all
vol all size 1
vol 3 size 0.5
vol 1 size 0.5
mesh vol all
block 1 add volume all
block 1 name "part"
 block 1 element type HEX20
sideset 1 add surface 25
sideset 1 name "fixed-end"
sideset 2 add surface 2 8
sideset 2 name "rbe-faces"

But when running on 2025.7, here is the second command and error:

(Non-Commercial License) Cubit>webcut volume 2 with plane normal to curve 34 close_to vertex 30


Performing webcut operation...
ERROR: C:\<...>, line 3. No curve with ID 34 was found
ERROR: C:\<...>, line 3. Syntax error.
       A single valid curve id must be entered.
       Type 'help location on curve' for correct syntax.
       Type 'help webcut curve' for correct syntax
(Non-Commercial License) Cubit>webcut volume 3 with plane normal to curve 34 close_to vertex 31
1 Like

Thank you for your feedback! I am investigating the issue. We did not update the underlying the geometry engine (ACIS). That will sometimes cause ids to change. But in this case, it looks like a bug to me.