I've written a batch exporter using bits and pieces of code I've cobbled together. src_files is an array that stores a list of max files to export. There a few variables which store whether or not to save a max file, which units to set and save locations of the max files and export flt files. The exporter works really…
use Try() and catch() to skip over crashing sequences. Using try and catch can slow down processor intensive loops, but for a batch exporter it should be fine. Ffor example say MyMaxFiles is an Array of max file names. The following code will try to export all files. If there is an exception, the loop will skip the error…
I've since found out that using the script above with PENs script works perfectly in 64bit. So now I have to clean the files before exporting in 64 bit, then export in 32 bit since the exporter will only run in 32bit. Not ideal but it's a workaround. I also tidied up the script so that it didn't save during the loop as my…
Ok I haven't got anywhere with the script with the exception that I've found that objects that are not editable poly are causing the script to break. In particular these are objects that start life as boxes, or lines with edit poly and uvunwraps in the stack. I tried using PENs great batch exporting script with the…
try and catch is on thing, the other thing I experienced to be valuable is to use a delay call which holds the script to hold for a few ms or seconds before it continues. Especially some of the export plugins (FBX in particular) may take longer and do not sync always with maxscript. So in those cases I often add a delay to…