ZBrushCentral

Questions & Troubleshooting for ZBrush 4R8

ZBrush Usage Questions
#281

The IMM auto hide button only works if you have a non-IMM brush (zmodeler counts as an IMM brush) active when you deactivate it, and then of course the setting doesnt save between restarts without script editing.

And thus my view of reality was bent so far over backwards all that was visible was its own butt.
I love software, with software all things are strange and wrong, yet colorful and and loud.
Is my eyelid twitching?
I digress.
So, what you are saying is that the stuff I read about this earlier in this thread actually didn’t make any sense and that’s why I didn’t understand it?
This is awesome.
I cant stop laughing, I love ZBrush so much that something like this actually makes me happy.
Aivar242 however seems visibly upset.

#282

It is a very peculiar requirement. This is listed in the first post of this sticky thread along with other known issues, BTW. This is also stated in the ctrl-mousover tooltip for the button.

#283

Hay!
You’re right! It is in tooltips! It’s just that I haven’t made them opaque yet and cant see them. Well crap, thanks for that.

#284

If I use Symetry (any) into Zmodeler, Zmodeler doesn’t work : doesn’t accept any action. Only me or a bug ?
Thanks for any answer
Michel

Found the culprit : I didn’t activate L Sym
I’ll be grounded

#285

Just wondered if anyone else has had this problem with 2d alphas.
I’m using a skin pore alpha and when I drag it out onto the surface its at a really low intensity/resolution at frist. As I continue to drag out it suddenly pops to a higher res/intensity.
I was hoping it may just be caused by a setting in the alpha pallet but I’m starting to think it might be a bug.
Please if anyone can help because at the moment this is really screwing up my workflow :frowning:

An Adaptive Map Size slider has been added to the Brush >> Alpha and Texture sub-palette. This allows for automatic MIP-mapping to be used to dynamically adjust the alpha or texture resolution for the size of the brush.

#286

@LeoAMD

Have you tried resetting the problem brush? Brush > Reset current brush ?

#287

Don’t know if any Pixos are still reading this thread, but by way of feedback:

Can anyone verify for me that the default MaxPolyPerMesh (preferences > Mem ) is now set to something like 50+ million polys? I’ve altered my config and cant remember the default.

I think this is wildly optimistic. I know advances have been made in Zbrush’s memory handling, but a mesh of that size is still going to be problematic for many of Zbrush’s features on many if not most systems. Inexperienced users could easily run up the polycount, only to end up with an unmanageable model. Before, when the limit was set much lower, it acted as a speedbump to let you know you were getting into uncharted waters.

#288

The default on mine is 31.09 million. I have 8 GB RAM and have not altered anything. It is possible, I guess, for that to be higher if you have more RAM.

I noticed that mine went up to 33.72 million when I put Compact Mem to 4096 from 256. A single subtool at 33.29 million will cause the cursor to lag a bit on my system which I don’t like. I would probably not go that high per subtool. At 8 million per subtool, it runs very smoothly.

#289

Perhaps it sets itself based on hardware specs then. In any event, I think that is too high as well. Sure, you can sculpt on a 30-50 million poly mesh, but a lot of other features aren’t going to work well, or at all, with it.

#290

@Spyndel:
Mines at 22 million and I haven’t changed it.

#291

@Spyndel
Yep, rest brush but still not working.

#292

@LeoAMD

I would need to see a video or some pics of the situation that is troubling you to have any idea what is going on.

#293

@ZBer:
I have the same amount of ram, and setting that to 4096 and hitting compact now didn’t change anything (It did take a while and I thought I was gonna crash for a bit).

#294

Yay… Patch out for the most common issues…

#295

Note MaxPolyPerMesh with Compact Mem at 256, change Compact Mem to 4096, save Config, restart ZBrush.

#296

In Zmodeler when I use the Alt key to select a polygon, it’s changing to white. If I clickagain it’s supposed to change to an other color and so again. But in my case it change only between 2 colors, not more. For example Alt click on a polygon : white, alt click again : back to the earlier color, Alt click again : white

Something is wrong for me

#297

@Michel

This is normal behavior.

When you press ALT before selecting a polygon, you’re in the ALT-selection mode that lets you make a custom selection that overrides the polygon target setting. So if you wanted to, say, select 4 specific polygons for the operation, you would hold down ALT and then click each in turn. Those 4 polygons marked in white will automatically be affected by the next operation, despite any target setting you have.

Pressing alt again while contacting a polygon already marked in white, will deselect it.

If, though, you have the operation set to POLYGROUP, and want to change the target to a new polygroup, you would press alt AFTER you have made contact with the target. It will change the polygrouping to a new group each time you press ALT.

TLDR:

Hold ALT before pressing polygon= Custom selection. White polygons= selected polygons.

Press ALT after pressing polygon = New Polygroup.

Note: Alt-polygon selection does not always work well with Live Booleans active.

#298

(I inadvertently posted this in the 4R8 announce thread but now I can’t delete that one. Sorry, admins.)

Looking forward to upgrading to P1 as it’s proven quite unstable on Sierra 10.2.5 but ZUpgrader does nothing. I drilled down into its folder structure and everything in there is from 2012 or 2014 so it appears not to have been updated for 4R8. Can anyone suggest a workaround? Thanks,

=G=

Update: Fixed! I failed to read the entire P1 announcement but the downloadable updater file worked just now: Mac OS X

Update 2: Thanks, admin. Might I be so bold as to suggest that Pixologic either a) update ZUpdater to work on current versions of OS X or b) remove ZUpdater from the 4R8 installer? :slight_smile:

The P1 announcement thread said exactly what to do:

  • If you encounter issues with the ZUpgrader, please download the appropriate updater for your platform: [Mac OS X](http://zupdates.pixologic.com/upgraderz4r8p1/ZBrush_4R8_P1_Updater_MacOS.dmg) or [Windows](http://zupdates.pixologic.com/upgraderz4r8p1/ZBrush_4R8_P1_Updater_WIN.exe). After downloading, this file can be run from anywhere on your system, including the Downloads folder. It will update you to ZBrush 4R8 P1 with no need to activate afterward.
  • If for some reason neither updater method will work for you -- or if you simply prefer to have a completely fresh ZBrush 4R8 P1 installation --
    • please uninstall ZBrush 4R8 and then install ZBrush 4R8 P1 using the full installer found at [Step 2 here](https://pixologic.com/zbrush/downloadcenter/instructions/). You do not need to deactivate 4R8 before doing this but you will need to do a new Web Activation after installing to generate a replacement activation code.

Thanks! :slight_smile:

Edit: It looks like we cross posted and you found your answer. I’ll leave this here, though, for anyone else.

#299

Oh yes now I remember : stupid me (but not so obvious in fact) :slight_smile:
Bad habits Sorry
Thank you Spyndel for this answer
Clear and short

#300

@Zber:
That caused it to drop to 20 mil!
Now what?
I want 22mil back!

ZBrush is crazy, on my old computer with half the memory I had this at 32 million…

EDIT: I just installed the p1 update and its now at 32.3 million, this is amusing!