ZBrushCentral

ZScripting the 4R7x64 way !!!!

So there we are !!!
New version, 4R7, and a double one - with x64.

So what’s up for us ZScriptFreaks ???

Now there’s ZPlugs and ZPlugs64 : How does that reflect in the code ?? I mean, when you call, for instance a dll, with :
[FileExecute, “ZSTARTUP_ZPLUGS/shrakbraka.dll”, shloobadoo]
Do you have ZSTARTUP_ZPLUGS pointing to the ZPlugs64 automatically when you’re using x64 and ZPlugs when you’re using x32 ???

And moreover, what’s new in ZScript ???

You can export the commands list as a text file. That’s what I did :wink:

no difference in command list => 4r7 comparing to 4r6

Are you certain? A closer look may be warranted. :wink:

Ha yeah didn’t think about exporting the commands…

So I compared byte by byte the new and old command list : Differences :

IButton, Image : " + .pct for Mac Systems" removed…
ZBrushInfo : 0 is now “version number” instead of “version numebr” :lol:, and added 16 that is “cpu” (I presume x32 / x64)

That’s all folks !!!

For calling a DLL, you can use the relative path if you want, using [FileNameResolvePath] to get the full path:

[FileExecute,[FileNameResolvePath,“MyPluginData_4R7/MyLibrary.dll”],MyFunction]

Or you can set the path after getting the processor:

[VarSet,file64DLL,"ZBRUSH_ZSTARTUP/ZPlugs64/MyPluginData_4R7/MyLibrary.dll"] [VarSet,file32DLL,"ZBRUSH_ZSTARTUP/ZPlugs/MyPluginData_4R7/MyLibrary.dll"] [If,[ZBrushInfo,16]==64,//64 bit [If,[FileExists,file64DLL], [FileExecute,file64DLL,MyFunction] ] ,//else 32 bit [If,[FileExists,file32DLL], [FileExecute,file32DLL,MyFunction] ] ]

Thanks marcus :slight_smile:

I didn’t even know about ZBRUSH_ZSTARTUP !!! I only knew ZSTARTUP_ZPLUGS…

For those that use it, a new version of ZFileUtils has been released. See here:

http://www.zbrushcentral.com/showthread.php?191848-ZFileUtils-updated-for-4R7