Jump to content
3DCoat Forums

V4.5 BETA (experimental)


Recommended Posts

Andrew, looks like the Cut & Clone and Clone tools are not working in the Sculpt Room. They are not copying/cloning any of the geometry, and once the operation is "completed", it goes to the top-most object in the VoxTree without doing anything noticeable. For troubleshooting: The object is in surface mode.

 

Thanks.

 

 

 

EDIT: Symmetry mode needs to be turned on. Otherwise it works. So, they are broken with symmetry mode on.

Link to comment
Share on other sites

  • Advanced Member

Artman was right.

Then I must misunderstand how it works, because I can't see how I can do what I described.

Try this:

-make a new layer, paste an image of a bolt on it.

-add another new layer, set it to overlay, paint a colour onto it.

-Clip the overlay layer with the bolt layer so it doesn't go outside of the bolt's boundaries.

-Now add another mask to the overlay layer, to add texture to it non-destructively.

 

Ofcourse I understand it's a seperate image that masks the layer, I'm not new to cg. Nevertheless, the practicality of this system is bad, and there's a good example right under our noses.

Link to comment
Share on other sites

Beta9

its me, or Sliders in the Paint Room now have far better response ?

Try please:

 

-Texture > adjust

- Switch any preview on /off

 

 

NOTE:

Andrew said: Pilgway and Allegorithmic were talking about Substance implementation inside 3DC last year, but still conversation is open. 

Link to comment
Share on other sites

  • Reputable Contributor

BETA9

- Longstanding problem with crashes in UV room/auomapping solved.

-PMR materials gizmo moves correctly in all mapping modes, hovering preview rectangle with gizmo will not hide material preview.

- Mapping in PBR materials correctly treated - no more locked to mappint that set in material settings. Preview in rectangle corresponds to mapping type in the top bar.

- Different preview introduced for planar/uv mapping of PBR materials.

- restored edit projection

Thank you, the obj file import with missing faces and incorrect unwrapping is now fixed... :D

Link to comment
Share on other sites

  • Reputable Contributor

What is the "import coarse mesh" purpose under the Baking menu in the Retopo room, there is no tool tip to explain the function of the operation...

I tried to bake without a retopo mesh in case it would ask me to import a mesh to be the retopo baking mesh that had a uv set before the baking function started. I was ask no such question and of course no baking was performed.

 

4.5.Beta9 windows 32bit running under wine in Linux

post-518-0-68677300-1422315843_thumb.png

Edited by digman
Link to comment
Share on other sites

  • Reputable Contributor

Yes, the sliders works realy nice now.

Much better as in the older versions, This is a big step in the right direction.

 

Many Thanks Andrew.

Guess the squeeky wheel gets the grease so...squeek, squeek. :D  ....

 

Sliders in the Paint Room....they be like

 

3318487786_64e03e0b8a_z.jpg?zz=1

There is a Southern (US) expression, "Slow as Molasses." That's what I meant with the picture, here. Paint dries faster than sliders update. Doesn't matter if it's PPP, MV or Vertex Paint. It only has two speeds. Slow and Stop.

 

  • Like 1
Link to comment
Share on other sites

  • Reputable Contributor

Have you tried this with Beta9?

Your Video shows Beta8.

There shouldn't be any changes as Andrew hasn't mentioned that being addressed at all. Been asking for this to get some attention for a long time, now. I have to believe that moving to DX11 and OpenGL 4 would help to some degree, as texture refreshing is something that is always being improved for enhanced gameplay. Perhaps Andrew could allow the user to set up a dedicated cache folder for all texture maps/data...and performance could be boosted by locating it on SSD drive. I think Mari does something like this.

Link to comment
Share on other sites

  • Contributor

And - forgot one change n beta9 - updating preview should be much less laggy.

 

Hm, maybe i am wrong, but i think it was better in my quick test.

I have testet only the sphere with 1024 in PPP and it feels like 5 or 10 times faster.

Not realtime, but better.

Maybe i should test it more, if the preview is faster or not.

Edited by Malo
Link to comment
Share on other sites

Nope. Im a "reporter" I can't delete anything. Anyway,I barely go there...Im too lazy.

