Sorn

OK then. Very good news! Thanks again for taking the time to explain it to us. It's really appreciated. Take care and happy coding.

Alright. Hopefully with the WSL implemented and working you'll be able to increase the cadence of the Linux builds. I don't think I have to make any mental gymnastics to understand why there might be a lot to consider for any number of reasons as to not buy a computer right now. By the way, if the matter is a question of availability or resources to procure one, would it be feasible to donate or send you one? Just an idea, but possibly doable. If this, or a similar arrangement could be made, please say so. In private if preferred, of course. You can message me and I'll send you my contact details. Thanks again, @SERGYI and the team.

@SERGYI Thanks for the explanation (and the build!!). It's very appreciated. Still, I didn't ask for a native Linux port of the application. You did offer it. And that's why I bought it in the first place. So I don't know what to say, here. Sincerely, is there any way we can help out with the Linux builds? I'll gladly help if that meant we could get parity with Windows builds, for sure. Truly. It's a bit inconvenient to have to wait long periods of time for a build with solved bugs that are already fixed (since there are available in other platforms (mostly Windows)). Those bug fixes are really helpful and not having them fixed in our software build affects our ability to work properly with our license of 3DCoat. If you will not have a machine dedicated to make those builds (I'm assuming you may have a very good reason for such apparently self imposed hindrance that escapes me) I understand that, therefore, it can be more difficult to produce new builds, yes. As stated before, I don't know how to help with that from my end. Please do tell if there's a way. Maybe WSL can finally work its magic and lets you code, compile and also have some time to rest! Maybe, then, a weekly build with the bugs fixed could do? I don't know if that'd be feasible. I imagine that while new tools are being developed, published as Beta, tested and refined, not having a machine to compile new builds daily or every few days can be more complicated for you. But certainly wouldn't hurt us to be able to also test those tools. And yet I would absolutely appreciate the bug squashing releases! They seem to appear mixed, though: new builds appear with bug fixes AND new tools or workflows implemented. Not sure how'd that work. Lately, you have managed to kill bugs at a really fast pace. The community seems engaged, reporting and testing. And that's a very good thing: the software is becoming way more stable, predictable and the users more confident: if something isn't working you fix it rather quickly! That's great! I only wish we wouldn't have to wait for months to get those bugs fixed. All that aside: In this monumentally difficult times in your country, asking for anything to you feels wrong. So I won't. I can, however, suggest or query if there's anything we can do to help improve your ability to produce builds at a cadence closer to the "main" one. That's it. I do, nonetheless, absolutely accept the situation as it is. And I can't imagine how do you manage to stay productive, innovating and fixing this fantastic software while keeping your sanity at the same time. I'm in awe. To reiterate, in synthesis, just in case: I'm NOT complaining. I accept how things are. Just expressing some concern and offering to help if that can be done. Just that. I'm grateful you are developing builds for Linux for us to enjoy. So there, thanks so much, for the software and for communicating openly the state of things around the development of your software. My best wishes to you, your team, family and friends.

Thanks for the 2022.43 Linux build! I was really waiting for that one!

Hi, here's hoping everyone is fine and safe. If at all possible, could we Linux users have a little love from the developers? It's been a while since our last hug.

@Rygaard I hope you are fine and you are just polishing the web, getting the digital stores ready, sorting out technical glitches and that kind of thing. If, on the other hand, it's your health that's at stake, here's hoping for a full and quick recovery. I'll be patiently waiting for all the good stuff along with many others as well, for sure. My best wishes to you!

I feel your... feeling. Latest Linux build available is still .34 so my keyboard has no F5 key anymore. Playing this refresh game has become a habit, part of my daily routine.

Fantastic news, @Rygaard! Thank you for the heads-up. I'll be waiting for the links.

Hi, Thanks for the updates! Fantastic news indeed! By the way, one thing I would recommend (and have been recommended to me before) is not to launch a product on a Friday. And not to launch it on a Weekend either, of course. And if possible, be rested for the launch. Make it possible. Really, be rested. Seriously. For realsies. Be rested. OK. There. If ready on Tuesday: take the day off, rest, leave everything ready and enjoy yourself doing something else. Sleep. Have fun. The reason may be obvious to some, but it's not uncommon to arrive exhausted to a launch date, having been pushing hard until the end: there, it's done!, we say. And it's only human to be mentally excited that the hard work is over and one will finally be able to show the work to the world. Launch the product. And expect to take a nap. Or the day off. Or feel a sense of relief, as the excitement wanes off... and then something goes wrong. Some parts of the world can't see it. Some credit cards won't accept payments from people whose name starts with an L or there's a gas leak in your neighbor's house and the fireman asks you to be there for some reason. It's hard to deal with a launch. And it's harder if it goes well! Lots more can happen if there's more traffic: more questions, more refunds, more e-mails of gratitude, comments on social networks, petitions, Nobel prize award rumours and talking... Be rested. Seriously. For real. Mate, come on, be rested. Also, to not miss on other people's excitement. Try to be there. Answer the first few days as much as possible on social networks, e-mail, customer service issues... There. You probably already know all this, but letting a day more pass can make such a big difference and I know it's difficult to wait for that last step. It is a step. The day before launch is rest day. Super good news, though!! Almost there! Thanks again, @Rygaard and sorry for the ramblings. I'm also excited apparently! PS: I'm not saying to brace for a disaster. Just sometimes things happen and if rested, they get solved and one moves on easily. The important bit is about being there, for the first days, to enjoy and comment with others the fruits of the hard work. That's it.

Thanks for the new Linux build. Yay!

Hi, @Rygaard Yes, I would make a playlist of the brush videos, and made it public, not private. It’s easier to find (even for customers) and it can serve as a promotion for the brush pack, and for the rest of the channel since some people will find those videos by search, and will look at the rest of the channel later. For the customers that buy the pack, it’s convenient to have the videos documenting the product in the same place where they bought it. I wouldn’t force them to search elsewhere for that. But they will eventually do a quick youtube peek once in a while anyway. I wouldn’t make that path difficult with unnecessary steps (like remembering a link to a private playlist). Current satisfied customers may recommend the brushes by pointing other potential customers to that list, and the rest of the tutorials on your channel. I wouldn’t put any obstacle to that scenario either. A 7zip (with multiple files if the size presumably warrants it to be) as a separate download from the brush pack in the store(s) would be ideal, I think. It can look something like this, as a series of download links (both Gumroad and ArtStation marketplaces allow multiple files to download per product): – Brush Pack.pack_extension – Brush_Video_Documentation.zip – Brush_Video_Documentation.001 – Brush_Video_Documentation.002 – Brush_Video_Documentation.003 – Read_Me.txt – Quick_Guide_To_Installation.pdf – License.pdf – Recommended_links.pdf – Notes_on_the_release.pdf – Thank_you_note.pdf It can also be made with straight zip files. As in Brush_Video_Documentation_1-5.zip, Brush_Video_Documentation_6-10.zip, etc... I think your choice of colours is spot on. Not too bright nor dark, so they can fit in different adjusted themes, and provide clear separation of different kinds of brush usages. Very good idea and choice of colours. Again, just my thoughts. You know what's best!

@Rygaard More thoughts about brushes and their videos: I would finish the brushes and their documentation (or videos) before embarking in making new ones. There will be time to update or add those after the launch. Forty-two is plenty to keep us busy for a few days, I assume. I think colouring the brush icons can be a very good idea. The criteria of the colour scheme should be explained, then, so it won’t be causing any confusion or generate too many customer questions afterwards. One thing I would do, though, is to put the colour coding of the icons behind the sphere of the brush, not on top of it as you showed before. As for the brush pack videos, I would make them short, as short as possible, and separate from each other. Not a long one explaining all or some of them. That long video can be made after the fact, just compiling them into one straight long demo video, if needed. But separate short and to the point videos will act as a guide, manual and reference. It can be zipped in one big or several big-ish files ready to download with the brush pack in the store(s). And even also put them on a playlist in your youtube channel and other sites. Or posted sequentially, or over time as a promotional reminders, in social media sites, one or a few at a time. You may re-use them, or some of them, if later on there’s new updates of your brush pack, or changes in 3DCoat make some of them obsolete but not others. Or use them to quickly answer questions, or feedback, to support your point, or intention. There's many potential uses for those and perhaps quite less for a big all-in-one video. The shorter, the better, as stated ad nauseam (sorry). Bits of them can then be used and combined, along with cuts from the long training for promotional purposes. If you can make an interesting edit of that, it could suffice. A promotional video has to be engaging, showing enough to make the targeted audience curious but it doesn’t need to include all the content. Long promotional videos have less impact than a few shorter ones, I think. Longer, extended videos about the brushes could in fact be made at a later point in time, as a bonus. Or (if) when some more are added to the pack. Or as a reminder, after a while, of the value of the brushes once the novelty has passed. Or for those that were not that inspired the first time around. As always, that's my opinion and you know best what's needed, what's not, why and when. Just engaging in the discussion to bounce some ideas around. You'll do what's best, for sure.

@Rygaard Hi, I have a few thoughts. But I'll release them in chunks, as you do. First, if I may, the brushes videos: As a general "rule", in each sculpt session we use just a few brushes for most of the work. We then use a few more, depending on the project, picked from a wide set of additional brushes. All those brush collections we all love are, generally, specifically designed brushes tailored to save time or effort in particular situations we find ourselves in during our work. So, depending on different scenarios, or the task at hand, we again pick just a few from a larger set of brushes. So for any job given, we tend to use a relatively small number of brushes. The bigger amount of brushes available are mostly there to guarantee that when the time comes, that selection can be made. Seldom is the case when we use all of them at once in a project. That is why I’d suggest to make videos of the brushes in three stages: 1- Show how the brush behaves. Preferably on the simplest scene possible. 2- Show its purpose: What is the intended usage. 3- Show one quick use case. Illustrate it on a mesh when its use is seen as a clear advantage. That can be made short. No need for a long tutorial. That makes the video useful beyond the presentation of the brush and serves as a reference afterwards. I’d avoid any explanation not directly concerned to the three points above. Any deviation or extra information belongs to some other video, like workflow or sculpting tutorial. Having those videos serves two functions: understanding what the brush is and making the selection of that brush in a sculpting session clear. In my opinion, that would make the whole pack of brushes actually used, cherished even. Remember, really seasoned users won't probably need those videos, but then again they probably make their own brushes when the need is apparent to them. For beginners and intermediate users, having a clear sense of when to use them makes the set really useful and helps the sculptors enormously. There. That's my take. When I find the time I'll drop some other ramblings of mine. Thanks again for your efforts and open communication, Rygaard.

It's good to know things are moving forward. Thanks for the update, Rygaard. Just don't forget to rest from time to time. We still need you alive and sound.

Hi, upon reading the first post by Carlosan in this thread, I find myself a tad confused. While I interpreted the thread topic "3DCoat features you would like to see resolved" as things to be finished, polished or make fully functional, Carlosan states "(...) existing features that you would like to see removed." Which I take as things that are maybe obsolete, superseded by new functionality or already improved somewhere else, as if one would like to suggest ways to avoid cluttering or malfunction in the software. Maybe the confusion is in my interpretation. It's been known to happen before, astonishingly! In any case, please feel free to move my posts to a more suitable thread if this one is not the appropriate or contradicts the spirit of the purpose of the thread. Apologies if my possible misinterpretation created any inconvenience.

Hi, I'd very much like to be able to change the UI font in in Theme Preferences in the Linux builds. As of build 2022.25 it doesn't work. [If anyone has it working please do tell how.] While the 3DCoat UI is fixed, can we edit some script to achieve that? Thanks in advance.

@mentalthink Did you solve it? It's been a while, but I just wanted to try Instant Meshes retopo in Linux and no, it's not there. I have an executable on Linux working fine, but it would be nice to have it integrated in 3DCoat. Sometimes it's the right algorithm, depending on the mesh.

Fantastic news, Rygaard!

Yay! 3DCoat 2022.25 build for Linux available! Thank you so much! :-)

