Linux updates news

[SreckoM]

Go into 3DCoat folder and execute 'ldd 3dcoat', paste output here. 

[nodespaghetti]

@SreckoMif this was for me, then 

nodespaghetti@noodlebot:/opt/3DCoat-2024.28-02$ ldd 3dcoat
    linux-vdso.so.1 (0x00007ffe3fbfa000)
    libgtk-3.so.0 => /lib/x86_64-linux-gnu/libgtk-3.so.0 (0x00007dea6b000000)
    libgdk-3.so.0 => /lib/x86_64-linux-gnu/libgdk-3.so.0 (0x00007dea6b8b2000)
    libpangocairo-1.0.so.0 => /lib/x86_64-linux-gnu/libpangocairo-1.0.so.0 (0x00007dea6b8a1000)
    libpango-1.0.so.0 => /lib/x86_64-linux-gnu/libpango-1.0.so.0 (0x00007dea6b836000)
    libharfbuzz.so.0 => /lib/x86_64-linux-gnu/libharfbuzz.so.0 (0x00007dea6aef3000)
    libatk-1.0.so.0 => /lib/x86_64-linux-gnu/libatk-1.0.so.0 (0x00007dea6b80a000)
    libcairo-gobject.so.2 => /lib/x86_64-linux-gnu/libcairo-gobject.so.2 (0x00007dea6b7fe000)
    libcairo.so.2 => /lib/x86_64-linux-gnu/libcairo.so.2 (0x00007dea6adaf000)
    libgdk_pixbuf-2.0.so.0 => /lib/x86_64-linux-gnu/libgdk_pixbuf-2.0.so.0 (0x00007dea6b7d0000)
    libgio-2.0.so.0 => /lib/x86_64-linux-gnu/libgio-2.0.so.0 (0x00007dea6abdf000)
    libgobject-2.0.so.0 => /lib/x86_64-linux-gnu/libgobject-2.0.so.0 (0x00007dea6ab7c000)
    libglib-2.0.so.0 => /lib/x86_64-linux-gnu/libglib-2.0.so.0 (0x00007dea6aa33000)
    libX11.so.6 => /lib/x86_64-linux-gnu/libX11.so.6 (0x00007dea6a8f6000)
    libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007dea6a80d000)
    libpng16.so.16 => /lib/x86_64-linux-gnu/libpng16.so.16 (0x00007dea6a7d5000)
    libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007dea6a7b9000)
    libstdc++.so.6 => /lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007dea6a400000)
    libGL.so.1 => /lib/x86_64-linux-gnu/libGL.so.1 (0x00007dea6a732000)
    libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007dea6b7c7000)
    libexpat.so.1 => /lib/x86_64-linux-gnu/libexpat.so.1 (0x00007dea6a707000)
    libutil.so.1 => /lib/x86_64-linux-gnu/libutil.so.1 (0x00007dea6a702000)
    libfbxsdk.so => LinuxLibs/libfbxsdk.so (0x00007dea69600000)
    libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007dea6a6d2000)
    libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007dea6a6cd000)
    libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007dea69200000)
    libgmodule-2.0.so.0 => /lib/x86_64-linux-gnu/libgmodule-2.0.so.0 (0x00007dea6a6c6000)
    libpangoft2-1.0.so.0 => /lib/x86_64-linux-gnu/libpangoft2-1.0.so.0 (0x00007dea6a6ab000)
    libfontconfig.so.1 => /lib/x86_64-linux-gnu/libfontconfig.so.1 (0x00007dea6a3af000)
    libfribidi.so.0 => /lib/x86_64-linux-gnu/libfribidi.so.0 (0x00007dea6a68d000)
    libepoxy.so.0 => /lib/x86_64-linux-gnu/libepoxy.so.0 (0x00007dea6a28c000)
    libXi.so.6 => /lib/x86_64-linux-gnu/libXi.so.6 (0x00007dea6a279000)
    libatk-bridge-2.0.so.0 => /lib/x86_64-linux-gnu/libatk-bridge-2.0.so.0 (0x00007dea6a23d000)
    libXfixes.so.3 => /lib/x86_64-linux-gnu/libXfixes.so.3 (0x00007dea6a683000)
    libxkbcommon.so.0 => /lib/x86_64-linux-gnu/libxkbcommon.so.0 (0x00007dea6a1f4000)
    libwayland-client.so.0 => /lib/x86_64-linux-gnu/libwayland-client.so.0 (0x00007dea6a1e4000)
    libwayland-cursor.so.0 => /lib/x86_64-linux-gnu/libwayland-cursor.so.0 (0x00007dea6a1da000)
    libwayland-egl.so.1 => /lib/x86_64-linux-gnu/libwayland-egl.so.1 (0x00007dea6a1d5000)
    libXext.so.6 => /lib/x86_64-linux-gnu/libXext.so.6 (0x00007dea6a1c1000)
    libXcursor.so.1 => /lib/x86_64-linux-gnu/libXcursor.so.1 (0x00007dea6a1b5000)
    libXdamage.so.1 => /lib/x86_64-linux-gnu/libXdamage.so.1 (0x00007dea6a1b0000)
    libXcomposite.so.1 => /lib/x86_64-linux-gnu/libXcomposite.so.1 (0x00007dea6a1ab000)
    libXrandr.so.2 => /lib/x86_64-linux-gnu/libXrandr.so.2 (0x00007dea6a19e000)
    libXinerama.so.1 => /lib/x86_64-linux-gnu/libXinerama.so.1 (0x00007dea6a199000)
    libthai.so.0 => /lib/x86_64-linux-gnu/libthai.so.0 (0x00007dea6a18e000)
    libfreetype.so.6 => /lib/x86_64-linux-gnu/libfreetype.so.6 (0x00007dea6a0c2000)
    libgraphite2.so.3 => /lib/x86_64-linux-gnu/libgraphite2.so.3 (0x00007dea6a09a000)
    libXrender.so.1 => /lib/x86_64-linux-gnu/libXrender.so.1 (0x00007dea6a08e000)
    libxcb.so.1 => /lib/x86_64-linux-gnu/libxcb.so.1 (0x00007dea6a065000)
    libxcb-render.so.0 => /lib/x86_64-linux-gnu/libxcb-render.so.0 (0x00007dea6a056000)
    libxcb-shm.so.0 => /lib/x86_64-linux-gnu/libxcb-shm.so.0 (0x00007dea6a051000)
    libpixman-1.so.0 => /lib/x86_64-linux-gnu/libpixman-1.so.0 (0x00007dea69551000)
    libjpeg.so.8 => /lib/x86_64-linux-gnu/libjpeg.so.8 (0x00007dea694ce000)
    libmount.so.1 => /lib/x86_64-linux-gnu/libmount.so.1 (0x00007dea69481000)
    libselinux.so.1 => /lib/x86_64-linux-gnu/libselinux.so.1 (0x00007dea69454000)
    libffi.so.8 => /lib/x86_64-linux-gnu/libffi.so.8 (0x00007dea69448000)
    libpcre2-8.so.0 => /lib/x86_64-linux-gnu/libpcre2-8.so.0 (0x00007dea69166000)
    /lib64/ld-linux-x86-64.so.2 (0x00007dea6b9d8000)
    libGLdispatch.so.0 => /lib/x86_64-linux-gnu/libGLdispatch.so.0 (0x00007dea690ae000)
    libGLX.so.0 => /lib/x86_64-linux-gnu/libGLX.so.0 (0x00007dea69415000)
    libatspi.so.0 => /lib/x86_64-linux-gnu/libatspi.so.0 (0x00007dea69074000)
    libdbus-1.so.3 => /lib/x86_64-linux-gnu/libdbus-1.so.3 (0x00007dea69025000)
    libdatrie.so.1 => /lib/x86_64-linux-gnu/libdatrie.so.1 (0x00007dea6901c000)
    libbz2.so.1.0 => /lib/x86_64-linux-gnu/libbz2.so.1.0 (0x00007dea69008000)
    libbrotlidec.so.1 => /lib/x86_64-linux-gnu/libbrotlidec.so.1 (0x00007dea68ffa000)
    libXau.so.6 => /lib/x86_64-linux-gnu/libXau.so.6 (0x00007dea68ff4000)
    libXdmcp.so.6 => /lib/x86_64-linux-gnu/libXdmcp.so.6 (0x00007dea68fec000)
    libblkid.so.1 => /lib/x86_64-linux-gnu/libblkid.so.1 (0x00007dea68fb1000)
    libsystemd.so.0 => /lib/x86_64-linux-gnu/libsystemd.so.0 (0x00007dea68ed1000)
    libbrotlicommon.so.1 => /lib/x86_64-linux-gnu/libbrotlicommon.so.1 (0x00007dea68eae000)
    libbsd.so.0 => /lib/x86_64-linux-gnu/libbsd.so.0 (0x00007dea68e98000)
    libcap.so.2 => /lib/x86_64-linux-gnu/libcap.so.2 (0x00007dea68e8b000)
    libgcrypt.so.20 => /lib/x86_64-linux-gnu/libgcrypt.so.20 (0x00007dea68d41000)
    liblz4.so.1 => /lib/x86_64-linux-gnu/liblz4.so.1 (0x00007dea68d1f000)
    liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x00007dea68ced000)
    libzstd.so.1 => /lib/x86_64-linux-gnu/libzstd.so.1 (0x00007dea68c33000)
    libmd.so.0 => /lib/x86_64-linux-gnu/libmd.so.0 (0x00007dea68c24000)
    libgpg-error.so.0 => /lib/x86_64-linux-gnu/libgpg-error.so.0 (0x00007dea68bfd000)

