I’m buildling .mzp packages at the mo, and one of my tools prints the current directory to the listener. It appears that when you drag a .mzp file onto the viewport, it runs in that directory.
Can anyone shed any more light?
Thanks,
Dave
by ‘current directory’ are you referring to sysInfo.currentDir?
I tried a .ms file, a .mzp file of that same .ms file, a .mzp file a mzp.run file that ran the .ms file… they all give me the same result – the folder I last accessed (to load a max file). Might something else have opened the %max%\express\ folder? If in doubt, try SysInternals’ Filemon?
fwiw – I don’t even have that folder in Max 9/2008/2009… 7/8 seem to have it… no particular info on in it / on it.
Hi Richard,
Quick of the mark as usual
Yes, I mean sysinfo.currentDir.
And the directory is the “project” branch of max’s filesystem, ie what would be C:\Users<User Name>\Documents\3dsmax\express for most users.
And I’m using max 2009 64 bit right now; yet to test in 3dsmax 9.
ogh… I’m hating all these different folders… I know it’s more appropriate, and Vista is definitely forcing hands, but… sheesh.
Anyway – confirmed the folder existing -there- not sure why it’s there for an ephemeral drag&drop… I would have expected it to be in the appdata one… or appdata temp for that matter.
Doesn’t get you any closer to knowing what that ‘express’ folder is, though… or why your script seems to report the currentdir being that
You can tell it what folder to use as the temp directory to unpack it in. I usually set this to the default Max temp directory or to a custom one if unpacking to net work installs. This is all out lined in the help but you need to do a seach for MZP. You are looking for extract to and this will need to be placed in the mzp.run file.
Thanks Paul,
I’ll go through the help again, and will check it all out more thoroughly.
.mzping is a new area for me!
Extract to is indeed a must – I wouldn’t extract to temp, however, if your scripts need to use any files extracted… reason is that temp can get cleared during max operation… making the files go missing.
However, I’m not sure if that’s related to the sysinfo.currentdir at all… in my tests I extracted to temp, but sysinfo.currentdir remained “c:\3dsmax2009_scenes_contest\etc”
maybe my test script was incorrect, though…
-- script "t.ms"
messagebox sysinfo.currentdir
-- mzp.run file
name "t"
description "t"
version 1.0
extract to $temp
run "t.ms"