I’m seeing another problem with double turned on, and this is outright weird:
Instead of the first object going all pixelated and the insert brush being visible only from the inside the first object vanishes completely till I am done drawing the insert brush… I can see both when I let go but I still have no idea what I’m doing since I cant see (while I’m drawing it I mean).
Is this me?
make sure you don’t have solo on.
Ahha!
It was Solo! thank you!
I was playing with transparency so I could see where I was putting mesh insert things to make holes…
Now is there any way of turning off that bloody thing where the object you are drawing on looks like it self and not a flat screen while you are drawing?
I have two queries:
1 - I cannot get my 16 bit custom alphas to load from the *Startup/Alphas folder - or from the ZAlphas folder…
Is there something I need to know to make this work?
2 - Polypainting with Curve Mode ON - the polypaint position doesn’t update with the curve when the curve is edited (moved).
Please help me on these issues - Thanks 
CeeKay
Hi, my download link for 4R4 is expired and I cant login to https://support.pixologic.com/ because I forgot my password. I requested the new password and entered my email and the system said the new password was sent but it is not coming. I tried several times. The email address is fine. What should I do ?
polypainting and layers bugs 1, 2, 3 and 4
Bug 1 - Polypaint information on a layer is not fully erasable by default - Able to reproduce 100% of the time.
Steps to re-create:
1. Load any model
2. Fill the base layer with a color
3. Create a 3D layer, turn on record
4. Paint some color on the layer with RGB set to 100
5. Erase the poly paint information that you just applied via the “alt+left click” method
6. Set your RGB down to a low level (around 5) and select a different color
7. Paint over the area where you initially laid down color
You will notice that the first color will show through, creating an artifact thus rendering erasing it in the first place useless.
Here is a video showcasing the issue:
http://screencast.com/t/T1cenvPze
The following steps are a workaround for the above issue:
- Create a layer, turn it on, hit record.
- Manually fill the entire layer with any color first (since “color > fill object” will also do nothing).
- Use the “alt+left click” to erase all of the color that you just painted. This basically makes every vert on the layer “dirty” and now you will no longer have any artifacts if you paint/erase any new color.
Fix outlined in video below:
http://screencast.com/t/TVHXmEbs
Bug 2 - Polypaint from texture will not work on a new layer - Able to reproduce 100% of the time.
Steps to re-create:
- Load any model
- Create a 3D layer, turn on record
- Make sure RGB is set to 100
- Load a texture onto the tool via - “tool > texture map”
- Click on “polypaint from texture” under “tool > polypaint”
You will notice that the 3d layer gets filled with 100% white as does the base layer which makes no sense.
Here is a video showcasing the issue:
http://screencast.com/t/OD7FmjKvaiT
A workaround for this is to first manually fill the entire 3D layer with any color first (since “color > fill object” will also do nothing). The same fix for the first issue in this thread.
Bug 3 - Polypainting from one layer can be baked into the base model undesirably - Able to reproduce 100% of the time.
Steps to re-create:
- Load any model
- Make sure RGB is set to 100
- Load a texture onto the tool via - “tool > texture map”
- Click on “polypaint from texture” under “tool > polypaint”
- Create a 3D layer, turn on record
- Make sure RGB is set to 100
- Manually fill the entire layer with any color first (since “color > fill object” will also do nothing).
- Load a different texture onto the tool via - “tool > texture map”
- Click on “polypaint from texture” under “tool > polypaint”
- Turn off “RGB” and turn on “Zadd”
- With the 3d layer record still on make a edit on your mesh with zadd
- Turn the 3d layer record off
- Turn the 3d layer record back on and make another edit on your mesh with zadd
- Turn the 3d layer record back off and turn the 3d layer visibility off.
You will now notice that the polypaint information from the 3D layer you just turned off has been baked down into the base models polypaint destroying your base polypaint information.
Here is a video showcasing the issue:
http://screencast.com/t/VHeUxcU08e
I have found no workaround/fix for this, as it is just an issue of working on a layer and turning record on and off which will happen to anyone dozens of time during a sculpting session.
Bug 4 - “Tool > Layers > Split” does not accurately split shape and polypaint information. - Able to reproduce 100% of the time.
Steps to re-create:
- Load any model
- Create a 3d Layer
- Make sure RGB is set to 100
- Manually fill the entire layer with any color first (since “color > fill object” will also do nothing).
- With the 3d layer record still on make some drastic and noticeable a edit on your mesh zadd
- Turn record off on the 3d layer.
- Hit the “Tool > layers > split layers”
- The newly created “shape” layer will only correctly show the shape information if “record” is turned on. If record is not on but the layer is visible, you will only see a very subtle change in the geometry, basically an artifact. This is useless.
Here is a video showcasing the issue:
http://screencast.com/t/ArOAW4JcTjE
Geometry issues with 3D Layers, bugs 5, 6, and 7
Bug 5 - Model explodes- Able to reproduce 100% of the time.
Steps to re-create:
- Select any model.
- Create a layer and turn on record at highest level
- Move down to lowest sub d level
- Make an edit
- Change layer intensity slider to 0.
- Go back up to the highest sub d level of tool
- Change layer intensity slider to
- Model will explode.
Here is a video showcasing the issue.
http://screencast.com/t/citQf54z
Bug 6 - Layer artifacts left over even when layer intensity is at zero. This issue has been in zbrush since the implementation of layers.- Able to reproduce 100% of the time.
Sets to re-create:
- Select any model.
- Create a layer and turn on record at highest level
- Make an edit
- Go to the lowest sub d level.
- Change layer intensity slider to 0.
- Go back up to the highest sub d level of tool
- There will be artifacts left over from the layer even though the layer intensity is at 0.
Here is a video showcasing the issue.
http://screencast.com/t/znEvFIbY
Bug 7 - Toggling layer visibility or changing layer intensity while not at highest sub d lavel causes corruption.- Able to reproduce 100% of the time.
Sets to re create:
- Select any model.
- Create a layer and turn on record at highest level
- Make an edit
- Turn off record.
- Go to the lowest sub d level.
- turn off the eye indicator on the layer
- Go back up to the highest sub d level of tool
- There will be artifacts left over from the layer even though the eye is off
Here is a video showcasing the issue.
http://screencast.com/t/4igw2d4GY9
Furthermore, I have found that doing any of the following things while not at the highest sub d level will produce drastic artifacts on the model, rendering layers useless.
- Changing the layer intensity slider at any level but at the highest sub d level
- Using the timeline to adjust layer intensity at any level but the highest sub d level.
- Turning the layer visibility on or off at any sub d level but the highest sub d level.
An easy fix for these issues (if Pixologic can’t fix the bugs) is simply to disable turning a layer on or off or adjusting a layer intensity while the tool is not at its highest sub d level. Simply grey out the layer eye icon and the layer intensity slider. That would fix all of these issues.
Can we have future updates where you are not required to reactivate ZBrush. It’s a lot of work for my school’s IT department to have to reactivate a whole bunch of floating licenses just because of a minor patch.
I noticed one other had one of these problems, but no answer has been posted. Please note, I am a Zbrush noobie, having only played with the 4.0 trial a while back, but I know it didn’t have these problems.
-
I created a new material and put it in the Lightbox folder. On next open it completely lost the material, reverting, instead, to what seemed a random default material. I don’t know if this is normal or not. I’m fairly sure having the other, default materials change to completely different materials at the same time, something else it did on that model, isn’t normal.
-
When I try to use a material from Lightbox, it replaces whatever default material I have selected at the time, so I’m not able to access it anymore until I restart zbrush. I can work around it by choosing a material I know I won’t work with to replace, but it isn’t exactly convenient. Again, I don’t know if this is by design or not.
-
When I try to assign a material to something with a UV/texture on it, it ignores the ‘fill object’ command. If I delete the UV, it will accept a material again, but the moment I put a new UV on it loses the material as if I’d never assigned one, and goes to whatever is presently selected. This, obviously, simply won’t work.
My box is:
Win 7 64bit
32GB ram
Intel Core i7-2600 [email protected]
This is a brand new computer, and a fresh load of Zbrush 4R4, with P2 update. I had no problems loading or updating, and have not installed any plug-ins as of yet.
There seems to be problem with Stroke > Curve Mode > Curve Modifiers. The ‘Intensity’ function works alright with the ‘Curve Falloff’ but the ‘Size’ function has very erratic behaviour.
For #1:
I personally never use LightBox for some reason, maybe because things that scroll sideways drive me up the wall.
Anyhow I find that the best way to save things like materials so that I can get at them with out thinking is to put them in the Materiel Pallet.
I have 64 Bit windows 7 as well so the directory should be the same:
C:\Program Files (x86)\Pixologic\ZBrush 4R4\ZStartup\Materials
Try saving them in there, that SHOULD do the trick, normally I would warn people that this can slow down the Materiel Pallet a tiny bit if you add a lot of files to it but your computer makes mine look like a clock radio from the 70’s.
For #2
That is normal, I don’t know why. The method I mention above fixes this in the long run. Basically all materials you make will be made of some other materiel, so you wind up being sort of forced to restart ZBrush to get them back, this gets irritating but you get used to it. This problem can destroy your work flow completely. However once you have it saved you are all set.
For #3:
I have no idea how UV’s and textures are supposed to work, in fact I would say that this is a question for someone else. I have never understood how that stuff works. I do know how to use UV’s to mangle things in interesting ways but that is not what you are asking.
I hope this helps.
Cheers!
Mealea
I didn’t use Lightbox at all in the trial version, but for some reason my brain switched while watching R4 tutorials and I no longer mind. It’s actually kind of fun and refreshing. It’s sad that this little break in workflow damps that down some.
As for the UVs vs. materials, come to find out it was the texture, not the UV. Support got back to me very quickly when I put in a ticket and suggested I use the material fill in the texture palette. Problem solved. I barely have an idea how this stuff works, myself, but I’m determined to learn. I want to be an excellent artist, and that requires knowing my tools. I suppose some things simply must be learned by mistakes. chuckles
By the way, thanks for the response. It helps a lot to know those other quirks are normal. I shall learn, adjust my workflow accordingly, and move on.
I have been having issues with my custom UI items still. I set up a bunch of custom menu palettes and then assigned them to hot keys. I stored both and rebooted zbrush. Everything seemed to be working, but then I changed one more menu in “customize ui” mode and then stored that and upon reload the hot keys still worked, but the menus only would have first 2 items in it and not load the rest?
Am I missing something here? Or doing anything wrong?
Thanks for the help!
The “Front” button in spotlight does nothing. The “Back” button works fine but the front does nothing.
I am also now having a random issue where my “command z” shortcut will stop working? then I will remap this to the “undo” button in the edit menu and shortly afterwards will have this stop working again randomly. I have almsot given up on what is causing these weird issues… also posted about my CPU usage being maxed out when using the software… dunno if I am just missing something? My software just seems buggy.
In the Stroke palette, under Curve, even with ‘Snap’ turned off, the curve still snaps to the underlying surface. ‘Snap’ will not turn off.
What brush or brushes? I tried with an insert brush earlier just to a cube, and with it off was able to drag curves every which way, entirely off the object.
Hello
I don’t know if its only me… but I did’t found much about this problem related to windows users.
At first I will tell my specs : Windows 7 Proffesional, Core i5 3570, GTX660 16GB Ram, Wacom Intuos 3.
I have an issue of screen tearing in Zbrush 4r4 with and without update 2 installed. It appears as a diagonal tear with additional artifacts looking like bigger pixels around moving area.
I tried to debug it a little and it seams to be connected with multidraw option. When I disable or limit multidraw to lower thread the issue goes away (2 thread out of 4 seems to fix most of a problem).
I read here that Mac users were having problems with thread priority. After setting higher priority in win7 task manager tearing was less visible. Although it wasn’t perfect so I searched some more.
I read on other forum that one user had same problem, but after lunching FRAPS it went away.
After lunching FRAPS in my case at first tearing was still present, but I checked some options and it went away when FPS counter display was turned on or there was ‘Monitor Aero Desktop’ option on.
So it gave me a hint that problem could be connected to Aero desktop. After disabling Aero there were no issues with tearing at all even in 4 threads multidraw.
I hope this will help someone
Of course if my hardware isn’t broken and I am not only one dealing with it :/… although I haven’t noticed anything similar in any other app lately.