I use vasp and py externals a lot but when I first load my patches because max tries to load some objects before it loads the external the objects fail and I have to close and reopen the patch before it works. Is there a way to autoload the vasp and py externals into memory when I first load max like I can in PD …. ?
|crx091081gb wrote on Wed, 25 February 2009 13:03|
|Is there a way to autoload the vasp and py externals into memory when I first load max like I can in PD …. ?|
You can always move the externals to the max-startup folder. (ie /Applications/Max5/Cycling ’74/max-startup/).
But this shouldn’t be necessary. Max will normally load everything it needs properly when you open a patch. Your problem may lie elsewhere. Or vasp/py may make some strange assumptions about how Max is set up that you need to take into account. Externals normally don’t belong in max-startup, particularly because that’s the last place you’ll think to look when you’ve got an external you need to get rid of (for whatever reason).
cheers that was totally what i needed
C74 RSS Feed | © Copyright Cycling '74