Thanks for the new Linux build (2022.24)! If at all possible, in the understanding that your situation is far from ideal, I'd also love to test the autoretopo improvements in the new beta 2022.25. It could really benefit our workflow in such a crucial step. Thanks in advance and please stay safe. I'm in awe seeing you manage to stay focused in such difficult times and plowing ahead with the development of this software.

Thanks. Alright so I have been trying to use it but it doesn't work for me, at all. Using the most recent 3.2 Blender build. Could it be because the 3DCoat Linux build is still 2022.16?

I'm confused as well. Which of the different versions and variants of the Blender Applink are we supposed to use, then? And where are we supposed to get it? Thanks for any clarification on the matter.

From the 2022.22 release notes: "- Fixed problem when exporting custom tools using the "Create extension" leads to losing the user-assigned icon of the tool." So the icons disappearing seems to be solved.

You may also consider the ArtStation marketplace, along Gumroad, to sell and promote the brushes. I wouldn't put all eggs in just one basket. It could unnecessarily limit the reach and visibility of your products.

Having videos explaining how the brushes work and their intended purpose will make them way more useful to the community. That's a very good idea. Seasoned 3DCoat users may be more inclined to make and adjust their own brushes, as you do, and probably won't be needing much explanation about the properties of a new or tweaked brush to begin with. On the other hand, people relying on brush sets from others probably won't mind being told the purpose and characteristics of the brushes in order to take advantage of them and effectively progress as 3DCoat users. I assume you are already in contact with the fine folks at Pilgway but, if you aren't, it might be a good idea to contact them to solve the vanishing brush icons mystery. Thanks for the updates on your progress.