Hi, my office is using the keyshot network license and saving our files on a local server. When we save keyshot .bip files to our project folders, we found that other workstations cannot locate the project resource files. So, we have been saving a package .ksp file along with our .bip file for every project. This can be a problem when users forget to update their .ksp files on a quick update job.
So here's my question, is there any reason why we shouldn't just work off .ksp keyshot package files and stop using .bip files altogether?
Chris Hanks
Hi, my office is using the keyshot network license and saving our files on a local server. When we save keyshot .bip files to our project folders, we found that other workstations cannot locate the project resource files. So, we have been saving a package .ksp file along with our .bip file for every project. This can be a problem when users forget to update their .ksp files on a quick update job.
So here's my question, is there any reason why we shouldn't just work off .ksp keyshot package files and stop using .bip files altogether?