This is the latest version 2024.28-2

Edited November 13, 2024 by nodespaghetti

[SERGYI]

On 11/3/2024 at 2:07 PM, SreckoM said:

On PopOS 22.04, X11, Nvidia card with latest drivers, also latest 3Dcoat, has issue that when switching to Sculpt mode it triggers bug that all floating windows get hidden unless I click and hold Alt key. Also objects also get hidden. Impossible to work with. Does not happen with 2024.06.

 

I am aware of this. For an unknown reason, "3DCoat" loses the OpenGL context after displaying modal dialogs, particularly after displaying the startup "Enter license" dialog. When the code for modal dialogs is commented, then "3DCoat" works as expected.

[SERGYI]

As I said, "3DCoat 202x" crashed after displaying a modal dialog. By excluding parts of the source code, I have found that GTK3 functions gtk_clipboard_wait_for_text, gtk_clipboard_wait_is_image_available, and gtk_clipboard_wait_for_image change OpenGL context in the main thread of the application. They should not do that, and they do not do that in GTK2. After working around this problem, I have built two versions of "3DCoat 202x". The first one is from the old branch for the year 2024:
https://pilgway.com/~sergyi/3DCoat-2024/3DCoat-2024.27-01.tar.bz2
The second one is from the new branch for the year 2025:
https://pilgway.com/~sergyi/3DCoat-2024/3DCoat-2024.32-1.tar.bz2
https://pilgway.com/~sergyi/links-Linux.html
Please compare the two. Some changes have been made since the old branch, 2024. Some tools may be working in the 2024 version but not in 2025. Please report this case directly to my email.
Known problems: (1) annoying flickering of the input license dialog with buttons "Login", "Free trial/demo", and "Load license" when moving the mouse; (2) the slow/incorrect response of the small buttons on the navigation panel: Adjust the contrast/intensity of lighting, Move/Zoom the camera, etc. I will fix the known problems (1) and (2). In the meantime, please compare the two builds and notify me about issues in "2024.32" since "2024.27". I can find the code that introduced a problem by reverting to commits.

