Jump to content
3DCoat Forums

3DCoat 4.8 BETA testing thread


Recommended Posts

  • Member

3DCoat 4.8.42SL  (and 41SL) freezes with Autopo wizard.

Tested with generic bust male scene,  it's not responding when "rounding_singular_points", or when it's ready to create geometry.

Also tried Instant meshes (Auto), not better luck there too.

p.s: Clean installation of each version.

autopo.jpg

Edited by geoath
Link to comment
Share on other sites

  • Advanced Member
On 7/14/2019 at 7:08 AM, lesaint said:

Oh wow, yes ! Now I can switch between the two and it is an acceptable workaround. Thank you.

The problem remains that 4.8-39 to 4.8.42 won't work with my old .3b files, it crashes when I enter the retopo room if there is a mesh in it, or if I try to import a mesh via the sculpt room or via import.
It only works with new scenes created after 4.8.38
image.png.6dfa4f6a6b139d4bd9827255a87dc418.png

 Have you tried DX version? I had this problem even though for new scene created in 4.8.40.  GL version crashes if there is mesh in retopo room.  DX version works fine.

//fixed

 

  • Like 2
Link to comment
Share on other sites

  • Reputable Contributor
1 hour ago, animk said:

 Have you tried DX version? I had this problem even though for new scene created in 4.8.40.  GL version crashes if there is mesh in retopo room.  DX version works fine.

Oh, Thank you so much animk.
Since 2015 I have only ever used GL, it's always worked fine, so it's just become automatic for me to go for GL version.
Sometimes I try DX when there is a problem, but up until today it never helped.

So yes, 4.8.42SL DX works fine for me too, with a mesh in the retopo room and with my old files.

I had to rename the exe to GL for it not to mess with my 3d mouse though.

So I guess this is the start of my days with the DX version. I have never understood the difference. But I still I hope GL version of future builds works again for both of us...

  • Like 2
Link to comment
Share on other sites

  • Contributor

Hi, I would like to report possible errors on the following tools in 3D-Coat 4.8.42 (SL) DX :
I'm having the same image issues I'm showing you in the tools:

1- Split,
2- Split & Joints

3- Cut & Clone
4- Clone.

All of these tools have errors at the cutting edge.
This has never happened to me before.

 

image.thumb.png.4494cb8e080e7f8f610a2f6eb75c7051.png

image.thumb.png.3bec8f5205126f6a1720ef4fa240a9c8.png

image.thumb.png.f93266332ab821f101c58e9f34e4b97a.png

Edited by Rygaard
Link to comment
Share on other sites

  • Member
On 2019. 6. 3. at 오후 3시 53분, superman punch said:

 

"3d-Coat-V4_8-40-64.exe / 3d-Coat-V4_8-40-64_sl.exe"설치 후 0xc000007b 오류가 발생했습니다.
실용적이지.
현재 버전 : 38.

I solved this problem by I updated my graphics card drive.614149589_.PNG.ecfcdfae883a5cc4bdb86ef60145e58e.PNG

Good luck.

  • Like 2
Link to comment
Share on other sites

  • Reputable Contributor
On 7/14/2019 at 3:22 PM, geoath said:

3DCoat 4.8.42SL  (and 41SL) freezes with Autopo wizard.

Tested with generic bust male scene,  it's not responding when "rounding_singular_points", or when it's ready to create geometry.

Also tried Instant meshes (Auto), not better luck there too.

p.s: Clean installation of each version.

autopo.jpg

I just now tested this same voxel model > 4k polys and it worked very well. Maybe close the app > delete "MyDocs/3DCoat 4.8/OPTIONS.xml" file. If that gets corrupted, it can exhibit bug-like behavior.

Untitled-1.jpg

Link to comment
Share on other sites

  • Member

Hi AbnRanger!

I noticed in your screenshot that you use the DX version instead of the GL one I was using and experienced this issue.

I tried your workaround for the GL version with no luck.

I made the same test with the DX version as you did and everything worked fine!

This makes me think that the autopo wizard issue is a GL version specific problem, so for now I'll go with the DX version

hoping that this issue will be fixed in a next build.

Thanks for your response, I'll have this workaround in mind before reporting any issue.

Link to comment
Share on other sites

  • Advanced Member
On 7/14/2019 at 4:44 PM, lesaint said:

Oh, Thank you so much animk.
Since 2015 I have only ever used GL, it's always worked fine, so it's just become automatic for me to go for GL version.
Sometimes I try DX when there is a problem, but up until today it never helped.

So yes, 4.8.42SL DX works fine for me too, with a mesh in the retopo room and with my old files.

I had to rename the exe to GL for it not to mess with my 3d mouse though.

So I guess this is the start of my days with the DX version. I have never understood the difference. But I still I hope GL version of future builds works again for both of us...

