Jump to content


Photo

3D-Coat 3.7 updates thread


  • This topic is locked This topic is locked
1786 replies to this topic

#1321 LJB

LJB

    Journeymen

  • Contributor
  • PipPipPipPip
  • 1,208 posts
  • Gender:Male
  • Location:UK

Posted 11 July 2012 - 09:33 AM

LiveClay Pose selection bug is back.
Posted Image


Confirmed, Real PITA too.
Posted Image
Check out my channel on vimeo Here

#1322 johnnycore

johnnycore

    Novice

  • Member
  • PipPip
  • 286 posts
  • Gender:Male
  • Location:Breda, the Netherlands
  • Interests:Houdini
    C++
    C#
    Python
    Anatomy
    Rigging

Posted 11 July 2012 - 09:36 AM

Also noticed this problem.. I solved it by doing this:

voxel --> clean surface

followed with

voxel --> clean memory


Everything seems te work correctly for me after doing this.. :)
Johnny

Desktop: Intel core i7 2600k 4GHZ, nvidia GTX 560Ti 2048MB, 16GB DDR3 1333mhz, Windows 8 Beta x64 - Linux Fedora 18 x64
Sony VAIO Laptop - Intel core i5 520M 2,4GHZ, nvidia GT330M 1024MB, 8GB DDR 1333mhz, Windows 8 Beta x64 - Linux Fedora 18 x64

My youtube channel: http://www.youtube.c...ohnnycorebrieee

#1323 randomguy_j

randomguy_j

    Neophyte

  • Member
  • Pip
  • 92 posts

Posted 11 July 2012 - 10:21 AM

@ LJB: Yeah that is a nasty bug.

Hey has anyone run into a problem with 3D coat crashing after creating and trying to use a custom pen brush? It has happened to me several times.

I am using 3.7.14A non cuda 64.

#1324 3DArtist

3DArtist

    Apprentice

  • Member
  • PipPipPip
  • 769 posts
  • Gender:Male
  • Location:USA

Posted 11 July 2012 - 02:58 PM

Also noticed this problem.. I solved it by doing this:

voxel --> clean surface

followed with

voxel --> clean memory


Everything seems te work correctly for me after doing this.. :)


That has worked in the past for me but now when I try it, it destroys my mesh.
Intel Core 2 Quad Q6700
6GB RAM
GeForce GTS 250 1GB
Windows 7 Pro 64bit

web: gregcopin.com

#1325 AbnRanger

AbnRanger

    Expert

  • Contributor
  • PipPipPipPipPip
  • 3,673 posts
  • Gender:Male

Posted 11 July 2012 - 03:08 PM

That has worked in the past for me but now when I try it, it destroys my mesh.

What about just Clear Memory?

#1326 johnnycore

johnnycore

    Novice

  • Member
  • PipPip
  • 286 posts
  • Gender:Male
  • Location:Breda, the Netherlands
  • Interests:Houdini
    C++
    C#
    Python
    Anatomy
    Rigging

Posted 11 July 2012 - 03:33 PM

Thats odd that it destroys the mesh.. I use it daily.. still no destroyed mesh.. :)
Just noticed that clean up memory alone also fixes this problem for me.. did not know that.. thanks!
Johnny

Desktop: Intel core i7 2600k 4GHZ, nvidia GTX 560Ti 2048MB, 16GB DDR3 1333mhz, Windows 8 Beta x64 - Linux Fedora 18 x64
Sony VAIO Laptop - Intel core i5 520M 2,4GHZ, nvidia GT330M 1024MB, 8GB DDR 1333mhz, Windows 8 Beta x64 - Linux Fedora 18 x64

My youtube channel: http://www.youtube.c...ohnnycorebrieee

#1327 3DArtist

3DArtist

    Apprentice

  • Member
  • PipPipPip
  • 769 posts
  • Gender:Male
  • Location:USA

Posted 11 July 2012 - 05:02 PM

If I remember correctly, clean surface poked holes in the mesh and clean memory turned it into abstract art, spikes everywhere. :blink:
I've also tried them individually and in combination so maybe my mesh is corrupted in some other way. But I will try again when I get home and if it still does not work I'll send the model to Andrew to look at.
Intel Core 2 Quad Q6700
6GB RAM
GeForce GTS 250 1GB
Windows 7 Pro 64bit

web: gregcopin.com

#1328 Psmith

Psmith

    Helper

  • Custodian
  • PipPipPipPip
  • 1,013 posts
  • Gender:Male
  • Location:Flagstaff, Arizona

Posted 11 July 2012 - 05:42 PM

Randomguy:

Can you post the steps you took to get that crash? Andrew needs the steps, or a short video.


Greg Smith

#1329 digman

digman

    Expert

  • Contributor
  • PipPipPipPipPip
  • 2,165 posts
  • Gender:Male
  • Location:Texas, USA

Posted 11 July 2012 - 06:43 PM

All those cleaning steps under the voxel's menu, I found in a number of meshes produce problems in the mesh. Now not all, so it must be somehow related to the state of the mesh. Maybe a combination of using LiveClay and surface mode brushes, the routine of the cleaning steps, older files and meshes. Right now, It would take several days of testing, recording all your steps along the way to get something that Andrew could reproduce in a consistent manner because there are so many factors involved in this bug problem.
I still do not have the time yet to do it yet...

If I use them, it is at an early state of the sculpting, where I can go back to voxels to clean up any surface mode problems with the mesh...

#1330 randomguy_j

randomguy_j

    Neophyte

  • Member
  • Pip
  • 92 posts

Posted 11 July 2012 - 11:44 PM

