ZBrushCentral

GoMax

Norman3D,

Every version up until this one has worked great.

Now I get an Maxscript error saying unknown property “use litsphere”.

Also, if I change the topology of the mesh in Max and try and send it back, I get a Z script error saying that the object can’t be found.

Weird.

Matt

EDIT: also, it adds a sphere to my Tool palette when it can’t find the object from Max. And, my .obj export gets reset to “no material” in Max everytime I try to import something from Zbrush.

I’m pretty sure you haven’t installed it properly :confused:
remember you have to run the GoMax.ms file at least once after updating, in case you are using the toolbar buttons.

Thanks buddy - I was just over-writing the files, not running the .ms file. All is well!

Spoke to soon - all is well in Max, but when I try and import back into Zbrush, I still get “interface item could not be found”.

It also says, “TOOL:Polysphere_1 in… [Get,TOLL:POlysphere_1]”

For the install of the macros, I overwrote the existing text files with the ones you provided.

Thoughts??

Ok, just renamed a sphere PolySphere_1, as per another users instructions, and it worked.

Once again, thank you soi much for your work on this amazing plugin.

Cheers,
Matt

this is a pretty amazing script.

just chiming in to say i’m also having the zbrush—>max2009 scale issue. the models come into max very small. my export settings in zbrush are always set to scale=1, offsets all=0.

also having an issue with the point order (or something like this) getting whacked out when i export from max into zbrush–the verts seem to be in the right places, but aren’t connected properly resulting in a mesh that looks like a big mess. when i manually export and import the same obj from max to zbrush it works perfectly.

This seems to be a mess for me.

Select Polysphere
Import OBJ A
Click “no” to replace

export obj A and import into max - Fine

Append Polysphere to A in Zbrush
Import OBJ B
OBJ B replaces polysphere

Export OBJ B and import into max - Fine

Append Polysphere
Send OBJ C over via GoMax 1.5
OBJ C replaces polysphere

Export A, B, or C and import into max - All of them are upside down and shrunk located well below my model.

Also during all this stuff I get an array off odd and scarily chaotic behavior like things telling me “teapot” already exists and material errors and max script pop up dialogs telling me something is wrong with a material. One time it just kept telling me it was importing back into max over and over (reapeat status bar infinitly). I cancel that and go back to zbrush and my whole document is jacked around, now at 256 x 256.

So far not so good.

Hey Norman,

Small problem: GoMax 1.5 resets the export scale to 1, but I need it set to 100 to match the scale of my scene.

Yeah, that scale issue screws up couse it gets so small in max that you cannot model new subtools at this scale, cause of viewport glitches that happens in such a small scale, subtools like clothing etc, so you get it to appear in the right place back in zbrush…

My workaroung is laughable but work nicely, I get the tool in highest subdivision to max, scale it up to match the correct scale again, model the clothes or whatever is needed, get the model back to zbrush and then i reconstruct the subdivision, then i get the new tools in zbrush and it should match the scale… pretty dumb but it gets it done…

I get an info-error when trying to export the model from 3dsmax to zbrush:

Unable To Open File
C:\GoMAX\GoMAX

… followed by another info-error:

Error
Error encountered while importing a file

The export to 3dsmax works, though … at least somehow/to a degree.
Clicking on the “import from zbrush” button mostly doesn’t do anything but asking me if the existing selection shall be replaced.
On some occassions the import works and I get to see the model from zbrush inside 3dsmax.
It’s very weird. I am working on a Vista 64bit system with UAC activated.

I have precisely the same scale problem. I just created an object in max 2010, started zbrush 3.5 R3, imported the object, modified it, imported it back to max and it was tiny. Several tries… doesn’t matter which tool I select before the import into zbrush. The transformation always gets reset to 1 0 0 0

That happened to be before quite a lot, so I made a workaround script that stores the scaling and sets it back later on the desired tool. Much better, than noting the value down and typing it in by hand again :confused:.

So my suggestion for GoMax is, if the problem can’t be fixed otherwise, to implement a workaround script like I just described.

Hey Norman,

is there any option to not export the maps from zbrush? like, normal map or poly paint or whatever they are.

I think sometimes people just want to modify the geometry without need the normal map and other stuff. Normal map exporting can take sometime depending on the model when going zbrush to max, and thats annoying when you just want to quick work the geometry.

I would sugest to add some check boxes in the script panel for exporting normal map and polypaint, so people can chose when they want these maps

thanks

amazing plugin! thank you wholeheartedly!

I think some of you guys don’t even read the readme file :confused:
First check if you have installed everything properly, then launch GoMax.ms from maxscript/Run script in 3dsMax, and use those buttons.

Have you tried to apply a resetXform before exporting from 3dsMax. I have currently made some changes to the script, and the scaling issue seems to be gone. I will be releasing it later today, so you guys can test it.

That’s the plan, but not just yet. :wink:

The scale issue happens even with reseted xform meshes… the problem is the export scale slider in zbrush is set to 0 instead of 1, by default… i guess if you just add this (scale vaule=1) to the script it will be fixed

Hey Norman,

I know you could not reproduce the error I mentined before. But there is another person having same issue.

Clappy71 is the 3rd person with this issue.
It seemed that I was the only one having the issue, but since there are others, maybe you can look into this again? If you don’t have time for that, it’s ok.

Thx again.

Yep, I’m aware of this problem, this happens when you don’t have a PolySphere_1 tool at all. Usually, when you startup you have a PolySphere drawn in the canvas, by default at least. So anyway, this is bug appeared because of another bug I fixed. And that is a strange problem with the moving brush, if you click the 3dsmax -> Zbrush button while the PolySphere is drawn in the canvas and selected.

So I think I’m going to revert this fix, because it’s only causing problems (to a small minority). But my point is, you shouldn’t have the PolySphere activated in the first place.
So yeah, I’ll revert the fix and you should not have that problem anymore.

I think it has nothing to do with that, since GoMax already sets the scale value to 1

Thank you for quick reply. You’re an awesome person.
I can’t stop using GoMAX!:smiley:

Actually… on a second thought… I have done some tests… and it seems that the export value also affects import!! What the…
I have now put those values in the import script as well. Everything should be fine now…

EDIT: wait, nevermind… let me double check this :o

EDIT2: Ok, seems like I was right the first time. The export scale seems to affect the import scale too!!!

ever for max / zbrush users.