Jump to content
3DCoat Forums

Possibly-mef

Member
  • Posts

    10
  • Joined

  • Last visited

Everything posted by Possibly-mef

  1. Additional insight -- found workaround for Autotopo Decimation Fail 1. WORKAROUND: If I explicitly enter a value for the Reduction Percent, the decimation is fine. If enter a numerical value for the Reduced Polygon Count, the decimation is mangled. I also noticed that when I enter a numerical value for the Polygon Reduction, the percentage value does not change to reflect the new value. 2. Consistent with an earlier observation following @Elemeno suggestion: After converting to Voxels, Decrease Object by 2x and then decimate the decimation is fine but no matter what I value I enter into the Reduced Polygon Count, I get at 40k tri, result.
  2. I ran the same test on a Windows machine and on an M1 MacBook Pro using different initial data (i imported a different scanned mesh with 4M triangles.) Same results. One notable thing I discovered was no matter value I put in for the Polygon Reduction (200k, 400k, 1M) it alway resulted in a 40k retopo PolyGroup m
  3. Hello Sergyi, Thanks so much for following up. I tried a couple of tests with both 2022.60 and with 2023.08. I deleted the Documents->3DCoat folder between each test. I am running this test on at 2017 iMac Pro (8-core Xenon W - 32Gb) running Ventura 13.2.1. I seem to be getting the same sort of results. See attached screen shots. The results are slightly different but still not right. Although likely not significant I noticed that after I deleted the 3DCoat file from Documents, each time I started the app a 3DCoatV4 folder was create as well at 3DCoat. And also as a side note it seems the the imported object in 22.60 and 23.08 is now centered vertically in the grid. Is that an expected change??
  4. Ok so the problem gets a little weirder - I did as Elemeno suggested: converted to voxels (went from from 4 011 720 tris to 5 208 516 tris) Decrease Object 2X (Increase Density) Autotopo via decimation (500 000) polys While it did not exhibit the same damaged mesh as in the prior example the resolution is too low for good renders in C4D (or other apps)The result is a 40 000 poly group no matter what value it put in to the dialog. I tried a few values between 300k and 400k). Always resulted in a 40k poly group BTW I ran this test on a Windows machine using version 2022.58 starting from scratch in a new 3DC document.
  5. Elemno. What value did you use for the decimation? -- based on the density of the mesh in the image you sent, it seem quite a bit high. I will try a higher density and see what happens.
  6. Carlosan, Thank you. I have encountered the same problem with the Windows version as well. I will follow up with Sergil.
  7. sorry. Here is a screenshot of result from 2022.49 and a link to the .3b file https://www.dropbox.com/s/4y7c83v1ab0w821/3DC-Angela-Take01-M4.3b.zip?dl=0
  8. Thanks for the quick reply. Here is the same file after Autotopo w/ decimation from 2022.49. Any version later than this produces the result I previously posted.
  9. I have noticed that Autotopo via decimation seems to be broken since 2022.49 I just tried 2023.07 and I it still seem broken. I have tried it on Windows as will a Mac. I am attaching an image that demonstrate the results I am now getting. I am taking a 4M face mesh down to 400k. It has worked flawlessly until any of the releases since 2022.49 (mac).
×
×
  • Create New...