Sorry about that. The version number in the top left corner is ZBrush 4R2B. Good to know that when I do get the update downloading that it won’t overwrite the folder name, however it’s not a case of me updating and just not realizing that it is already done.
Ok, I’m not on a Mac but I imagine the proceedure would be the same. You downloaded the Installer from Pixologic website. The installer for me was about 230 MB and came in a zip file. In that zip file were two files, the installer and the installation instructions. The installer was put into the root directory of ZBrush 4R2b, at which point I double clicked on it and it installed version 4R3. At this point, all I had to do was activate my license.
Ok, I am having some strange sparkling artifacts in BPR renders. I have changed lights, materials, on multiple files. Very strange, and different with each render. There are pure RGB spots, very evident on fibermeshes, and seem to be along mesh borders, and subtool edges. I have tried all types of adjustments, and they have popped up on every render since I got the ZB4R3 update.
Check it out…
Notice along the edges of the violin, bow, and chest hair??
Thoughts???
I am on a PC, Win7, quad core if that matters.
same for me!
MacBook Pro 13, OSX 10.6.8
I have Zbrush4R3 installed both on my dell laptop and my sweet little Samsung Slate 7 Tablet pc. it installed and runs just fine on both except that when I click Auto Update(check for updates) on the Slate 7 I get the 2 errors which you can see in the attached screenshots.
Both systems are running windows 7 64 bit and both seem to have various msvcr100.dll files in exactly the same locations.
Any ideas? I don’t want to go through a re-install loop without knowing if that actually fixes the problem, which I doubt because the install seemed to work flawlessly on the Slate.
Ok, I figured it out. The artifacts were being caused by settings in the BPR filters. The main culprit was the sharpen filter, and the blend mode and mask settings.
SEE
No more sparkles. Problem solved, carry on with your lives.
I already submitted a support ticket on this bug/issue, but I found a workaround, so I thought I’d post it here for those that might run into the issue and need a temporary workaround:
Bug Description:
Now, the bug I found is that after rendering with HD Geometry ON in the Render settings, on an object with significant density AND polypaint, ZBrush will repeatedly attempt to “Preview” HD geometry once rendering is complete (as if you pressed the “A” key with the cursor away from the tool to activate HD preview) even without the appropriate Hot Key, and the UI becomes partially unresponsive. You can navigate in the editing area, sculpt, etc., but you cannot click on most buttons. They simply don’t respond. Essentially, rendering with HD geometry on a detailed tool with polypaint functionally hangs parts of the program.
System Specs:
Windows 7 Ultimate, 64 bit, 12GB RAM, Core i7 Quad Core w/HT, NVIDIA GeForce 280 dual graphics cards in SLI.
Tool object:
33 million HD polys, 2 million standard polys, though I’m not sure if this will happen with fewer polys, it’s possible, though 8 million HD polys total did NOT trigger the problem, so it seems to be memory dependant.
Steps to reproduce:
-
Start with a clean install of 4R3 (I upgraded using your 4R3 patcher from a clean install of 4R2, I even double checked downloads with multiple downloads and file comparison utilities to ensure that the file integrity was good.), all options set at default. In the case of my system, 8 threads is the max setting default, as would be expected for a quad-core with hyperthreading.
-
Create a sphere tool, convert to dynamesh, and subdivide until you have ~2 million polys, then subdivide HD until you have ~33 million HD polys.
-
Fill the object with polypaint, a solid color is fine. The bug DOES NOT manfest if there is no polypaint.
-
Set your render settings to include HD Geometry and hit the BPR button.
-
After rendering, the bug will be present, forcing a shutdown of ZBrush, as the UI becomes essentially unusable.
In my diagnostic process, I discovered that limiting ZBrush to ONE thread seems to prevent the bug from happening, suggesting it may be an issue with thread deadlocking, or a thread simply not exiting it’s loop properly, but I haven’t seen your code, so I can’t say for sure. In any case, that’s a reasonable workaround if one is willing to wait for the rendering to take significantly longer to complete.
I hope you find this report helpful. It will be really nice to have fixed ASAP so I can render HD geometry with polypaint once again using all 8 logical cores my machine affords.
This probably won’t be terribly helpful, as I know you’re already working on a 64-bit version, but since the bug DOES seem to be memory dependant (poly count seems to make a difference), and since ZBrush could DEFINITELY benefit from more RAM far moreso than it could benefit from the great tools you’ve added (like fibermesh)… so if you guys would make a 64-bit version a top priority I know that would address a LOT of issues, especially as you continue to add great new features which undoubtedly utilize even MORE memory than previous versions. Just sayin’ 
OK, that’s all for now. Let me know how this progresses, and let me know if you have any questions. I can be reached by email or by cell xxxxxxx.
- Robb Ryniak
If reinstalling doesn’t fix your issue, try installing the file you need from Microsoft’s website… it’s the Visual C++ 10 runtime: http://www.microsoft.com/download/en/details.aspx?id=5555
For some reason spotlight doesn’t seem to be working-- looks like it painting a mask instead of color. It also looks like there’s an alpha applied to the brush when I narrow the radius even though no alpha is selected. ANyone else having spotlight problems?
Love the new fibermesh stuff btw
Thanks,
–TK
hi the micromesh select button in the display property’s sub-tool pallet is not there? the lowest button available is a button saying bpr smooth normal instead?
i have tried pressing the micro-mesh button in the render pallet no joy
edit: answered question
discovered the issue… its been moved to the geometry pallet now just called “micromesh” press to select the tool you want to use
Hi everyone.
I’m excited with the new update, but there’s one little freaking problem.
I can’t download it!!!
It says MISSING PLUGIN.
What plugin? I’m eager to install it!
PS. Using Win7 Chrome
Got the exactly the same problem on 10.6, updating r2B to r3 and downloading the files again fixed it. Thanks.
another thing i’ve noticed when the preview window for editing the exported jpeg comes up the file size says 0kb and cannot be adjusted. so it’s definitely letting me know there’s nothing there to edit. please help!
I’ve also noticed the jpeg export problem. I can still export .psd just fine though.
yes. to note .psd export works fine for me too and of course that means i can always export an image. the new jpeg option was just very nice and makes things a lot easier. would love to have it again.
Crashing constantly on a mac OSX 10.6.8, not just 4R3—it crashes the whole mac.
No particular workflow, just basic Dynamesh & standard brushes.
No other programs running. Wacom Bamboo tablet attached.
Any ideas?
Thanks
What hardware are you running? I’m on 10.6.8 and having no problems.
Thanks for getting back 
I have a 27" imac Quad core. I’m finding if I save continually the crashes are less. Maybe its memory management?
I have max memory (can’t remember exactly how much that is though)
Thanks a lot man, that actually did the trick.
I would have thought the Visual C++ runtime is always up to date through windows update. apparently not. live and learn