Troubleshooting Slow File Load Times | GibbsCAM | CAMCO-ne Support : CAMCO

Summary

If GibbsCAM takes an unusually long time to open part files, the cause is often related to the location of the files rather than the files themselves. Slow load times are most commonly observed when opening files from network drives, file servers, or cloud-synchronized folders where network latency, permissions, or security software can delay file access.

This article provides steps to determine whether the delay is caused by the file itself, the network, or the workstation environment.

Table of Contents

Procedure
Common Causes
Best Practices
Troubleshooting
Related Articles

Symptoms

You may experience one or more of the following:

GibbsCAM takes a long time to open part files.
Files open quickly on some computers but slowly on others.
Files stored on a network drive load significantly slower than local files.
Saving files to the same location is also slow.
No error messages are displayed during the load process.

Procedure

Step 1 – Determine the File Size

Large part files naturally require more time to load.

Determine:

The approximate size of the file.
Whether the behavior occurs with all files or only particularly large files.

If only very large files are affected, the load time may be expected.

Step 2 – Compare Local and Network Load Times

Copy the affected .VNC file to a local folder, such as:

C:\Users\<username>\Documents

Open the local copy using GibbsCAM.
Compare the load time with the same file opened from the original network location.

If the local copy opens significantly faster, the issue is likely related to the network or storage location rather than GibbsCAM.

Step 3 – Verify Folder Permissions

Confirm that you have full access to the folder containing the files.

Verify that your Windows account has:

Read
Write
Modify

permissions.

Insufficient permissions can increase the time required to access files over a network.

Ensure the workstation has full access to the file location.

Step 4 – Check Antivirus or Endpoint Security Software

Security software commonly scans files as they are opened and saved.

This is one of the most common causes of slow file loading from network locations.

If permitted by your organization's IT policies:

Temporarily disable antivirus or endpoint security software.
Test opening the file again.
Re-enable protection immediately after testing.

If this resolves the issue, configure exclusions for:

GibbsCAM
.VNC files
.ZOOB files (temporary save files)

Note: The .ZOOB file is created temporarily during the save process and may also be scanned by security software, increasing save times.

Step 5 – Verify Network Performance

If files are stored on a network share:

Verify the network connection is stable.
Check for excessive latency.
Test loading files from another workstation connected to the same share.

If multiple users experience similar delays, the issue is likely within the network or file server environment.

Step 6 – Test with Another Storage Location

Copy the file to:

Another network share.
A different file server.
A local SSD.

Compare the load times.

This helps determine whether the issue is specific to one storage location.

Expected Result

Part files load at normal speed, and opening files from network locations performs comparably to local storage.

Additional Information

Common Causes

Slow file loading is commonly caused by:

Network latency.
Endpoint security software scanning files.
Antivirus software inspecting network files.
Insufficient folder permissions.
Slow network storage.
Large part files.
Congested file servers.

Best Practices

Store active projects on fast local storage whenever practical.
Keep network infrastructure and file servers properly maintained.
Configure antivirus exclusions for GibbsCAM and its file types if approved by your IT department.
Use wired network connections when working with large files.
Verify that users have appropriate permissions on shared folders.

Note: When files load quickly from local storage but slowly from a network location, the issue is almost always environmental rather than a problem with GibbsCAM itself.