Andrew Shpagin

Not easy to understand, please explain what is different if you restart and not restart.

The fonts system changed essentially, so I am not absolutely sure that Chinese and Japanese text displayed correctly. Could be good if someone may check.

Updated to 10 to fix font issue

I discovered that this happens if 2024.09 installed, run and then you roll back to 08 or below or run some older version. I will correct this in 10, but if this problem appears, remove the folder: c:/Users/your_user/Documents/3DCoat/data/Unicode/

Corrected this in 2024.09. Now context is fresh each time. And since 2024.09 coat.io.showPythonConsole() brings the console window to foreground.

In 08 this problem solved principally: Fixed problem when new tools (sometimes) does not appear when you install the update. Of course, if you created own custom room, you need to add new tools there manually (looking at the script).

Use Edit->Relocate 3DCoat's data to place the date in another folder

Fixed in 08

Is there any lag when you switch to some other tool? Maybe if lag exists it is counted as the 'delay' that activates sticky activity? And yes, in 2024.08 I will add the option to turn off sticky.

First, try default cube. Second, try mouse and pen. Is there performance difference?

I will fix it in 08, but if you will turn off Geometry->Incremental Render all works as expected.

And I fixed countless amount of bugs in 2024.07 (comes today), please check it there (when released).

I see there was no crash reports? They are really useful, I may understand all in depth...

Maskig will be corrected in next build - it will work with color and transparency and expected.

Masks will appear in 2024.06 build

I recovered the scene and sent to you. Looks like there is problem with opening zipped scenes, we will correct it, now please turn off zipping in preferences.

For me personally use andrewshpagin@gmail.com Regarding other - way to reproduce is №1 always.

Please refer Flat Shading report if possible (I seen it somewhere, but lost).

If it is about picking VDM alpha from the model, use Sculpt->Pick VDM. It will export EXR with true vector displacement. But there is no way to bake this figure onto texture and get VDM, there is only baking along the normal.

Could be good if you will drop me the link to the material example to test if my fix is correct.

The process() works only for python. In c++ use virtual bool ProcessInEditor(BaseClass* Parent) { stage += 1; if (stage == 5) { coat::ui::cmd("$MyClass::Integer"); } return true; }

It is possible via script. You may get retopo scene as mesh, then iterate over all sculpt objects, get transform matrix, multiply over inverted matrix of initial sculpt object apply it to mesh and merge into the retopo scene.

Thanks! I will do 40 today to fix it.

This is (I hope) is what you need: # This example demonstrates the power of the dialogs and UI. It describes how to register the elements into the UI. import coat # let's define the class. Then we create the ui function that exposes the ui elements list class MyClass : def __init__(self) : self.Integer = 0 self.stage = 0 def process(self) : self.stage += 1 # we use comparison to 5 to give some time to dialog to appear and to avoid constant clicking if self.stage == 5 : coat.ui.cmd("$BaseClass::Integer") # this section used for the class serialization and visual presentation in the UI def ui(self) : # since ui called constantly, we may do some actions there, for example click over controls self.process() # there you define the list of variables and functions to show in the dialog. # This list is dynamic, this function is constantly called, any changes in list # will be exposed immediately return [ "Integer" # we write there the name of variable we want to expose to the UI ] p = MyClass() # show the dialog coat.dialog().ok().cancel().params(p).caption("Hello!").show(); There is sort of workaround, in 38 there will be more logical solution, you will be able to pass process callback into the dialog.

I will add it there.