Jump to content
3DCoat Forums
Andrew Shpagin

3DCoat 4.7 (BETA testing thread)

Recommended Posts

Downloading/uploading the mac/Linux builds of .21 to Drive right now. It will take a few hours, the download from Germany takes a long time, but once it's here for me, it won't take long to upload for folks.

Share this post


Link to post
Share on other sites

Not sure if its a bug, but the scrape tool will not work with the line brush. It works fine with the curve brush tool . Image attached

using latest version 4 .7.20

Screenshot_3.png

Share this post


Link to post
Share on other sites

Reported, and this is the answer from dev team:

I disabled line drawing in this tool. It is better to use Spline Stroke.

 
Andrew
  • Like 1

Share this post


Link to post
Share on other sites
20 hours ago, Carlosan said:

Reported, and this is the answer from dev team:

I disabled line drawing in this tool. It is better to use Spline Stroke.

 
Andrew

If that is the case, then he should just remove the line draw mode, altogether

  • Like 1

Share this post


Link to post
Share on other sites

You right.

In the next release all the strokes disabled are ghost.

  • Like 2

Share this post


Link to post
Share on other sites

From my "very" limited experience in 3D coat changing the alpha for some brushes (clay) does not seem to make a difference. If this is the case could this option be ghosted as well. If easily possible.

I would be also be happy if this was stated in the brush description.

Edited by 3DCNC
added details

Share this post


Link to post
Share on other sites

4.7.22

- Import tiles as UV sets fixed problem with negative tiles

- Warning about incorrest scene scale.

- Polished, improved retopo primitives

- curve / line drawing problems corrected.

Published only small changes for stability improvement. No slowdown there. Big things are in development.

  • Like 6

Share this post


Link to post
Share on other sites

I am not able to use the numeric input fields in the pose tool window.

Second: Undo does not set the gizmo position to the previous position in pose tool. Only anew undo command does it. 

Can someone confirm this please?

Thank you

  • Like 1

Share this post


Link to post
Share on other sites

Undo does not set the gizmo position to the previous position.

confirmed

  • Like 1

Share this post


Link to post
Share on other sites
1 hour ago, Carlosan said:

Undo does not set the gizmo position to the previous position.

confirmed

Thank you Carlos.

What about my first issue? Are you able to move a pose selection (line f.e.) by typing values into input fields?

Best wishes
Chris

  • Like 1

Share this post


Link to post
Share on other sites

Does anyone elce have this Problem?

-Using the text tool will not apply any Mesh once Applying.

-Using the latest 3dconnexion Driver with a older Hardware ( Space Traveler )   It works fine in Blender and other CAD Programs real smooth too! Yet here only the old Driver seems to work and if I use the old Driver it works, but it is real clunky and very rough even on the best settings. Now it doesn't even work at all. Did something change?

Share this post


Link to post
Share on other sites

You mean direct move ?

after typing values into input fields and press Enter... yes, it moves

 

DirectMove.jpg

  • Like 1

Share this post


Link to post
Share on other sites
8 hours ago, Carlosan said:

You mean direct move ?

after typing values into input fields and press Enter... yes, it moves

 

DirectMove.jpg

No. I mean the regular gizmo. The old gizmo does not update the coordinates and does not move to the new position. Coordinates are always 0,0,0 what is useless if you want to reproduce movements.

  • Like 1

Share this post


Link to post
Share on other sites

confirmed

The typing values in the XYZ position change only the position of the displayed gizmo, until the gizmo arrows are selected.

Then the geometry jump to the new value previously typed.

1.jpg2.jpg3.jpg

 

Share this post


Link to post
Share on other sites

В новых версиях попробовал навигацию свою сделать-у меня поворот вьюпорта за счет пкм как в браше,так вот при использовании инструмента отрезать/cut не работает этот самый поворот пока под курсором сама модель. За холст работает-но это не удобно.

Share this post


Link to post
Share on other sites
Hi! I installed the new version of the 3D coat 4.7.23 and I would like someone to confirm if the same type of error that I am going through in the Retopology option is happening.
I'm importing a .obj mesh from a head with only 1.2 million polygons. As soon as I import the mesh in the option of up to 2 million polygons the head is imported with the polygons completely exploded and wrong and 3D-Coat gets very slow with low fps. I imported the same head in the retopology option with huge files and it made the situation even worse: 3D-Coat was completely slow and locked with very low fps (smaller even than in the first commented option) and the polygons were completely blown.
I have already uninstalled and installed again, but in the option of retopology the same errors happen, I have already tested with other meshes and gave the same errors, that is, it is not a problem of .obj mesh.
I'm attaching an image so you have an idea.
 

error_3dcoat_4.7.23.jpg

Share this post


Link to post
Share on other sites
7 hours ago, Ausdemenon said:

В новых версиях попробовал навигацию свою сделать-у меня поворот вьюпорта за счет пкм как в браше,так вот при использовании инструмента отрезать/cut не работает этот самый поворот пока под курсором сама модель. За холст работает-но это не удобно.

alt нажимай когда курсор над моделью

Share this post


Link to post
Share on other sites

Not at all , on the other hand i am getting superior results with autoretopo on 4.7.23

Also huge speed improvement especially with the latest nvidia drivers. 

 

148538924379.jpg

 

Settings :

Poly : 7200

Symmetry on X : on

Quadrangulation on : Best quality

Capture details : 70%

Influence Multi : 1x

Decimate if above checked on :  40

Smouth resulting mesh : on

Edited by Michaelgdrs
  • Like 1

Share this post


