Ply ASCII

Use this forum for general user support and related questions.
Forum rules
Please upload a testscene that allows developers to reproduce the problem, and attach some images.
User avatar
nigec
Posts: 141
Joined: Mon Mar 11, 2019 8:50 am

Ply ASCII

Post by nigec »

Is it possible to load ASCII Ply files?
User avatar
Dade
Developer
Developer
Posts: 5672
Joined: Mon Dec 04, 2017 8:36 pm
Location: Italy

Re: Ply ASCII

Post by Dade »

nigec wrote: Mon Mar 18, 2019 7:12 pm Is it possible to load ASCII Ply files?
Yes, LuxCore supports both binary and text format.
Support LuxCoreRender project with salts and bounties
User avatar
nigec
Posts: 141
Joined: Mon Mar 11, 2019 8:50 am

Re: Ply ASCII

Post by nigec »

Morning Dade, it complains of a

Code: Select all

Ply: Not a PLY file. Expected magic number 'ply\n'
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
Attachments
cubetest.rar
(6.49 KiB) Downloaded 134 times
acasta69
Developer
Developer
Posts: 472
Joined: Tue Jan 09, 2018 3:45 pm
Location: Italy

Re: Ply ASCII

Post by acasta69 »

nigec wrote: Tue Mar 19, 2019 7:20 am it complains of a

Code: Select all

Ply: Not a PLY file. Expected magic number 'ply\n'
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.

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.
Support LuxCoreRender project with salts and bounties

Windows 10 64 bits, i7-4770 3.4 GHz, RAM 16 GB, GTX 970 4GB v445.87
User avatar
nigec
Posts: 141
Joined: Mon Mar 11, 2019 8:50 am

Re: Ply ASCII

Post by nigec »

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
User avatar
nigec
Posts: 141
Joined: Mon Mar 11, 2019 8:50 am

Re: Ply ASCII

Post by nigec »

Fixed it :D
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
User avatar
Dade
Developer
Developer
Posts: 5672
Joined: Mon Dec 04, 2017 8:36 pm
Location: Italy

Re: Ply ASCII

Post by Dade »

nigec wrote: Tue Mar 19, 2019 9:40 am Fixed it :D
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
Check tone mapping, the script may assume auto-linear tone mapping or, if you are using LXS parser, some setting may be not translated :idea:
Support LuxCoreRender project with salts and bounties
User avatar
nigec
Posts: 141
Joined: Mon Mar 11, 2019 8:50 am

Re: Ply ASCII

Post by nigec »

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
User avatar
nigec
Posts: 141
Joined: Mon Mar 11, 2019 8:50 am

Re: Ply ASCII

Post by nigec »

The camera location/direction isn't translating either..
User avatar
Dade
Developer
Developer
Posts: 5672
Joined: Mon Dec 04, 2017 8:36 pm
Location: Italy

Re: Ply ASCII

Post by Dade »

nigec wrote: Tue Mar 19, 2019 2:42 pm The camera location/direction isn't translating either..
But it is a LuxCore LXS parser problem or an export script problem ?
Support LuxCoreRender project with salts and bounties
Post Reply