[SERGYI]

7 hours ago, Grakino said:

Linux and graphics tablet support

I am a Linux user, Linux is my main working OS. One of the reasons I bought 3DCoat is the Linux support. 3DCoat has been transitioning to GTK3 for a year now. The current version 2024-28-2 is not workable, and my graphics tablet does not work with it. 3DCoat 2024.06 does not work properly with modern Linux operating systems (including Ubuntu). Also, this version requires additional settings from the terminal to make my graphics tablet more-less work. I do not like this. Programs such as Maya, Blender, Mari, Substance Painter/Designer (steam Linux version) support my graphics tablet out of the box without any additional settings, and also has a much better support of linux than 3DCoat.

Please try the latest build from here:
https://pilgway.com/~sergyi/links-Linux.html
In my test, it works as expected under Ubuntu 20.04. Still, there are two noticeable glitches: flickering of the input license dialog and slow/incorrect response of the small buttons on the navigation panel. Regarding tablet support, I don't know what to suggest because my Wacom Intuos 3 works out of the box.

[SERGYI]

8 hours ago, Grakino said:

I want to give a detailed answer to this question.

Outstanding comment. Based on such comments, any product should be developed. Regarding tablet support, here is my idea: email me at sergkryzh AT gmail DOT com. I will build some tiny test executables with experimental code on tablet support.