Link to post
Share on other sites
17 hours ago, Rygaard said:
Hi! I installed the new version of the 3D coat 4.7.23 and I would like someone to confirm if the same type of error that I am going through in the Retopology option is happening.
I'm importing a .obj mesh from a head with only 1.2 million polygons. As soon as I import the mesh in the option of up to 2 million polygons the head is imported with the polygons completely exploded and wrong and 3D-Coat gets very slow with low fps. I imported the same head in the retopology option with huge files and it made the situation even worse: 3D-Coat was completely slow and locked with very low fps (smaller even than in the first commented option) and the polygons were completely blown.
I have already uninstalled and installed again, but in the option of retopology the same errors happen, I have already tested with other meshes and gave the same errors, that is, it is not a problem of .obj mesh.
I'm attaching an image so you have an idea.
 

error_3dcoat_4.7.23.jpg

Why are you importing a dense mesh into the Retopo Room? That's why it's sluggish. You import dense meshes into the Sculpt Room and use the Retopo room to build a LOW poly copy of it, on top of the Sculpt Object.

https://www.youtube.com/watch?v=OPD8xldxLS8

Share this post


Link to post
Share on other sites

Hi,

AbnRanger, thanks for responding!

I chose Perform Retopology because thinking that importing straight into the retopo room, for example a heavy scanned mesh, 3D-Coat might give me the option of manually working the retopology without the program being slow or without problems in the mesh polygons. So I used the - import huge reference mesh option from the main menu. But after choosing this option the mesh of polygons explodes and 3D Coat is very slow according to the images that I presented previously.

But when I do the longest path (which you commented on to be done and what I usually do too) for retopology that is to choose the Voxel Sculpting option from main menu, import the mesh without voxelization - being in surface mode and then go to Retopo Room, the mesh polygons are correct.
However, when I import without voxelization, in SURFACE MODE, I'm noticing problems with the Strokes tool that is not responding to Spline Points Density, because it's only putting a straight or curved lines with a maximum of 3 points since a set for example 399 for Spline Points Density option, and when I try to closed loop, the Loop circle appears with an orange dot.

But when I choose for the model to be voxelization and I go to the Retopo room, everything works perfectly with strokes tools with no errors commented on the surface mode.

I'm attaching an image!
What do you think?

Thank you!

3dCoat4.7_retopo_not_ok.jpg

Share this post


Link to post
Share on other sites
On 1/26/2017 at 11:58 AM, Rygaard said:

Hi,

AbnRanger, thanks for responding!

I chose Perform Retopology because thinking that importing straight into the retopo room, for example a heavy scanned mesh, 3D-Coat might give me the option of manually working the retopology without the program being slow or without problems in the mesh polygons. So I used the - import huge reference mesh option from the main menu. But after choosing this option the mesh of polygons explodes and 3D Coat is very slow according to the images that I presented previously.

But when I do the longest path (which you commented on to be done and what I usually do too) for retopology that is to choose the Voxel Sculpting option from main menu, import the mesh without voxelization - being in surface mode and then go to Retopo Room, the mesh polygons are correct.
However, when I import without voxelization, in SURFACE MODE, I'm noticing problems with the Strokes tool that is not responding to Spline Points Density, because it's only putting a straight or curved lines with a maximum of 3 points since a set for example 399 for Spline Points Density option, and when I try to closed loop, the Loop circle appears with an orange dot.

But when I choose for the model to be voxelization and I go to the Retopo room, everything works perfectly with strokes tools with no errors commented on the surface mode.

I'm attaching an image!
What do you think?

Thank you!

3dCoat4.7_retopo_not_ok.jpg

It might be that in Surface mode, it's too low res. You can look at the poly count at the bottom-right, in the statistics bar, and it's also a good practice to toggle wireframe on (W key) whenever you want to see how dense the model actually is. Just click the INCREASE RESOLUTION icon at the bottom of the Vox Tree layer panel (it looks like a grid), and that may help. I'm thinking density matters for the Strokes tool because 3D Coat may want to drop a control point down, but there is no vertex beneath that point, so it doesn't apply one. Just a wild guess. Maybe Andrew could answer it, better.

So, in voxel mode, it probably was more dense than the surface mode object. You might find this 3 part series helpful.

 

Share this post


Link to post
Share on other sites
Hi,
AbnRanger, thanks for the tips and videos, it helped a lot.
You're right, the dot density of the Stroke tool is related in some way to the density of the mesh's polygons. I did the test by increasing the resolution in surface mode and the tool worked as in voxel mode.

It also seems to me that the size of the mesh also has influence. I used the Transform tool and increased the size of the mesh, it seems that if its object is too small, it will need to increase its size.

Could you answer me when or what occasion I could use on main menu screen option >> Perform retopology >> Import Huge Reference Model?
Because as in the video, import to voxel, prepare the mesh if you need to and then go to the Retopo Room seems to me to be the best choice.

thank you

Share this post


Link to post
Share on other sites

@Andrew Shpagin is there a chance 3D Coat could stop creating 4(!!!!) separate folders upon launch? It's really bad. Why not one? Or even better - single hidden folder? What's the thinking behind it?

Why not a setting during the first launch (and the one you can later modify in Preferences) where you specify where you wish to keep those settings folders. Current implementation is awful.

I really hate when 3D Coat does that in my $Home folder. Linux versions are being patched by Sergii, so at the very least I could use COAT_FILES_PATH variable to specify place for those files, but it always gets back after each update and 3D Coat stops respecting this setting (on my end it suddenly got worse as the version I knew worked in the past somehow does not respect the variable).

 

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.

×