ZBrushCentral

QRememsher Mac P2 Patched Installed - still getting !:/users/Shared/ZBrushData/Temp/

ZBrush Usage Questions
#1

Hi folks, tried updating to the P2 Patch for 4R4 for the mac but still getting the message !:/users/Shared/ZBrushData/Temp/objOut every time I attempt to use QRememsher. After operation “rememshing error encountered remeshing aborted” appears in top interface progress feedback.

I read this suggestion:

Now go to the Permissions section at the bottom of that window (you may need to click on it to expand it). It should say “Read & Write” for the Everyone user group. If it does not, change it and then click the gear icon beneath the list to choose the “apply to enclosed items” option. If it does say Read & Write, try changing it to something else, apply to enclosed items, then change it back and apply to enclosed items again.

Hopefully this will resolve the issue.

Unfortunately this didn’t seem to do the trick.

Any further system suggestions with regard a solution to this issue would be most welcomed.

Many thanks

the name of the file created in the /ZBrushData/Temp/ folder is objIn.OBJ
the path of the ZBrushScratchDiskPath.TXT file is /users/Shared/ZBrushData/

computer restarted and all disk permissions repaired also

System: Mac 10.5.8 2GHz Intel Core Duo

#2

I wonder whilst awaiting illumination/ divine intervention if someone could advise on the procedure for a complete clean deinstall and reinstall of ZB4R4 that I may try again in the hope that this may help?

I have ZR3 on my machine and working and would not wish to screw up the working of other versions

From the notes I could find on 4R2b:

In the ZPlugin menu, choose Web Deactivation and proceed to the license deactivation, as explained in Activation and Re-Activation. If you do not deactivate prior to un-installation, the un-installed machine will continue to count against your serial number and potentially prevent you from reactivating! On Windows, use the Windows Control Panel uninstall utility and follow the steps. On Mac OS X, simply move the ZBrush folder and the Users/Public/Pixologic folder to the Trash. Check the location where ZBrush was installed for extra files which haven’t been deleted by the installer. You can delete those folders if you do not intend to use ZBrush on this computer again.

Does this hold too for ZB4R4? Will it maintain and leave unaffected the ZB4r3 version live on my machine?

#3

Hello boozy,

I’m afraid I can’t help with the QRemesher issue - I suggest you submit a ticket at the Support Center for that (if you haven’t already).

If you want to re-install ZBrush 4R4:

  1. Don’t de-activate anything.
  2. Move the ZBrush 4R4 folder to the trash.
  3. Move the Users/Shared/ZBrushData folder to the trash.
  4. Re-install ZBrush 4R4 from the installer.
  5. Re-activate ZBrush 4R4 via the web (you should simply be given a copy of the activation code).

After re-installing you will need to use the updater again to get Patch 2.

Edit: You will still be able to use ZBrush 4R3.

HTH,

#4

Marcus, much obliged to you good Sir. I shall do as you kindly suggest and if the problem still persists after a reinstall I shall submit a ticket with regard this issue.

One further question Marcus - should I also delete the Pixologic folder (within the Shared folder) containing the GoZ exchange components?

Many thanks.

#5

Yes, if you wish, though I don’t think that’s essential.

#6

Alas Marcus, my attempts to rectify the QRemesher issue with a reinstall have come to naught.
Again thank you with your help on this matter, much appreciated.

It appears that after an initial installation of ZBrush 4R4 - disk utility reports

" Group differs on Users/Shared" , should be 0, group is 80

However repairing this permission before installing the P2 update Patch had no effect on QRemesher working - exactly the same alert as before. I can report that after the P2 patch no such permission issue resurfaces and whether ZBrush is installed on my system, permissions fix or no with the Users/Shared folder - QRemesher will not work.

It appears that it’s time to finally place ticket report with Support in hope of a solution.

#7

Sorry jumped the gun…, Thanks Marcus.