[Maya-Python] More performance in VP2 for a custom locator?

[Andrea Pinto]

Hello everyone,
I am trying to create a custom locator, drawing a circle always face to
camera

I noticed when duplicate the locator 500 times, the scene is very very slow.
but If I create 500 spaceLocator that isn't happens

Can you know why?

thanks a lot
Andrea

[Chad Vernon]

It depends on your draw calls. Make sure you are not reading plug data in the draw function.

[Andrea Pinto]

Hi chad! thanks for reply.

I started from the footPrintNode example
https://github.com/autodesk-adn/Maya-devkit/blob/master/win/devkit/plug-ins/scripted/pyFootPrintNode.py

Yesterday I tried the footPrint in maya 2016/2017 and I had the same
result, viewport 1 e 2 very slow.

Sorry I am noob
thanks again

Post by Chad Vernon
It depends on your draw calls. Make sure you are not reading plug data in
the draw function.

[Andrea Pinto]

This example hasn't any problems in viewport, I will try to study it.

https://github.com/autodesk-adn/Maya-devkit/blob/master/win/devkit/plug-ins/scripted/pyFootPrintNode_GeometryOverride.py

Post by Andrea Pinto
Hi chad! thanks for reply.
I started from the footPrintNode example
https://github.com/autodesk-adn/Maya-devkit/blob/master/win/devkit/plug-ins/scripted/pyFootPrintNode.py
Yesterday I tried the footPrint in maya 2016/2017 and I had the same
result, viewport 1 e 2 very slow.
Sorry I am noob
thanks again

Post by Chad Vernon
It depends on your draw calls. Make sure you are not reading plug data
in the draw function.

[Chad Vernon]

The problem with the first example is that getMultiplier function. It's reading the plug value to get the multiplier and is called in both the boundingBox function and prepareForDraw function. The second example looks like it caches the plug values and only reads them when they change.

[Andrea Pinto]

I tried again the first example.
drawing only a simple circle, but nothing it is still slow.

Can you suggest to me a way to create a custom shape face the camera?

