Jump to content
3DCoat Forums
Andrew Shpagin

3DCoat 4.9 BETA testing thread

Recommended Posts

17.11.2019 4.9.10 [beta]

 

- Corrected EXR export using export constructor. Correct support of mono (R) export.

- Correct direction of alpha with stamp mode, stamp works if the pen is on empty space as well.

- Fixed 16k AO and light baking.

- Correct Windows->Store/restore workspace.

- Navigation within the image color picker restored.

- Mark seams with SHIFT corrected.

- Fixed .HDR panoramag import problem, it was importing as greyscale.

- a lot of small bugs fixed.

  • Like 5
  • Haha 1

Share this post


Link to post
Share on other sites

Thanks for fixing the smart materials/assigned to layers in 4.9.10. One thing i`m noticing though is that the material pop-up when using a pen is very sensitive , could it be adjust to be more forgiving if you move the mouse pointer.
Also, if you can add a search function to smart materials/stencils etc that would be a massive help to increasing workflow.
Thanks

3dcoat_smartmats.thumb.gif.deb56461fe873652f7f7eb2a50e437de.gif

Share this post


Link to post
Share on other sites

Just discovered 4.9.10  that if you attach a smart material to layer, then go upto smart materials, and then "attach to the current layer" (again)..causes crash.

Share this post


Link to post
Share on other sites

I have a problem with some of my custom shaders - in Sculpt room viewport everything looks fine, but in Render room I get filled with black look, something like silhouette.

Any idea where the problem lays or some workaround?

Edited by Mihu83

Share this post


Link to post
Share on other sites
52 minutes ago, Mihu83 said:

I have a problem with some of my custom shaders - in Sculpt room viewport everything looks fine, but in Render room I get filled with black look, something like silhouette.

Any idea where the problem lays or some workaround?

Are they PBR Shaders? If they are old ones (created before PBR shaders) that is probably why.

Share this post


Link to post
Share on other sites

The texture baking tool is also missing 16k export. It seems like it needs updating for PBR output as well. I've got older projects that were almost completely painted until I discovered  topology glitches , surface not compatible with tessellation/displacement that was created outside 3DCoat and from non ideal mesh import settings.

Share this post


Link to post
Share on other sites

4.9.10

Edge Loop tools works again for me, Yay !

In paint room Fill tools works on sculpt mesh but seems to have no effect on paint object ?

In layer Blending clip mask dropdown still requires a restart to refresh.
 

Share this post


Link to post
Share on other sites

I installed the 9.10 and then my 9.5 (most stable for me) loses the sculpt presets and also  made the 9.5 unstable(closes without popups or anything).

Share this post


Link to post
Share on other sites
On 11/19/2019 at 10:59 PM, Mihu83 said:

I have a problem with some of my custom shaders - in Sculpt room viewport everything looks fine, but in Render room I get filled with black look, something like silhouette.

Any idea where the problem lays or some workaround?

Just replace these attachments in your shaders in the folder "MyDocuments\3D-CoatV49\Shaders\PbrShaders\#A Stuart Folder\A Base Shader."

Your shadel comes from very old templates, you need to replace the mcubes.glsl and mcubes.hlsl files with new ones

mcubes.zip

  • Like 1

Share this post


Link to post
Share on other sites
On 11/17/2019 at 1:58 PM, Andrew Shpagin said:

17.11.2019 4.9.10 [beta]

 

- Corrected EXR export using export constructor. Correct support of mono (R) export.

 

@carrots I wasn't working with the export constructor initially and when I realized that's what the fix was for, I tried it and the EXR export came out to 1.2 mb for 16k texture output -didn't work.  I used a preset and added displacement output 32 bit EXR "zero is grey,normalized" which does work but isn't the correct type (doesn't scale correctly). 32 Bit EXR Grey-based, not normalized seems like the correct one - I tried 16 Bit tif using grey-based,not normalized and it seems correct in scale but is missing the detail to displace all areas, especially the seams (pics sent in pm)  Because the 16 bit grey based was scaling correctly I then tried 32 Bit EXR grey based and it scaled correctly in parts and other areas it was erratic and I noticed the texture was a mix of blue and red! i imported it into photoshop, initially it looked black with some small red parts. I then increased the levels and sure enough there was a blue background. 

I sent some images in a pm to you to show what it looks like.. I don't know if that particular EXR grey based is supposed to have blue in it but anyways I hope you can force a RED monochrome from the Grey Based option or make a new on for it. When I sent you a pm I was having difficulty trying to explain it so i hope you bare with me.;)

Share this post


Link to post
Share on other sites

4.9.11[beta, close to stable]

- Restored missing "Edit curves" in pens tab.

- 16K support in "Change mesh & texture resolution."

- Layers masking correct functioning restored.

- stability and UI issues fixed.

  • Like 3
  • Thanks 1

Share this post


Link to post
Share on other sites

It seems baking a multi mesh with AO goes on infinitely (16K) + default AO settings.  -past 100%  and beyond 2000%

Multi mesh subdivide + smoothing also doesn't work in 4.9.11

Thank you for updating/adding 16k to the texture baking Tool!

Edited by Ascensi
update

Share this post


Link to post
Share on other sites
2 hours ago, Ascensi said:

Multi mesh subdivide + smoothing also doesn't work in 4.9.11

Multi mesh subdivide + smoothing also doesn't work in 4.9.11 - it skips it and loads fast..    A 3rd party program caused that problem (importing and exporting.. 3DCoat works fine for smoothing.

Share this post


Link to post
Share on other sites

How do you feel - how stable this build is? I want to do community build before BlackFriday, so your opinion about general stability is important. At least in comparison to 4.9.05.

Share this post


Link to post
Share on other sites

I'm not heavily stressing  the latest build..but I don't seem to get crashes so far doing what I do 

In that sense it feels stable.

on another topic:

Is there any plan to bring back Antialiasing in new Render engine? 

Share this post


Link to post
Share on other sites
On 8/20/2019 at 6:24 PM, druh0o said:

Probably I've found a bug.

v4.9.05 DX and GL (also v4.8.38). Windows 7. Tested on two computers, so...

1) In Retopo room with the Strokes tool active (let's say after Autopo)

2) zoom in to your retopo mesh (this is important too!  let's say with Shift+A or with Alt + <mouse>  ) so the retopo mesh occupies a significant part of the viewport.

3) activate Transform and move your retopo mesh somehow

4) Ctr+Z - doesn't work (actually i noticed that 3d-coat kinda "counts" vertices of retopo mesh, so i started to hit Ctrl+Z many times - like ALOT, then suddenly it can undo Transform, but after A LOT of Ctrl+z)

 

If the Strokes tool is not active, looks like there is no undo Transform bug.

If you zoom out of the retopo mesh, so it's occupies a small part of viewport, looks like there is no undo Transform bug, even if the Strokes tool is active (or at least that bug is very rare, i don't know all of reasons of that bug).

 

UPD: tried in v4.7.24 -  it doesn't have this bug.


4.9.11 has the same bug.

Share this post


Link to post
Share on other sites
21 minutes ago, druh0o said:


4.9.11 has the same bug.

With Painting, it does this as well. I have to undo about 3 times before the program realizes that's what I want to do, but I've always thought that's how the program works, that it somehow needs to allocate memory or something before it can work.

Edited by Ascensi

Share this post


Link to post
Share on other sites
4 minutes ago, Ascensi said:

With Painting, it does this as well. I have to undo about 3 times before the program realizes that's what I want to do, but I've always thought that's how the program works, that it somehow needs to allocate memory or something before it can work.

Some of that may be the fact that it stores things in UNDO history that you might not expect...like hiding a layer or selecting one, etc. I find the most common time UNDO fails is right after AUTO-SAVE. I absolutely hate that and brought it up to Andrew. Maybe he isn't able to immediately re-produce it, but it certainly happens.

Share this post


Link to post
Share on other sites

Hi, using ToothPaste, muscle tool in Surface Mode is causing holes in the mesh surface.

image.thumb.png.6ce5074dd7253c6588eca5bf65628129.png

 

Share this post


Link to post
Share on other sites

×