[3DCoat 2024 development thread]

On 1/27/2024 at 11:06 PM, phil said:

same here, i am on fedora kde. file browser crashes as soon there are pictures involved, browsing 3d files works. my current workaround is drag and drop from the file browser to 3d coat. using it atm for reference planes. long time since i used ubuntu... hope 3dcoat changes to the official "linux reference platform" https://vfxplatform.com/

my setup notes ->
## 2023.37
dnf install python3.10 python3.10-libs
### startup
#!/bin/sh
export PYTHONHOME="/usr/lib/python3.10"
export COAT_PEN="Wacom Intuos4 4x6 Pen stylus"
export COAT_ERASER="Wacom Intuos4 4x6 Pen eraser"
export COAT_MOUSE="Core Pointer"

cd /mnt/data0/software/3DCoat-2023.37/
./3dcoat-Ubuntu20.04

### icc msg
cd /mnt/data0/software/3DCoat-2023.37/
find . -type f -name '*.png' -exec mogrify \{\} \;

 

I posted a general solution that should enable 3D Coat to work on any modern linux distribution in the following forum post, including fedora (I'm currently running Fedora 39).  The tl;dr is to use a tool called distrobox, which lets you very quickly wrap processes in lightweight, distro-specific containers. In 3D Coat's case, I configured it to run  out of an ubuntu 22.04 container.  Another important upside of this workflow is that you can declare exactly what is installed in each container, in effect, getting a deterministic, reproducible, and versioned runtime environment for whatever tools are executed out of the container -- no more of that "what have I changed on my host distro that is bothering this tool." That would also let you do things like spin up a new container when a new version of ubuntu comes out and if you run into problems, just immediately use the old version (or spend 2 minutes and let the tool recreate it from scratch). I'm not associated with distrobox at all, but it's a real game changer for linux for me since it brings the mature capabilities of containers into practical, daily usage.  Good luck, and let me know if this works for you!  

edit: most relevant to this thread is that this can help disambiguate what are genuine 3DC 2024 bugs versus a bug that is related to the runtime environment.

 

 

[[Solved] 3Dcoat crashing when trying to open thunar (file explorer) on EndevourOS (arch-derivitive linux distro)]

I had the same problem of 3dcoat crashing immediately after I selected File > Import > Model for per pixel painting, I happen to be running on Fedora 39 and was using the 3dcoat-Ubuntu22.04 binary for 3DCoat-2023.40.

I solved the problem by running 3dcoat in an Ubuntu 22.04 container using distrobox (see https://github.com/89luca89/distrobox ).  I expect this will enable 3dcoat to function fine on *any* modern linux distro that supports distrobox.  After you've installed distrobox:

1. Create a container image that uses Ubuntu 22.04 as the parent image, note that I've got an nvidia card so am instructing distrobox to give access to it.  You can see the official distrobox documentation for more info for your setup:

distrobox create --image ubuntu:22.04 --name ubuntu-nvidia --nvidia

2. (Only needed one time) Open a shell connected to that container image and install spacenavd, which fixes the "Space Navigator daemon for 3Dconnexion devices" error you can see in weeb_developer's problem report above

❯ distrobox enter ubuntu-nvidia

reshen@ubuntu-nvidia:~$ sudo apt install spacenavd
Reading package lists... Done
Building dependency tree... Done
...

3. Now just launch 3dcoat from within the container, and this makes 3dcoat happy (no longer crashes on model import) as it has all of the ubuntu environment setup correctly:

reshen@ubuntu-nvidia:~$ cd 3DCoat-2023.40/

reshen@ubuntu-nvidia:~/3DCoat-2023.40$ ./3dcoat-Ubuntu22.04
-----------------------------------------------------------------
Environment variable "COAT_PEN" = empty
(define the name of your stylus input device from the list below)
Environment variable "COAT_ERASER" = empty
(define the name of your eraser input device from the list below)
...

 

You can wrap the last command in a desktop file to make it available in whatever desktop environment you use and distrobox also lets you create manifest files so you can automate step 2 in case you distro hop. Distrobox is a remarkably powerful tool that makes cross-distro tool compatibility a non-issue.

Hope this helps!