epernod

Hi,

the normal you see in the window are coming from the OglModel of your scene.
Each OglModel has a Data normal. I’m not used to create scene in python but I’m quite sure you can access directly Data values of component.

Be sure to have updateNormals set to true in the OglModel

Erik

And be sure to work on a nearly up to date version of SOFA from github because several bugs on the topology operation have been fixed in the past months.

Did someone say topology? Did I saw the bat-topology-signal?

Hello Wendy,

yes sorry, all those components are still a bit messy. It is on the todo list to have a clearer api.

Until then, for basic suppression/add of topological elements, I would suggest to have a look at those…[Read more]

Hi,

no sorry, I didn’t had time to check that and I have other deadlines for the moment.
I let you know if I make progress on that topic.

Erik

Hi,

@outtt I see the delay in your video but I tested the liver18.12.scn on my computer and I don’t have the delay.
Could you tell me exactly which version of SOFA you are using. Is it the 18.12 from github that you compiled or a package?

Are you able to test on an up to date version of SOFA? There might have been additional fixes not included…[Read more]

Hello @Wong

ok I understand, the data binding has not been canceled. The code from the Geomagic didn’t changed.
But the API on how to solve the constraint changed to be more accurate. The delay is due to tool position computation regarding the constraint.

When you speak about the 50 FPS, is it using the demo scene of the plugin or your scene?

Erik

Ok, yes it is because the omni position is now gathered inside the Omni node where there is mechanicalStateController.
To link to the Instrument model, it uses VectorSpringForceField.

Letting the first Data link was creating inconsistencies between the collision and controllerState nodes communicating using the VectorSpringForceField and the…[Read more]

Hi,

could you just post the old scene with the data binding you are highlighting.
I will check if this is still possible or with another mechanism.

The change in the scene were a consequence of changes in the constraint resolution API inside SOFA.

regards,

Hi guys,

just going quickly through the scene example, I think the tag “CarvingSurface” is missing on the target collision Model.

Then the class TopologicalChangeManager can give you which combination of collision model can be used for carving.

And yes only one collision model at a time can be used for your tool.

regards,

Ok great!
You are welcome. Could you set the field as resolved. Thanks.

Hi @Zhichao,

I had the same problem, it was because the cgal dll files were not found by CGALPlugin.dll

So you should add the cgal bin directory to your env path or look at this PR I try to fix that problem:
https://github.com/sofa-framework/sofa/pull/958

best regards,

Hello @tgaury,

could you describe what is the result you obtain. Is it crashing, nothing happen?
Do you have any output log?

like this I could see 2 options. Either attachConstraint work only with defaultAnimationLoop or you have to specify indices1=”@../M1/np1.indices1″

Regards,

Hi,

yes you need a tetrahedron topology. I checked and only triangle model collision is working well at the moment. So you will need something like (code not tested):

<CarvingManager active="true" />
<Node name="Grid" >
<RegularGrid name="HexaTop" n="12 12 12" min="-10 -6 -10" max="10 14 10" />
<MechanicalObject name="ms"…[Read more]

Hi,

@Binesh I just give a quick look at UncoupledConstraintCorrection. I saw that:
, d_handleTopologyChange(initData(&d_handleTopologyChange, true, "handleTopologyChange", "Enable support of topological changes for compliance vector (disable if another component takes care of this)"))

Do you know in which case “another component takes care of…[Read more]

Hi,

thank you for raising this issue up.

Regarding you scene, you have in the same node a Mesh and EdgeSet components.
I will add an issue on github regarding that because this should not be allowed.
This means you have 2 topologies in the same node so the other component like MechanicalObject and Spring don’t know which topology to rely…[Read more]

Hi,

I can see the 3 skipped in your log. But could you identify which projects are failing.
And post the log.

thanks.

Hi,

sorry for my speed to answer…
Could you resend the picture of the result you get, it would help me understand what is the problem.

Could you also do a quick test, is your point_idx a list of several edge indices?
If yes could you do a loop to send destruction of the edges one by one:


for (int i = 0; i < point_idx.size();…[Read more]

Hi @Wong
I’m sorry, I can’t develop that part for the moment as my current work rely on this.
I hope to publish a first version of Sofa-Unity API in a few weeks. Then I will be happy to help you using it.

But clearly, in Unity, it is not possible to interpret directly a C++ class pointer that you passed through C bindings.

Yes, you need to go with C bindings in middle. This is what I’m doing in the API.