Migrating Workgroups between Softimage versions

#1

Hi,

I have a problem with scripts every time I upgrade and wonder if anyone can cast some light on it.

I keep all my custom scripts (just simple ones that help my workflow) in a XSI version workgroup. I’ve had bad experiences with migration so I just copy and rename the workgroup for new version.

However, I have problems with my scripts. When I try to run them they seem to try and access the old workgroup not the new one. Can someone help me with a set-up that works between different workgroups? Or a way of updating the scripts for new workgroups?

Many thanks,

Alan

#2

workgroups are readonly location and there should be no issue using them with different versions. Afaik, they are not migrated.

the only thing that migration does it copy over your user preferences and other settings in your user folder.
since which workgroup you are connected to is a user preference, then you’ll still be connected to the old workgroup. If you do not want that, go in the plugin manager to choose which workgroup you want to connect to. Or you can delete your user preference file to start fresh with the defaults.

#3

Luceric,

Thanks for your reply.

Ok, I understand your answer re. migration.

Can you help with my scripts? For example, I have a main folder named “Workgroup for XSI6”. The folder has sub-folders for scripts, plugins and shaders. I create a simple script say to toggle the visibility setting on a layer and save it to the script sub-folder.

I copy the workgroup and rename it “Workgroup for SI2010”. I then use the plugin manager to connect the sub-folders in the new workgroup folder to SI 2010. When I try to run the script mentioned above, I get an error - the bottom bar turns red and the error message mentions that the script was trying to look in “Workgroup for XSI6” folder not “Workgroup for SI2010”.

Now, I could just re-save the simple script, but its a brute-force way of fixing the problem. Also, I don’t want to have to do this for all my scripts.

I’m thinking that this could be to do with the way in which I save scripts.

Any thoughts?

Regards,

Alan

#4

How do your run the scripts after you connect to the new workgroup? From a toolbar?

Why do you need to make a copy of your workgroup? Can’t you just connect to the same workgroup from both versions of XSI?

#5

Stephen,

Thanks for your reply.

I am running them from toobars and hot keys. Either way of running the scripts generate the error.

I suppose I could have all versions point to a common workgroup. Is this the recommended approach? Although, I have seen people comment about calling different workgroups for different functions - I think this was on the list.

I adopted the workflow of copying the workgroup so I could adapt all my library of scripts, shaders, etc., for those that worked (and are needed) for a particular version.

Regards,

Alan

#6

I think your problem is with the toolbar and keymaps that you use.

If you created toolbar buttons by drag and dropping the script onto the toolbar, it creates a command button that contains an absolute path to the script.

Instead, to have something that doesn’t bind to the path of the script, you should create a “Script Button” and type in the name of your command.

The best thing to do would be to is zap your user folder start fresh. Get rid of all the cruft.

To instead manually clean up, delete the Custom Script Commands_{…some long number here…}…DSDynamicCommandMap file to get rid of all references to old commands, and delete the toolbar file as well. You may have to re-bind the keymap keys

#7

This thread has been automatically closed as it remained inactive for 12 months. If you wish to continue the discussion, please create a new thread in the appropriate forum.