Jump to content
3D Coat Forums

bfriedman

Member
  • Content count

    5
  • Joined

  • Last visited

Community Reputation

0 Neutral

About bfriedman

  • Rank
    Newbie
  1. bfriedman

    New Curve tools. snapping and cutting questions/issues.

    Here's a quick capture of the snapping behavior. Showcasing that it snaps in viewspace without snapping in depth. https://www.youtube.com/watch?v=5k_pc_bmlG0&feature=youtu.be
  2. bfriedman

    New Curve tools. snapping and cutting questions/issues.

    4.8.20. Downloaded and installed fresh today. Specifically to enable and try out the curve tools that were released. Exposed using the "Show Beta Tools" preference.
  3. bfriedman

    New Curve tools. snapping and cutting questions/issues.

    Alas, no. Snap to surface only works on surfaces. It doesn't snap to curves or curve points at all. While this will work if you happen to be trying to snap to a curve that is also snapped to a surface, it doesn't work when working with curves alone, in 3d space.
  4. I've just given the new curves tools a workout and have two questions/issues. Curious if anyone has found solutions. 1)When I turn on "snap to curve points" and "snap to curve" I do get snapping. However, it's only in 2D, not 3D. That is to say, it looks like it snaps perfectly in the current view, but then when you tumble, you'll find it didn't snap in depth. I can see how a 2d "view based" snap can be useful too. But I feel the 3d snap is extremely important. Am I somehow doing this wrong? Is there a way to get a 3d snap with some other key press? If this is a feature oversight, I'd think a toggle under the snaps for 3d/2d snapping would be useful. 2) When I use the "Split Self Intersections" tool, with "Joint intersection" and "Split to Segments" I get mostly what I'd expect from a "cut curves" tool. I get a new parent with child curve pieces all cut up by intersection points. However, the original curves remain, which isn't what I want in most (but not all) cases. I'd very much like an option to delete and replace the originals. In a small curve cage, it's not too much of a nuisance to manually delete the originals. But in a larger curve cage that you are building and cutting and building and cutting, it will become too complex to manage. It's more ideal if there is a mode where curves that don't intersect, are left as is; and curves that are cut, get deleted and are replaced by the new segments. Is there an existing way to make it work this way, that I'm missing? If not, I'd suggest adding it for the purposes of working and refining complex curve cages efficiently. Thanks. -brad
  5. Question: My pipeline tool (larger content management system) is acting as an "App" with AppLink. Which lets me send assets to 3DCoat for work to be done, and to then pick up the results and file them away again. Which relieves users of the responsibility of adhering to complex naming conventions and file system structure. Which is great. But I seem to be limited to obj, fbx etc. Ideally I'd have my system pushing assets in this way, and retrieving work products this way. And that works. However, I'd also like to be able to manage their working files, which would be "3b" files. I noticed you added the [3b] import mode for opening 3b files directly via the applink. Which is great. And solves half the problem. I was wondering if there is an equivalent way to "export" or "save" files to 3b via the AppLink, rather than the various export formats. I had thought originally that if I specified a file with a "3b" extension on the second line it might be smart enough to execute a "save" rather than a "export." But it doesn't seem to work that way. I wanted to check if there's a simple way to do what I'm looking for, that I'm overlooking. Otherwise I'm likely to go a much heavier route, via the scripting engine, to see what I can come up with. Which I'd like to avoid if possible. The AppLink is so very close to handling everything I need. Thanks. -brad
×