Przemas

I wonder - is it possible to add presets to quick access menu? That was one of my main gripes with 3dc - I wasn't a fan of default settings for previous brush engine (haven't tested the new one so can't tell much about it), some of the presets were IMO better, but at the same time I didn't use them much as those were "hidden" in separate menu.

Super excited by the mould tool. Will take me a while before I'll be able to test it (as my main workstation is Linux only), but if it works as it should this will be a game changer. Had a chance to take a peek at new version - I was pleasantly surprised to see that default vp settings in sculpt room are better than before, better suited for sculpting. Not a fan of new icons and the interface still looks crowded and a tad messy. But I'm extremely happy to see that UI is much more customizable now - definitely a good direction and when final release is out I'll definitely spend some time working on my own "rooms". In general this quick peek I had was quite positive - didn't encounter any issues I got while using latest v4 builds.

the trick is to understand how voxels work (v next to layer name). It is a 3d grid with uniformly sized "cells". So to get the finest quality you need to crank up voxel density prior to voxelizing your mesh object. When it voxel mode fill all air pocket and other things that can cause issues, then turn your model into mesh again (you should get "s" next to layer name) then decimate to reasonable value. There's no single "correct" value - all depends on model scale and what your machine (3d printer / mill etc) can handle. You should aim to get as few polygons as possible - but enough to retain all the features you need. For me voxels are one of the main reasons I have 3D Coat in my arsenal. It allows me to fix files that would be a major pita otherwise.

Mihu, I guess that's to be expected - it seems we're getting quite a bit of new features and features rewrite / optimizations (which probably is one of the reasons Linux builds got suspended) and that's BETA thread after all . But totally agree that at one point I'd love to see bug fixes and workflow improvements.

as others I'm looking forward for the updated Linux build - some of the features (like improved booleans) would come in handy in my workflow. If you can top it off with 3dConnexion support all the more awesome.

any updates on getting Linux version up to speed? Would love to try those improvements - especially with booleans. Also I think that ability to set up data folders via menu entry is nice touch - save a bit of hassle in form of settings up env variables.

Thx for the reply Sergyi . Thumbs up for keeping Linux builds going. I second the sentiment of trying to build under Centos 7 (7.5) - in my workshop we use "enterprise" distro as well, and those tend to have glibc that is not as "fresh" as the one in recently released Ubuntu.

not my intention pbowmar - I'm just trying to point to a solution that at the very least will please SOME users, rather than relying on one that won't please the ones you're talking about (if WINE is ok - I still fail to see why appimages / flatpaks that would bundle wine and 3dc would be a bad choice, studios would still have an option to do WINE stuff manually) and would be a hassle for the rest . As said I have no clue how much of a percentage of total 3DC sales studios that need to follow AMPAS make. P.S. Got any link to AMPAS certification standards? Curious about those... @ajz3d I'm not saying WINE is ok - check my post. I'd definitely prefer good native version. But as members of Pilgway team mentioned Linux builds have been dropped for the time being and direct us to use WINE I'm trying to make the best of the situation.

