Search the Community

When opening a large model (about 29M faces), 3D Coat 2024 (and 4.9 as well) crashes when application memory usage reaches about 4 Gig. Just before the crash, it displays a rather ridiculous message about increasing VM size in the OS settings (which isn't even possible). This is a 64 bit app, on a 64 bit OS, on a machine with 160 GB of RAM and about 8 TB of free disk space. Full crash reports and a sample file can be provided. Let me know what you need to help debug this issue in your code. --------------------------------------- Process: 3DCoat [13840] Path: /Applications/3DCoat-2024.31/3DCoat.app/Contents/MacOS/3DCoat Identifier: com.Pilgway.-DCoat Version: 2024.31 (1) Code Type: X86-64 (Native) Parent Process: launchd [1] User ID: 501 Date/Time: 2025-06-13 15:12:23.3744 -0700 OS Version: macOS 14.6.1 (23G93) Report Version: 12 Bridge OS Version: 8.6 (21P6074) Anonymous UUID: 096D5B68-B94E-63F0-17DD-11136D1F6B88 Time Awake Since Boot: 2300000 seconds System Integrity Protection: enabled Crashed Thread: 0 Dispatch queue: com.apple.main-thread Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000 Exception Codes: 0x0000000000000001, 0x0000000000000000 Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11 Terminating Process: exc handler [13840] VM Region Info: 0 is not in any region. Bytes before following region: 4467380224 REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL UNUSED SPACE AT START ---> __TEXT 10a46d000-10c7de000 [ 35.4M] r-x/r-x SM=COW /Applications/3DCoat-2024.31/3DCoat.app/Contents/MacOS/3DCoat Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 libsystem_platform.dylib 0x7ff805b67aa9 _platform_bzero$VARIANT$Haswell + 41 1 3DCoat 0x10bf5107f BaseMesh::create(int, int, int) + 75 2 3DCoat 0x10b529146 comms::cMeshContainer::CreateHardsurfaceStaticMesh() + 712 3 3DCoat 0x10aaea7e6 VoxelSculptTool::OpenRawMesh(comms::cMeshContainer*, bool) + 2344 4 3DCoat 0x10aaf02dc VoxelSculptTool::SEL_MESH() + 854 5 3DCoat 0x10a4abaab _ImportForVertexPainting() + 698 6 3DCoat 0x10af368ce coat::Scene::importMesh(char const*, comms::cMat4 const&) + 60 7 3DCoat 0x10bd47233 merge(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char>> const&) + 42 8 3DCoat 0x10bd47266 merge1() + 36 9 3DCoat 0x10bb20e0e endstack + 72 10 3DCoat 0x10bb20ca8 CallSystemFunctionNative(asCContext*, asCScriptFunction*, void*, unsigned int*, void*, unsigned long&, void*) + 1488 11 3DCoat 0x10b9d2a5c CallSystemFunction(int, asCContext*) + 353 12 3DCoat 0x10b7ddd82 asCContext::ExecuteNext() + 762 13 3DCoat 0x10b7dd7da asCContext::Execute() + 284 14 3DCoat 0x10add1760 Script::Run(int, char const*, bool) + 1066 15 3DCoat 0x10add1aa2 Script::Run(char const*, char const*, bool) + 80 16 3DCoat 0x10add1b8b Script::Run(char const*, bool) + 181 17 3DCoat 0x10c0901ec do_mitem_cmd() + 6140 18 3DCoat 0x10a52860f _tcallback<void>::call() + 175 19 3DCoat 0x10b06aa58 BaseWidget::CallCallbacks(unsigned int) + 730 20 3DCoat 0x10b06faf6 Widgets::ProcessWindowsMessages(tagMSG&) + 932 21 3DCoat 0x10b091539 IntfWidget1::OnButtonDown(int) + 167 22 3DCoat 0x10ad4230e comms::cWidgets::HandleInputEvents() + 1322 23 3DCoat 0x10bab71e8 comms::cMain_OnRender(comms::cRect const&) + 123 24 3DCoat 0x10ad4b25e cMacMain_OneIterationOfMessageLoop() + 2312 25 3DCoat 0x10ad522be main + 22929 26 dyld 0x7ff8057af345 start + 1909

Hello, I just wanted to reported a kind of bug I've found. Here the specs: MacBook Air M2 - Sequoia 15.3 3DCoat 2024.32-2 Steps to reproduce: 1. Go in Sculpt Mode 2. Open the Brush Preset Tab 3. Add New Folder in The Tab 4. Click on Three Dots Menu and Load Presets from a file *.*.preset 5. No Presets Are loaded and displayed Is this a known issue? If yes, are there any workaround? Thanks!

Hi there - this bug started after mac version - 2023.28. It's still present in the latest one 2023.40. My hardware M1 Max 32gb - 4k External monitor - Mac OS Sonoma 14.2.1 (23C71) Here is a video of the issue https://monosnap.com/file/BaezWzqolVoAaizpyf5oByNnSGOPCZ I've also attached an image comparing the functionality

3DCoat 2021.6 on MacOS Try to use cloth tool and just get spinning beach ball. Force quit after waiting 5 minutes. Running cloth tool on Windows with the same objects and settings starts almost instantly and finishes in a few seconds. Would like to use this on MacOS since it is where I do most of my work. -Kevin

I only get a black screen when I try to launch the latest beta version of 3D Coat on MacOS Sierra - 10.12 (16A323). Am I the only one? If not are there known work arounds (I thought I saw one about 3D Coat 4.7.8a working, but I had the same result, black screen). Any links, info is welcome Thanks all! Here are the properties of my 15' MacBook pro... - MacBook Pro (Retina, 15-inch, Mid 2015) - 2.8 GHz Intel Core i7 - 16 GB 1600 MHz DDR3 - RAM - Intel Iris Pro 1536 MB - Graphics Card