[Grakino]

1 hour ago, SERGYI said:

In my test, it works as expected under Ubuntu 20.04.

In Windows terms, it's the same as saying on my Windows 8 everything works fine, i don't know what you talking about. We already have Windows 11, Windows 12 coming soon, guys.

20.04 support end in april 2025. I don't want to use old and outdated OS for one soft, while your competitors offer good linux support for modern OS.

Your link lead me to 2024.28-02 version (i tested it technically work but not suitable for work), i guess you mean 2024.32-1.

Edited January 15 by Grakino

[Grakino]

15 minutes ago, SERGYI said:

Outstanding comment. Based on such comments, any product should be developed. Regarding tablet support, here is my idea: email me at sergkryzh AT gmail DOT com. I will build some tiny test executables with experimental code on tablet support.

Ok, i am following "Linux updates news" i will test your new build and then I'll write to you. I need couple days.

Edited January 15 by Grakino

[Sorn]

48 minutes ago, Grakino said:

Ok, i am following "Linux updates news" i will test your new build and then I'll write to you. I need couple days.

You may want to test 3DCoat Linux builds in a not outdated distribution (or old version of a distribution), and see that it doesn't work, really, to have a base reference. See the what, the how and the why, possibly, to 3DCoat not working in a modern Linux.

Then, you can try the Distrobox route. I haven't written a proper guide yet, was waiting for some things to improve first; anyway, there are step-by-step instructions around these forums, in the Linux section. Basically, one has to install distrobox, then an Ubuntu 20.04 (oh, dear!) image with Nvidia support to have hardware acceleration if one uses nVidia (--nvidia flag now works, it didn't for a few months), and then run 3dcoat from the distrobox image. It works, mostly. There are ways to make launchers to bypass entering a terminal and then entering the distrobox image and then launching 3dcoat but that's for another day.

In my case, scaling doesn't really work well, so tiny interface in a 4k monitor; and I forgot if the Wacom did actually work (I assume it didn't, but maybe now it's better). Since there were a few more things not ready yet, I confess to have given up, waiting for more mature, newer versions of 3DCoat.

That being said, and as annoying it is that releases take months, then a few quickly in a row, then crickets again for weeks... SERGYI did make several substantial changes that are not precisely minor to make 3DCoat work well in Linux going forward. It's clearly improving, although with serious hiccups here and there. The move to GTK3 was sadly done so late, that we're now about to ask a port to GTK4 with some urgency before the GTK3 port is really working fine. I think SERGYI will not like that very much, poor soul. We've talked about that in the past. :-)

Anyway, if you already knew all of this, sorry for the the intrusion. If not, and need further assistance testing with distrobox (it's really not difficult and it sort of works, yay!) ping me or some of the other Linux users around here. You seem to be determined to try it out. We should help you do just that if you need us.

Thanks for your past posts here, by the way. I couldn't agree more with you, as others have also stated. I'm also very pleased by the reaction of the people in charge here. It's good to see how well they take [well presented] criticism and suggestions alike. Good stuff.

Edited January 15 by Sorn

[SreckoM]

On both versions I am having issues with modal windows disappear, also when going into sculpt mode viewport disappears ... Same as it was with 28.02 version.

[SreckoM]

And @SERGYIwhy do not you go Flatpak route? Wouldn't that give you more control and way to target every distro? 

[SreckoM]

15 hours ago, Sorn said:

You may want to test 3DCoat Linux builds in a not outdated distribution (or old version of a distribution), and see that it doesn't work, really, to have a base reference. See the what, the how and the why, possibly, to 3DCoat not working in a modern Linux.

Then, you can try the Distrobox route. I haven't written a proper guide yet, was waiting for some things to improve first; anyway, there are step-by-step instructions around these forums, in the Linux section. Basically, one has to install distrobox, then an Ubuntu 20.04 (oh, dear!) image with Nvidia support to have hardware acceleration if one uses nVidia (--nvidia flag now works, it didn't for a few months), and then run 3dcoat from the distrobox image. It works, mostly. There are ways to make launchers to bypass entering a terminal and then entering the distrobox image and then launching 3dcoat but that's for another day.

