Jump to content
3DCoat Forums

Andreas Wolmer

Member
  • Posts

    13
  • Joined

  • Last visited

Andreas Wolmer's Achievements

Newbie

Newbie (1/11)

4

Reputation

  1. Just installed 2022.34 for Mac OS, but it does not start up. I get a very generic error message saying it can't start because of "a problem". I should add that 2022.24 did not have this issue. The more detailed error report says the following: Process: 3DCoat [1038] Path: /Applications/3DCoat-2022.34/3DCoat.app/Contents/MacOS/3DCoat Identifier: com.Pilgway.-DCoat Version: 2022.34 (1) Code Type: X86-64 (Native) Parent Process: ??? [1] Responsible: 3DCoat [1038] User ID: 501 Date/Time: 2022-07-01 18:41:22.986 +0200 OS Version: Mac OS X 10.14.6 (18G9323) Report Version: 12 Anonymous UUID: A38AB001-9F22-EA23-E1C0-C70E30BA0D5B Time Awake Since Boot: 1100 seconds System Integrity Protection: enabled Crashed Thread: 0 Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Exception Note: EXC_CORPSE_NOTIFY Termination Reason: DYLD, [0x1] Library missing Application Specific Information: dyld: launch, loading dependent libraries Dyld Error Message: Library not loaded: @rpath/libosdGPU.3.4.4.dylib Referenced from: /Applications/3DCoat-2022.34/3DCoat.app/Contents/MacOS/3DCoat Reason: no suitable image found. Did find: /Applications/3DCoat-2022.34/3DCoat.app/Contents/MacOS/../Frameworks/libosdGPU.3.4.4.dylib: cannot load 'libosdGPU.3.4.4.dylib' (load command 0x80000034 is unknown) /Applications/3DCoat-2022.34/3DCoat.app/Contents/MacOS/../Frameworks/libosdGPU.3.4.4.dylib: stat() failed with errno=1 Binary Images: 0x103168000 - 0x105163ed7 +com.Pilgway.-DCoat (2022.34 - 1) <3ACB055C-BB9F-3A59-9FEF-3F9C1DC3285C> /Applications/3DCoat-2022.34/3DCoat.app/Contents/MacOS/3DCoat 0x115ef5000 - 0x115f5f70f dyld (655.1.1) <4842B61A-B868-3146-9CA9-5582C4198B25> /usr/lib/dyld Model: MacPro6,1, BootROM 428.140.7.0.0, 8 processors, 8-Core Intel Xeon E5, 3 GHz, 32 GB, SMC 2.20f18 Graphics: kHW_AMDFireProD500Item, AMD FirePro D500, spdisplays_pcie_device, 3 GB Graphics: kHW_AMDFireProD500Item, AMD FirePro D500, spdisplays_pcie_device, 3 GB Memory Module: DIMM1, 8 GB, DDR3 ECC, 1866 MHz, 0x80AD, 0x484D54343147553741465238432D52442020 Memory Module: DIMM2, 8 GB, DDR3 ECC, 1866 MHz, 0x80AD, 0x484D54343147553741465238432D52442020 Memory Module: DIMM3, 8 GB, DDR3 ECC, 1866 MHz, 0x80AD, 0x484D54343147553741465238432D52442020 Memory Module: DIMM4, 8 GB, DDR3 ECC, 1866 MHz, 0x80AD, 0x484D54343147553741465238432D52442020 AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x135), Broadcom BCM43xx 1.0 (7.77.61.3 AirPortDriverBrcmNIC-1305.12) Bluetooth: Version 6.0.14d13, 3 services, 27 devices, 1 incoming serial ports Network Service: Wi-Fi, AirPort, en2 PCI Card: AMD FirePro D500, Display Controller, Slot-1 PCI Card: AMD FirePro D500, Display Controller, Slot-2 Serial ATA Device: APPLE SSD SM0512F, 500,28 GB USB Device: USB 2.0 Bus USB Device: Hub USB Device: BRCM20702 Hub USB Device: Bluetooth USB Host Controller USB Device: USB 3.0 Bus USB Device: Hub USB Device: CodeMeter-Stick USB Device: Balance USB Device: iRig Keys USB Device: Hub USB Device: EIZO USB HID Monitor USB Device: Razer Nostromo USB Device: Intuos5 touch M Thunderbolt Bus: Mac Pro, Apple Inc., 19.2 Thunderbolt Bus: Mac Pro, Apple Inc., 19.2 Thunderbolt Bus: Mac Pro, Apple Inc., 19.2
  2. Hey guys, I just installed the latest release (2021.70 for Windows) and the sensitivity still does not seem to work. It's kind of a shame, I really would like to start using 2021, but for now I have to go back to an earlier version to be able to sculpt. Any idea about when this might get fixed? Kind regards Andreas
  3. I've started using 3DCoat 2021.21 on Windows 10 recently, and it seems to me that the Smooth tool (or smoothing when using the Shift key when sculpting) does not appear to respect pen pressure from my Wacom. Pressure sensitivity does work when using other tools though, when sculpting or painting. I've only noticed it when smoothing. Anyone else noticed this behaviour? Kind regards Andreas
  4. Thanks! I tried those settings, but sadly it still creates overlapping polygons. But I just noticed that you wrote that you are using version 4.9.46 win (a beta version I suppose?), so perhaps the tool behaviour has changed between 4.9.37 and the version you are using? It would be great if there was a way to reset all tools to default.
  5. Hi! Yes, unfortunately it happens at much lower values, even from around 25% and upwards it becomes noticeable. What version and OS are you using, by the way?
  6. Thanks for the reply Carlosan! I have 3D Coat both on my work Windows 10 machine and my home office Mac, so I tried installing the latest (4.9.37) version on my office PC, and when I used the default Pinch tool, I did not get the overlapping problem, it looked as expected. However, after selecting a Pinch Preset, the problem occurs again! I'm not sure how to reset the Pinch Tool to its original settings, so now when I select the default Pinch tool it retains the faulty settings unfortunately. Is there a way to just reset a specific tool to default? I can't seem to find it. Thanks! Andreas
  7. Hi! Ever since version 4.9.42C, and also in 4.9.44B, the pinch tool appears to be broken. You get these weird polygon overlaps, regardless of tool direction. If I go back to the previous version I used to run, 4.9.02, it works as expected. I'm on Mac OS 10.14.6 by the way. / Andreas
  8. Hi! Just installed latest version of 3D Coat (mac version), and it appears all my tool presets, brushes etc automatically migrated over to the new install, which is nice. I have versions all the way back to 4.7 installed, and that certainly seems like a waste of hd space, so I just want to make sure that it's fine to delete/unistall older versions of the program, and that nothing breaks if I do so? Regards Andreas
  9. Yep, it would be sweet to be able to simply "right click -> reset tool".
  10. Thanks, but that seems to be for controlling what tools etc appear in the UI. I'm looking for something that just resets tool settings such as radius, falloff, steady stroke etc to default. Cheers Andreas
  11. Hi! First off, I apologize if this is a really stupid question. Maybe I'm missing something really obvious, but I just can't seem to find a way to reset a Surface or Voxel tool to the default settings after having changed them either myself or by selecting a tool preset. Have googled and searched the forums, but no luck. Can anyone shed some light on this mystery? Thanks in advance / Andreas
×
×
  • Create New...