Search the Community
Showing results for tags 'Linux'.
-
Hi, here's a list of steps to set-up 3DCoat for Linux in a workstation for a single local user. It may be useful to some, and as a reference to me. Download the latest Linux build (obviously) As of today, we can do this by going to https://pilgway.com/~sergyi/links-Linux.html Alternatively, we can download the last stable build in our ACCOUNT profile page at https://pilgway.com Unpack the file and place the resulting folder wherever we find it most appropriate. For the purpose of this list, I'd say I downloaded the file 3DCoat-2023.37.tar.bz2 in my downloads folder (/home/USERNAME/Downloads) In my file browser, I then extracted the contents of the file with right-click>'Extract Here' over the downloaded file. We can do that in a terminal or with a similar command in another file browser (using Gnome in this instance, with Files file browser) if we wish. It's quite a big file, it may take a little while to extract depending on our computer system. I finally get a folder called 3DCoat-2023.37 in my downloads folder (it's the folder extracted from the downloaded file, containing all files 3DCoat needs to start running). Rename the folder to 3DCoat-2023 (or whatever name we find practical, really, but I'll stick to that name in this little how-to). Move the folder 3DCoat-2023 to its final destination place if we wish, now. I've moved it to /home/USERNAME/Programs in my workstation (this is really not necessary, but we'll need to remember the folder location anyway in an upcoming configuration step whether we move it or not, mind you). Create a text file called 3DCoat.sh in our home folder (/home/USERNAME/). (It can be anywhere, in fact, we just must remember where we place it for a future step). The text file should contain just two lines of text: cd /home/USERNAME/Programs/3DCoat-2023 ./3dcoat-Ubuntu22.04 This is the file that will actually run 3DCoat in our system: It goes to where the program executable is and runs it. Remember to change USERNAME in the lines above to our actual user name. (Since 2023 came about, 3DCoat has two versions for Linux: 3dcoat-Ubuntu22.04 and 3dcoat-Ubuntu20.04. In the example above I used the more recent one, but it can be changed by typing 3dcoat-Ubuntu20.04 instead in the text file if there are issues running 3DCoat in your machine to see if that helps.) Since this text file is meant to run as a script, a command, we must tell the system we authorise the text file to run as a program instead of treating it as an ordinary text file. We do it by right clicking the text file and in Properties tick "Allow executing file as program" in Permissions tab. Alternatively, with a terminal open in the directory (folder) where the file is, we type: sudo chmod +x 3DCoat.sh Create a .desktop file in /home/USERNAME/.local/share/applications called 3DCoat.desktop We can do it by using any text editor. A .desktop file is a Gnome Desktop Environment launcher for programs. Since 3DCoat will not be doing it on its own, we'll do it ourselves to have a nice way to run the program, with an icon, in our user's Desktop. The text file lines will be: [Desktop Entry] Encoding=UTF-8 Version=1.0 Type=Application Terminal=true Exec=/home/USERNAME/3DCoat.sh Name=3DCoat Icon=/home/USERNAME/Programs/3DCoat-2023/data/Icon/3DCoat.png Categories=Graphics;3DGraphics; StartupWMClass=3dcoat We must change USERNAME the above text lines to match our actual user name. Also, make sure that the icon folder description is correct too (if we placed our 3DCoat unpacked folder somewhere else, now is the time to edit that line to fit our folder structure). If, for some reason, we want 3DCoat to run without any output on a Terminal, we can change the line Terminal=true to Terminal=false in the text file 3DCoat.desktop The added StartupWMClass=3dcoat makes sure that when using a Dock panel in Gnome it won't duplicate visible icons when running 3DCoat (otherwise 3DCoat will appear as an additional icon in the dock when running, alongside the icon to launch it) We can create this text file anywhere and then move it to /home/USERNAME/.local/share/applications afterwards. If we can't find the folder .local we can hit CTRL+h in our home folder file navigator window and it will show it, with other folders starting with a dot. Linux uses a dot at the beginning of a folder (or file) name to mark it as "hidden." Those are mostly configuration folders (and files) that a user hardly ever needs to see or touch manually. Hitting the shortcut CTRL+h once more will let all configuration folders hidden again; if we wish to tidy up the home folder appearance, that is. Restart the desktop or log out. Most times, after creating a desktop application launcher, we must "refresh" the desktop environment to make it available. We can do it like this: Reboot the system (a tad drastic but it will work for sure.) Log out. Then log in again. That restarts the desktop for the user. Press ALT+F2 hotkey shortcut and type r (just the letter R) and Return if a prompt appears. This sends the command "restart" to our desktop environment in most Linux distributions using Gnome. Run 3DCoat: Now we press the Super key (in many keyboards that key has a Microsoft Windows logo printed on it) and find the 3DCoat icon. We can just type it and it should show up. (Sometimes, depending on our Linux distribution, we may have to press SuperKey(the MS Windows logo one)+A or SuperKey+S to get to all the icons of the software installed). We can launch 3DCoat from here or pin it to a dock if we want the launching icon in the dock (if we use one) for convenience. Correct benign error messages appearing in the Terminal: As of today (version 2023.37 of 3DCoat for Linux) there are some png files' icc profiles in the 3DCoat folders that prompt a warning in an otherwise useful terminal output. They look like a lot, or many, "libpng warning: iCCP: known incorrect sRGB profile" messages. We can fix it by doing this: Open a terminal and go to where we placed the 3DCoat unpacked folder. (In my case, to /home/USERNAME/Programs/3DCoat-2023) and execute a command that will find any png file in any directory (folder) inside our 3DCoat folder and fix it. cd /home/USERNAME/Programs/3DCoat-2023 find . -type f -name '*.png' -exec mogrify \{\} \; Next time we run 3DCoat it shouldn't complain about those sRGB profiles. Remember to change USERNAME in the lines above to our actual user name. Also, if the path (where the folder containing 3DCoat) is different, adjust it accordingly too. When a new build of 3DCoat is published, we can download the file and extract it over the current 3DCoat folder in /home/USERNAME/Programs/3DCoat-2023 (or wherever we placed it before). I just delete the folder and place the new one, renamed to just 3DCoat-2023 where the old was. In this way, I don't have to change any other file in the system, nor risking any old files that stays there as a leftover causing any trouble. Just to be practical and safe. If we don't want to rename the folder, and leave it as 3DCoat-2023.56 (as an example of a possible decompressed new build folder), or move the folder where the old one unpacked was, just remember to change the path in the 3DCoat.desktop and 3DCoat.sh text files with the new one. We can also repeat Step 9 for the new updated 3DCoat version. Licensing our 3DCoat build: I omitted the licensing prompt that appears the first time we run 3DCoat. It will only be asked the fist time we run 3DCoat with our user or until we actually load the license. I just load the license downloaded from my account when prompted and that's it. We will not have to do it again after the first time, nor when a new version is installed like we did here, until it expires and we need to load a new one. 3DCoat creates some folders for us, with our user's preferences and settings in our user's Documents folder. Here, we've seen how to install the program in our user's Workstation. The configuration folders are left untouched. That's it for now. Happy 3DCoating!
-
I just installed 3dcoat textura on my Linux system. Trying to import a mesh closes the system or opening a file or doing almost anything
-
BUILD: 3D Coat 2023.17 OS: Arch Linux, Kernel 6.3.9-zen, KDE Plasma 5.27.6 HARDWARE: AMD Ryzen 5800x, AMD Radeon RX 6700 XT, Samsung Evo 970, 32gb ddr4 RAM BUG DESCRIPTION: When I attempt to open an external image file (aka not included with 3D Coat build) I see no image files in the directory they are located. After a few seconds, 3D Coat crashes immediately with no pop-ups. STEPS TO REPRODUCE: Download 3D Coat 2023.17 for Linux Unpack 3D Coat download Double click on 3D Coat executable file Load object for per-pixel painting Open or import an image file that isn't included within the 3D Coat build (i.e. textures and previews) Navigate to the directory of the image file to open Wait a few seconds Log copy.txt
-
Hi, I see that 3d coat 2021 will work with Linux Ubuntu, but I was also wondering if it would also be supported on RHel6 and RHel7? Thanks!
-
Hello there, I was wondering if the new Textura program supports the Blender Applink plugin. I have tried but failed to make it work.
-
As far as I know, 3DC has Linux support. I wonder why it's not available on Steam? The result is that I can't install 3DC on my Ubuntu, which is rather sad =(
-
3D coat is throwing an error when attempting to save a project. (<unknown>:8910): Gtk-WARNING **: Failed to read filechooser settings from "/home/megavotch/.config/gtk-2.0/gtkfilechooser.ini": Too many open files I'm able to continue working. And 3dcoat seems stable. However not being able to save is a bit of a problem. Please help. Votch Levi
-
It seems that every time I start 3D-Coat on my Arch box after every few runs I get a message prompting me for my key again. It's something along the lines of, "Your system has changed significantly since the last time 3D-Coat has run. Please enter your license information again." So I put my license information in again, and 3D-Coat closes and takes me to the registration verification page, but when I open 3D-Coat again it says that I'm running a demo, and in a few more runs it asks me for my license again. I'm running 3D-Coat 4.0.04B 64-bit, without Cuda, on a fully-updated Arch linux 64-bit system. I installed the beta version before I installed the stable version. Does anyone have any ideas for workarounds or some diagnosis as to what the problem might be?
-
BUILD: v4.00.BETA9C (GL64), nonCUDA OS: Linux Ubuntu 12.04 (precise) 64bit, kernel 3.2.0-35.generic, Gnome 3.4.2 HARDWARE & DRIVER: nVidia GeForce 6600 GT, nVidia driver version 295.40 BUG DESCRIPTION: The shaders in Voxel room are not showing in the pallete. It is probably related with the problem causing the models made in the stable version of 3D-Coat (3.7.18F) and opened or merged into the Beta version being without a shader (not visible in Smooth Shade Views), but only in case when any shader got applied in the stable version. When no shader change has been made in stable version, the object appears in Beta, but still without apperance of the shader (and still without Shaders in pallete in voxel room). Curious thing is, that if I save from stable version a file with two objects and load it into Beta, they are displayed (although without apperance of the shader) as long as one of them still has no any shader applied. When both of them has a shader applied (even back to Default shader), they are not dispayed at all in Beta using Smooth Shade Views (in Voxel room). Even though they are still correctly visible in Relief Only, Flat Shade and Specular Only View. In Paint and Retopo rooms the affected objects are rendered with a lot of artefacts (when a voxel object) or as semi-transparent dark objects without any shading when the object has a paint on it (when a suface object). I hope I described it comprehensively. I'm available for any further tests or to make more in-detail description of the issue. Thanks! STEPS TO REPRODUCE: 1. Launch Linux version 3.7.18F (GL64) and make an object in Voxel room and apply any Shader to it. 2. Launch Linux version 4.00.BETA9C (GL64), notice lack of shaders in Shaders pallete. Load the file from step 1. 3. See the object in different rooms and in different views.
-
Having to re-register all the time
Drocket posted a topic in SOS! If you need urgent help for 3DCoat
Hi, I am running 3DCoat 3.08B on Arch Linux x64. It has mostly been okay apart from the odd crash here and there, but today I will start 3DCoat and find I am running in demo mode (so I cannot export textures etc), I got prompted a couple of times during the day to register at which point it would work again for a while. Other times shutting 3DCoat down and relaunching it again after a short period would solve the problem but it is a real pain because I don't notice it immediately and so do some work and come to export the texture to find I can't. Any one else had a similar problem? Thanks, Andrew.