You are welcome.  The only differences I notice between DX and GL are that GL has better response for resizing main 3d-coat window on both AMD & Nvidia card, and slower FPS than DX on my old AMD card (without entering full screen mode) 

Edited by animk
  • Like 1
Link to comment
Share on other sites

  • Member

Open GL is the oldish Graphics Language Standard that is pretty raw but bulletproof, DX is kinda floofy Direct X but has had more recent dev develop time and may outlive Open GL tragically.

  • Like 2
Link to comment
Share on other sites

18 hours ago, ajz3d said:

Please update us on the progress. :brush:

Recently I am working on problems with "3DCoat" under macOS. But under Linux Ubuntu 19.04 I have built our standalone standard pen pressure test http://pilgway.com/~sergyi/TEST STROKE/TEST STROKE.tar.xz (run from Terminal) and have started to investigate "3Dconnexion" support using http://spacenav.sourceforge.net/

  • Like 1
Link to comment
Share on other sites

20.07.2019 4.8.44

- OpenGL version works correctly

 - Deleting selected faces in retopo room leads to boundary edges selection.

- Create retopo patch of quads in VoxLayer tool. A lot of refinement is VoxLayer, more accurate custom edge.

- Soft booleans for volumes accessible not only via picking but through menu for boolean operations as well.

- Correct split in surface mode with symmetry

- serious problem fixed - unselecting random vertices/faces

- Instability related to undo fixed

  • Like 7
Link to comment
Share on other sites

  • Member
On 7/19/2019 at 7:14 PM, SERGYI said:

Recently I am working on problems with "3DCoat" under macOS. But under Linux Ubuntu 19.04 I have built our standalone standard pen pressure test http://pilgway.com/~sergyi/TEST STROKE/TEST STROKE.tar.xz (run from Terminal) and have started to investigate "3Dconnexion" support using http://spacenav.sourceforge.net/

as others I'm looking forward for the updated Linux build - some of the features (like improved booleans) would come in handy in my workflow.

If you can top it off with 3dConnexion support all the more awesome.

Link to comment
Share on other sites

  • Reputable Contributor

4.8.44SL (GL) Seems to work fine...

BUT..... the Reproject tool is still missing !!!

Also I am not sure but I think the sphere tool is acting weird : when you start drawing, it seems to get lost and does not know where to start the stroke.

Link to comment
Share on other sites

  • Contributor

In both DX and GL builds I'm having a lot of atifacts,holes when using Soft Booleans and Cutoff tool.

Especially when using it multiple times and having bevel subdivision level to anything but zero.

It's easily reproducable using the E-panel circle and the Default 3Dcoat head bust.

Im using the SL build,I will try the regular one and report.

 

EDIT:same results in regular build.

cutoff.png

Link to comment
Share on other sites

  • Contributor

Hi,
I'd like to report a problem that's been going on with me for a while. I do not know if someone else has already passed or goes through this same problem as me.
In VoxTree, I created a hierarchy of a group called Cloth and Rock (empty) and inside it I have the Cloth and Rock geometries in their respective layers.

image.png.d5e9e9f9c5a10ca94b89a33b89a16a5e.png
Having said all that, as I am saving my progress, at a certain point the whole hierarchy is empty. As if I had erased my geometry.
Because I have saved my progress, I was able to reimport again the geometries that the program deleted.

Honestly, I do not know how this is possible in 3D-Coat, this problem of erasing geometries without the user realizing.
Imagine a situation where you do not have a backup for some reason and when you open your project some created geometries are gone or have been deleted.
Since I know that 3D-Coat has some weird insights I've been saving and making multiple backups of my objects and projects.
I would just like to report this strange problem that has been happening to me in 3D-Coat 4.X SL (DX) if that helps anything.

6 hours ago, lesaint said:

Reproject tool is still missing

I also do not have the Reproject Tool ... It's gone!

Link to comment
Share on other sites

  • Reputable Contributor
7 minutes ago, Rygaard said:

at a certain point the whole hierarchy is empty. As if I had erased my geometry.


Yes I have seen this many times over the years.
In my case it only happens with voxels.

Strangely I have not been bothered with it for quite some time, but I know it still happens.  Nowadays I usually end in surface mode, that is why it has not bothered me so much I think.
However, I sometimes notice that my voxel backup is gone.

In the case that the vanished voxel layer is the only copy of your sculpt, I know I had a workaround that would restore the geometry. I don't know if it would still work, I don't have a case to test with at the moment, but you could try.

You need to know where the geometry was in your scene.
You need to place an object in relatively the same space on another layer.
turn off auto pick
select the vox layer that has the deleted geometry
select the fill tool, and set depth to zero (so that it does nothing in normal circumstances).
Finally start brushing the area of the lost voxels, using the second object as a base to start your brush strokes.
The lost voxels should now reappear under the brush. You need to brush the whole outer surface of your object to make it reappear completely.

  • Like 1
Link to comment
Share on other sites

  • Contributor
23 minutes ago, lesaint said:


Yes I have seen this many times over the years.
In my case it only happens with voxels.

I did not know that this problem is old and happened to other people.
Previously, I had thought of this also that this problem only happened with VOXELS.

I use a lot more Surface Mode, so I was surprised when I saw my geometries erased and these geometries are Voxels. I think I'll convert to Surface Mode.
The only problem with this is that if I need to return to voxels I will have to configure a geometry with more polygons so that I do not lose the details that I have already done in the part.
I know that converting to Voxels is no problem, there is only the bad side of having more polygons in geometry if you still want the details that have already been made.

You've drawn my attention to the geometries in Voxels.
I saved my hierarchy in extension .3b.
So far, even though it's in Voxels I have not lost any geometry in this extension, maybe it's because I saved in .3b.
But I'll keep an eye out for that too.

 

23 minutes ago, lesaint said:

You need to know where the geometry was in your scene.
You need to place an object in relatively the same space on another layer.
turn off auto pick
select the vox layer that has the deleted geometry
select the fill tool, and set depth to zero (so that it does nothing in normal circumstances).
Finally start brushing the area of the lost voxels, using the second object as a base to start your brush strokes.
The lost voxels should now reappear under the brush. You need to brush the whole outer surface of your object to make it reappear completely.


Thanks for the technique. This tip I had never seen before.
If it happens again, I'll test your tip to see if it returns the two geometries that have disappeared.

 

Thank you

Edited by Rygaard
Link to comment
Share on other sites

  • Reputable Contributor

I *think* that if you don't notice the missing geometry when you open the file, then continue working as if nothing had happened (because you don't know it has), and then you save your file again... and close 3d-Coat....
Then, I *think* that your geometry is lost forever.

 

Link to comment
Share on other sites

  • Reputable Contributor
1 hour ago, Rygaard said:

Hi,
I'd like to report a problem that's been going on with me for a while. I do not know if someone else has already passed or goes through this same problem as me.
In VoxTree, I created a hierarchy of a group called Cloth and Rock (empty) and inside it I have the Cloth and Rock geometries in their respective layers.

image.png.d5e9e9f9c5a10ca94b89a33b89a16a5e.png
Having said all that, as I am saving my progress, at a certain point the whole hierarchy is empty. As if I had erased my geometry.
Because I have saved my progress, I was able to reimport again the geometries that the program deleted.

Honestly, I do not know how this is possible in 3D-Coat, this problem of erasing geometries without the user realizing.
Imagine a situation where you do not have a backup for some reason and when you open your project some created geometries are gone or have been deleted.
Since I know that 3D-Coat has some weird insights I've been saving and making multiple backups of my objects and projects.
I would just like to report this strange problem that has been happening to me in 3D-Coat 4.X SL (DX) if that helps anything.

I also do not have the Reproject Tool ... It's gone!

If there is any way to repeat the problem, Andrew can fix it. I've had some similar issues with opening older files, and finding that when I uncache a layer, the volume is missing. I reported this to Andrew, but he didn't know how it could happen. It's not a frequent problem, but one does need to use Auto-save, for sure, and when I have an object I want to make sure is preserved, I will either RMB click the VoxTree layer > Save as .3b file or drag and drop the layer into the MODELS pallet.

Link to comment
Share on other sites

  • Reputable Contributor
9 minutes ago, AbnRanger said:

If there is any way to repeat the problem, Andrew can fix it. I've had some similar issues with opening older files, and finding that when I uncache a layer, the volume is missing. I reported this to Andrew, but he didn't know how it could happen. It's not a frequent problem, but one does need to use Auto-save, for sure, and when I have an object I want to make sure is preserved, I will either RMB click the VoxTree layer > Save as .3b file or drag and drop the layer into the MODELS pallet.

At the time when it happened to me a lot, I came to be convinced that it happened when I closed 3d-Coat after saving, and not waiting long enough.
However, that was a long time ago, and now I think we have been told that 3dc continues saving in the background even when we close it, so, I don't know anymore.

I had this problem a lot at one point, and there is a  reason why I did not point it out, or if I did, I forgot. (but I remember giving the solution to restore the voxels to some people, I don't know where, probably on the facebook group).

It's a strange reason, probably.
To me voxels have always had a magical quality to them. Strange and unexpected things happen with them.

AND I LOVE THAT :)

So... I did not want to draw attention to any problem with voxels, for fear that it would be fixed and lose its magic.

Here is one such odd behaviour. In the video I dig into the cube with CTRL+ grow tool.
Then... I grow it back
https://www.youtube.com/watch?v=0tGAmzg8mHg

https://www.youtube.com/watch?v=0tGAmzg8mHg

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
 Share

×
×
  • Create New...