Ply ASCII
Forum rules
Please upload a testscene that allows developers to reproduce the problem, and attach some images.
Please upload a testscene that allows developers to reproduce the problem, and attach some images.
Re: Ply ASCII
Morning Dade, it complains of a
error, the same file loads into LuxRender
If I convert the Ply to binary with meshlab it'll then load into luxcore, but that's not practical on a proper scene
here's the file its an export from su2lx
Code: Select all
Ply: Not a PLY file. Expected magic number 'ply\n'
If I convert the Ply to binary with meshlab it'll then load into luxcore, but that's not practical on a proper scene
here's the file its an export from su2lx
- Attachments
-
- cubetest.rar
- (6.49 KiB) Downloaded 134 times
Re: Ply ASCII
I think I've already met this problem time ago, it's because your ASCII file has Windows-style line breaks (CR+LF) instead of Unix-style (LF only). Our ply import code is probably an old version that understands only the latter.nigec wrote: ↑Tue Mar 19, 2019 7:20 am it complains of aCode: Select all
Ply: Not a PLY file. Expected magic number 'ply\n'
Has your file been exported directly in that way, or have you manipulated it with a text editor? That could have corrupted it.
As another workaround, you could open it with a text editor able to handle both end-of-line formats (e.g. Notepad++) and convert to the Unix format.
Re: Ply ASCII
The Ply file is what the plugin exported, I haven't opened it with anything else
So basically I've got to get the plugin to save LF only
So basically I've got to get the plugin to save LF only
Re: Ply ASCII
Fixed it
I just had to change a write option in the exporter script..
Next to figure out why its exported scene is insanely bright, I've noticed the classroom example in the SDK does the same
I just had to change a write option in the exporter script..
Next to figure out why its exported scene is insanely bright, I've noticed the classroom example in the SDK does the same
Re: Ply ASCII
Check tone mapping, the script may assume auto-linear tone mapping or, if you are using LXS parser, some setting may be not translated
Re: Ply ASCII
The ISO, shutter speed, F Number settings aren't exporting from the plugin, for some reason the settings dialogs aren't updating..
But anyway, I can set those manually so its not a massive issue, I need to find a Ruby guru lol
But anyway, I can set those manually so its not a massive issue, I need to find a Ruby guru lol
Re: Ply ASCII
The camera location/direction isn't translating either..
Re: Ply ASCII
But it is a LuxCore LXS parser problem or an export script problem ?