Vertex Color Tools

[trueBlue]

Rosetta UU9
Simple Cloth Plane; 100x100 elements with an Editable shape, on top of a Cube.

Morph Animation current version.
Make Morph
Would you like to delete the original source cloth object?
Yes
Crash

Vertex Color Animation current version.
Make Vertex Color
Would you like to delete the original source cloth object?
Yes
Crash
Takes over 2 minutes to process before getting the question.

Model Vertex Animation current version.
Make Vertex

Model's AutoKey does not make any difference for me if it is Checked or Unchecked.
What does matter is the Step Frames and the python timeIncrement must equal 0
Using Cloth Fixations will show in Model as bumps in the Cloth

[clintonman]

Rosetta UU9
Simple Cloth Plane; 100x100 elements with an Editable shape, on top of a Cube.

Morph Animation current version.
Make Morph
Would you like to delete the original source cloth object?
Yes
Crash

Vertex Color Animation current version.
Make Vertex Color
Would you like to delete the original source cloth object?
Yes
Crash
Takes over 2 minutes to process before getting the question.

Model Vertex Animation current version.
Make Vertex

Model's AutoKey does not make any difference for me if it is Checked or Unchecked.
What does matter is the Step Frames and the python timeIncrement must equal 0
Using Cloth Fixations will show in Model as bumps in the Cloth

That's pretty wild. No idea why it crashed but both crashes are fixed now.

Thanks for the steps, now I can see the pause. I'm surprised it could handle a mesh with that much geometry. 100x100 mesh makes animation images 10201 pixels wide. There's probably a limit that needs to be set, maybe something like 16384 vertex count.

I agree about autokey. I think what I was seeing was the python script running when modelspace was opened. Now I empty the python script before switching back to workspace. If autokey was the reason I would have gotten keys on every frame not the expected keys(every 10 frames for my testing)

[clintonman]

Fixed crash when deleting the original in morph and vertex color runs
Added status line feedback to the vertex color run
I tested vertex color as high as 16512 vertices, 127x128 and it still worked, so I won't be setting any limits at this time. Though it does look like the cloth tool crashes if it's too big, somewhere between 175x175 and 180x180.

[trueBlue]

I think I found the problem with the the UU layouts. The slowdown occurs when the Scene View is open. Several UU layouts have the Scene View open permanently, meaning there is no way to close it.

Steps:

Default Layout
Open LE window for convenient selecting - selections are fast
Switch to Model
Open the Python Editor
Selections are now super slow
Run the attached script to close the Scene View
Selections are fast again

Can restart tS to get speed with the Scene View open

I think the combination or python scripts and scene view is unstable and the scene view should be closed when running python scripts.

Super happy you found the culprit for Model's Script Editor!
Can not wait to see if this resolves the issue with the D3D Renderer.
Does not fix Model's Scene Editor though!
BTW... you can Ctrl Drag the Scene View's title bar out from its Docked position.

[clintonman]

I think I found the problem with the the UU layouts. The slowdown occurs when the Scene View is open. Several UU layouts have the Scene View open permanently, meaning there is no way to close it.

Steps:

Default Layout
Open LE window for convenient selecting - selections are fast
Switch to Model
Open the Python Editor
Selections are now super slow
Run the attached script to close the Scene View
Selections are fast again

Can restart tS to get speed with the Scene View open

I think the combination or python scripts and scene view is unstable and the scene view should be closed when running python scripts.

Super happy you found the culprit for Model's Script Editor!
Can not wait to see if this resolves the issue with the D3D Renderer.
Does not fix Model's Scene Editor though!
BTW... you can Ctrl Drag the Scene View's title bar out from its Docked position.

There is no title bar to drag or close it.

[trueBlue]

I think I found the problem with the the UU layouts. The slowdown occurs when the Scene View is open. Several UU layouts have the Scene View open permanently, meaning there is no way to close it.

Steps:

Default Layout
Open LE window for convenient selecting - selections are fast
Switch to Model
Open the Python Editor
Selections are now super slow
Run the attached script to close the Scene View
Selections are fast again

Can restart tS to get speed with the Scene View open

I think the combination or python scripts and scene view is unstable and the scene view should be closed when running python scripts.

Super happy you found the culprit for Model's Script Editor!
Can not wait to see if this resolves the issue with the D3D Renderer.
Does not fix Model's Scene Editor though!
BTW... you can Ctrl Drag the Scene View's title bar out from its Docked position.

UUNoTitleBar.jpg
There is no title bar to drag or close it.

Yes there is.
The horizontal blue gray area

[clintonman]

Super happy you found the culprit for Model's Script Editor!
Can not wait to see if this resolves the issue with the D3D Renderer.
Does not fix Model's Scene Editor though!
BTW... you can Ctrl Drag the Scene View's title bar out from its Docked position.

UUNoTitleBar.jpg
There is no title bar to drag or close it.

Yes there is.
The horizontal blue gray area

Vertical, and well hidden. Didn't even know it was a title bar.

[trueBlue]

UUNoTitleBar.jpg
There is no title bar to drag or close it.

Yes there is.
The horizontal blue gray area

Vertical, and well hidden. Didn't even know it was a title bar.

Just like my daughter, always correcting my bad grammar!

[trueBlue]

Looking good so far
I set my Command History to 200
You can completely undo the Morph Animation and Model Vertex
Do not think that this is going to be good for various reasons.
Mind you, this was only a 2 second animation.
One being if a User only has the default 20 Undoes set, and they use Undo a few times or all twenty could screw up the whole process.

The Vertex Color process freezes the Command History entries, so there is no Undoes.
Not a big deal, I guess, as soon as you select something, the frozen entries disappear.

[clintonman]

Vertex Materials

from left to right: Solid base material, VertexColorAdd, VertexColorInterpolate, original first material
front to back: white, gray, black

The VertexColorAdd compound material, second from the left matches the appearance of the Solid base material by adding the vertex color to the material color

The VertexColorInterpolate material, 3rd, places the color of the vertices on top of the material color and mixes based on the intensity of the vertex color

The original material worked well if the material color was white. As shown it sort of falls apart if the vertex color is black. Earlier tests I think had white as the base vertex color, here it is black and completely covers up the white and gray of the spheres.

Both materials have a strength control like the Solid base material.