In my case, scaling doesn't really work well, so tiny interface in a 4k monitor; and I forgot if the Wacom did actually work (I assume it didn't, but maybe now it's better). Since there were a few more things not ready yet, I confess to have given up, waiting for more mature, newer versions of 3DCoat.

That being said, and as annoying it is that releases take months, then a few quickly in a row, then crickets again for weeks... SERGYI did make several substantial changes that are not precisely minor to make 3DCoat work well in Linux going forward. It's clearly improving, although with serious hiccups here and there. The move to GTK3 was sadly done so late, that we're now about to ask a port to GTK4 with some urgency before the GTK3 port is really working fine. I think SERGYI will not like that very much, poor soul. We've talked about that in the past. :-)

Anyway, if you already knew all of this, sorry for the the intrusion. If not, and need further assistance testing with distrobox (it's really not difficult and it sort of works, yay!) ping me or some of the other Linux users around here. You seem to be determined to try it out. We should help you do just that if you need us.

Thanks for your past posts here, by the way. I couldn't agree more with you, as others have also stated. I'm also very pleased by the reaction of the people in charge here. It's good to see how well they take [well presented] criticism and suggestions alike. Good stuff.

This could be solved going Flatpak route. 

[SERGYI]

18 hours ago, Grakino said:

In Windows terms, it's the same as saying on my Windows 8 everything works fine, i don't know what you talking about. We already have Windows 11, Windows 12 coming soon, guys.

Based on a response from Gemini, Ubuntu 22.04 uses GTK3. Ubuntu 24.04 uses GTK4. What is your proposition? If I build "3DCoat 202x" under Ubuntu 22.04, it will still use GTK3. When I make it under Ubuntu 24.04, it will use GTK4 but will increase the version of standard libraries (particularly GLIBC). As a consequence, "3DCoat 202x" will not run under other distros because the required GLIBC version will be higher. Building "3DCoat 202x" under outdated Ubuntu 20.04 on purpose makes it compatible with a broader range of distros. Please make your counter-arguments here.

[SreckoM]

Yes this is result of long standing dependency hell with linux. Sergyi really can not do much here, what ever he builds up someone from other distro mighht have issue.  Thus Flatpak, Appimage or Snap.Distribute  as Flatpak and you will cover all distros with one build. Plus much more control about libraries that should be used etc.  Share it over Flathub and you will be only pro sculpting app shared to growing Linux community. 

[SERGYI]

18 hours ago, Sorn said:

You may want to test 3DCoat Linux builds in a not outdated distribution (or old version of a distribution), and see that it doesn't work, really, to have a base reference. See the what, the how and the why, possibly, to 3DCoat not working in a modern Linux.

Thanks for your comment. Technically, I can build "3DCoat 202x" under the latest Ubuntu 24.04 against GTK4. I cannot install the old Ubuntu 20.04 and the new Ubuntu 24.04 alongside. If I upgrade, all subsequent builds of "3DCoat 202x" will be made under Ubuntu 24.04 against GTK4. Also, the version of GLIBC will increase. Should I do that? Please provide your opinion on this matter.

[SERGYI]

2 hours ago, SreckoM said:

This could be solved going Flatpak route. 

I was thinking about Docker. But, asking Gemini, it seems Flatpack is better for desktop apps. What should I do: upgrade to Ubuntu 24.04 and build "3DCoat 202x" against GTK4 OR stay with Ubuntu 20.04 and incorporate Flatpack?

[SreckoM]

You can also build against GTK4 and still distribute as Flatpak and target every distro that has Flatpak installed., You will distribute GTK4 libraries within Flatpak. 

[Sorn]

59 minutes ago, SERGYI said:

Thanks for your comment. Technically, I can build "3DCoat 202x" under the latest Ubuntu 24.04 against GTK4. I cannot install the old Ubuntu 20.04 and the new Ubuntu 24.04 alongside. If I upgrade, all subsequent builds of "3DCoat 202x" will be made under Ubuntu 24.04 against GTK4. Also, the version of GLIBC will increase. Should I do that? Please provide your opinion on this matter.

At this point, I think going the AppImage or Flatpack wouldn't be the worst idea, albeit not being the preferred choice for almost nobody in the DCC software world. If it's the only way to make 3DCoat work, let's go for it. Right now, this is not working for many of us anyway.

The thing is, Linux is going to evolve, like other platforms. It's always going to be a moving target. When it's not this, it'll be that thing over there, and so on. So some work will always be needed to keep up with the times. Right now, though, we're behind the times, and in some aspects, significantly.

We can strive to make 3DCoat run on everything, maximise the amount of machines and systems it can be launched on. Or, we can NOT do that, explain what's supported and what's not, and stick with it. Here's one reasoning for the latter approach:

I work with my Linux machine. In order to use my relatively powerful hardware I need newer kernels that support it, and up to date drivers to extract the maximum from my machines. I can't afford to run outdated distributions that won't be supporting my hardware or limit what I can do with it. I switched from Ubuntu based distributions a long time ago precisely because of this. I can't afford to use older hardware with limited support and power to work.
How's working with obsolete hardware and drivers for how long with specialised software like 3DCoat? Who are we actually serving by being "the most compatible"? The ones that'll run out of ram, GPU power, CPU as soon as they attempt anything moderately ambitious? This is not a word processor, and most users need power, so they get that if and when they can.

That said, other professional and commercial software I use on Linux don't have all this issues, and they DO NOT rely on Flatpack and AppImage (for many reasons I won't get into now). Everybody seem to have figured out how to run a professional DCC software in Linux without relying on containers, or semi-containerised formats. I'd hope 3DCoat would do that too.

