gbball

Thanks for confirming Digman. I had a feeling it was probably a focus issue. Hopefully it can get sorted out.

@digman I hadn't been using the new curves, just the polyonal and freehand lasso tool. All the beta features are enabled though. I edited my earlier post to mention that after your comment I did try to see if the curves would work and they did. Subsequently, the polygonal lasso and freehand lasso tool did end up working as expected. However, this only worked the one time I tried it and subsequent attempts to get the lasso tools working properly by using the curves first didn't work.

Trying it again, I'm not having the same issue. I think it might be related to a different bug where when I open the color picker by pressing the 'b' key, the color picker didn't disappear when my cursor came off the window. After testing a little more. It happened in both GL and DX versions of 4.9.58 Unfortunately, I can't seem to replicate the bug. But it seems when the color picker dialog remains open, the polygonal and lasso cutoff tools don't work in either version. I haven't tested to see if it's the same with other dialogs like the alphas window. I'll post again if I can get more clarity. EDIT: Okay, steps to reproduce. Open the Color Palette Dialog through Windows->Panels->Color Palette. Undock it if it's docked. It should stay visible whether your cursor is hovering over it or not Try using the cutoff tools polygonal or freehand lasso tools and it shouldn't work. EDIT II: After Digmans response I tried using the new Beta Curves to see if that would work and it did. After using the Beta Curves, I was able to get the polygonal and freehand lasso tools work correctly while the undocked Color Palette dialog was opened. However, in subsequent attempts, the Polygonal Lasso tool and Freehand Lasso tool are no longer working again when the Color Palette is open. Very strange.

I noticed a bug in version 4.9.58 GL version only. The polygonal lasso and freehand lasso tool don't work when using the cutoff tool. Works fine in the DX version. Can someone confirm?

Yeah, looking at it some more, I've found that it's still an issue in an older project that I started a few months ago. I don't have any problems when I use the applink in a fresh Blender scene. I was going to try what you said to confirm whether or not it was the fact that it was an old project or not. The other thing I was going to test was whether or not the number of instances in the Blender project had any effect. Thanks for pointing out the workaround.

I got it working. I ended up deleting the applink and installing the new version of Blender. 2.83.5 hoping that it would just work. Unfortunately, when I did that, there was no 'getback' button, so I deleted the applink included in that version and installed the version you posted here and now it works. I wonder if the problem I had previously was related to the fact that I installed the applink in my AppData folder instead of in the Blender installation folder? I didn't check so I'm not sure if that was the issue or if it was the version of Blender that I was using. I hope that helps. Thanks again for your work on the Applink! It makes things go way smoother.

I'm using Blender 2.83 and the data.json file does exist. Could it have anything to do with the location of my exchange folders? If I leave those fields blank what will happen?

Hi @haikalle Thanks for all your work maintaining the Blender Applink. I've been having some trouble with it since Blender 2.83. Is that version supported? I can send to 3DCoat no problem, but I'm having problems when I try to bring textured assets back. Below is the error I'm getting. I'm using the version of the applink you posted here most recently. Hopefully you can point me in the right direction. Thanks! Traceback (most recent call last): File "C:\Users\gavin\AppData\Roaming\Blender Foundation\Blender\2.83\scripts\addons\io_coat3D\__init__.py", line 339, in invoke workflow1(ExportFolder) File "C:\Users\gavin\AppData\Roaming\Blender Foundation\Blender\2.83\scripts\addons\io_coat3D\__init__.py", line 1356, in workflow1 blender_3DC_blender(texturelist) File "C:\Users\gavin\AppData\Roaming\Blender Foundation\Blender\2.83\scripts\addons\io_coat3D\__init__.py", line 1130, in blender_3DC_blender tex.matlab(objekti,mat_list,texturelist, is_new) File "C:\Users\gavin\AppData\Roaming\Blender Foundation\Blender\2.83\scripts\addons\io_coat3D\tex.py", line 697, in matlab readtexturefolder(objekti,mat_list,texturelist,is_new, udim_textures) File "C:\Users\gavin\AppData\Roaming\Blender Foundation\Blender\2.83\scripts\addons\io_coat3D\tex.py", line 300, in readtexturefolder createnodes(index_mat, texcoat, create_group_node, objekti, ind, is_new, udim_textures) File "C:\Users\gavin\AppData\Roaming\Blender Foundation\Blender\2.83\scripts\addons\io_coat3D\tex.py", line 441, in createnodes with open(json_address, encoding='utf-8') as data_file: FileNotFoundError: [Errno 2] No such file or directory: 'C:\\Program Files\\Blender Foundation\\Blender 2.83\\2.83\\scripts\\addons\\io_coat3D\\data.json' location: <unknown location>:-1

This will be a very useful feature. Good work!

Agreed, It would make sculpting with PBR shaders a lot better. Currently, I use matcaps for sculpting because they simulate this effect.

This is great!

Is that in Voxel mode or Surface mode? Can you share a video? I tried to confirm, but wasn't 100% sure what I was looking for. I did notice that there was very brief period of time that it took for a Voxel sculpt to remesh when I got up to and around 1million polygons. But it was a fraction of a second while it remeshed the marching cubes.

If I have problems with merging in Surface mode, I will usually switch to Voxel mode which always works properly.

It's in the newest beta. You can find it in surface mode just above the new basebrush tool.

2 other longstanding bugs that I should mention. 1 - in the retopo room, when using the point, faces tool. If you assign delete polygons, delete edges, or collapse to the CTRL or CTRL+SHIFT action, it will perform the action of that tool, but it does so as though you're pressing CTRL. This isn't usually the desired outcome. For example, if i want to delete one or two polygons, I will have to swith tools instead of using the modifier because the modifier will delete everything. 2 - If I do a smooth all immediately after extruding, the extrusion will be lost and the smooth all will happen on the un-extruded version of the mesh.