id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
2117	Modelica3d: Complete redesign needed	Christian Schubert	Martin Sjölund	"Looking at the definition of Modelica.Utilities.Internal.PartialModelicaServices.Animation.PartialShape I noticed that all ""parameters"" are defined as inputs:
{{{
  input Real lengthDirection[3];
  input Real widthDirection[3];
  input SI.Length length;
  input SI.Length width;
  input SI.Length height;
  input Types.ShapeExtra extra;
  input Real color[3];
  input Types.SpecularCoefficient specularCoefficient; 
}}}
Thus, they can change their value during simulation (and do as in the case of prismatic joints!)

Currently, the Modelica3D implementation treats them as parameters, i.e. they are sent at the visualization engine only during initialization.
Clearly, they have to be sent either at every frame or whenever they change (difficult since they are continous in general).

Then one should reconsider the modbus library as, as far as I know, it sends all data encoded as text (Is this true?). If that is the case, we should swith to some binary protocol or even simple udp messages, where we simply serialize the information from PartialShape together with the id of the object and the current time."	defect	closed	high		Third-Party Libraries	trunk	wontfix	modelica3d	Martin Sjölund Christoph Höger Adeel Asghar Volker Waurich