You are set to developer Status as I see it right. Developers can delete issues.

:-)

 

If you don't want this I can set you back to reporter status.

 

Best wishes

Chris

Link to comment
Share on other sites

  • Reputable Contributor

Hm, maybe i am wrong, but i think it was better in my quick test.

I have testet only the sphere with 1024 in PPP and it feels like 5 or 10 times faster.

Not realtime, but better.

Maybe i should test it more, if the preview is faster or not.

Just tested Beta9. I don't think there have been any changes. Seems about the same. On a 2k map, it's usable, but that's about it. There is still a few seconds of lag when using the layer Adjustments (TEXTURES menu > ADJUSTMENTS > Hue/Sat/Lightness). On 4k maps, forget it.

 

tumblr_n5wg8b6ljU1smmsbuo1_250.gif

Link to comment
Share on other sites

  • Reputable Contributor

One solution I think could help is perhaps an option cache all layers and image maps to a specific folder, and to down-res what is shown in the viewport...a similar concept to caching a layer in the Sculpt Room. You cache all the 4k maps/texture files, and while you are working in the viewport, 3D Coat is actually using a down-sampled version, so performance remains relatively brisk. And at any point, the user can uncache a layer they are painting on, to work on or preview in the viewport or render room


I still think it's way past time to move to DX11 and OpenGL 4

Link to comment
Share on other sites

  • Reputable Contributor

Maybe, this down-res technique can be applied at least when using sliders in the Paint room, if for no other purpose. To me, though....I think it would be a smart idea to be able to cache certain layers and show a lower res proxy. For example....if all you have is a solid color on one layer, why does 3D Coat need to use 4K for that, when even a 1k will suffice. Only layers that need to show 4k+ would be ones with some level of detail. I don't know if this would be feasible from a coding standpoint. But having the ability to down-sample certain layers should help reduce the load on system resources

Link to comment
Share on other sites

  • Member

One solution I think could help is perhaps an option cache all layers and image maps to a specific folder, and to down-res what is shown in the viewport...a similar concept to caching a layer in the Sculpt Room. You cache all the 4k maps/texture files, and while you are working in the viewport, 3D Coat is actually using a down-sampled version, so performance remains relatively brisk. And at any point, the user can uncache a layer they are painting on, to work on or preview in the viewport or render room

I still think it's way past time to move to DX11 and OpenGL 4

And to 64-bit Assembler for speed sensitive code parts, like paint room.

Link to comment
Share on other sites

  • Member

I think i found a bug. Sub / child volume's are missing there visibility icon

 

Steps to reproduce:

 

Open a new voxel sculpting object

select the split tool and split the volume

select the copy000 volume

select the split tool and split the copy000 volume

 

volume*_copy001 visibility icon is missing

 

changing the parent of copy001 to the root of the VoxTree makes the icon visible

 

This behavior can also be seen in the VoxTree after loading the Mannequin voxel sculpting preset

Link to comment
Share on other sites

  • Advanced Member

When editing layers externally, both Gloss and Metaln layers are saved to a 'Layersspec.psd', meaning you can't open both in Photoshop at the same time.

 

AbnRanger: Ah yes, I was only testing on 1k. Sadly, I've found 4k to be impossible to work on within 3dCoat anyway. I'll doublecheck if I'm using the correct .exe (dx cuda), because I've heard from others that 4k works quite well.

 

edit: Yup, dx64 Cuda. Hmm.

Edited by Mighty Pea
Link to comment
Share on other sites

  • Contributor

@ABNRanger

Damn, you are right,

On lower resolution it works much better but as more you go up as more unusable it gets.

I should test more stuff in the future until i say it is good or better.

 

About the caching idea

What about if we work in the oposite way?

I mean everything gets stored on a 8 or 16k map, but you choose the resolution in the viewport you want to work with.

I know you dont like what i am saying next, but Substance Painter works in that way.

You paint in SP with a 1k or 2k map and if you want to export your maps, you switch to 4k, and you get a perfect 4k HD map not an upscaled pixelated 1k or 2k map.

If that would be possible, it would be enough to paint maximal on 4k, but you where always able to export 8k or 16k.

What did you think?

Edited by Malo
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...