Jump to content
3DCoat Forums

Rygaard

Contributor
  • Posts

    654
  • Joined

  • Last visited

4 Followers

Contact Methods

Profile Information

  • Gender
    Male
  • Interests
    making of, action figures, digital sculpting, courses, 3d tutorials, 3d tips, 3dcoat

Recent Profile Visitors

9,304 profile views

Rygaard's Achievements

Apprentice

Apprentice (4/11)

  • Great Support Rare
  • Great Content Rare

Recent Badges

327

Reputation

  1. Thank you very much for subscribing to the channel. This will actually help strengthen the channel. At the same time, other people who would like to learn will have the opportunity to discover the channel.
  2. Hi everyone! All the menus at the top of the 3DCoat interface can be changed however you want and imagine. Customization of the menus at the top of the interface can be done by the users themselves in an advanced and even complex way depending on their objectives through the scripts (Edit the current room settings button). Below are some examples of what can be done in relation to customizing the menus at the top of the interface. Currently, there are 2 sides to using scripts for customization in 3DCoat. Using scripts will give you great powers in customization, but on the other hand... here is a responsibility that the user will always have to update on their own any changes or new features that are added in the future by the developers. --- Summarizing the use of scripts: 1- Positive side: Many advanced and complex customizations can be made. 2- Not so good side: Users on their own will always have to manually update custom menus if they enable the use of scripts because the program will not update the menus if there are additions or changes to functionality. --> And perhaps a "small detail", users will have to deal with programming to make customizations, so they must have knowledge of what they are doing to not explode 3DCoat (joking). By the way... If people are interested in doing these advanced (complex) customizations, but don't want to blow up 3DCoat (joking again), then... I'll help with that! Because I created an incredible free course that is available on YouTube, in which I explain everything in detail from the basics to the more complex things (and more secrets that I discovered and share with everyone). If the free course I created helps you... I would like to ask you to subscribe to the channel and also Like the videos so that the course can reach other people (and also help them) because of the YouTube algorithm. YouTube channel and course link: https://www.youtube.com/channel/UC9OKFOOes9bNZrwMgQb62Qg Thank you very much.
  3. @digman Yes definitely! I completely agree with you! All opinions and healthy and respectful discussions are welcome! By the way, I just created a private playlist (youtube) and it includes the 3DCoat UI suggestions video. The link is: https://youtu.be/tNhuAmu-gUw Thank you very much!
  4. Thank you for your interest! On the YouTube channel, I had to configure a few things. I created a private playlist and included the video about 3DCoat UI suggestions in it. If you can't see it, let me know... The video link is: https://youtu.be/tNhuAmu-gUw
  5. I promise I won't say anything else about UI here because this topic is related to something else. It's true, everyone has an opinion and that's amazing! I completely respect any opinion! Plurality is important to arrive at something that everyone can benefit from! But....I hope @Oleg_Shapo doesn't mind me sharing with everyone what I told him about the UI suggestions: " My main objective was to do something (from my own experience using 3DCoat) in which new users who have never used the program, and of course also users who already use 3DCoat, can get a good read of the program on their first contact. This means that with a cleaner interface, in which the functionalities are not cluttered in the same place (this causes confusion and even interface elements become cut off or without visibility), but rather organized or grouped into something that does sense to the user, this would result in a more user-friendly and easy-to-use interface. Apart from the fact that all the things suggested would actually be important features that would incredibly help the user's workflow within the program, and at the same time the user would do the work they needed to do faster. Therefore, the main objectives of this suggested UI was exclusively to make the interface: 1) Cleaner (visual), 2) Completely organized aimed at improving the users' workflow through what was suggested (more user-friendly interface) and... 3) With many customization options. " In the end.... It's all based on work > flow and easy to use. I think we are speaking in different languages, but with the same objective.
  6. I appreciate your attention to me! I agree....It's true! Sorry about that! I understand that there are many suggestions, but I sincerely hope that these can help in some way to improve 3DCoat even further. Because that is my true intention. Speaking of topics... It's been a while since I created a topic related to the 3DCoat UI, in which I try to present and explain suggestions aimed at the interface. There I try to explain the reason for each suggestion and what they would provide within the program in relation to usability.
  7. Hi @Oleg_Shapo , thank you! To be honest, I didn't really focus on whether the interface would look good (But I think it's not that bad!). I made this UI look quickly without any worries... Certainly, knowing which UI elements could be used and with the correct polish in everything... So yes, having as one of the objectives of what the interface would actually look like, I think we would have as a result an interface that would become very good. My main objective was to do something (from my own experience using 3DCoat) in which new users who have never used the program, and of course also users who already use 3DCoat, can get a good read of the program on their first contact. This means that with a cleaner interface, in which the functionalities are not cluttered in the same place (this causes confusion and even interface elements become cut off or without visibility), but rather organized or grouped into something that does sense to the user, this would result in a more user-friendly and easy-to-use interface. Apart from the fact that all the things suggested would actually be important features that would incredibly help the user's workflow within the program, and at the same time the user would do the work they needed to do faster. Therefore, the main objectives of this suggested UI was exclusively to make the interface: 1) Cleaner (visual), 2) Completely organized aimed at improving the users' workflow through what was suggested (more user-friendly interface) and... 3) With many customization options. I know I left a lot of suggestions out of the video related to UI, but in the future these could be presented and maybe could be added. I think the suggestions that were shown to everyone would really be "the main ones" that could completely change 3DCoat and humbly speaking would start a great interface.
  8. Hi everyone! Yesterday I made a post precisely about the 3DCoat UI (By coincidence, in one of the topics I also talk about Activity Bar). Therefore, I made a video in which I try to explain and demonstrate modifications and suggestions on the subject. The topics in the video are: 00:00 - Introduction and the biggest problem with the interface. 00:44 - Menus at the top of the interface in a single button. 01:14 - Main Button to access all brushes, tools and commands. 01:28 - Button that contains features common to all brushes and tools (which could be a floating menu). 02:15 - All properties organized on the side. 02:37 - Shift, Ctrl+Shift and Ghosted features within a single button (which could be a floating menu). 03:17 - Mask Conditions functionalities within a single button (which could be a floating menu). 03:56 - Important changes to the Left Panel. 05:12 - Customized panel with quick access to the tools, brushes and commands most used by the user. 05:50 - Important changes to the Activity bar. 06:47 - Customizing the position of the viewport buttons. 07:12 - Navigation cube and with the option to have an .obj as a reference. 08:16 - Customizable user panel. 08:46 - On the right side of the top of the interface - area reserved for user customization. 09:07 - Rooms menu listing on the top right side of the interface. If you want to see, please below is the thread link: Thank you very much
  9. Hi everyone! If there is a problem viewing the video I made in the previous post about the 3DCoat UI, then I am making this post with images taken from the video. 1 - Menus at the top of the interface in a single button: 2) Main Button to access all brushes, tools and commands: 3) Button that contains features common to all brushes and tools (which could be a floating menu): 4) All properties organized on the side: 5) Shift, Ctrl+Shift and Ghosted features within a single button (which could be a floating menu): 6) Mask Conditions functionalities within a single button (which could be a floating menu): 7) Important changes to the "Left Panel": 8 ) Customized panel with quick access to the tools, brushes and commands most used by the user: 9) Important changes to the Activity bar: 10) Customizing the position of the viewport buttons: 11) Navigation cube and with the option to have an .obj as a reference: 12) Customizable user panel: 13) On the right side of the top of the interface - area reserved for user customization: 14) Rooms menu listing on the top right side of the interface: --> Below would be the image without explanations: I hope I was able to summarize through the images what was done in the video I made (in which there are better explanations and demonstrations). Thank you!
  10. Hello everyone! It's been a while since I posted anything here and I believe now would be a good time to do so. I have a YouTube channel rygaardcreations where I did a lot of hard work to teach everyone advanced customization and many secrets of the program regarding the interface. BUT.... 3DCoat 2024 presents changes to the interface! So due to my constant use of 3DCoat and through my experience with it... I made a video with some suggestions that in my humble opinion would be useful. Therefore, I tried with these changes to improve the interface with the main objective of facilitating and above all helping the user's work within 3DCoat, which would make the program more user-friendly. friendly ui 3dcoat.mp4 00:00 - Introduction and the biggest problem with the interface. 00:44 - Menus at the top of the interface in a single button. 01:14 - Main Button to access all brushes, tools and commands. 01:28 - Button that contains features common to all brushes and tools (which could be a floating menu). 02:15 - All properties organized on the side. 02:37 - Shift, Ctrl+Shift and Ghosted features within a single button (which could be a floating menu). 03:17 - Mask Conditions functionalities within a single button (which could be a floating menu). 03:56 - Important changes to the Left Panel. 05:12 - Customized panel with quick access to the tools, brushes and commands most used by the user. 05:50 - Important changes to the Activity bar. 06:47 - Customizing the position of the viewport buttons. 07:12 - Navigation cube and with the option to have an .obj as a reference. 08:16 - Customizable user panel. 08:46 - On the right side of the top of the interface - area reserved for user customization. 09:07 - Rooms menu listing on the top right side of the interface. Who knows, this could happen in the future... Thanks!
  11. First of all, Happy New Year to everyone! I would like to comment on the search icon to all the right. With all due respect to your opinion, but I disagree about repositioning the search button to the right (like the image above with the red arrow). I think it would be a little dangerous. In my humble opinion, the biggest reason for this is that currently there is already a delete button (trash bin) on the right and this means that there would be a great possibility of unpleasant situations happening. Imagine the following situation. The user is working and for some reason, either due to distraction or a rush to click on the search button... then the user accidentally and instead of clicking on the search button, unfortunately the mouse cursor goes a little further to the side and ends up clicking where? That's right, the delete button! I speak from my own experience with this type of unpleasant situation... because in the tool options palette (talking about Brushes), in the modifiers bar there are 3 buttons (two arrow buttons: up and down to reposition the modifiers and a delete button on the right) and it has happened several times I pressed the delete button trying to press the arrow button to reposition the modify in the palette because in my rush or distraction the mouse was positioned right between the two buttons. So I accidentally deleted the modifier (losing everything I had done) and that is very terrible in every way. I agree with you that this functionality is not the main one. But repositioning this functionality next to a delete button wouldn't be so good (dangerous). Just an opinion... Perhaps... it could be in Second position after the new layer button (because at the moment... it has the Merge layer bellow button on the side of the Group Layers button) new layer --- SEARCH --- group Layers --- merge bellow The placement of this can also be a matter of taste, but in my case... if I can prevent a feature that I use a lot from being next to a delete or merge button, I would personally avoid it so as not to cause me problems. By the way... It would be wonderful if the user could customize the order of these commands (buttons). Then the user himself would decide the positioning.
  12. Really, I'm speechless ... just sharing the test I did with a bust of 15 million triangles that speaks for itself. Cutoff operation has been completed in just 12 seconds. So far, I don't even believe this is happening! I'm IMPRESSED! Looks like I'm exaggerating, no? But I say that because I have the AMD processor and I know what I went through (really hard times)... I believe to those who have Intel must be even faster! Is not true?! Have I said I'm impressed? Thank you very much!
  13. Andrew... you really don't exist! Are you sure you are this world? I say this with all my respect and admiration! I am completely impressed with the result. I'm speechless ... to describe my happiness with the result I got. Because unfortunately using the AMD processor, in my case the Ryzen 9 3900X was horrible using the Cutoff tool! Everyone can see what happened in my previous tests, including a fatal error. Cutoff operation really took a long time between 50 seconds up to more than 1 and a half minutes (sometimes even much longer) to complete and also sometimes freezing 3DCoat with memory related problems or closed the 3DCoat abruptly. Now, happily I would like to share the result of my tests using version 3DCoat2023 . 09: 1) Test with screen recording program: - Geometry (sphere) with 8 million = took 8 seconds to be completed. cutoff_2023build09_speed_test.mov 2) Test without screen recording program: - Geometry (sphere) with 8 million = took 8 seconds to be completed. 3) Test without screen recording program, but with more complex curve: - Geometry (sphere) with 8 million = took 10 seconds to be completed. --> Note: When updating to version 3DCoat-2023 09, as I use Windows 10, it was not necessary to perform any type of procedure regarding KB5023706, the update flowed normally and successfully. I confess that I am excited to test the Surface Mode in boolean operations. Will I have a better performance too? Andrew, I thank you so much for the magical work you did.
  14. Fortunately or unfortunately, I still use Windows 10, so when I looked for this installation under "Installed Updates", I didn't have KB5023706 installed ( --> It looks like it's only for Windows 11). Now, I was worried about this because I don't have this KB5023706 installed. So @Andrew Shpagin , maybe... Is there another type of installation similar to KB5023706 that is installed and is causing this issue for Windows 10 users? For sure, when I have this build (3DCoat 2023.09), I'll do the tests and check the possible problems here if they happen... and I'll post the results. Thank you so much for your hard work and incredibly quick response.
  15. I did some tests using the cutoff with the sphere subdivided into 8 million: -> In the tests below, an AMD Ryzen 9 3900X processor was used. 1) Test without screen capture recording took the operation in 51 seconds. 2) Test with screen recording: - Fatal error in 30 seconds. fatal_error.mov 3) Test with screen recording after Fatal Error: - And the operation took 52 seconds. cutoff_8millions_test.mov @Andrew Shpagin , if I can help in any way and if you need more testing with this AMD processor please contact me. As always I am very grateful for the brilliant and fantastic work you and your entire team do. Thank you!
×
×
  • Create New...