Twitter discussion: What Andrew is currently doing.

[Taros]

I am working over big speed-up of surface tools. They have really great potential.

That's really interesting. "surface" is a generally word, so I hope he means the voxel surface.

By the way: You are invited to use this thread to discuss all running twitter posts from Andrew.

[haikalle]

That is interesting. I would guess he is talking about polygon surface... But we have to wait and see.

But I surely smell 3.2 or even 3.5 here...

[haikalle]

It seems that someone is trying to destroy Andrew's computer... Maybe someone from z-team or maybe even Bill Gates. Guys, install linux right now....go..go...

[Javis]

He's talking about voxel surfaces in those posts.

[Taros]

At least my system recovered. Really strange situation - windows downloaded update -> out of space -> crash -> unable to boot....

Never forget to make a periodic image copy of your system. This can save your job life fast and clean. I know what I say...

[ghib]

That's a shame, I thought for a second that he meant the actual paint surfacing tools which in my opinion could REALLY do with some speed-up.

[Taros]

That's a shame, I thought for a second that he meant the actual paint surfacing tools which in my opinion could REALLY do with some speed-up.

As I know nobody really knows what he mean and all is only anyone's guess...

[cuffins]

So maybe instead of guessing around it's better to ask Andrew

[Andrew Shpagin]

By mo means the main problem of voxel sculpting is speed.

So, I tried to speed up voxel tools in surface mode because they have big potential to be improved.

It opens good workflow - work with voxel objects up to 4-6M/object, then make tiny details with surface tools on bigger resolution.

[artman]

By mo means the main problem of voxel sculpting is speed.

So, I tried to speed up voxel tools in surface mode because they have big potential to be improved.

It opens good workflow - work with voxel objects up to 4-6M/object, then make tiny details with surface tools on bigger resolution.

Speed improvement is useless if you dont get rid of dots/streaks artifacts problem first .

(Speed is already pretty cool...but if you get a dot artifact on a model at its final stage and there is details around that dot well...you cannot smooth over it, otherwise the details underneath get destroyed.In my opinion that is the main problem with surface tools right now.(especially SF Pinch))

[Taros]

Speed improvement is useless if you dont get rid of dots/streaks artifacts problem first .

(Speed is already pretty cool...but if you get a dot artifact on a model at its final stage and there is details around that dot well...you cannot smooth over it, otherwise the details underneath get destroyed.In my opinion that is the main problem with surface tools right now.(especially SF Pinch))

I don't agree. Speed and bugs with pens belongs tightly together. If you spend all your cpu speed for calculating voxels, which speed you will have at the end for correct brushes?

No, I think this is the right way for optimisation all voxel elements.

Keep going on Andrew!

[artman]

Speed and bugs with pens belongs tightly together.

DotsNStreasks artifacts after voxels-to-surface conversion have nothing to do with speed.

Because in surface mode all surface operations gets converted without any disturbance from the brushes operations,it got the cpu all for itself

:the problem is the conversion itself in relation to the precision of the surface operations applied.It clearly manifests when doing precision work with SFPinch.

My point was just: even if it takes you a nanosecond to sculpt a Rodin ,

if there is artifacts on the endmodel you cannot use that mesh to bakes normal maps or displacement maps or get any render out of it.

And you cannot smooth the artifacts either because there is some details under it.

Thats all that I meant.

I dont care, Im just an amateur doodlist.

But professionals need the end model to have no artifacts.It is ground base simple.

Even if performance is superfast the end result needs to be usable...Otherwize its the whole use of the surface tools that is compromised even if they get very very fast.

Andrew is already working on fixing this ,but the ideas he has to fix the problem are

much harder to implement and will take longer time(he wrote about this)and Im aware of that,

so my post was stupid because I know the answer.

Speed imrprovements are probably much possible and also very welcomed.

Andrew seems to do what is the best+most possible at all given time which is best way to work.

And Im sure all very hard problems are given a lot of thinking time.

Im a SfClay/SfPinch addict so news about speed improvements are great.

[Taros]

DotsNStreasks artifacts after voxels-to-surface conversion have nothing to do with speed.

...

I haven't known this. I am not a programmer, just a professional user (as some people says this about me... )

But I agree the rest of your post. Come on, let's see what will happen. I am shure the programmers are listening and know what is important and what not, and what is feasible or not.

The users are the same everywhere: They would like to see all functionality now and immediatly...

[Taros]

trying to solve one of the most complex problems - artifacts after pose tool... It takes some time...

I hope with this solution the move tool artefacts will disappear too. That would be really great.

I guess, if Andrew really removes the artefacts in the posetool, a lot of other similar problems will disappear too.

Be creative

Chris

[Taros]

Woohoo! At least after 3 days of terribly complex work I got rid of pose/move tool artifacts (sometimes long lines and dots appeared).

It is the second principal problem of voxel sculpting (the first is speed of course).

Yes yes yes!!!