Hi, I’ve been tinkering with r3 for a day and while it’s good and innovative it is very buggy and unstable. I’ve had numerous freeze crashes, and strange UI “freak outs” where the UI just blips on and off and none of the navigation tools work. When I restart I get this…
Also a lot of the Alphabetical buttons for the brushes don’t work.
Looks like a major patch will be needed to get r3 up to speed.
Yeah. I’ve seen that messed up polysphere a couple of times myself.
It’s as if the sphere got masked and scaled. In my case its in three
axes though (I get a many-pointed star), in your example it looks like
it got scaled on only 1 axis.
I’ve also had R3 crash on startup twice (with what looks like heap corruption
according to the JIT debugger - it crashes in the runtime heap allocator).
But so far, I’ve not had any problems once I have it up and running.
I’ll be keeping my fingers crossed for some more ‘testing’ tonight.
G.
Same here but now I have the “crash heeby jeebys”, high blood pressure inducing fear of a crash, followed by a slight depression and anger.
You can turn off the default polysphere by editing the startup script.
Details here: http://www.zbrushcentral.com/showthread.php?t=76803&highlight=turn+default+polysphere
If it’s not there it can’t mess up right 
I’ll try it later.
It could well be that the messed up PS is the result of cached data
corruption from a previous ‘unplanned exit’. Of course knowing that
doesn’t help much.
I guess I never thought that it could just be the sphere. It seems to me that something is very wrong on the backend. My first intuition was to blame the Visual C++ install, but I always tend to blame Microsoft first.
Here’s a variation of ZBrushBugArt 
I’ll just keep posting the differing variations.
Aside from the MeshSphere3d ZB 3.5 r3 seems to be working better now after some performance and threading tweaks.
Here’s my entry…
[
](javascript:zb_insimg(‘170434’,‘StartupPSEntry.jpg’,1,0))
G.