In the attachment a snapshot of the my custom locator
The scene becomes slow with 40 locators :(

<Loading Image...>

Post by Chad Vernon
The problem with the first example is that getMultiplier function. It's
reading the plug value to get the multiplier and is called in both the
boundingBox function and prepareForDraw function. The second example looks
like it caches the plug values and only reads them when they change.

[Alex Hrazhdan]

Hi, Andrea. the significant slowdown is because of one shader per override
locator instance, and because of transparency
(MShaderInstance::setIsTransparent())...

[Andrea Pinto]

Hi Alex thanks, Do you mean I have to create a MShaderIstance?
I am using the MPxDrawOverride method of the footPrintNode example.
In that example the footPrint isn't trasparent, but it is slow.

I don't know, Probably I have to find a way to don't create the position
list and triangles for every update.
I am creating the circle face the camera, multiplying every point with
cameraPath.inclusiveMatrix() and objPath.inclusiveMatrix().inverse()

Post by Alex Hrazhdan
Hi, Andrea. the significant slowdown is because of one shader per override
locator instance, and because of transparency
(MShaderInstance::setIsTransparent())...

[Alex Hrazhdan]

*Hi Andrea. Isn't it more efficient to draw simple sphere than circle? In
that case you dont have to multiply vectors by matrix every draw update...*
*And instad of MPxDrawOverride, I recoment to use MPxGeometryOverride...
You can declare couple of MShaderInstance as static variables and use it
for every locator instance in different cases (selection lead, selection
active, defoult state). *
*But in that case you will lose your ability to switch color per locator
instance.*

[Andrea Pinto]

thanks again for your advice, you are right, the sphere was my first idea.
My fault I would like to do something more 2D hehe.
Create different shapes when changing the segments.
Surely in c++ would be better.

[Andrea Pinto]

<Loading Image...>

Hi! I was working about it again in these Days.
In the geometryOverride I tried to print out the semanticName of the
vertexBufferDescriptor
The result is only "POSITION", it hasn't a semantic "Normals"

How I can create the Normals? or Do you have some solution for this problem?

Is it possible to use a geometryOverride and drawOverride togheter?

thanks in advance

Hi, sorry if I continue to ask some question here, I was trying to create
a sphere with MPxGeometryOverride.
This is the result.
Wireframe is ok, but the shaded it is strange.
Is it a problem with the normals?
<https://lh3.googleusercontent.com/-72oOsjB4-8A/WFkcftvxmJI/AAAAAAAAc4M/s5gJgljP2Zc9r8TQ9s-2X_nXiezNGgu4ACLcB/s1600/sphere_geoOverride.jpg>

Post by Andrea Pinto
thanks again for your advice, you are right, the sphere was my first idea.
My fault I would like to do something more 2D hehe.
Create different shapes when changing the segments.
Surely in c++ would be better.

[Andrea Pinto]

Hello! Yesterday I saw the example of apiMeshShape.
More or less I understand how to create the shape.
I'll try to follow that example.

Post by Andrea Pinto
<https://lh3.googleusercontent.com/-72oOsjB4-8A/WFkcftvxmJI/AAAAAAAAc4M/s5gJgljP2Zc9r8TQ9s-2X_nXiezNGgu4ACLcB/s1600/sphere_geoOverride.jpg>
Hi! I was working about it again in these Days.
In the geometryOverride I tried to print out the semanticName of the
vertexBufferDescriptor
The result is only "POSITION", it hasn't a semantic "Normals"
How I can create the Normals? or Do you have some solution for this problem?
Is it possible to use a geometryOverride and drawOverride togheter?
thanks in advance

Hi, sorry if I continue to ask some question here, I was trying to create
a sphere with MPxGeometryOverride.
This is the result.
Wireframe is ok, but the shaded it is strange.
Is it a problem with the normals?
<https://lh3.googleusercontent.com/-72oOsjB4-8A/WFkcftvxmJI/AAAAAAAAc4M/s5gJgljP2Zc9r8TQ9s-2X_nXiezNGgu4ACLcB/s1600/sphere_geoOverride.jpg>

Post by Andrea Pinto
thanks again for your advice, you are right, the sphere was my first idea.
My fault I would like to do something more 2D hehe.
Create different shapes when changing the segments.
Surely in c++ would be better.

[Andrea Pinto]

Hi, after so long, I resume this discussion.
I wanted ask you.
Do you know if there is a way to update the function populategeometry in
the method geometryOverride when I am scaling the transforme node.

I would like to have the shape with same size multiplying it with inverse
matrix
I mean I did that, but it update when I deselect and select the transform
node after the scaling

do you know how can I update it directly with scaling?

thanks in advance
Andrea

Post by Andrea Pinto
Hello! Yesterday I saw the example of apiMeshShape.
More or less I understand how to create the shape.
I'll try to follow that example.

Post by Andrea Pinto
<https://lh3.googleusercontent.com/-72oOsjB4-8A/WFkcftvxmJI/AAAAAAAAc4M/s5gJgljP2Zc9r8TQ9s-2X_nXiezNGgu4ACLcB/s1600/sphere_geoOverride.jpg>
Hi! I was working about it again in these Days.
In the geometryOverride I tried to print out the semanticName of the
vertexBufferDescriptor
The result is only "POSITION", it hasn't a semantic "Normals"
How I can create the Normals? or Do you have some solution for this problem?
Is it possible to use a geometryOverride and drawOverride togheter?
thanks in advance

Hi, sorry if I continue to ask some question here, I was trying to
create a sphere with MPxGeometryOverride.
This is the result.
Wireframe is ok, but the shaded it is strange.
Is it a problem with the normals?
<https://lh3.googleusercontent.com/-72oOsjB4-8A/WFkcftvxmJI/AAAAAAAAc4M/s5gJgljP2Zc9r8TQ9s-2X_nXiezNGgu4ACLcB/s1600/sphere_geoOverride.jpg>

Post by Andrea Pinto
thanks again for your advice, you are right, the sphere was my first idea.
My fault I would like to do something more 2D hehe.
Create different shapes when changing the segments.
Surely in c++ would be better.