Jump to content
3DCoat Forums

Search the Community

Showing results for tags 'Materials'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • General
    • Announcements
    • Tutorials and new feature demos
    • New Releases, Bugs Reports & Development Discussion
  • 3DCoat
    • General 3DCoat
    • Coding scripts & plugins
    • SOS! If you need urgent help for 3DCoat
  • Community
    • CG & Hardware Discussion
    • Content exchange
    • Artwork & Contest
  • International
    • Chinese forum - 3DCoat用户讨论组
    • Japanese forum - 日本のフォーラム
    • German Forum - Man spricht Deutsch
    • French Forum - Forum Francophone
    • Russian Forum
  • 3DC's Topics
  • 3DC's Tips
  • 3DC's Topics
  • 3DC's Paint
  • 3DC's Hipoly
  • 3DC's Lowpoly

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Google+


YouTube


Vimeo


Facebook


Location


Interests

  1. Current transform gizmo has a huge and annoying drawback. Its transform center is always and only in the center of material texture. It turns precise positioning of projected picture /material into a huge pain in the a.. Especially being accustomed to scale from a randomly placed center in Photoshop(by digits only), Zbrush, Fusion, any vector soft etc. So for example if I want to paint a window from some render or photo I first have to crop source file the way a corner of the window would be in precise center of a file. Only that way I could scale precisely from that corner . If the source file is big enough and the detail I want to project is far from image center the positioning it on the screen/model turns into a pure torture. Not sure if placing the center of transform randomly is a huge problem or not. I am asking for that feature for many years already, long before the transform gizmo appeared. But it's a main reason I still rather use Zbrush for texture painting than 3d coat.
  2. Please, consider the following scenario. 1. If you import this .obj file to 3D Coat for laying out UVs, you get: - Materials named: ->materialA - containing objects A-D, ->materialB - containing objects E-F, ->materialC - containing object G. - UV-sets named: ->materialA - containing UVs of objects A-D, ->materialB - containing UVs of objects E-F, ->materialC - containing UVs of object G. This is very convenient and I like it. 2. Let's see what happens if you import the same model to PPP. What you get is: - Materials: ->materialA - containing objects A-D, ->materialB - containing objects E-F, ->materialC - containing object G. - Objects: ->objectA, ->objectB, (...) ->objectG. So again, it's very convenient. You can hide, fill, etc. multiple subobjects sharing a certain material, but you can also do the same with individual subobjects. 3. When imported to Voxel Room, the model is separated into subobjects and each subobject receives its own layer. Perfect. BUT... 4. If you import the model to Retopo Room, here things look a bit different. - Groups: ->materialA - contains objects A-D, ->materialB - contains objects E-F, ->materialC - contains object G. - UV-sets: -> NO UV-SETS ARE CREATED! This can be good or bad, depending on what you want to do. If baking with names correspondence is your goal, than it's damn awful, because you now have to: ->create a Group for each subobject and name it correctly (using former subobject name that was lost when you imported the model to Retopo Room, ->move each subobject from a group that it shares with other subobjects, to its individual group you have just created. ->recreate UV-sets and move objects according to their former UV-set linkage. Let's say, you're done with this additional work and are ready for baking with names correspondence selected. The result is: 5. Paint Room: - Materials: ->objectA_materialA - contains objectA, ->objectB_materialA - contains objectB, ->objectC_materialA - contains objectC, ->objectD_materialA - contains objectD, ->objectE_materialB - contains objectE, ->objectF_materialB - contains objectF, ->objectG_materialC - contains objectG. - Objects: ->objectA_objectB_objectC_objectD_objectE_objectF (a combination of all object names, up to 50 characters) - contains ALL SUBOBJECTS(!). So it goes completely bananas here when compared to how it worked in point #2. Is this behaviour intentional or is it a bug?
  3. Greetings, I have been trying to dig into the logic behind folders (brushes, materials, etc) so I know where things go, backup or can group differently, etc. Is there a straightforward outline of what goes where and where those folders are? I feel confused. Thank You, Kevin L
  4. I am totally knew to 3d coat but it seemed just what i needed for character texturing at the time. before i start learning more than the basics i want to know if i can export my model(textured in 3dcoat) with a separate material and diffuse/normal map for the feet, torso, head, skin... if so how? thanks oh and i dont want to have to seraprate my character into objects
×
×
  • Create New...