Jump to content
3D Coat Forums

Search the Community

Showing results for tags 'subobjects'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • General 3DCoat
    • Announcements
    • 3DCoat
    • 3DCoat Printing
    • New Releases and Betas
    • 3DCoat AppLinks testing
    • SOS! Only for official urgent help
    • General Discussion
    • InstantLight Real Time Render
  • Galleries & Challenges
    • Finished & Wip projects
    • Official Contest
    • Community Challenges
    • Archived: Gallery of Finished Works
  • Resources & Development
    • Tutorials and New Feature Demos
    • 3DCoat Exchange Library
    • SDK, Plugins and Programming
  • Russian Forum
    • 3d Coat
    • Поддержка
    • WIP
    • Уроки
    • Предложения, вопросы
  • Gallery & Competition
  • French Forum - Forum Francophone
    • Questions relatives au Forum Francophone
    • Discussions sur 3DCoat
    • Tutoriaux
    • WIP Travaux en cours
    • Galerie Travaux Terminés
    • Hors Sujets et Créations numériques 3D / 2D associées
  • German Forum - Man spricht Deutsch
    • Fragen und Antworten zu 3D Coat
    • Tutorials
    • Stellenanzeigen

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

Found 1 result

  1. 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?
×