Jump to content
3DCoat Forums

Search the Community

Showing results for tags 'ptex'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • General
    • Announcements
    • Tutorials and new feature demos
    • New Releases, Bugs Reports & Development Discussion
  • 3DCoat
    • General 3DCoat
    • Common workflow
    • Coding scripts & plugins
    • SOS! If you need urgent help for 3DCoat
  • Community
    • CG & Hardware Discussion
    • Content exchange
    • Artwork & Contest
  • International
    • Brazil Forum - falamos português
    • 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


  • Community Calendar

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL











Found 13 results

  1. slick3d.art


    This character was painted in 3D Coat using ptex. Then, I did the lookdev, layout and rendering in Lightwave 3D 2020. The post effects were done using Denis Pontonnier plugin for Lightwave, DPFilter.

    © Slick3d.art

  2. Hi, I think I may have found a bug when trying to import multiple ptex maps. I used the "object by object" export option and that wrote out the maps perfectly, but I'm running into a problem trying to import those maps back onto the models. I made a video below showing what happens. I would like to Suggest: Would be great if when using the "object by object" export option (since the ptex maps names match the mesh names) if there were an option to load the "object by object" maps from choosing a directory that contains the ptex maps. This would map the ptex maps to the corresponding mesh based on the ptex/mesh names all at once, rather than loading each texture one by one. On a complex set, that could take lots of time. I've included my simple test object if anyone would like to test with it. Thanks so much! ptexPerObjectMaps.mp4 ptexObjects.obj
  3. Hoping someone can help me out here. I'm trying to get this to work, and I'm up against a bit of a time constraint. I've been trying to bake a ptex displacement map from my highpoly mesh object to my lowpoly mesh. But after the bake process the model doubles in scale, but this only seems to happen when baking to Ptex. Am I doing something wrong? Here's a video with my process. Thanks for any help with this! ptexBakeScale.mp4
  4. Hi everyone, this is a WIP and not (yet) official guide, I'm working on a tutorial that might be clear-cut method from start to finish. You can leave a comment if I'm missing something, or point out an error. Some information is entirely my own understanding, some may have been used from your own posts etc Subheading: PaintRoom --> Retopo Room --> Bake to MicroVertex --> Bake Displacement to Lowpoly mesh This Article discusses the the complete workflow(s) from model creation to Baking both Material maps and mesh of your Highly detailed Per Pixel Painting, Microvertex and Ptex Projects using Smart Materials that utilize displacement maps. 1. Displacement Topology - Preparing your model: Voxel meshes are ideal for displacement due to uniform faces that prevent painted textures on the surface from stretching and other glitches. It's also very important that your models don't contain hard edges otherwise faces will likely mix into each other creating distortion. If you need high performance in your 3D application, tris are best for game engines due to efficiency, performance and file size but Micro Vertex working with tries can create artifacts. Using Quads with Microvertex maybe more ideal to paint characters and in general quads are preferred for smoother surfaces and better deformations for animations. For Film & Game Engine Optimization that uses Automatic Frustum & Occlusion culling, plan your model. Large objects such as cliffs or walls can hide/disable other parts or areas not seen by the camera or animation viewport, so it's ideal to slice the model in such a way as allowing parts to be automatically hidden to speed up Renders and Game Performance while making visible and focusing only on what the camera actually sees. There is an essential rule of mesh resolution that needs to be followed and that is that your lowpoly model needs enough resolution initially to be subdivided from. The reason is that your model could likely be full of cracks in other programs when displacement maps are applied, it doesn't have enough actual geometry to deform (even with tessellation) You will see that smooth mesh by subdivision helps but may not fix the problem, the model needs enough resolution from the beginning of the paint job. There are a few methods of preparing your model for painting and we have it numbered from best to least under: Displacement Topology -Preparing your model, UV Mapping, Painting and Baking the Mesh. (1) Per-Pixel-Painting Topology: Ideal for landscapes -use meshes with tries (can be set upon import) Import a low poly mesh, in the menu set to "Triangulate" if using quads, set UV to "keep UV" , Subdivision can either be 0 of you want to use tessellation instead while painting (faster but lower smooth quality) or use "subdivide" (higher quality but slower to paint) If you use Subdivide 3DCoat may automatically choose a medium setting which may be sufficient. You can always add tessellation to each of your paint objects (models) later. Choose "full smoothing" if you want accuracy using Smart materials that use height maps. (2) Ptex Topology Method Topology: Ideal for Characters using quads. Upon New Ptex project topology, import model, choose" Auto-Retopo with Ptex". -It will do the the retopology for you and then send you directly to Ptex painting. (3) Micro Vertex Topology Topology- Ideal if you have to use models with quads for quality Character deformations in animations. -unless it's best and safe to convert them to tris upon import and simply export the maps but the maps might have to be exported for quads. UV Mapping: Manual UV tip: Best approach to avoid glitches is to cut UVs in a grid with straight lines, Voxel topology makes areas to cut easier to identify. Cutting into grids has equal/balanced pull on the vertices in all directions. To get more detail especially with landscapes that don't need organized UV islands, aim for islands to be square or rectangular and aligned vertical or horizontal. The more UV space filled in the better. Automatic UV Method: (1) Using Per-Pixel-Painting Mode: (Community input required for the general consensus of the best UV creation in 3DCoat -ideally with parameters that are used in the manual UV creation process) (2) Using Ptex Method Mode: The Ptex Paint method provides automatic UV mapping upon export. (3) Using Micro Vertex Mode: (Community input required for the general consensus of the best UV creation in 3DCoat -ideally with parameters that are used in the manual UV creation process) Painting Tip: When painting displacement closer to less rounded edges, reduce Depth value to approximately10 or lower, paint and test, undo, reduce or raise value, paint and test etc. Some Smart Materials contain AO, after selecting one that has AO maps you will be asked if you want to generate an AO layer because the smart material requires it. This is optional, It might be better to keep your project light, and bake AO at the end of your painting but painting with AO can help you see details better and know what you're getting right away. You can create and edit your smart materials to fine tune it. Learn about creating Smart Materials Here (You can create Smart Materials in any existing or empty project) (1) Per-Pixel-Painting: is currently the Best Method to paint Smart Materials using displacement, to understand why, visit this link (2) Ptex Painting: Since Ptex and Smart Materials have been made compatible with each other, more investigation is needed to determine if it's more advantageous over Per-Pixel-Painting but at this time it uses Quads but can it be exported to tries and still look good? (Community input required for this for the general consensus) (3) Micro Vertex Painting: Since Micro Vertex and Smart Materials have been made compatible with each other fairly recently more community input is required to determine the benefits. *Micro Vertex is compatible with creating displacement maps and "in theory" is compatible with Vector Displacement Smart Materials which should open the door to paint complete whole Colorful photo-scanned models but Smart Materials may or may not yet have added Vector Displacement Map Compatibility. A Smart Material with Vector maps maybe the first of its kind to produce Vector Displacement and Color at the same time. Baking Displacement to low poly to reduce the need for high tessellation in other 3D applications -WIP This wasn't the workflow in the past. Generally Displacement maps are created from the differences between the original and the high poly version (which is what you want) however, this is just for creating the correct displacement maps. During your painting with displacement maps used in your Smart Material, as it changes the vertex positions in the high poly it also changes some in the low poly. Bake To Hi Poly Mesh (1) Using Per-Pixel-Painting Mode: bake the displacement into a newly created high poly mesh added to a layer in the paint room using "Bake sculpt mesh onto paint room mesh" (Top Menu Under Bake) Exporting Textures: Normally when exporting textures with subdivision levels, layer o must first be selected. The (1) Using Per-Pixel-Painting Workflow: (2) Using Ptex Method Workflow: (3) Using Micro Vertex Workflow: Bake Displacement -To-Lowpoly Mesh: (1) IF you're using "Per-Pixel-Painting" send to: Retopo Room, choose "bake into scene Microvertex" then bake sculpted mesh to sub-D (you set it with option menu when bake) + displace applied mesh in paint room as polygon group name layer. (real deform high polygon mesh) (2) IF you're using "Ptex Painting" send to: The Ptex Paint method provides automatic UV mapping upon export. (3) Send Micro Vertex to: Different Displacement painting methods and evolution - what you need to know before you decide your workflow: https://3dcoat.com/wiki/index.php?title=3.1_Per_Pixel_vs_Microvertex Methods of Setting up Displacement in external applications Using traditional Methods - Adding extra geometry to instruct the shader or the program to add more vertex points and positions 1. Tessellation - Set tessellation level only as high as the details need to be. Tessellation can come in two common forms; 1.Distance-based that offers Level of detail (LOD) on the model the closer it is to the camera and 2.Full tessellation (currently used in 3DCoat) 2. Smooth mesh By Subdivision - Subdivision like full tessellation offers no ability for LOD, meaning it's going to reduce performance but like tessellation you can increase or decrease levels. It's the best visually and if tessellation doesn't close cracks due to lack of geometry, smooth mesh by subdivision might fix that. This mode is also incompatible with some GPU Renderers like Iray and will greatly slow it down. Your application may let you combine both methods; "Smoot Mesh By Subdivision" and "Tessellation." Generally using Level 1 of "Smooth Mesh By Subdivision" and "Tessellation" level between 1-2 gives optimal results for rendering. Emerging No Extra Geometry Methods 1. Screen Space Displacement mapping (SSDM) - Some initial experiments from developers have shown real-time game play of 500-1000+ FPS in Unity from the developer "Oddity Interactive" (Using the performance heavy photo-scanned RD-Textures was more in the 400 FPS range) Another Example
  5. Hi, I think I ran into a BUG. I'm noticing that when working in Ptex mode that calculating curvature and occlusion maps don't work correctly. Below is an example of a model with multiple meshes, and what happens when I try to calculate occlusion. I'm showing my test with occlusion and not curvature because the curvature example is just a brighter version of the model but doesn't add any real curvature. The occlusion example shows the error better. If you want to see the topic discussion and the different things, I've tested here's a link to that: Thanks, -Alex
  6. Hi, I think I came across a bug. I've run into this issue when calculating curvature whenever I am working with Ptex. this happens in 3dcoat v4 and 2021. It leaves block artifacts In the curvature map. You can see an example below I have tried this in both PC and Linux versions. Thanks, Alex
  7. This appears to suffer the same issue as with 3D Coat 2021. When painting using PTEX, there doesn't appear to be an option to export the color map. I've attached a screen capture below. Link to the reported issue for 3DCoat 2021. 3D model community • 3D modeling forum • 3D printing forum - 3D Coat
  8. Hi, I'm using 2021_B52. Not sure if anyone else has run into this, but I ran into a reproducible issue when choosing Ptex Paint from the main menu, and choosing either the head or creature model. It appears to start to load with the progress bar, but then just hangs and doesn't come back.
  9. Hi, I noticed that the Color to Ptex option is missing from the Texture export menu, but is available from the Texture import menu. It's available in v4.9 if that's helpful. Thanks!
  10. Hello All, I've always worked with microvertex painting, as I utilize deep displacement in Houdini, but thought I'd try PTEX, to get the most bang for my buck, map resolution wise. I'm having difficulties getting it to export the depth info into the displacement map. It bakes out as a flat grey map. If the polys spill over to a second ptex plane, it's displacement map contains the depth info, while the first plane remains blank grey. The scale for the first also reads out as #INF00 rather than a numeric value. I'm working within 4.5.19, but I've also tried it with the latest 4.7 beta release w/o any further success. Anyone dealt with this before?
  11. Hi Everyone! I just started mucking about with Ptex, and I remember from early videos of this technology that the big advantage of ptex was the ability to increase the resolution of the texture in specific areas. If you didn't have enough resolution for a set of polygons (such as an area with text), you could just select the area and bump up the resolution. Am I misremembering? Is there such a feature in 3d Coat and I am just missing it? I can't find a way to -globally- change the resolution of a ptex model. It's like the resolution is locked when you load the model. That seems... inflexible to me.
  12. Hi guys and gals (appologies if this is in the wrong area). I had an immediate query regarding ptex texture baking. Was wondering if it is possible, to say. if you have a ptex model ready to go and you want to transfer those textures to another model. also setup for Ptex. So basically taking ptex data from one model and transfering to another (not transfering Ptex texture data from a model and baking down to uvs) Cheers and thanks for the great software
  13. Been working on this forever it seems and tried googling and searching all the forums. PTEX is included in 3d-coat but hardly a word on how to use it. Since Maya 2013 in its hardware render mode can render ptex I thought be nice to export a voxel from 3d-coat to Maya with ptex textures. I first AUTOTOPED WITH PTEX then exported it as an obj (also tried fbx). Then in the paint room I exported a PTEX COLOR TEXTURE. In Maya went the HD RENDER VIEWER imported obj (and tried fbx) and then applied the Ptex to the color channel. Just cant get it to work correctly. I have tried a million different things. ANY advice on this would be so appreciated. I love the hardware 2.0 render in Maya and use it all the time. It would be a dream to be able to use PTEX (no uv's! hurray) models from 3d-Coat.
  • Create New...