Linux communities manage to help each other "bridge" the "compatibility issues" most of the time, if dependencies are well stated and not overly absurd. So usually there's not really major issues installing and running in a modern machine with a current distribution (using current kernels/drivers) software like Houdini, Maya, Blender, DaVinci Resolve, Blackmagic Fusion, Plasticity 3D... and many more.
I know that in order to run DaVinci resolve in one of my machines, I have to make sure some dependencies are met and delete some files in a folder. That's it. It works fantastically well. I'd hope that would be the case for 3DCoat.

It seems to me 3DCoat runs fine, it's the desktop integration that fails all over the place. Tools are there, working fine. But window managing, file dialog... that can't be unsolvable.

Anyway, I hope I made some sense. I'd like to know I can use 3DCoat in a modern machine without worrying too much, like all other DCC professional software I use. If that's impossible, sure, use Flatpack. But there are reasons why nobody seriously uses that, outside of hobbyist environments.

I have been writing this while working, so I possibly made a mess of a post. I'll see at another time if I can condense what I meant and make it clear. Thanks for your patience and consideration.

Oh, one more thing: it's really important and appreciated that devs directly engage with the users of their software for feedback. You'll know best what to do, but it's truly appreciated.

Edited Thursday at 05:13 PM by Sorn

[Grakino]

@SERGYI I installed Ubuntu 20.04 just to test, your latest build. I made a quick look 3DCoat behave same as on my Mint 22. My table pressure didn't work, also painting behave weird. Give me couple days, i need more time to do more test, i will record a video for you, to make it clear and understandable.

About 3DCoat Linux future. I agree with @Sorn. I want to add a few words.

1. You don't have to be compatible in every distribution. You can be compatible with only one distribution, and that's ok. Many developers do that: Maya(redhat only), DaVicnci(Rocky only), Substance(Ubuntu only). I managed to run all of them on Debian, Mint, Ubuntu, Fedora. Yes it wasn't always smooth but i did )

With Maya it was a fun story, look at this, Autodesk says to me "man don't do that" but i did https://www.autodesk.com/support/technical/article/caas/tsarticles/ts/653FjR7SuamMJ5Y4v9XkXg.html

But what is important, you don't have to be outdated, you have to fit with this platform, distro which you chose. I managed to run your 2024.06 on Fedora, but i can't use in properly, not because you don't support it, but because it super old, modern Fedora just don't understand what is GTK2 , but Debian 12 understand what is it )

