Jump to content
3DCoat Forums

3DCoat 2024 development thread


Andrew Shpagin
 Share

Recommended Posts

  • Advanced Member
1 hour ago, poeboi said:

A short while ago I sent a bug report for 2021.17 , experiencing some initial crashes on repeat attempts with the muscle/tube tool using alpha on a roughly 500k vox layer, while it was fine in 2021.16

I think my bug report can be safely dismissed after all, because after a while the crashing ceased completely and it works fine now without any problems:unknw:

I got up to 40mil and i got bored but... I tried all the stroke tools and they were fine I couldn't replicate it

crashtry.jpg

  • Advanced Member
2 hours ago, poeboi said:

A short while ago I sent a bug report for 2021.17 , experiencing some initial crashes on repeat attempts with the muscle/tube tool using alpha on a roughly 500k vox layer, while it was fine in 2021.16

I think my bug report can be safely dismissed after all, because after a while the crashing ceased completely and it works fine now without any problems:unknw:

nope it does crash you're correct lol i wasn't using alpha

  • Advanced Member
4 hours ago, Silas Merlin said:

I'm not convinced.

I played with the N key to move objects in combination to 3d mouse. I really tried, spent some time with it, on different days.
It's really a fun novelty, yes. but. I'd love to hear about someone who has really put it to practical use.
My conclusion was/is that I want the 3d mouse for... navigation. So, I would/will use the trace mode, yes, but not with the N key.
(and in fact it is not really a novelty, Second Life has has it for years, but I have never heard of anyone who uses it. It is just not practical, because while you manipulate the object you lose the ability to navigate... and without the ability to navigate it become impossible to judge the real position of the object, because you are in 2d the whole time).

Your suggestion is appealing, but I think it would be like what I just described. a nice novelty, probably not practical.
As it is, it is possible to define the stroke origin point by "touching" an object at the distance at which you want your stroke to start. Normally you can then move into the void (being careful not to touch anyting else) before you start your stroke (except at present if you do that with muscle tool your stroke depth will be zero).

No, what would be really nice would be to be able to manipulate the stroke origin some other way, (and to manipulate an object N-key style too).
For that, the only thing that would make sense to me would be to do it with hand gestures in the air. (kinect style).

 

Actually, what you can try Silas is ghosting the layer and changing the pick behaviour to act, but don't pick.  That should help in the situations where you draw over existing geo.

  • Thanks 1
8 minutes ago, Elemeno said:

anyone else got a slight lag when fast movement left to right its become unresponsive.. not sure if its my end or not but blender at 2 mil is a lot more responsive

You forgot to write the parameters of the brush, what tool.
There is no need to compare warm to soft.
Also, the result depends on the size of the mesh.

  • Advanced Member
9 minutes ago, Gorbatovsky said:

You forgot to write the parameters of the brush, what tool.
There is no need to compare warm to soft.

sorry that was silly of me, for me the clay thick layer is very slow in voxel mode 

thick layer parameters

thicklayertool.jpg

the responsiveness is quite slow.

and the voxel tools grow tool crashes me instantly 


 

Edited by Elemeno
  • Reputable Contributor
7 minutes ago, Elemeno said:

can anyone else check the carve tool on voxels please.. mine isn't doing anything at all

Carve tool works here but it seems that after a tool has been updated in a new build you may need to right click it > restore default.
Except that of the pure voxel tools, only Build and 2d-Paint seem to have that option.

The build tool did not work for me at all when it was reintroduced, until an ulterior version.

  • Contributor

Since there are no dx versions or 32bit users you can rename 3DCoatGL64 to 3DCoat2021_buildver. 

I am very happy that you released 2021. It has a great potential! Don't hide.

All the best,

Niklas

31.07.21 2021.18

- Very important changes in brushing, First, if the pen touches the tablet and you paint something exactly all trajectory that was really drawn on the tablet will be drawn in the model. It makes drawing really responsive, solves the problem of "backstroke" mentioned before in TabletPC mode, solves the problem of shorter strokes than actually drawn. This should strongly improve the drawing experience.

- Offset problem principally fixed. But currently (at this build) at a cost that all rendered 1:1 in screen resolution without system scaling, so UI looks smaller. Probably you will need to set Large font for 4K monitors. Or use custom. Generally, I like how it looks on my 4K monitor, much sharper. This solution is still under the consideration.

-  Fixed crash in muscle/pen, toothpaste.

 

Treat this build as BETA because of that two big changes, then need at least a short time to be tested.

  • Like 3

Drawing is really responsive, but i cant avoid this bumpiness when stroke (wacom).

Spacing switched on/off same result.

Thanks

bump.jpg

//fixed

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...