I have a scene with multiple mechanical objects and their mapped visual models.
Through out the simulation I successfully deform my mechanical objects and via the mapping my visual models appear bent like they probably should be.
The problem appears when I try to export each visual model with :
AO replied to the topic SofaPython3: Troubles starting Sofa GUI from Python script in the forum Programming with SOFA 2 months, 4 weeks ago
As @ScheicklP told me a few days ago you might want to type :
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:Mypath/sofa/build/liband retry.
(with the correct path)
If it works you can add this line to your .bashrc file.
Alright, I managed to found a solution to the problem but it’s clearly not what should be done in the long term. I hope at some point we will be able to get the original sender as a data from the value argument.
An event class is often declared as such :
class SOFA_SIMULATION_CORE_API MyEvent : public…
I have a scene that roughly looks and works like this :
Since each solver is working on a different object I need to be able to discriminate the sender in my python script. Is there a (clean ?) way to do so ?
I tried to find informations from the value argument in the
def onDoStuffEvent(self, value)function but it does not provide…[Read more]
From the last update we now have two differents ways of setting a value from python to C++.
The first and old one is:
my_data.value = my_python_variable
The new one is:
with my_data.writeable() as foo:
foo = my_python_variable
What’s the difference between both in terms of accessibility and what’s the benefit of the second one…[Read more]