... yeah, because WINE will , c'mon... But apart from that (WINE not a solution if we take your strict standards), but what's the problem with Appimages? They can be sandboxed etc. If you go Flatpak way you get even more security - and some extra benefits when it comes to "unbundling" your app from the libraries (but with a price - you need to get into its architecture and from what I hear harder to set up). Both solutions IMO way better that asking us to set up WINE. Side note - I run a small workshop and wouldn't have any issues running Appimage / Flatpak. My guess is for huge chunk of users it wouldn't be a problem as well (don't know sales data so it is wild guess). If it is a problem for a given studio... simply don't use it... Go manual WINE etc route we're directed towards at this point of time.

ouch... so if it is running better under Wine my suggestion is to package 3DCoat+preconfigured WINE as an Appimage. This way we'll get well performing application that will run easily on almost any modern distro (with Appimage / Flatpaks you can bundle all required libs along and those will get used instead of system ones). https://appimage.org/ On top of that it will make it easy to handle desktop integration (shortcuts, icons and so on).

any chance for the Linux build to get an update?

on Linux with Gnome 3.26.2 and Nvidia 410.78 (GTX 980) realtime render is broken. Does not refresh correctly and makes other windows stuck (for example if you play a video in your web browser you don't see the actual progress of the video, but you can hear audio working normally - as soon as you stop realtime preview the "state" catches up). Tried on Xfce and there it works as it should.

any chance to see updates to the Linux builds?

sorry for not getting back sooner. On my end I didn't see any bugs in the log. And here's the interesting part - after trying to make it work for an hour or so I gave up and removed the applink. To my surprise when I launched 3DC a bit later it started with a mesh I've wanted to transfer via applink. So it seems I might have given up too early - I'll try to make it work again in a near future. It would come in handy as I've started using 3DC a bit more recently and a way to quickly move models between 3DC and Modo would come in handy. In a future I hope that Foundry will open up a method they use for Unreal a bit and also hope 3DC would be able to use such option - of course if it will mean we'll get transfers from app to an app faster and more reliable .

is there a known back version without this regression? Tried 4.8.18 and I'm getting the same problem. It can be workaround by duplicating the layer (duplicated layer work for a time, then you need to duplicate them again), but I'll gladly fall back.

thank you Carlosan, that's it . I'm struggling with one bug though - in both voxel and surface mode sometimes unhidden part of the object is getting damaged (sort of like surface has been offset a tad) . It does not happen every time - but makes me super careful when dealing with the vox/srf hide.

I'm trying to use window (rectangle) selection with surface hide. The problem I have with it is that only front facing items get hidden - I'd like to include backfaces as well. Is it possible?

it's not doing anything on my end too . I'm on 12.1v1 (Linux version). Clicking buttons does nothing except a minor blink of the menu. I've set 3d Coat path and exchange folder path. Is there a way to change "User docs path" , "Modo project dir" and "Modo 3D Coat dir"? I'd like to use my own as those do not take into account locales (so I'm getting Documents directory, while in my locale it should be Dokumenty instead).

I'm wondering whether 3DCoat Printing has STL file repair functionality similar to Netfabb or Magics? The dongle for my license of Netfabb is failing and I've started researching my options. It looks a tad grim - both Netfabb or Magics are available now as regular products (subscription only) and there are almost no alternatives. The only one I found is LimitState:FIX. But it seems extremely limited compared to Netfabb for example (lack of booleans , arranging on build platform etc). Would love to see 3DC-P as an alternative, as I'm already using full 3DC for file fixing in very tricky situations. It would have to mimick a tad workflow found in Netfabb / Magics though (STL repair room?) which does what is says - concentrates on fixing and arranging the models in a very agnostic way (at first look it seems 3DC-P is closer to Cura etc and aims FDM printing - and for example in my workshop we don't use FDM at all as the quality is not good enough).

I'm seeing some weird rotation added to items exported from 3DC (checked on STL and FBX export). Here's a sample - the one that is selected is original one, the other one is item exported from 3DC (did voxelization, fill , back to mesh, decimation and export to STL there).

I got "out of memory" error while loading huge FBX as soon as memory usage in system monitor reaches around 9GB (I have way more in my PC). Running 3D Coat 4.8.14 on Linux.

thx guys, in the end I got it working. But this part of the workflow makes no sense to me - I don't want to bake anything until I got all my UVs clean and sorted out in the uv room.

I'm trying to use 3DCoat to render turntables and I'm hitting some annoying limitations. First of all - how do you set rotation center? Is it fixed at world/item center? There's no visual cue. Secondly - output path. When I set 3DC to saving image sequence I can't specify folder outside "RenderedImages" folder (also can't specify naming scheme pattern). Pretty annoying. Is there any way around that?

dammit, I must have hit some weird bug. I don't believe it should behave this way. I see uv sets in retopo room. When I go to uv room they are not there. Clicked add uv set... and 3DC crashed.

Can anyone hel me out how the heck I apply the retopoed (and uved mesh) so it is visible in uv and paint rooms? So what I did is to load a hi res mesh for sculpting - I see it in vox tree in the sculpt room. Then I clicked file -> import -> import retopo mesh . I've chosen a previously retopoed (and uved mesh) from a separate file. It loaded and it switched me to retopo room. I hit apply and I see the low res in the retopo toom (and in retopo objects I see it as a layer named "uved"). But when I switch to uv or paint room I don't see it. What am I missing / doing wrong? I find it extremely counter intuitive.