QRemesher not updating objOut.obj...

[Sarford]

Hi all,

Up untill today QRemesher worked fine but now it started giving problems.
I remeshed a sculpted pilar today and QRemesher came back with a torch, a remesh of a sculpt I did last week.
I tried different polycount settings, thinking that maybe would solve the problem, but it didn’t, I still got the torch.

The next thing I did was to rename the Temp directory from /users/shared/ZBrushData, as that is the directory QRemesher writes its files to. Upon restarting Zbrush created a new Temp folder. I loaded my file again and applied QRemesher.
A few new files were written to the Temp directory, including a objIn.OBJ but in the end QRemesher gave and error stating it couldn’t write to objOut.obj. Strangely enough Zbrush didn’t create a new objOut.obj file.

Then I copied the objOut.obj from the renamed Temp folder to the new Temp folder, restarted Zbrush and re-applied QRemeshed. It again came back with a torch…

I updated to Zbrush4R5 and tried the same thing again with the same results. The priorities of the ZBrushData folder are read and write for everybody and ZBrush does write new files, it just doesn’t update the objOut.obj it seems…

Is there anything I can do to solve this problem?

Cheers, Simon

[chrono1081]

I have the same thing happen! I can’t use qRemesher because of it. Everyone raves about how great it is but I have yet to see it.

Basically a work around provided to me from Pixologic was to delete the temp folder, then try and remesh the default sphere scene that is in Lightbox. It worked for me but since qRemesher always crashes for me I stopped using it all together. Hopefully you have better luck.

I should also mention I can duplicate it on all three of my OS installs. I’m on Mac OS, not sure if it does it on Windows.

[Sarford]

Hi chrono1081, thanks, that was really helpful. It didn’t solve the problem but it did write out an objOut.obj file and set me on the path to a solution!

Well, it seems the problem is solved. Seems the problem in the end wasn’t QRemesher but the mesh itself.

After trying chrono1081’s tip by QRemeshing the standard sphere I got a nicely remeshed sphere back. Next I tried the torch (a sculpt from last week) and that also worked. That made me suspect the pilar mesh was the culprit. So I deleted the highest subD-level to get a mesh of about 1 mil pollies and saved it as a separate ZTool. I then closed and re-opened Zbrush and loaded the pilar tool. Just to be sure I checked the mesh integrity and it came up with a few small problems. After fixing the mesh I applied QRemeshed and everything worked fine again!

Cheers, Simon

[carver]

Hey guys, I’m a bit late to the party, but I might have a solution. Do you use CCleaner? It is a tiny, yet powerful piece of freeware for cleaning all of the fragments that gather in temp memory, and also all the other gunk that builds up like cookies, etc. Most of the recent enhancements to Zbrush are extremely memory intensive. I have had the same thing running Qremesher, and other plugins like decimation master, and especially Dynamesh. When I get a wonky error, I just run CCleaner and it has solved my problems every single time. I don’t even close ZBrush first, I just launch it with Zbrush running. It only takes about 20 to 45 seconds.

I teach Zbrush and do in house coaching for a number of companies, and that is the first complaint I hear. “Why is it sooo sloooow.” Or, “Why do I keep getting these buggy results.” I carry CCleaner around on a thumb drive and install it and the first time it runs it can take a few minutes because who ever is doing the IT isn’t doing much to keep the machinery well oiled. After it finishes I will launch Zbrush and do the exact same process they are having problems with, perfect results, and their eyes bug out in wonder.

The link is http://www.piriform.com/ccleaner/download. I have always used the last downloading mirror from Piroform, the makers of the software. Check it out. It can’t hurt.

Derek