WHITE PAPER
Formlabs Logo

PreForm software issues and troubleshooting

PreForm software issues and troubleshooting

PreForm print preparation software helps configure 3D files for printing. Always ensure you are running the latest version of firmware and software before attempting troubleshooting. If you are experiencing an error message on a printer's touchscreen, check the support article for your printer to learn more:

Tip:

Download PreForm log files and printer diagnostic logs to aid Formlabs Support in troubleshooting your problem.

File import error message

PreForm warns you if an STL/OBJ/3MF file has flipped faces or other irregularities. When detected, the software offers to attempt an automatic repair. Check the support article Preparing a valid model in PreForm to learn more about what features cause a FILE IMPORT or BROKEN MODELS DETECTED error. Changes to the model's mesh may be necessary.

If the repair is successful:

  1. Slice through the model to ensure that there are no unknown values causing holes or other irregularities.
  2. Support your model.
  3. Orient your model.
  4. Save your model as a FORM file.

3Dconnexion 3D mouse not working

3Dconnexion 3D mice may not work correctly with older versions of PreForm due to driver incompatibilities. If you are having issues with your 3Dconnexion 3D mouse, update PreForm to version 3.11 or later.

Offset cursor with multiple monitors

When using PreForm on multiple monitors with different resolutions, the cursor may be offset from the true location on screen. To resolve, close out all instances of PreForm and restart the application. In rare instances where the issue persists, reinstall the latest version of PreForm.

Firmware compatibility

If you update your printer’s firmware after adding a print job to its queue, the printer may be unable to print the job. If a queued job fails to print, remove it from the queue, update update PreForm,and reupload the print job.

Additionally, when updating either PreForm or your printer's firmware, you may be required to update the other to maintain compatibility and be able to print. Keep both PreForm and your printer's firmware fully up to date for best results

If the problem persists after reuploading your print job, contact Formlabs Support or your authorized reseller.

Form 1+ appears disconnected

Sometimes PreForm’s orange Print button may display the disconnected USB icon even when your printer is connected and otherwise recognized as a device. This can happen if you have two instances of PreForm open.

To resolve:

  1. Save your models as FORM files.
  2. Close all instances of PreForm.
  3. Reopen a single instance of PreForm.

Tip:

If you cannot see a second instance of PreForm, open your task manager to check for other instances of PreForm running in the background. Close additional instances.

 

Alternatively, if you only have one instance of PreForm open, you can restart your Form 1+:

  1. Ensure that a print is not currently in progress on your printer.
  2. Disconnect the USB cable from your computer.
  3. Unplug the Form 1+ and wait 30 seconds.
  4. Plug the Form 1+ back in.
  5. Reconnect the USB cable into a different USB slot.

Tip:

If the printer remains Disconnected in PreForm, open your device manager to ensure that your computer is recognizing the Form 1+. If it is not recognized, uninstall and then reinstall PreForm.

Software crashing

The most common causes of a software crash are out-of-date graphics card drivers and large STL/OBJ/3MF files. Make sure the file you import is not too large (100 MB or greater). Contact your computer manufacturer to update your graphics card drivers if you are experiencing frequent crashes.

Supports not generating

The most likely reason supports will not generate is out-of-date graphics card drivers. Contact your computer manufacturer to update these and then resume with support structure generation.

Updating firmware and software

Ensure you are using the latest firmware and software versions available.

To view the currently installed version of PreForm:

  1. Open PreForm.
  2. Click Help > About PreForm.
  3. Check the support article PreForm downloads and release notes to ensure you are running the latest version of PreForm.

Tip:

PreForm automatically prompts an update if a new firmware version is available. If an automatic update is unavailable, perform a manual firmware update.

 

To view the firmware version currently installed on your printer:

  1. On your printer's touchscreen, tap Settings.
  2. View installed firmware:
    • On a Formlabs LFS printer (Form 3 or later), tap Settings > System > Printer Info.
    • On a Form 2, tap Your Printer > Settings > Printer Info.
  3. Check the support article Firmware downloads and release notes to ensure you are running the latest version available.

Tip:

View the support article Updating firmware for Formlabs SLA printers to learn more.

Could not open DFU device

To correct this error:

  1. Ensure that a print is not currently in progress on your printer.
  2. Unplug the printer and wait 30 seconds.
  3. Plug the printer back in.
  4. Save open files in PreForm as a FORM file.
  5. Close PreForm.
  6. Re-open PreForm.

Note:

If PreForm continues to display Could not open DFU device, then the printer may be in DFU mode or your computer is not recognizing the printer. Contact Formlabs Support or your authorized reseller for instructions on how to reload your firmware.

Running in a virtual machine

We do not support running PreForm in a virtual machine. If you want to try running in a virtual machine, make sure you have 3D graphics acceleration turned on for best results.

To enable in VMWare:

  1. From the menu bar, click Virtual Machine > Settings > Display.
  2. Enable Accelerate 3D graphics.

Note:

The virtual machine must restart in order to make this change.

Surface Pro installation

If you are experiencing an issue opening PreForm on your Microsoft Surface Pro:

  • Update your operating system to Windows 8.1 or later.
  • Update your graphics driver directly from the manufacturer's website (e.g., Intel), rather than using the Microsoft updates.

