Bad Point Imports from Space Delimited File

Waterline Endings with Sheer Strake.txt (204 Bytes)

The attached file is normal .CSV but I cannot upload a .CSV to this site. When I read it in, the first point is at

Point at (4635416666671.636,13.271,66.000).

while the file has it at

26.4635416666667 13.2708333333333 66.00

I have found the same problem reading a number of files. This is the shortest example I could come up with.

I get the same problem if I make it comma delimited.

Dunno, the attached is what I get when I import into Rhino for Windows… Looks correct.

WL-Pts.3dm (20.2 KB)

Mac text interpretation (delimiters linefeed/carriage return) is different from Windows, I have had trouble in the past with text files going from one platform to the other. Maybe that’s part of the problem, haven’t got time this morning to test further.


Problem38.3dm (34.4 KB)

I am having the same problem with comma delimited file. The X coordinate of the first entry got changed from 863.5 to 0.5

I do this kind of import with a text file that includes the command, like so:

InterpCrv degree=3

and then use the command ReadCommandFile, ending with Enter


As bigjimslade reported there is a problem when loading point files on Mac, the first point is ignored.
Minimal example:
Import a file with the following points:
0 0 0
0 1 0
1 0 0
1 1 0
You should get 4 points, but Rhino only load 3.

test.txt (23 Bytes)

Hi Romain - Thanks, I see that. Seems to work if there is an empty line at the top of the file…


FYI: This issue should be fixed in the latest RhinoWIP.