Jump to content
3DCoat Forums

roentgen

Member
 View Profile  See their activity

  • Posts

    77

  • Joined

  • Last visited

 Content Type 

Posts posted by roentgen

  5. Blender Applink

    in 3DCoat AppLinks

    Posted

    Is there anything update on this?

    Please let me know if it reproduces or does not.

     

    On 4/27/2020 at 11:27 PM, roentgen said:

    thanks @haikalle

    I attach the file.

    `__staffB` is an object was created by AppLink. UV-sets of this are consolidated to one, and can see/edit on 3d-coat.

    'staffB' is an original of '__staffB', has UV-sets can not see/edit on 3d-coat.

     

     

    staff_b.blend

  8. Blender Applink

    in 3DCoat AppLinks

    Posted · Edited by roentgen

    I can't preserve UV-maps for an object has multi UV-sets among my workflows.

     

    1. 'Send'-ing an object has multi UV-sets to 3d-coat, to do 'UV-Mapping'.

    2. Unwrap in 3d-coat for each UV-set

    3. Send back to blender

    4. (Here a object has correct UV-set for material)

    5. 'Send' again the object of (4) to 3d-coat

    6. I see some UV-sets are broken

     

    Do I have to keep  materials one  forever?

    Or does any idea to do good for multi materials?

     

    ---

    3d-coat applink version 5.0.0

    3d-coat 4.9.37 (win64)

     

  12. Switching a layer resets an object that be created by 'Coat'-tool

    in New Releases, Bugs Reports & Development Discussion

    Posted

    Hi.

     

    I have tweaken an object on 'Shape' layer by some tools. This object and its layer had been created by 'Coat' tool.

    Then switching a layer and  return to 'Shape' layer again, I just see  an object before tweaking and a spline that used to coating.

    It seems to be new just 'Coat'ed object now, my teaking is gone.

    Any idea to fix 'Coat'ed object?

     

    best,

     

    3d-coat(GL) 4.9.05
    Windows10 (64bit)

  19. 3D-Coat 3.7 updates thread

    in New Releases, Bugs Reports & Development Discussion

    Posted

    I'm afraid I have also seen this happen many times when I turn off symmetry. All I've been able to do is select and delete the extra polys and then turn symmetry back on.

    I turned symmetry tool off/on at once or ... twice.

    Let's take a look this figure.

    Some blue points that are used in 'Points/Faces' tool still leaved themselves on symmetry's another side.

    This is something wrong, isn't that?

  21. 3D-Coat 3.7 updates thread

    in New Releases, Bugs Reports & Development Discussion

    Posted

    Happy new year all,

    I tried 3D-Coat ver 3.7.02C for mac.

    LC-CutOff-brush causes a crash.

    I guess that 3d-coat recursive-called itself and killed by stack-overflow when the application build an AABB tree up.

    the debugger told me this:

    Program received signal EXC_BAD_ACCESS, Could not access memory.

    Reason: KERN_PROTECTION_FAILURE at address: 0x00007fff5f3fffec

    0x0000000100725588 in bmAABBNode::Init ()

    (gdb) bt

    #0 0x0000000100725588 in bmAABBNode::Init ()

    #1 0x00000001007259d8 in bmAABBNode::Init ()

    #2 0x00000001007259fd in bmAABBNode::Init ()

    #3 0x00000001007259fd in bmAABBNode::Init ()

    ** sniff **

    #30792 0x00000001007259fd in bmAABBNode::Init ()

    #30793 0x00000001007259d8 in bmAABBNode::Init ()

    #30794 0x00000001007259d8 in bmAABBNode::Init ()

    #30795 0x00000001007259d8 in bmAABBNode::Init ()

    #30796 0x00000001007259d8 in bmAABBNode::Init ()

    #30797 0x00000001007259d8 in bmAABBNode::Init ()

    #30798 0x00000001007259d8 in bmAABBNode::Init ()

    #30799 0x00000001007259d8 in bmAABBNode::Init ()

    #30800 0x00000001007259d8 in bmAABBNode::Init ()

    #30801 0x00000001007259d8 in bmAABBNode::Init ()

    #30802 0x00000001007259d8 in bmAABBNode::Init ()

    #30803 0x000000010072736c in bool_struct::do_boolean ()

    #30804 0x000000010072f14e in BasicMesh::boolean ()

    #30805 0x00000001006e6cf7 in VolumeObject::SurfaceRectCut2 ()

    #30806 0x00000001006e5995 in DoRectCut ()

    #30807 0x00000001006139d1 in MakeSymmOpVO ()

    #30808 0x000000010070c43b in CutterExt::OnRectSelectionEnd ()

    #30809 0x00000001006b5438 in VoxelSculptTool::OnRectSelectionEnd ()

    #30810 0x00000001001f7799 in BasicTool::btOnLMB_Up ()

    #30811 0x0000000100420d8b in SceneWidget::OnButtonUp ()

    #30812 0x00000001000df67d in comms::cWidgets::HandleInputEvents ()

    #30813 0x00000001005f9e12 in comms::cMain_OnRender ()

    #30814 0x000000010007ad5a in cMacMain_OneIterationOfMessageLoop ()

    #30815 0x000000010007a28f in main ()

    (gdb) info reg

    rax 0x1745afa20 6247086624

    rbx 0x7852 30802

    rcx 0x7852 30802

    rdx 0x0 0

    rsi 0x179281000 6327635968

    rdi 0x1745afa58 6247086680

    rbp 0x7fff5f4000e0 0x7fff5f4000e0

    rsp 0x7fff5f3fffe0 0x7fff5f3fffe0

    r8 0xb 11

    r9 0x1eaa40 2009664

    r10 0x0 0

    r11 0x1e9760 2004832

    r12 0xffffdc00 4294958080

    r13 0x0 0

    r14 0x1745afa90 6247086736

    r15 0xf4240 1000000

    rip 0x100725588 0x100725588 <bmAABBNode::Init(bmAB*, int, int)+20>

    eflags 0x10202 66050

    cs 0x2b 43

    ss 0x0 0

    ds 0x0 0

    es 0x0 0

    fs 0x23 35

    gs 0xf 15

    (gdb)

  23. 3D-Coat 3.5 updates thread

    in New Releases, Bugs Reports & Development Discussion

    Posted

    Hi,

    3.5.27a for Mac64 still be killed by out of memory.

    I tried to run the version on debugger, found an illegal malloc-call.

    When the class named cRenderGL stores an image to the data (thumbnail? I dont know), the image size was a negative value.

    I guess an image format may be wrong.

    int16_t bpp = image->getFormat(); // bpp is a large or a negative value

    buf = new char [width * height * format]; // failed to allocation

    something like this.

    much much easy to fix if the developer see the callstack.

    I will post it when I get home, otherwise is it better to send it to someone?

  24. 3D-Coat 3.5 updates thread

    in New Releases, Bugs Reports & Development Discussion

    Posted

    Hi,

    I have problem with mac 3.5.25C, always gives "out of memory" error and quit unexpectedly upon saving ...

    Have tried clear up all previous versions and preferences, reinstall twice, still the same error.

    Going back to 3.5.24 for daily use now, which is quite solid imho, looking forward to .26 for mac :)

    That case may be same to me ... if it occurs on the painting mode. Some people reported same issue.

    I thought that Andrew said "use DX version" for the issue, but DX's not available on mac.

    Please use DX version. GL drivers from NVidia still have problem.

    My spec: iMac i7, 8G ram, os 10.6.8

    That's exactly same to me ;-)

×
×
  • Create New...