itās work for 4R7 version?
Iāve been using this plug-in and itās great. I have a little niggly problem though that is driving my nuts.
I typically leave all the settings at the default. Sometimes when Iām trying to dynamesh an object (normally one that is not already dynameshed) I get the following errorā¦
It still dynameshes, but at incredibly low res. Problem is I canāt find any things to change. When it eventually works (normally after Iāve changed something about the object, it works fine. Any ideas what I can do to stop this happening?
Any ideas?
Gordon Robb, Iāve also run into this problem a few times. To anyone who may know the answer, is there some obvious info Iām missing?
So hereās what Iāve managed to figure out (And there really doesnāt seem to be much logic to it - some parts of similar size work fine). If I get this message, I undo to the point before dynamehs started messing with it (quite a few steps). then I save (as sometimes after you get this message, ZBrush will crash if you try again). Then I use the āscale upā button. I try it at times 1, but might to to 2 or 3. I then try to dynamesh with normal dynesh. Once I get the result I want, I hit the āscale downā button. That works a treat. You can even scale up a few times - as long as you scale down the same number of times when youāre done 
@Gordon Robb, @Justo: I apologize for the extremely late reply on this; Gordon you are correct the error appears to be related to the scale of the mesh. If the model is too tiny when it attempts to calculate the resolution to generate close to the desired Polycount it will throw that error (basically telling you that part of the mesh will result in no vertices at that resolution.)
I will look into seeing if I can remove this from happening
-Joseph
Yes Joseph, but Iāve had it happen with tools that normal dynamesh will work with, but just not enough resolution. Iāve also found that it sometimes doesnāt work with a or unitive, but will once itās been dynameshed. Also, it gives you the error, and then goes ahead and creates a really low res tool, rather than stopping.
Thanks for sharing this awesome plugin.
I really do like the idea of the polycount slider a lot.
But when I add the Dynamesh button and the resolution slider to my custom interface ZBrush hangs and has to be closed by force. Tried this several times and each time I get the same result.
I use Win7Pro with the latest 4.7
@Erik Heyninck: You should be able to drag these into a custom UI and still have them work (I can not get the buttons to cause a crash on any of my machines.) Do you have an overabundance of Zplugin buttons linked to your UI? If you load the default UI and create a fresh custom UI with only those two options does it still crash?
-Joseph
I love this plug in and have used it for a good while. Thanks so much for sharing it with us Joseph!
Iām having a problem on a 3D print Iām preparing. I have a project for a character made of several subtools with a total of 13 million points. However when I start to combine these subtools and get down to one I canāt seem to get higher than 3 million points. I get this result regardless of settings in Dynamesh Master. I also get the same results in the standard Dynamesh plugin.
Changing the physical size of the tool seems to have no effect. I can start the slider at 128, hit Dynamesh and get a low rez result as expected. However, as I move up in resolution I hit right around 2.97 million points and thatās it.
Itās almost as if there is a hard limit setting for Dynamesh but I donāt know of any such thing and Dynamesh Master appears to allow for much higher resolutions.
The only setting that appears to allow for more points is to leave Group turned on, but that leaves me with intersecting forms within the single subtool which I think will not allow for printing.
I seem to remember not having this issue before so Iām sure itās something simple that Iām just not realizing right now 
Any ideas? Thanks!
@HeavyTheory: I have encountered the max resolution item as well; most of the time it is related to the model being ālong and skinnyā (example: gun silencers, missiles, telephone poles etcā¦)
To start check the Size of your model in [Tool:Geometry:Size]. The DynaMesh process usually generates the maximum amount of resolution in 4R7 P3 with a XYZ Size anywhere from 2.0 - 2.5 and resolution set to 4096 (If you DynaMesh a default cube you end up with ~10 mil.) After the size goes larger then that you will probably not see an increase in DynaMesh resolution. (The DynaMesh Master plugin auto scale function was created to primarily work with small sized objects.)
If you hit the DynaMesh maximum you can always divide the mesh and then project. So you can āMerge Visibleā on the model to create a single Subtool then append that to your scene. Then create the DynaMeshed version of the model that is giving you the 2.97Mil point count. From here divide the model up as you would normally (This will get you above 11 mil no problem.) With the DynaMeshed version selected and the Merged tool visible; change your project all setting Dist to .1 [Tool:SubTool:Project:Dist .1] then do a āProject Allā [Tool:SubTool:Project:ProjectAll]
This should project the details back from your 11mil model to the Watertight DynaMeshed version. Let me know if that helps at all
-Joseph
Hey Piggyson, just wanted to say that youāre awesome and thanks for sharing this. The problem with the scale of the mesh can be a bit tedious, but itās a minor thing when compared to such an awesome thing. The way I solve it is to export as obj the mesh, import, and then dynamesh it (for some reason thereās not a problem anymore if I do that).
@Piggyson Hey Joseph. Thanks so much for the quick response. I looked at my physical size and I was all the way up at 30 for some reason. I brought it down to 2 (If I was understanding you correctly that itās the best range for Dynamesh) and tried again at 4096 and then in Dynamesh Master at around 6 million, but both options just barely got me to 3.1 million. It still seems there is something going on thatās causing a hard limit but Iām not sure at this point. Just so Iām not crazy - there is no way a setting in Zbrush could be causing this is there? Seems like it would be a built in limitation. Itās still probably something Iām missing. Iām including a grab to show the proportions of this tool. I have this kid laying on his back. Could it be something about his orientation?
However your suggestion about going with the low rez Dynamesh, subdividing, and projecting is going to most likely get me to the finish on this one and I greatly appreciate it. Thanks so much!
P.S. I live in Charlotte. If you get a chance Iād love to talk to you offline about meeting up for some paid Zbrush training/consulting if that wouldnāt be a conflict for you. Thanks man.
@Justo I tried your suggestion of exporting as an OBJ and importing again but it still yields the same low rez results for me. Iām glad it works for you though:D
Great post! like it.
This is very cool 
. Well done. 
Big fan of this script. Would love a zremesher equivalent 
Why I canāt get meshes higher than 4.125 millions polys with this plugin?
@final fight: The max resolution; most of the time it is related to the model being ālong and skinnyā (example: gun silencers, missiles, telephone poles etcā¦)
To start check the Size of your model in [Tool:Geometry:Size]. The DynaMesh process usually generates the maximum amount of resolution in 4R7 P3 with a XYZ Size anywhere from 2.0 - 2.5 and resolution set to 4096 (If you DynaMesh a default cube you end up with ~10 mil.) After the size goes larger then that you will probably not see an increase in DynaMesh resolution. (The DynaMesh Master plugin auto scale function was created to primarily work with small sized objects.)
If you hit the DynaMesh maximum you can always divide the mesh and then project. So you can āMerge Visibleā on the model to create a single Subtool then append that to your scene. Then create the DynaMeshed version of the model that is giving you the 2.97Mil point count. From here divide the model up as you would normally (This will get you above 11 mil no problem.) With the DynaMeshed version selected and the Merged tool visible; change your project all setting Dist to .1 [Tool:SubTool:Project:Dist .1] then do a āProject Allā [Tool:SubTool:Project:ProjectAll]
This should project the details back from your 11mil model to the Watertight DynaMeshed version.
-Joseph
This plug is great! Thankyou very much indeed.
There seems to be an annoying change of behaviour. I used to be able to press Scale up Visible, and it would increase the size of the subtool selected. Now it scales up all the subtools which have the eye on. This means that the subtool I have selected (whcih never has the eye on) is the only one that does not scale up.
What gives? I havenāt chaned anythign.