Note:

Future Microsoft updates may replace the manufacturer's drivers.

FL0 generation failed

To correct this error:

  1. Clear disk space on your computer.
  2. If your Windows username includes special characters such as accents or Unicode characters, create or log into an account that does not include those characters.

Unable to open PreForm/Application error (Windows)

PreForm gets stuck on splash screen

When you open PreForm, it displays a splash screen with the software version number, copyright information, and a highlighted Formlabs product while it loads. Various software issues can cause PreForm to hang at this splash screen and not finish loading. To resolve this issue:

  1. Uninstall and reinstall PreForm.
  2. Uninstall the current version of PreForm and roll back to a previous version.
  3. Try opening PreForm in compatibility mode.
  4. Use the Windows Program Install and Uninstall troubleshooter to uninstall PreForm and remove any associated registry keys, then reinstall PreForm.
  5. If the issue persists, contact Formlabs Support or your authorized reseller and attach the PreForm log file to your message.

PreForm fails to open with Application Error

As of PreForm version 3.29.0 and later, PreForm requires the installation of Visual Studio 2015, 2017, 2019, and 2022 to support Dental Workspace functionality in Windows. If the runtime library is not installed, PreForm cannot open and displays the error message PreForm.exe - Application Error.

Preform error messaged Application Error

To resolve this issue:

  1. Download and install the latest Visual Studio 2015, 2017, 2019, and 2022 version for X64 architecture.
  2. If the issue persists after downloading and installing Visual Studio, contact Formlabs Support or your authorized reseller.

Error 0x80070643 Setup Failed

Error 0x80070643 Setup Failed and the error message "The feature you are trying to use is on a network resource that is unavailable." indicate a corrupted or misplaced installation file on a Windows computer.

To correct this error:

  1. Run the Windows Program Install and Uninstall troubleshooter.
    1. Go to Fix problems that block programs from being installed.
    2. Click Download.
    3. Click Run or Open. Follow the steps in the troubleshooter.
  2. Manually browse for the PreForm installation file.
    1. Click Browse in the error message box.
    2. Browse to the path where the .exe is located within the install source media.
    3. If the install package is missing, reinstall the latest version of PreForm.
    4. Continue with the updated installation.
  3. Use the Registry Editor to rectify the installation source path.
    1. Search REGEDIT in the Windows search bar.
    2. Double click Registry Editor. The Registry Editor opens.
    3. Follow the path to HKEY_LOCAL_MACHINESOFTWAREClassesInstallerProducts
    4. Click on each Product until you find the PreForm installation file. Your PreForm installation file may have a different name than in the example.
    5. Right click the malfunctioning PreForm installation file. Select Delete. The computer deletes the malfunctioning PreForm installation file.
    6. Close the Registry Editor.
    7. Restart the computer.
    8. Install the latest version of PreForm.

If the issue persists, contact Microsoft Support.

Calibration step failed

A failed job upload with the message Calibration step failed generally indicates a connectivity problem. To resolve this issue:

  1. Uninstall and reinstall PreForm, then try again. If you have multiple versions of PreForm installed, uninstall all copies and then install the latest version.
  2. If you are trying to upload the job via Wi-Fi, try connecting to your printer via Ethernet or USB instead.

Update Error (macOS)

Starting with PreForm 3.56, PreForm requires macOS 13 or later. If you are on an earlier version of macOS and try to update to PreForm 3.56 or later, PreForm will display an Update Error message. To resolve this issue, update to macOS 13 or later, then try updating PreForm again. If you cannot update your operating system, you will not be able to update PreForm.

PreForm Update Error

Software bugs

We are always working to improve our software and appreciate your help in spotting potential problems. If you encounter what you think is a software bug, check if you have the latest version of PreForm software installed. If the bug persists after updating PreForm, contact Formlabs Support or your authorized reseller with details, screenshots of your experience, and information about your operating system, PreForm version, graphics card, and processor. Our support team will resolve the issue as soon as possible.

Downloading the PreForm log file

To access the PreForm log file:

  1. Open PreForm.
  2. Click Help > Open Log Directory. The PreForm logs folder opens.
  3. Attach the log.txt file when contacting Formlabs Support or your authorized reseller.

To manually access the PreForm log file:

macOS

To download the PreForm log file on macOS:

  1. Hold the Option key on your keyboard, and click the Go menu in the Finder menu bar at the top of the screen.
  2. Select Library from the Go menu (while holding down the Option key) to access the hidden folder.
  3. In Library, select the Application Support folder.
  4. In Applications Support, navigate to /Formlabs/PreForm/Logs/log.txt.
  5. Attach the log.txt file when contacting Formlabs Support or your authorized reseller.

Windows

To download the PreForm log file on Windows:

  1. Press the Windows key + E on your keyboard to open the File Explorer.
  2. Follow the Windows instructions to show hidden files in the File Explorer.
  3. In File Explorer, navigate to C:UsersUSERNAMEAppDataLocalFormlabsPreFormLogs, replacing USERNAME with your local user name.
    • If you're not sure what your user name is, navigate to C:Users to view a list of user names in use on the computer.
  4. Attach the log.txt file when contacting Formlabs Support or your authorized reseller.

For information about printer and accessory logs, see Downloading and sending diagnostic logs.