2. GTK4 or Flatpak? Really don't care . Here's my point.

If you choose to use Flatpak, I will say - great, now i can run 3DCoat in any distribution.

If you choose GTK4, i will say - great, 3DCoat is a modern 3D soft. But distribution which don't support gtk4 won't be able to run 3DCoat - It's their problem. If you make a 3DCoat on GTK4 i will find a distribution which can handle it, the reason is very simple - gtk3 is old. gtk4 - it's an actual version for a few years. The Linux distribution which don't support gtk4 is dead for me, that's all. Come on, you are not Linux user, if you don't jump from distribution to distribution .

If you decide to make GTK4 and it will work properly in Ubuntu 24.04, but it won't work in my any distro because it doesn't support gtk4, i swear I will not say anything bad about you. I will say Segryi did good job, Segryi made a good porting on modern technology, і взагалі Сергій красава, так тримати.   Goodbye my distro - your're too old now.

It doesn't important for me how you do that, GTK4, Flatpak, .deb package, .run script, you can even switch to Qt ), but what is important for me, it must work, it must support my hardware and not to be an old grandpa.

Edited Thursday at 06:32 PM by Grakino

[SreckoM]

  

Quote

 But there are reasons why nobody seriously uses that, outside of hobbyist environments.

Reason for not using it is mostly cause it is relatively new.  Other DCCs are doing it by not caring much will it work with latest or older distros. Like Maya, they do not even distribute anything but RPM. Good luck with average user who does not want to dribble with alien or asking for any kind of support. This is fundamental problem with Linux world. Ppl need to start thinking outside their preferences.  These things are stopping wider adoption of Linux in desktop world. Consequence of that is, that such small userbase, is not interesting for developers, way too much work for gain, and we are running in this circle for 20+ years. 3DCoat is probably feeling the same, there is one person working on this, cause there are maybe 10 of us on Linux. Every app, even Blender and Houdini will have issues with latest drivers, some issues not right visible some straight as crash. Also if Sergey targets GTK4 and latest Ubuntu (not using Flatpak), good luck with every studio around the world that uses Linux and always follow VFX platform guidelines.

With Flatpak you distribute or target everything you know works best with your app.  And most important thing is that you can do proper support. If Sergyi builds on latest ubuntu, he can not provide proper support for anything else, so that will shrink Linux userbase even more. At some point it will be more profitable to kill linux support entirely. Seen this too many times.  Not to talk about how every proprietary apps works 2x better on Windows or OSX exactly because of this. 

But at the end I also agree that I would like something that works. Right now only version that works for me on Ubuntu PopOs is version 24.06 from Feb 2024. 

Edited Thursday at 06:27 PM by SreckoM

[Grakino]

@SreckoM Yes, I understand your point, and you know - you're right. I can't deny anything. We have to thinks about regular user not only Linux enthusiasts i forgot about it for a minute. Also the advantage of flatpak is an additional marketplace flathub, why not. Imagine install 3DCoat, from terminal, that's sounds great for me. Also it can give you a bit more advertisements. Some Linux youtubers can make video about it "10 3DSoft  for linux you should try" =)

Edited Thursday at 06:59 PM by Grakino

[Sorn]

Sometimes it's not straight forward to access the system from a container (or containerised launcher, as it were). This means "connecting" different software can be tricky; for instance, bridging 3DCoat with Blender or other DCC software.

Using the bridge add-on for Plasticity 3D and Blender is fantastic. Works flawlessly. I don't know if that would be an issue here. If not, go for it!
I may be wrong, or things improved, I don't know. If different Flatpack or mix of native and Flatpack programs can "see" each other, then great!

As I said, at this point, I really don't care how they do it, frankly. I just want it to work and be on par with bug fixes and new tools available on the main builds.

And please, please, pretty please, please, make 3DCoat alert the user when a new version is available like in Windows. It's even more important in Linux, where we don't have builds for months and then out of nowhere a few in a row land. It's crazy having to refresh a forum page daily for months and still miss a build with crucial bug fixes because one just stopped looking into it with the morning coffee.  Please, please. Please.

Please.

 

But yes, what @SreckoM and @Grakino said, make it work already and let's everybody move on!

Edited Thursday at 07:39 PM by Sorn