1786 replies to this topic

[moska]

hi Sergy
i just upgrade one of my macs to lion and notice that 3dcoat cant import a model for PixelPainting!
thats with v 3.7
could you tell me if Lion is already supported?
thanks

hi again
i love this software but aside from my ugly face i need some feedback

[The Candy-floss Kid]

Ok, I may confirm it. Thanks for reporting!
I will discover the reason.

Thank you Andrew.

[Andrew Shpagin]

Thank you Andrew.

Ok, found the reason.
One + was missing...
Now fixed. I will re-upload build.

[Andrew Shpagin]

Updated to 3.7.06C to fix brushing problem mentioned above.
Upcoming Mac&Linux builds will include this change too.

[Andrew Shpagin]

Mac & Linux builds updated to 3.7.06B
It is equivalent to win version 3.7.06C

[cl-apps]

Can't wait to try this this evening

[michalis]

Mac & Linux builds updated to 3.7.06B
It is equivalent to win version 3.7.06C

Thank you.
Wrong and confusing naming though.

[michalis]

Wrong auto UVs on default cube, once again!
On all these last builds! I wonder.

Attached Thumbnails

• 

[Eric Cosky]

3.7.06C corrects the Merge with NM crash I was experiencing. Thanks!

[The Candy-floss Kid]

Ok, found the reason.
One + was missing...
Now fixed. I will re-upload build.

Thank you Andrew - you have solved it. Brilliant news.

[SERGYI]

Wrong auto UVs on default cube

Please specify step by step how did you get those UVs. Because Voxels/Merge/Cube.obj/~1M/AUTOPO/AUTOPO for Per Pixel works fine.

[SERGYI]

could you tell me if Lion is already supported?

There is no any reason why 3D-Coat should not support Lion :-D Please try this test executable.
http://www.3d-coat.com/~sergyi/3D-Coat-10.6.zip
It has been compiled against the latest SDK. But frankly speaking I think that the reason is within another video driver,
which, most probably, was also updated during system update.
Maybe it doesn't support big textures like 8K and above? Have you tried 4K, 2K?
What exactly do you see during import for PPP: crash, flickerings. hang over?

[michalis]

Please specify step by step how did you get those UVs. Because Voxels/Merge/Cube.obj/~1M/AUTOPO/AUTOPO for Per Pixel works fine.

Right, it works. Now, let's voxel paint, it works again. Let's do some resampling, now it's broken.
Of course I cleaned all rooms before testing. IM cube or 250K doesn't change anything.
I can't confirm if it's the resampling that causes it. It looks a rather random behavior. It happens every 3-4 tests.

[haikalle]

There is this mantis report:

http://3d-coat.com:8...view.php?id=261

I remember that it would had fixed in the past but when I tested it again it still there.

[BurrMan]

Updated to 3.7.06C to fix brushing problem mentioned above.
Upcoming Mac&Linux builds will include this change too.

Whatever changed in this last build, had a noticable difference on my system startup. Pre= Launch 3dc and wait 6 seconds for "Show on startup" screen. Select large Voxel sphere and wait 8-10 seconds. Post= Immediate "show on startup screen" upon launch. 1 second wait on large voxel sphere selection... FYI.

Dual quad core xeon. Nvidia quadro fx 5600. 8 gb ram.

[Javis]

I do believe that is part of the advantage of using poly painting. You can do that kind of editing. Mind you, it will mess it up a little bit, but it makes it easier to tweak after the fact. This happens a lot in game development.



EDIT: This happens a lot, as in, editing after the fact it has been finished.

[The Candy-floss Kid]

For attention of Andrew,

Feedback report concerning non editable retopo mesh after an autopo in 3DC Beta V3.7.06B version for the Mac.
Also apparent , an issue with the Retopo mesh being buried.



OS 10.5.8

[JimB]

Whatever changed in this last build, had a noticable difference on my system startup. Pre= Launch 3dc and wait 6 seconds for "Show on startup" screen. Select large Voxel sphere and wait 8-10 seconds. Post= Immediate "show on startup screen" upon launch. 1 second wait on large voxel sphere selection... FYI.

Dual quad core xeon. Nvidia quadro fx 5600. 8 gb ram.

I have had the same problem for a while in the 3.7.x.x series I just put it down to my machine specs,I get about 10 seconds of white screen on startup
and about 6 seconds wait after selecting a voxel primitive,most annoying.

[michalis]

Why do you chance messing with Resampling after Voxel Painting? It's like screwing with a mesh after you've spent hours doing UV's and texture painting. There is a reason why you do those AFTER you've finished modeling.

I'm just testing Abn.
I thought this painting was messing things in 3dc. It's not what causes the problem, I think so.
Just merge a cube, ask for autopo with PPP and everything works fine. Clean all rooms, resample the cube, try again and face a possible issue in UVs.
BTW, to resample a vertex-painted object isn't a good idea, indeed.
However, vertex painting is rather a fast way to start and can be helpful when painting on it after baking (PPP)

Edit:
1. Confirming what The Candy-floss Kid reported on the OSX version (under 10.6.8 )
2. Resampling has nothing to do with what I already reported. The bug is random. Just used a ~200k cube and happened again. Depends on the resolution value? How can I check this?

[The Candy-floss Kid]

For attention of Andrew,

Feedback report concerning non editable retopo mesh after an autopo in 3DC Beta V3.7.06B version for the Mac.
Also apparent , an issue with the Retopo mesh being buried.



OS 10.5.8

------------------------------------------------------------------------------------------------------

3.7.06B Also: wish to report that edges and verts are not showing in manual retopo .
See attached image below.