[FIXED] Error while importing .obj

[justineo14]

The file in question seems to have been generated in Rhino and casues simplify3d to crash.
The error is that the file has a number of " \ " in the file.
I ended up manually editing the file and removing all the offending characters.
The exception is the one at the start of the file.

Thank you for your time.

Code: Select all

vn -0.03280431777238846 -0.192561686038971 -0.9807363748550415
vn 0.02241070754826069 0.125806525349617 -0.9918016195297241
vn 0.02937261387705803 0.1583808213472366 -0.9869410991668701
vn 0.01272853091359139 0.05317310988903046 -0.9985041618347168
vn -0.004895499907433987 -0.03634065389633179 \
 -0.9993274807929993
vn 0.02128755487501621 0.1237761676311493 -0.9920818209648132
vn 0.01565244793891907 0.09188580513000488 -0.9956465363502502
vn -0.01075020898133516 -0.06096754595637322 -0.9980818629264832
vn 0.007083691190928221 -0.01284881122410297 -0.9998923540115356
vn -0.01608465798199177 -0.1098584532737732 -0.9938170909881592

[rrdavis]

can you attach the OBJ file?

[justineo14]

can you attach the OBJ file?

This file is a paid file if/when I get permission I will upload the .obj what I will do is upload what happens to the interface.

It also seems that the crash only happens after I start editing the file.

[justineo14]

The creator gave permission so here is the file

https://drive.google.com/open?id=1WYa3- ... epqrAIIdjt

[rrdavis]

When I try to import that file, it just says "non-numeric data detected at line XXX" then nothing shows up. So yes, it seems there is something odd about the format for the file.

So when you say it was crashing when you edited the file, what do you mean? Were you able to import the file?

[justineo14]

When I try to import that file, it just says "non-numeric data detected at line XXX" then nothing shows up. So yes, it seems there is something odd about the format for the file.

So when you say it was crashing when you edited the file, what do you mean? Were you able to import the file?

Sorry for the slow response.

Yes if you open the .obj in a text editor of your choice like notepad++ you can remove the offending line breaks.
It seems that if you would remove an arbitrary amount of them it would cause a program crash. But with that said I haven't tried to reproduce that since I got it to print so it could be from just system instability as well.

I would also say I believe this could just be from how the author of the file *insert assumption here start* exported the file *insert assumption here end* .
I was rather amused that repetier-host v2.0.5 + Slic3r 1.3.0dev would load and slice it no problem.


At any rate the immediate problem is resolved in a workaround of editing the file. Thank you for your time/effort.

[cpknight]

I am having this same issue importing obj files that had been exported from Rhino all of which also import and slice without issue in Slicr. The "\" is also the offending character. I came here hoping to find comment about if this parsing error had come up for anyone else and if there is comment on if it is being fixed.

Anyway, I have a different work-around that saves some time over editing the OBJ files. Instead of editing the obj files, the work-around that I found that is working for me is to change the "OBJ Export Options" export setting in Rhino that says "Wrap long lines" and uncheck it to turn it off. That will prevent the "\" that Simplify3D is not parsing corrrectly from being put into the file is the first place. As long as the file is never opened in an application that trims lines that it considers too long there will not be an issue.

[S3D-Chris]

I’m happy to announce that this issue should be resolved now in the latest 4.1 release. Our team successfully tested multiple obj files from threads mentioning this issue with model importing. As you can see from the picture attached, this specific model definitely works in 4.1.0. This was just one of many improvements to the software. All of which are detailed on our Release Notes page.

Thank you for your help reporting this issue!