Jump to content
3DCoat Forums

kbrilliant

Member
  • Posts

    55
  • Joined

  • Last visited

Everything posted by kbrilliant

  1. Hi, I was wondering if there is a way to automatically select voxel layers while sculpting without having to go over to the Vox Tree. For instance--hold a hot key and click on the voxels in the sculpting window? Thank you Ken
  2. Attached is a bit more progress. Initial color and spec work done and rendered in 3D Coat. So far, the performance in the program is decent. I'll post more if I see complete more on this creature. Thanks for looking.
  3. Here is a little update: Pictured is the mesh created with auto-retopo after some minor cleanup and the rendered model with displacement map in Softimage. I'll move onto the other texture maps in 3D coat and see how that aspect of the program has been shaping up. Thanks for looking Ken
  4. The model is at almost 8 million triangles and I have 8 gigs of RAM. I suppose I could go to the live clay tools to add more detail where desired, but I don't like the fact that you can loose your live clay work if you switch back to voxels. So, I haven't explored those tools too much. digman---I like your technique for hiding troublesome or complex parts of the object for auto-retopology. I never thought of that--thanks! Michalis--thank you! I'll post more when I progress Ken
  5. Thanks for the comments. The model is at almost 8 million triangles and is still fairly comfortable to work with. I wonder how auto-retopo will work with this.
  6. Just what everybody's been looking for---another digital alien. But I had fun freeform picking away at this. All voxel level sculpture work. I may take it further into texturing--perhaps try the per-pixel painting. Questions or comments welcome. Ken
  7. I noticed recently that 3D Coat wasn't responding to my Space Navigator. I went back one driver version, and now it works. I wonder if this is something 3D Coat has to rectify or is it on the 3D Connexion end?
  8. Hi Andrew, What is the best way to submit this file to you? It's rather large. For the record, I had this problem today with a simple per-pixel paint model and one 4k texture. The problem happened more frequently on the larger model. The only other bit of information I can provide is that I work with a 3D connexion space navigator controller Thank you for looking into it. Ken
  9. BUILD: 3.5.23 Cuda (GL & DX) OS: Windows Vista 64 bit HARDWARE: (If applicable) Intel Core 2 Quad CPU9450 @ 2.66GHz 8 GB RAM NVidia Quadro D 1GB memory BUG DESCRIPTION: Per Pixel Memory Leak STEPS TO REPRODUCE: I'm attempting to work on a model (43K polygons) with 17 materials (17 UV tiles). The textures rage in size from 256 - 2K (5-2K, 7-1K, 2-512, 1-256). Memory and performance seems ample at first, but soon depletes until system and program freeze. This can happen even when not painting or adding layers. Any insight is appreciated. (deadlines!) Ken
  10. I'm experiencing a memory leak on v 3.5.23C Cuda 64 bit Windows Vista while per pixel painting. I'm not sure how to recreate other than working on the scene. I can send it in if needed. Ken
  11. Hello, I'm wondering what the UV tile limit is for per-pixel painting. I seem to have encountered a limit, but I'm not sure how much I'm over. Is there a grid configuration where you shouldn't go over X in U or V? Thank you in advance for any assistance. Ken
  12. I get some strange shading when using the surface pinch and smooth tools. It goes away when switching back to voxels, but returns when using those tools in surface mode. I didn't get this in previous versions.
  13. I've noticed a slow down too, but haven't measured the memory usage. Someone posted a tip that seems to help: Toggle the voxel proxy mode. Once back to the full voxel model, it seems to speed up again. I hope this can help in tracking down the issue.
  14. For Lightwave, I've been using normal maps generated from 3D coat. They work well as a bump map type shading
  15. Hello, I am getting a consistent crash when attempting to use the voxel clone with symmetry feature (right click in the Vox tree). It can be repeated from a new document and any simple voxel tools. The Symmetrical copy from the voxel menu does work, however. Non cuda 64 bit Windows build 4.5.08 Thank you
  16. Hello, I've noticed on this latest build 3.5.06B that the magnify/reduction brush doesn't seem to work at all. You can test this by just loading a default model from the title screen for ppp painting. I can post this in a bug section if it helps too. Thank you for the attention
  17. Perhaps since this is a beta, I shouldn't heap on more comments. But I am a bit confused at the various conditions of the brushes and modes. For example, the strips feature doesn't seem to work in voxel mode, but it does in surface mode, while the stamp mode works in voxel and not in surface. Consistency in the way tools perform will go a long way in ease of use and enjoyment. It get's to be a bit tiring to keep these conditions in mind and switch back and forth. Lastly, the flatten brush has problems in that it jumps all over the surface. I'm excited about the developments, though, and look forward to their continued refinement.
  18. I'm also enjoying the speed and feel of the voxel engine. The only thing I'm experiencing is using the stamp brush mode in surface sculpting mode. It doesn't seem to work with the draw, clay, inflate brushes, and there is that flattened clipping happening with the others (in surface and stamp mode). Is this on purpose? Forgive me if this has been addressed already. I've tried to read most of the posts here, but there are so many. Ken
  19. I found that working with re topology was slow as well until I made the high resolution mesh locked (objects panel). It was faster after. In previous versions, I didn't need to do this. I also experienced the bug with the stamp and paint with rectangle brush method in PP paint mode.
  20. I found out the missing step to repeat this issue. Make sure "show displaced mesh" is checked before changing the mesh resolution. Turing it off and on again does seem to fix the model. Thank you for looking into it. Ken
  21. Hello, I'm seeing a repeatable bug when attempting to re size a texture map. 1. start a new scene and select any default model for per-pixel painting. Keep the default values. 2. got to edit: Mesh and texture resolution. Change the texture size to any other size. 3. The mesh "explodes". I'm working on Windows Vista Business 64 Bit. Non Cuda version of 3DC. Thank you for your attention to this matter. Ken
  22. BUILD: 3.3.09 64 bit (non-Cuda) OS:PC HARDWARE: (If applicable) BUG DESCRIPTION: Microvertex painting corruption with edit projections in external editor STEPS TO REPRODUCE: 1. load the default werewolf model for microvertex painting with a 4096 texture resolution. 2. create a new layer. Paint some color. 3. go to edit: edit projections in external editor 4. in external editor Photoshop, paint some new color in layer. save. 5. upon returning to 3d coat, the model is geometrically a mess, or the projection doesn't return and the layers are gone. 6. another quirk is that Photoshop states that "could not open...because the file was in use or left open" This happens on a clean reboot too 7. Upon further testing, a similar issue happens with per pixel painting. This seems to happen with any model, not just the default one. Thank you
  23. I'm experiencing a flickering of all the menus when I use the smooth tool--with the shift key or tool. Has anybody else had this issue v3.3.2 I did have this in the previous build. 64bit, non-CUda Thank you
×
×
  • Create New...