Advanced Member BluEgo Posted June 5, 2008 Advanced Member Report Share Posted June 5, 2008 Actually I'm planning to use 3D-coat most for its texturing skills other then for sculpt. The first thing I noticed, is how layer palette is so slow to manage. For example if I check on or off a layer, if it contains depth values, I could wait more than a little to see the result Also managing layers attributes like "Transparency" or "Specular Brightness", or blending options like "Standard mode" or "Modulate", is so slow I imagine that this is cause every layer contains depth, color and spec values So, as I read in the thread "Indicators on the layers" by philnolan3d, I think that separating depth by color in every layer should be really a good idea I think 3d-coat linking abilities with phothosop have great power, but there are some things could be refined. For instance, exporting and importing color layers with "Edit all layers in external editor" command takes too much time. Anyway, could we have in 3D-coat the same blend modes than photoshop? At least the most used should be introduced, like "multiply" (even if in 3d coat seems to be "modulate", but photoshop doesn't recognize it), "screen", "color burn", "color dodge" and "overlay" Besides, photoshop layer's opacity doesn't update transparency in 3D-coat. In the end, every time I add a mask in a photoshop layer, and then I save the document, 3D-coat creashes. I think that 3D-coat should have a mask system like photoshop, instead of linking masked areas of a layer to another layer, so working in both software will be more "standard" I know that 3D-coat isn't photoshop, but photoshop masks are great In the meanwhile, masks in photoshop layers could be flattened when re-importing in 3d coat, instead of crashing it Quote Link to comment Share on other sites More sharing options...
Andrew Shpagin Posted June 5, 2008 Report Share Posted June 5, 2008 The time of operation depends on actual layer square. If layer is a several storkes changing params work immediately, it it fills the whole object, it works slowly. Yes, I want to unify & call operations like in PS. It is in my plans. Ok, I will look at masks. The only problem - I am on the way to 2.10 and so I must make make changes in old sources (2.09) and new (2.10) so I am trying to avoid big changes in 2.09 because I must duplicate changes in 2.10. Sources of 2.09 and 2.10 are very (but not so much) different because of 2.10 is based on new graphical engine. But anyway I fix bugs that was found in 2.09 and make update every time on request. 1 Quote Link to comment Share on other sites More sharing options...
Advanced Member rimasson Posted June 5, 2008 Advanced Member Report Share Posted June 5, 2008 Hi Andrew. About the Merge Down Bug i found today, I can perfectly live with, until 2.10. Quote Link to comment Share on other sites More sharing options...
Advanced Member geo_n Posted June 5, 2008 Advanced Member Report Share Posted June 5, 2008 Yeah I was thinking about the layering terminology of 3dc before why it doesn't use the same as ps. It would be much easier to understand for new users imho. Quote Link to comment Share on other sites More sharing options...
Advanced Member BluEgo Posted June 5, 2008 Author Advanced Member Report Share Posted June 5, 2008 Of course these are some suggestions for the future of 3D-coat, and as rimasson told, I can wait 2.10 or later releases to see some of these implemented in this beautiful piece of software Quote Link to comment Share on other sites More sharing options...
Advanced Member SonK Posted June 10, 2008 Advanced Member Report Share Posted June 10, 2008 i kind of wish Andrew would add a node base system instead of the PhotoShop layer approach or at least have it as a optional way to work in 3DC(maybe in 3.0!) Quote Link to comment Share on other sites More sharing options...
philnolan3d Posted June 10, 2008 Report Share Posted June 10, 2008 i kind of wish Andrew would add a node base system instead of the PhotoShop layer approach or at least have it as a optional way to work in 3DC(maybe in 3.0!) I have a hard enough time figuring out nodes in LightWave and Map Zone, now you're suggesting them in 3DC? Quote Link to comment Share on other sites More sharing options...
Advanced Member SonK Posted June 10, 2008 Advanced Member Report Share Posted June 10, 2008 I have a hard enough time figuring out nodes in LightWave and Map Zone, now you're suggesting them in 3DC? Well a PhotoShop layer can get really complicated to see whats going on very quick..when you have alot of them and lots of fx. with a node system its easier to see how things are hooked up even for a newb like me. I should stress, that it should be a optional method not the only method. I dont have a problem with XSi RenderTree 1 Quote Link to comment Share on other sites More sharing options...
philnolan3d Posted June 10, 2008 Report Share Posted June 10, 2008 I should stress, that it should be a optional method not the only method. Well as long as it would still be optional, then those of us who are nodally challenged won't get left out in the cold. :lol: Quote Link to comment Share on other sites More sharing options...
Advanced Member BluEgo Posted June 11, 2008 Author Advanced Member Report Share Posted June 11, 2008 Well a PhotoShop layer can get really complicated to see whats going on very quick..when you have alot of them and lots of fx. with a node system its easier to see how things are hooked up even for a newb like me. I should stress, that it should be a optional method not the only method.I dont have a problem with XSi RenderTree I am not agree in this case. What we want in sculpting/texturing software, is a fast way of layering all the stuff. I like a lot nodal networks, from shaders to compositing for animations, but to paint strokes, to blend them, and adjusting colors, photoshop way is yet the best and fast workflow IMO. If I would be in modo for example, I would like nodes to make complex rigs in 401. But simply in 3D-coat I cannot see why should be implemented a nodal network. Maybe for assembling shaders, but 3D-coat has not an offline render engine, and for a realtime preview of our model a simple CG shader is enough. I don't mean I would not be satisfied if I will see this one day, but I think is better to focuse on what is better for sculpting and texturing stuff Quote Link to comment Share on other sites More sharing options...
Advanced Member rimasson Posted June 11, 2008 Advanced Member Report Share Posted June 11, 2008 I am not agree in this case.What we want in sculpting/texturing software, is a fast way of layering all the stuff. I like a lot nodal networks, from shaders to compositing for animations, but to paint strokes, to blend them, and adjusting colors, photoshop way is yet the best and fast workflow IMO. If I would be in modo for example, I would like nodes to make complex rigs in 401. But simply in 3D-coat I cannot see why should be implemented a nodal network. Maybe for assembling shaders, but 3D-coat has not an offline render engine, and for a realtime preview of our model a simple CG shader is enough. I don't mean I would not be satisfied if I will see this one day, but I think is better to focuse on what is better for sculpting and texturing stuff i Agree. a Nodal network layer system is not a necessity Quote Link to comment Share on other sites More sharing options...
Advanced Member geo_n Posted June 12, 2008 Advanced Member Report Share Posted June 12, 2008 i Agree. a Nodal network layer system is not a necessity eek nodes, steep learning curve is not good. dealing with maya and lightwave nodes is enough for me. brain can't absorb anymore. :lol: Quote Link to comment Share on other sites More sharing options...
Recommended Posts
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.