Is Steady Stroke turned OFF ?

Desktop 2025-01-17 21-48-30.mp4   2024.32 broke voxel brushes  

Does anyone know why this is happening? I am sculpting the box. If I use the mouse it works fine. If I use a stylus, my stylus pointer is at the corner of the box where it should be, but as soon as I start drawing, a black line appears moving the sculpting cursor a few inches away from where it should be. So now, that circle is digging into the face of the box instead of sculpting the edges. As soon as I lift the stylus, the cursor jumps back to where it should be. Any ideas what is going on?? Thanks

Hi Oleg, This happens using the tablet pen and also the mouse. As you can see, it is marked to store practically all options, including symmetry.   symmetry_problem_3dcoat2024.mov   When I click on any brush or tool in the left panel, the symmetry is maintained. But every time I click on the preset (using mouse or pen tablet), the symmetry is immediately deactivated.  

Bless you)

Hi Try switching to restore default text size on Edit > Preferences > Themes

When i switching full screen mod all interface elements get mixed up and break. 

I checked, the tablet has nothing to do with it. Is the symmetry saved in the preset settings?

Okay, so as I refered to Anton Tenitsky as being the golden standard of how 3DCoat is taught/demoed in a professional way, today we got a new feature video about infinite move. . .which is 6 minutes long. Six minutes for a feature that can be demonstrated effectively even with examples in 30-40 seconds. There needs to be more pro teachers and pro artists who represent 3DCoat. Even in bite sized videos. 

Hello! Does this only happen when using a tablet? I tried my presets with symmetry saved and it works fine with a mouse.

Please, could someone tell me if the tablet's pen sensitivity is working properly? Here, when I make brush strokes in sequence, it's as if one brush stroke wasn't working. Example: One brush stroke appears, the next one doesn't, then it appears normally and then it doesn't... -------------------------- I just tested it in Blender... and the brush strokes are normal... there are no errors in the sequence... I closed 3DCoat, opened it again to test... and the problem is happening of not making the brush strokes correctly in sequence... | one brush stroke appears normally, but the next one doesn't, and so on... in the brush stroke sequence. ----------------------- NEW TEST:  - I went back to version 31 to test if the 2 problems I mentioned exist. To recap: 1) Brush strokes are not working properly (one stroke works and the other doesn't). 2) Automatic deactivation of symmetry when clicking on a preset. Therefore, the result is that the same problems that I reported about version 32 are also occurring in version 31. thank you

Another thing I forgot to mention about using the "symmetrical copy" button is that sometimes, as soon as you press the command, 3DCoat closes immediately. Solution: Always save! Or, in the preferences: - Let the "auto save" feature enabled (I had disabled it a long time ago). But now, I've set it to save 2 copies (Autosave depth history) in sequence every 10 minutes (autosave time)...  If 3DCoat continues to close like this, I'll change the time to every 5 minutes or 3 or less...  

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!

@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" =)

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. 

@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.

Infinite MoveView the full article

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.