-
Posts
246 -
Joined
-
Last visited
Sorn's Achievements
-
You could try with Bottles. https://usebottles.com/
-
Interesting. Did you manage to have hardware acceleration and Wacom working in 3DCoat in WINE? Is there a guide somewhere on how to proceed with that? Thanks in advance for any tips and info on this. It could be helpful until we have a proper working port to Linux. By the way, I love your add-ons for Blender. Happy customer here!
-
I do understand the frustration. And there's some history behind all of it, sure. And the people at Pilgway and us the users we've all had our fair share of joy and pains for years, now. And yet, they didn't fail on purpose, I assume. They also didn't just cancel Mac and Linux ports either. So, now what? Well, they are really trying, and improving; we can also see that. And some problems are yet to be solved. And us, the users, we can leave, stay, renew licenses or not. I myself seldom use this software any more (for now). But to discourage the improvement of the software or their efforts towards making it work serves no purpose and benefits nobody. It won't make you feel any better either. And we don't need to know if you stay or leave, really; it's your personal choice. I still want it to work well on Linux, and I won't use it until then for actual work. But I won't discourage them from trying if it's not working for me yet. I understand contacting them for a refund, asking CS for some clarification... but I wouldn't shame them publicly for no gain whatsoever. That's hardly ever the best way forward for anyone involved.
-
I can confirm in Arch it crashes on using the file dialog. To test it, I installed a fresh Endeavour OS (basically Arch with some script helpers and saner installer) with Cinnamon desktop (to rule out Gnome and GTK4 issues) on a spare SSD and yes, it launched fine, but on using the Save as... menu it crashes immediately. I could install any other distro/desktop if needed, but I think this is getting us nowhere. With the available knowledge, time and other resources, the sooner SERGYI manages to make a Flatpak the better, really. Put everything needed inside, and be done with it.
-
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!
-
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.
-
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.
-
Just to let others know, for users using distributions other than Ubuntu, 3DCoat-2024.28-02 is working fine in a distrobox ubuntu:latest image created; all visual glitches seem to be gone and file loads and saves also work fine. Speed seems OK too. Good stuff.
-
Hi, in case anyone wishes to try 3DCoat 2024.27.01 on an Ubuntu image created with distrobox inside an Arch variant distribution, here's a link of what I tried: If you have a better working solution please do chime in.
-
Installing Ubuntu though distrobox on my machines running variants of Arch have now an issue with nvidia drivers. It goes roughly this way: The Ubuntu image created with distrobox will try to use the host's nvidia drivers when we create it with the --nvidia flag (look above for the post with the command to install an Ubuntu image though distrobox: https://3dcoat.com/forum/index.php?/topic/29582-solved-3dcoat-crashing-when-trying-to-open-thunar-file-explorer-on-endevouros-arch-derivitive-linux-distro/&do=findComment&comment=192900 ). There's a mismatch between nvidia drivers installed on Arch variants and Ubuntu distributions (latest, whatever it is as of today). Latest nvidia drivers require a newer kernel than the one provided by Ubuntu, so the drivers on our host running Arch won't work on the Ubuntu created with an older kernel. For now I installed the Ubuntu image without the --nvidia flag, then installed inside the image the latest nvidia driver available to Ubuntu with apt and it seems to work. Now 3DCoat launches and it can open and save files (yay! ) although I can see the already mentioned visual glitches and have some interface scaling issues. There is indeed some good progress! I'm also not so sure it uses GPU acceleration, so I'll check whenever I have some time how to make sure 3DCoat launches in the Ubuntu container using the GPU if that is not the case. Please do chime in if you already solved it. Summary of steps I tried this time: distrobox create --name ubuntu-nvidia --image ubuntu:latest distrobox enter ubuntu-nvidia sudo apt update && sudo apt upgrade sudo apt install libcanberra-gtk-module nvidia-driver-550 Edit: Apparently there's a way for the image installed [the Ubuntu image] to get access and use its own GPU drivers properly [as opposed to the host's provided ones], but it's a tad more involved than to just install the GPU drivers inside the running [Ubuntu] image. If anyone has the knowledge or a step-by-step guide please do share it, it could potentially help many now and in the future. Meanwhile I'll get to it whenever I can scrap a few minutes here and there. Surely more improvements are being made to 3DCoat for Linux as we speak nonetheless. Good stuff. I'm eager to use 3DCoat again. Edit2: OK, so after the steps detailed above, then I enter the image created (didn't change the name used in the instructions posted by @veris trying to avoid any possible confusion, but the name ubuntu-nvidia can be whatever you want) and it stalls trying to set host's nvidia integration. Then I interrupt the action with ctrl+c (it cancels the command) and enter the image again. This second time it does work and we can run 3DCoat with GPU acceleration. There's a more polished way to achieve all this, sure, but meanwhile it really works, here. Steps after installation (see above), and making sure we're already in the 3DCoat unpacked directory: distrobox enter ubuntu-nvidia ctrl+c distrobox enter ubuntu-nvidia ./3dcoat Once I'll figure out if there's a more elegant way to proceed with installation and a proper way to export the binary so it can be launched directly from the host operation system and with a desktop launcher I'll update the guide I did for the whole installation. For now, al least here on my machines, it does work! Yay! If any of you already solved all the remaining bits please do share them here, since I have (really) limited time now. Thanks in advance.
-
On EndavourOS (Arch Linux variant), GNOME 46.5 and Wayland, after unpacking the 3DCoat-2024.27-01.tar.bz2 file and running ./3dcoat I get this: $>./3dcoat Exit code: 134 Gdk-Message: 18:00:01.039: Unable to load sb_up_arrow from the cursor theme Gdk-Message: 18:00:01.039: Unable to load circle from the cursor theme I tried changing the cursor theme but it says something very similar, but slightly different cursor theme error message. $>./3dcoat Exit code: 255 Gdk-Message: 18:06:29.629: Unable to load sb_up_arrow from the cursor theme Gdk-Message: 18:06:29.629: Unable to load tcross from the cursor theme free(): invalid pointer zsh: IOT instruction (core dumped) ./3dcoat 3DCoat just doesn't launch after that. Edit: I tried it in Gnome X11 and it launches successfully, but crashes on attempting to save the scene to a file.
-
Thanks @Carlosan. I wouldn't want to bother him directly to his e-mail inbox just for this, not being the question about the software functionality, bug, installation or feature request. Also others may welcome the answer he'd potentially give here.
-
So, how are we doing @SERGYI? Is there any progress to report?
-
It's possibly a change in GTK (your system now relying on GTK4). It's been a problem for quite some time for many with the exact same symptoms. You'd want to head here, where we're keeping track of the latest Linux developments (link to a relatively recent post from the 3DCoat Linux developer): Also, there's a temporary way to keep using 3DCoat until it's fixed: using distrobox, installing ubuntu-nvidia image, and launching 3DCoat from there. Link: