Jump to content
3DCoat Forums
  • Posts

    • SERGYI
      After migrating 3DCoat from AngelScript to Python, the project became completely broken under macOS and Linux. With our combined efforts and a lot of time, we were able to resolve the Python issues on macOS, but they remain unresolved on Linux.
    • Carlosan
      All this info is detailed here  
    • Britain
      Theres a bit of confusion about the app. Where is the correct one located at? The github appears to be outdated. Blender extension has none or least I cant locate it. The video doesnt mention what app is being used. For me Ill use the old fashion import and export ways
    • 45cend
      Hey Carlosan! Thanks for a speedy response! The link itself is working. The video shows the exporting of a Vertex Painted sculpt and it's imported only once there, but this was not the issue. We were discribing a scenario where we would export an unwrapped mesh from the Painting room to Blender, make changes to textures in 3DCoat and re-export to Blender. In this case it would carry over a new mesh instance to Blender even with the export geometry option is disabled. Blender will treat this as a new object and append 00# suffix to its name. In my understanding the Applink should recognise that it's the same instance unless the output mesh is given a different name or the connetion between two apps is aborted.  
    • Carlosan
      This issue was not solved on latest version 2025.15 ?  
    • Carlosan
      yes please , we don't have other reports but yours.
    • tcwik
      Nothing works like before; shortcuts do nothing; all those previous types of surfaces seem like they won't change anything; maybe some big changes are made; perhaps I need to reinstall all the software again :/..
    • 45cend
      Apologies for being annoying with this. I had hopes this will have been resolved with the Blender 5.0 update, but it still persists. Could you please let us know what priority level the fix is given. With large projects this is rather a significant issue, as texturing is an iterative process and after several rounds of exporting blender gets polluted with redundant geometry pretty quickly. Just to re-iterate, when re-exporting textures of the same object it would be nice if new material is assigned to the originally exported object - for situations when "Export texture" is enabled and "Export geometry" option is disabled. So the bridge always 'remembers' what object is being worked on as if blender is a continuation of 3DCoat as one of its rooms (I know it's a bit more complex than that in reality xD). Thanks for attention! 
    • Carlosan
    • flagpole
      Ah okay, thanks for replying. Ive noticed working with wine prefixes trough a Launcher there's still some stuff in 3DCoat what's working different compared to the native 3DCoat. Small glitches etc. I'll keep in mind what you're saying SreckoM, thanks.
    • Carlosan
      Can you explain what is not working and the steps to replicate it ? thanks
    • Carlosan
      Hi  Install latest version 2025.15 3DC do it automatically  
×
×
  • Create New...