Hi,
i was going to try to build the deb packages for OpenMesh. However, i
was immediately stopped in the first place, since there are rules
contained building the apps which require QT4. In recent Ubuntu/Debian
versions QT4 has been dropped.
So i ask:
* If building debian packages is something which happens in your CI
(have not found anything in the code)
* if the debian build rules may be a subject to change -> essentially
skipping building the apps.
Thanks,
- Robert
Hi Folks,
for our project we needed support for texture files and have built it
into Openmesh and also exposed it in openmesh-python.
What we did in detail:
OpenMesh:
- added param 'texture_file' to the Options class, it specifies the path
to the texture file
- added param 'material_file_extension' to the Options class, it
specifies the material file suffix, default is ".mat" as it was before,
we needed it becuase Blender expects ".mtl"
- removed default and copy constructor and destructor as well as
assignment operator, because these are not necessary here, see
https://en.cppreference.com/w/cpp/language/rule_of_three
openmesh-python:
- exposed the above features
- exposed .is_locked and .set_locked
- documented it in trimesh.rst
I attatched the git diffs for OpenMesh and openmesh-python.
Please let me know if it could be merged and if necessary what we could
do better ;)
regards
Philipp Auersperg-Castell
Pretty much the title.
I am trying to clip a mesh against a plane, to that effect i need to check each face against the plane and either delete the face or modify it introducing new vertices.
I am trying this to access the vertices:
```cpp
MyMesh::FaceIter f_it, v_end(mesh.faces_end());
uint count = 0;
for (f_it=mesh.faces_begin(); f_it!=v_end;)
{
auto old_it = f_it;
MyMesh::FaceVertexCCWIter fv_iter = mesh.fv_ccwiter(old_it);
std::vector< MyMesh::VertexIter > new_face_verts;
for (; fv_iter.is_valid(); ++fv_iter)
{
mesh.point(fv_iter);
}
++f_it;
mesh.delete_face(*old_it, true);
}
mesh.garbage_collection();
```
But this is apparently invalid. As no method in the mesh accepts that iterator.
I would like to use openmesh in python just to read a mesh from .obj from ShapeNet model. I did following:
import openmesh as om
from openmesh import *
mesh = om.TriMesh()
read_mesh(mesh, filename)
And I have got error, "name 'read_mesh' is not defined". Was
read_mesh replaced with something else?
Hi all,
I am facing an issue dealing with complex faces in openmesh via the
python interface. I have a mesh I am loading via trimesh (hard requirement
at this time), and using that to build an openmesh mesh. This mesh (and
others i work with) is degenerate in the sense that it has complex faces,
and trying to ignore that problem leads to the python process crashing
(either hanging or segfault/bus error depending on the mesh). If i
proactively try to delete the complex faces immediately after they are
created, I get a seg fault. I have attached a minimum working example
complete with degenerate STL, I would appreciate any assistance debugging
this and/or working around it!
Cheers,
Bruce
Hi,
I would like to report a bug in OBJReader of Open Mesh. I have written a
program to read OBJ files and to render them using OpenGL. This program
uses OpenMesh for loading files. When I load the attached file
(CubeCol.obj), the program displays a gray coloured cube instead of a red
cube (CubeCol.mtl defines the colour of the cube as red). All other object
loaders and viewers (including Windows 3D viewer) displays the cube
correctly with a red colour. I spent hours trying to identify the problem,
and finally found out that if I remove the space character at the beginning
of the last three lines in CubeCol.mtl, the cube gets displayed correctly.
Apparently, OBJReader ignores lines in the mtl file where there is a space
character in the first column. All other obj readers that I have used load
the file correctly.
Also, I have noticed that it is not sufficient to request face colours
(mesh.request_face_colors()) before reading the mesh file to get the colour
values from the mtl file. I also had to include IO::Options::FaceColor as
the argument for the read_mesh() function to get face colours using
mesh.color(faceHandle); I couldn't find any documentation giving the
actual procedure for loading data from mtl files. Please let me know if I
am using the correct method for loading obj files along with material
properties.
Thank you.
Kind regards,
Mukundan
mukundan2013(a)gmail.com
Dear All,
I am about to submit a paper where I used a simulation which uses OpenMesh. First, let me thank the developers, contributors and everyone on this forum who helped me with my questions and problems on the way. Second, I was wondering whether there is one or more papers you would prefer me to cite.
Thank you,
Botond
Hi OpenMeshers,
currently the OpenMesh submodule is at
db8c0608830ae7324b2b2e1d91e4db565b2d3eae dated from Apr 23.
I wanted to bump to OpenMesh master, but there are serveral
incompatibilities in the build.
as the git log tells, there are serveral changes to Openmesh, so it
would be fine to have the new version bundled.
So I wanted to ask if there are plans to bump to a newer OpenMesh version?
Best regards in advance
Philipp
Hi,
Attached you find a patch for ignoring shared objects in
openmesh-python. I added this to avoid unneccesary terminal overhead
with git submodules.
Is it possible to apply this patch upstream?
BTW - what's the preferred way you want to receive possible
patches/contributions?
Thanks
- Robert