GoZ opens new instance of Max

[Anonymous]

Hey everyone, I can't seem to figure this one out and I'm hoping someone has a solution. I've got 3ds Max 2018 and Zbrush 4R8 P1 and the GoZ function just isn't working like it used to in Max 2014. 

Max>Zbrush = fine, no problem
Zbrush>Max = model goes back to original Max scene, but also opens a new instance of 3ds max with nothing in the scene.

[laomusic_arts]

This is NOT a supermarket !
Forget about selling or buying and come up with solutions.
"To think" is for free !

[Anonymous]

This is NOT a supermarket !
Forget about selling or buying and come up with solutions.
"To think" is for free !

Yeah thanks for the reply and the solution. Im not sure I want to blow my Z prefs every time I need to use items from Z in max. GoZ from Max 2018 to Z works fine, just Goz to max is broken. In the meantime just exporting an obj from Z to max and importing it works well enough in the meantime.

[hot]

How can you send an object to Max - if you've reset the scene ? The object will be deleted - it's ok to send to ZB from Max but sending back creates a new instance of Max ?

[Anonymous]

How can you send an object to Max - if you've reset the scene ? The object will be deleted - it's ok to send to ZB from Max but sending back creates a new instance of Max ?

Yup. Only need to send from Max for substance painter. Z has a better FBX exporter. Only need to send decimated shells from Z to Max for retopo and uvs so Im sorted. If I need to send from Z to Max obj export works fine. Just means I have to delete the previous instance in Max if I am setting up the export prefs in Z. and that is only at the beginning of a project.

[laomusic_arts]

Initializing ZBrush resets the interface and palettes to their default state, clearing data including customized tools in the Tool palette. You should save you work before pressing this button.

Your actual configuration should be stored by pressing the Store Config button in the Config sub-palette or Shift+Ctrl+i on the keyboard. Preferences adjustments are not saved automatically.
More here:

http://docs.pixologic.com/reference-guide/preferences/

[laomusic_arts]

What is hgoing on in my System is that I can send to ZBrushfrom within Max and after Init/ZB I have the model back. I DO not send it back: I just Init ZB !

[bksong]

I've tried the suggestions and I still have the problem.

Anyone ever figure out a solution? I'm almost inclined to just downgrade max to 2017 just to get goz to work seeing how long this has been an issue. 

[Anonymous]

I also had the same problem.

[teriannUQJ6J]

Sorry I am new and a little desperate for a solution... I am also having the same problem, which is unfortunate because this slows me down considerably at work. 

Exporting manually and importing every time you make a minor adjustment to complex models with multiple subtools is not a solution so far, neither is save+restart.  This does not seem to work with GoZ "All" or "Visible" as a solution. 

Trying the initialize Zbrush method I still have to reset for every subtool in a complex file.

Has there been any acknowledgement or updates regarding this from Autodesk? Has anyone here submitted a ticket yet?

[Anonymous]

Max 2 ZB works so I think its a ZBrush thing.

[teriannUQJ6J]

Good point, I think I was hoping it was Max because if 4R8 P2 didn't fix it then hopefully it will be for next release, whenever that is...

[hot]

This isn't a ZB issue - this is a Max 2018 problem I believe.
Use Goz to export to Max 18 & it will open up a new instance of Max.

In the same ZB session change the path of Max in GOz pref' to point to Max 2017 and you can shuttle models between Max 2017 and ZB quite happily.

[Anonymous]

Hi,

I believe I found the solution for this problem.

I had to import a obj file as you would normally do.

When the import tab opens you have to uncheck the option RESET SCENE at the top right on the import tab.

[teriannUQJ6J]

---

@Anonymous wrote:

This isn't a ZB issue - this is a Max 2018 problem I believe.
Use Goz to export to Max 18 & it will open up a new instance of Max.

In the same ZB session change the path of Max in GOz pref' to point to Max 2017 and you can shuttle models between Max 2017 and ZB quite happily.

---

You're correct Hot, it is an issue between Zbrush 4R8 and Max 2018... however changing to Max 2017 does not solve the problem in 2018, unless I am misunderstanding your post.

The problem is how to fix GoZ for 2018... currently I would have to request all our seats be upgraded/downgraded to 2017 to hope it will fix this problem, which is not a viable solution right now during crunch time. 

@Anonymous

---

@Anonymous wrote:

Hi,

I believe I found the solution for this problem.

I had to import a obj file as you would normally do.

When the import tab opens you have to uncheck the option RESET SCENE at the top right on the import tab.

---

I believe this was brought up earlier in the thread, adjusting the OBJ import settings to uncheck that box (which in my case was never on) unfortunately did not fix the GoZ issue from Zbrush. 

So unfortunately my solution was to downgrade to 2016 which is the most stable I found that worked previously with GoZ.  Hoping someone can shed some light once this is fixed either on Pixologic side (since Max > Zbrush seems to work fine).

[hot]

I'm highlighting the fact that it still works in 2017 and not in 2018 - therefore it's a 2018 problem. 

[Anonymous]

My 'Reset Scene' box is unchecked. Still opens a new instance of Max 2018.  Tested it again this morning. Everything seems to be working fine except opening the new scene. I can live with that.

[Anonymous]

Pixologic has mentioned his compromise to maintain GOZ for Maya but said nothing about Max, and certainly in Max 2018 GOZ is not functional and is yet in Max 2017.  That means that unless Autodesk do something I doubt we will have GOZ for Max in the future, including Max 2019.

There is a plugin that covers part of the funtionality of GOZ cost 5$ https://gumroad.com/l/iDdF

It has some advantages and some disadvantages. I rather would have GOZ but it is better than exporting and importing manually.

[teriannUQJ6J]

FYI I did try this paid plugin the disadvantages far outweigh the advantages for the GoZ> All/Visible functionality. 

The plugin essentially can send back and forth one object at at time with no subdivisions, and will replace that dummy OBJ object in the Temp folder when flipping back and forth from Zbrush to Max, unless I missed a setting.

As someone said earlier encouraging a paid plugin that does not actually solve the problem should not be a viable solution... it is a good suggestion for people working with very simple projects, not complex projects with multiple subtools.  

As an example, I work in manufacturing and use Zbrush and Max for components with organic sculpting various complex parts (ie. Mannequin hands, fixture details, decorative finials, etc.) These tools require multiple subtools with various subdivisions for revisions.  My workflow without a working Max GoZ is slowed down considerably, hence why we downgraded to the stable version.

Not to keep bumping this with no new info but is there any way we can mark this not solved for Max 2018, in case a fix does come out in the future?

[Anonymous]

GOZ doesn't send subdivisions either, always default to the lower subdivision when this plugin sends whatever subdivision is active. Something that I prefer as with GOZ I'm forced to delete lower subdivisions if I want to send anything that is not the lower subdivision. GOZ also saves in a temp folder when flipping back and forth from Zbrush to Max . The plugin can send polygroups but I agree is worse as it is limited to single objects and as I said I would prefer GOZ. I think it is a big lost that GOZ is not available any more.

 I bought the plugin just like you did, not relation with the developer and it is up to the people if it is useful for them or not, for me is. Not all people works with the same kind of model workflow as you do. Also I don't think the posts (mine, older and  yours) were adding not new info. 

[Anonymous]

This thread is useful because there is always a chance that someone will find a fix without having to delete ZB prefs or diving into the registry. Judging by this thread only a few of us are having difficulties.