Fail to read mesh from obj in CentOs
See original GitHub issueDescribe the bug, what’s wrong, and what you expect:
On linux it fails to load obj file while the same loads on Windows. The model is a simple box exported by Ansys tool. If needed I can send the file.
To Reproduce
import pyvista as pv
data = pv.read(file)
Screenshots If applicable, add screenshots to help explain your problem.
System Information: Linux CentOs
Issue Analytics
- State:
- Created 2 years ago
- Comments:10 (6 by maintainers)
Top Results From Across the Web
MeshLab / Discussion / Help: Error when loading an obj file under ...
With the svn build of Meshlab (Ubuntu 8.04 gcc 2.4.2) when I attempt to load an obj file I sometimes get this error:...
Read more >How Do I Fix the "Read-only file system" Error When I Delete a ...
Scenario 1: File System Mounted as Read-only · Run the following command to check how the directory containing the deleted file is mounted:...
Read more >missing texture for a obj - CloudCompare forum
I've a .obj with texture and work properly using meshlab. However, all texture lose when open it using cloudcompare.
Read more >Runtime errors on Centos 7 system - Ansys Learning Forum
Also, trying to start Mesh results in "failed determining temp ... The above bug happens when ANSYS fails to have read access to...
Read more >Wavefront OBJ File Format - Library of Congress
See 3D Model Appearance factor below. The OBJ file format supports definition of the geometry for object surfaces using polygonal meshes or ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
No issue with:
pyvista.Report
:My recommendation is to upgrade your Python environment (3.6 has passed the end of life and we are half-heartedly support 3.6 at this point). After upgrading Python to say 3.8 or 3.9, then also try upgrading VTK vo v9