Jump to content
3DCoat Forums

lambertj21

Member
  • Posts

    73
  • Joined

  • Last visited

Everything posted by lambertj21

  1. Thanks @Allabulle. So, I downloaded the latest linux build and installed it on a fresh new Ubuntu 20 LTS setup. I installed spacenavd and a few other libs called out here in this forum. 3DCoat launches perfectly but won't recognize pressure sensitivity (painting nor sculpting). Krita and Blender both recognize pen pressure.
  2. Got linux version up and running on Ubuntu 20 but I don't have pressure sensitivity. I changed the little mouse icon over to pen and locked it. I also checked stroke type but that doesn't really matter because no amount of pressure makes a difference. Any help/suggestions?
  3. Did this ever get addressed? As I play more and more with presets, I have to keep deleting the 'my documents' folders to get back to a starting point.
  4. @Andrew Shpagin, lighting in the sculpt room is discussed by several others here over the past few days. I think this is required to keep up with other tools and to provide expected user experience.
  5. Werner_Z is reporting the same performance issues we identified after the move tool optimizations. @Werner_Z, you reported .38 build. Can you confirm the issue in the most recent .39 build? (I'm in meetings right now so can't test it.)
  6. Got a little quiet here; assuming this is due to the focus on getting the Mac version updated. Hard to explain but there are a lot of performance issues across the sculpt room since the recent move tool fix.
  7. @Carlosan, how did you get the Custom group and to those settings?
  8. Also, the sluggishness is on a higher tri count than the base sphere for those testing this.
  9. Regarding Rygaard's last post, I can confirm Live Clay Tools being sluggish once the radius gets up over 20. Basically unusable at that size and above. Smaller radius is fine though (for me). I have the same complaint for the smooth brush; once the radius is set larger, it is unusable. @Andrew Shpagin, the move tool is now awesome, ty. Could you have refactored something that impacted many of the other brushes? Even the snake clay is acting up once the radius is bumped up a bit.
  10. Yes, that and many other settings can be controlled by the preset mechanism. After you use a handful of brushes, you have no awareness of how a tool/brush is going to work without testing it. This is why I said it seems like if you are going to use presets, you have to stick to just presets.
  11. It seems that the solution is to duplicate the actual brush first (right click and choose duplicate and give it a proper name) before using any presets of that brush. This gives you one to base presets on and one to grab as an 'original'...something you can expect default functionality from. I don't find this very intuitive or user friendly. A preset should toggle you into a copy of the brush.
  12. Can't do a video at this time and screenshots won't capture it. This is for vox or sculpt mode. Res+ the starter sphere up to ~2million tris. The move tool will have a very obvious delay at that point.
  13. @Carlosan, the above sequence is to use the default brush, switch to a preset based on the same brush, and then use a totally different brush so that you can switch back to what the sequence started with. But, you can't get back to the beginning since the preset is what is still being put into action.
  14. (I haven't found an answer for this elsewhere, hopefully not a duplicate.) Using a new install sequence: Install the app. Open into surface sculpting. Use rapid smooth brush - get used to how it works by default, no tweaks besides radius/depth. Switch to the out of the box presets, choose Polish group and then select "Polish Flat" which is a preset configuration of the rapid smooth brush...basically it digs in. Now there is no switching back to a default rapid smooth brush that goes back to building up instead of digging in. That is, unless I switch to another preset that I like for the rapid smooth. The preferences settings for "Remember Brush..." and "Remember Own Brush..." don't make a difference here. Am I missing something? It feels like presets completely stomp on a default functionality that you would start with. This makes me use ONLY presets and therefore the nicer tool selector window and the space bar quick access window are of little value. I hope I'm missing something.
  15. @Andrew Shpagin, with limited tris, you can really get interactive with the move tool. No delay, as fast as you can click. Once I get a a certain amount of tris though, there is a 1-3 second delay at the end of each stroke.
  16. @Andrew Shpagin, I can confirm the spikes tool fix. Thank you. What are your thoughts on the move tool? I use it excessively but once up over 1m tris, it has a delay. Once you focus on this delay, it is hard to focus on anything else.
  17. Spike tool still crashes the app for me after a fresh .35 install. Also, move tool still very sluggish.
  18. Spike tool will instantly, or within 3 strokes, crash the app. Tested in DX and GL and happens in vox and surface mode. Bug report sent.
  19. Thank you Carlosan, I'm in. This topic has been added to the beta testing thread in case anyone is following.
  20. Issue: Slow move tool and unusable smooth brush. System: ryzen5, 32gb ram, geforce 1660 super 6gb Reproduce: ~2million tris in either vox or surface mode. Any size of move tool has a pause; making for slow move tool based approaches which is critical to me. Larger sized smooth brush is basically unusable while small brush size is perfect. I have cuda turned on. Desired state: A performing move tool would be great. Comparison: Blender sculpt mode on the same machine with 8million tris has a perfectly smooth, non hesitating move tool and the smooth tool can be quite large with little to no delay.
  21. @Carlosan, I'm sorry to bother but I definitely can't post to the beta channel or any of the threads. I can't start a new topic or add a comments. Could this be because I"m new to the forums? I'm not finding instructions or a guide to the forums here.
  22. @Carlosan, the beta thread won't let me post. I was going to mention this there...although .34 isn't beta since it was released as stable.
  23. I'm using the most recent (.34) but it has always been like this for me. Thank you.
×
×
  • Create New...