First thing I will do is make a cube and/or cylinder. In voxels mode I will carve it, sculpt it, etc. Sometimes I will take it to surface mode and tweak it or add another primitive. When I am done, I will export the object as an OBJ and import it into zbrush where I will tweak it a little more. Then I will use the applink in Zbrush to send it back to 3D coat as a pen alpha. After adjusting depth (Usually a negative value) and leaving size at 256, I create the new pen alpha, create a new cube primitive, put the cube in surface mode, and sculpt with BuildClay using the new alpha while tweaking the rotation, spacing, etc. Usually when I am testing the alpha is when 3D coat will give me a message about stability issues giving me a chance to save before crashing. This is a stubborn bug and isn't always consistent. Even if I just import an OBJ as a pen alpha without going through Zbrush I sometimes will get the crash warning.

As a side note, I have also noticed for a while that depending on how complex your surface is, the LC CutOff tool in surface mode doesn't seem to do anything.

#1331 3DArtist

3DArtist

    Apprentice

  • Member
  • PipPipPip
  • 769 posts
  • Gender:Male
  • Location:USA

Posted 12 July 2012 - 04:49 AM

If I remember correctly, clean surface poked holes in the mesh and clean memory turned it into abstract art, spikes everywhere. :blink:
I've also tried them individually and in combination so maybe my mesh is corrupted in some other way. But I will try again when I get home and if it still does not work I'll send the model to Andrew to look at.


Looks like exporting the layer to an obj (without decimation) and merging back into the scene fixed it.
Intel Core 2 Quad Q6700
6GB RAM
GeForce GTS 250 1GB
Windows 7 Pro 64bit

web: gregcopin.com

#1332 randomguy_j

randomguy_j

    Neophyte

  • Member
  • Pip
  • 92 posts

Posted 14 July 2012 - 05:22 AM

I have had plenty of times where my mesh will have holes and clean surface/ clean memory will only make things worse. What works for me is to either increase the resolution or take the model into then out of voxels mode before using clean surface/ memory.

#1333 Andrew Shpagin

Andrew Shpagin

    3DC creator & admin

  • 3D-Coat Developer
  • PipPipPipPipPipPip
  • 6,268 posts
  • Gender:Male

Posted 14 July 2012 - 08:58 AM

Mac&Linux builds updated to 3.7.14B.

#1334 pavig

pavig

    Neophyte

  • Member
  • Pip
  • 37 posts
  • Gender:Male
  • Location:Melbourne Australia

Posted 14 July 2012 - 11:49 AM

Mac&Linux builds updated to 3.7.14B.

Mac build appears to be missing some assets (or have a screen rendering issue).
Posted Image

#1335 zebrap

zebrap

    Newbie

  • Member
  • 6 posts

Posted 14 July 2012 - 02:06 PM

I have the same issue.
Voxel room is flickering with fullscreen white.
Going from paint room to voxel room will crash 3D Coat systematically.

Can't use this build.

Screen Shot 2012-07-14 at 12.55.16.jpg

Macbook pro 15 inch early 2011
Mac OS X Lion 10.7.4 (11E53)
2.2 GHz Intel Core i7
4 GB 1333 MHz DDR3
AMD Radeon HD 6750M 1024 MB

#1336 LorenzoS

LorenzoS

    Novice

  • Member
  • PipPip
  • 135 posts
  • Gender:Male

Posted 14 July 2012 - 03:15 PM

Same here. Lot's of graphics on the UI missing. Just like zebrap's screen grab.
God is my favorite artist. He created the Heavens and the Earth!

Macbook Pro4,1 - 10.6.8 - 2gb Ram - 512mb VRAM

#1337 digman

digman

    Expert

  • Contributor
  • PipPipPipPipPip
  • 2,165 posts
  • Gender:Male
  • Location:Texas, USA

Posted 15 July 2012 - 12:54 AM

Thanks Andrew for the linux build. I know with all the new beta features going into 3DCoat for Version 4 there will be more than the normal amount of bugs. Once all the features are added, bugs squashed and some more brush tweaking, 3DCoat Version 4 will kick the tires and light the fires... By the way the icons are looking great...

Linux 64 bit version 3.7.14B non cuda.

I got a fairly major bug in the retopo room. When moving a single vertex to snap to another vertex the vertices fail to weld. That means there is no way of connecting polygons when moving single vertices. Symmetry is not turned on. Take just two polygons and try to weld (snap) the vertices to connect them, it's a no go in the Linux version.

#1338 3DArtist

3DArtist

    Apprentice

  • Member
  • PipPipPip
  • 769 posts
  • Gender:Male
  • Location:USA

Posted 15 July 2012 - 06:40 AM

I have had plenty of times where my mesh will have holes and clean surface/ clean memory will only make things worse. What works for me is to either increase the resolution or take the model into then out of voxels mode before using clean surface/ memory.


Thanks for the tip, next time I'll try increasing the resolution a little.
Intel Core 2 Quad Q6700
6GB RAM
GeForce GTS 250 1GB
Windows 7 Pro 64bit

web: gregcopin.com

#1339 SERGYI

SERGYI

    Developer

  • 3D-Coat Developer
  • PipPip
  • 107 posts
  • Gender:Male

Posted 15 July 2012 - 07:09 AM

Voxel room is flickering with fullscreen white

There was an error in one shader. The build 3D-Coat 3.7.14B for Mac OS X has been updated. Please download it again.

#1340 zebrap

zebrap

    Newbie

  • Member
  • 6 posts

Posted 15 July 2012 - 01:30 PM

There was an error in one shader. The build 3D-Coat 3.7.14B for Mac OS X has been updated. Please download it again.




Thanks Sergyi.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users