Jump to content
3DCoat Forums

lesaint

Contributor
  • Content count

    356
  • Joined

  • Last visited

Community Reputation

37 Excellent

About lesaint

  • Rank
    Novice

Contact Methods

  • Facebook
    https://www.facebook.com/merlin.silas

Recent Profile Visitors

925 profile views
  1. lesaint

    3DCoat 4.9 Open Beta testing thread

    I just remembered something that is in contradiction to this problem every occuring anymore. You said that you had saved your file with ghosted volumes. However, since quite a few releases now, whenever I save or there is autosave, all my ghosted volumes become visible ! (maybe this happens only when I am in the sculpt room though) so, either you don't have this "bug" (is it a bug?) or you saved while you were in the paint room maybe ?
  2. lesaint

    3DCoat 4.9 Open Beta testing thread

    I'm not entirely sure hidden voxels vanish when you exit 3dc too early after saving, I don't have proof. What I can say is that it has been my habit now for a long time to always wait a few seconds after saving before I exit 3dc (more seconds if the file is big, just two or three seconds if the fils is small) Ever since I do that, I don't think it happened again. Honestly I thought maybe the problem had gone away when I heard that 3dc would continue saving even after you close. So when it happened to you it was the first occurence I heard of in a long time. I think yes a progress bar for saving would be a really cool idea, in any case. **** There is another possible bug related to saving, but again I am not entirely sure : Sometimes saved files can't be opened. I believe this happens when I have deleted a bunch of paint layers and vox layers from a complex file, and then continued working on the remaining objects. **** So I try not to take saving for granted. I tend so save incrementally, so as to not lose everything. However, you don't really know until you have tried reopening the files, and I remember at least once when quite a few of my incremental saves were corrupt, and so were the autosaves.
  3. lesaint

    3DCoat 4.9 Open Beta testing thread

    By the way, I personally believe that this occurs when you close 3d-Coat too soon after saving. (and yes I know that 3d-C supposedly continues saving after you close it).
  4. lesaint

    3DCoat 4.9 Open Beta testing thread

    the old curves (green) seem to have vanished ? :( disabling beta tools only removes the curves menu : if you select closed spine stroke mode it still brings up the new (red) curves, without their menu.
  5. lesaint

    3DCoat 4.9 Open Beta testing thread

    Not sure I understand, what do you mean? You recovered your voxels through this method, yes ? (lucky about the undo's, saving makes the lost voxels vanish for good)
  6. lesaint

    3DCoat 4.9 Open Beta testing thread

    Follow these steps : -create a new layer with geometry in roughly the same space as your lost voxels. -Select a layer with lost voxels. -Select the fill tool and set its depth to 0 -"paint" with the fill tool on the geometry you created in the first step for that purpose, but with the empty layer selected. The lost voxels should start reappearing where you paint.
  7. lesaint

    3DCoat 4.9 Open Beta testing thread

    Don't erase the file Edit : AND DON't SAVE IT!
  8. lesaint

    3DCoat 4.9 Open Beta testing thread

    It would be nice if the scrape tool did something with CTRL like the chisel tool does.
  9. lesaint

    3DCoat 4.9 Open Beta testing thread

    Yes when doodling, just experimenting with shapes and all, having to always be afraid to perform an action is quite distracting and can break the mood... That is why I stay away from surface mode as much as I can. Because it is surface mode operations that are the most dangerous. There are bugs with undo that can break a voxel layer too, though. And I feel it is absolutely impossible to train onself to use undo carefully.
  10. lesaint

    3DCoat 4.9 Open Beta testing thread

    I usually take a pragmatic approach and look for workarounds. But yes I agree that the most intuitive commands, the ones that first come to mind *should* work... When you test the merge visible method you will see that it works best when the surface mesh is watertight. When it is not, it creates artifacts that sometimes ruin/hide part of the mesh. The solution to that can be quite tedious and time consuming. Again we stumble accross a simple function that *should* work, but doesn't, in most cases. I always dread to try this, and I make sure I save my file before I attempt to use the "close holes" function from the geometry menu. Sometimes it works like a charm, but too often it just fails, but that is nothing compared to the numerous times it leads to 3d-c freezing and you have no other option but to end the process. So, you need to thicken the surface mesh, just enough, not too much or it will spill over to the wrong side in thin areas. After you have thickened the mesh you can use merge visible on a vox layer without any artifacts. Then comes the tedious part : you have to fill the inside by hand somehow, without altering the surface.
  11. lesaint

    3DCoat 4.9 Open Beta testing thread

    To me, it makes much more sense to create a new vox layer, choose a resolution for it, and then right click > merge visible. This method is : - quasi instantaneous, - it gives you much more control than simply entering a number in the box and praying that the outcome will be what you want. - It preserves the original surface mode object - It gives you a vox layer that has a density that is compatible with your other layers (1 - 2 - 4 - 8, etc)
  12. lesaint

    3DCoat 4.9 Open Beta testing thread

    The problem when you use resample and don't get an even number like 1 is that when you later increase resolution, instead of getting 2, 4, 8, etc, you will get to other numbers like 3, 6, etc...
  13. lesaint

    3DCoat 4.9 Open Beta testing thread

    Well, there is still this thing that is one button, but I never use it because it changes the scale of your object The button that decreased resolution was at the bottom of the voxtree. It was also not just one step though : It created a copy of the vox layer at a lower resolution. so you had to delete the original as an extra step, and if you wanted to decrease more than once you had several copies to delete. Nevertheless, it was quite useful. Now there are other solutions, but... one solution is to right click vox layer > resample but if you do that you don't get a resolution that will match other layers precisely (you might end up with something like 0.7 instead of 1 for example) The method I use at present without the button is to create a new vox layer at the resolution I want, and then I right click it > merge visible The problem (besides being several steps) is that you cannot go below resolution 1
  14. lesaint

    3DCoat 4.9 Open Beta testing thread

    Am I the only one who misses the "decrease resolution" button ?
  15. lesaint

    3DCoat 4.9 Open Beta testing thread

    Sometimes I did get a dot instead of a line with the sphere tool. That doesn't seem to happen anymore. The dot would appear in the line of sight between my view and the pick point (I think not behind, but not entirely sure)
×