PDA

View Full Version : lwo3 importer -> open source



tischbein3
01-04-2018, 05:47 AM
this one:

https://www.lightwave3d.com/assets/plugins/entry/lwo3-loader/

make it open source, so other can integrate the new lwo3 file into their projects.
One of the reasons there was / is a wide support to lwo was that it had their loader
aviable as source and documented.

gar26lw
02-07-2018, 07:50 AM
hope this happens

jwiede
02-13-2018, 09:04 AM
Yeah, this needs to occur ASAP, and ideally with a BSD or equivalently-permissive license.

daforum
02-15-2018, 02:36 PM
this one:

https://www.lightwave3d.com/assets/plugins/entry/lwo3-loader/

make it open source, so other can integrate the new lwo3 file into their projects.
One of the reasons there was / is a wide support to lwo was that it had their loader
aviable as source and documented.

Will the lwo3-loader work with much earlier versions of LW?
Or maybe i should ask, what versions of LW will the loader work?

daforum
02-18-2018, 11:34 AM
Does anyone know if it does or not?
Thanks

UnCommonGrafx
02-18-2018, 01:21 PM
Theory: it works based on the new engine, therefore, no.

Bill Carey
02-18-2018, 04:36 PM
Will the lwo3-loader work with much earlier versions of LW?
Or maybe i should ask, what versions of LW will the loader work?

It doesn't work with 9.61 32bit. Says the loader failed to load.

daforum
02-22-2018, 06:13 AM
Theory: it works based on the new engine, therefore, no.

Thank you for the info UnCommonGrafx


It doesn't work with 9.61 32bit. Says the loader failed to load.

again, thank you for the info Bill

gar26lw
02-22-2018, 06:24 AM
x64 only?

jwiede
02-23-2018, 06:02 PM
x64 only?

I suspect so.

jwiede
02-23-2018, 06:08 PM
Theory: it works based on the new engine, therefore, no.

Really shouldn't matter, it's back-porting LWO3 into older versions in the first place, so it isn't like ANY older versions have the new engine.

As gar26lw noted, I suspect the main issue for back-compat. is due to it being a 64-bit plugin (and LWO3 is a 64-bit-native format, IIRC).

Myagi
02-25-2018, 05:16 AM
The SDK documentation has a full format description of LWO3, assuming it is accurate, just like it has had for the previous formats. I always assumed that documentation was the reason why LWO had wide support, that it was a well documented format. Over the years, or rather decades *shudder*, I've whipped up a couple of LWO readers, and at least for me it was always based on the format documentation.

Going by the doc there is not a single 64-bit data type in LWO3 (not even double floating point vals) so there shouldn't be any 64-bit requirement dictated by the file format.

gar26lw
02-25-2018, 06:23 AM
The SDK documentation has a full format description of LWO3, assuming it is accurate, just like it has had for the previous formats. I always assumed that documentation was the reason why LWO had wide support, that it was a well documented format. Over the years, or rather decades *shudder*, I've whipped up a couple of LWO readers, and at least for me it was always based on the format documentation.

Going by the doc there is not a single 64-bit data type in LWO3 (not even double floating point vals) so there shouldn't be any 64-bit requirement dictated by the file format.

what apps were the readers for?

Myagi
02-25-2018, 07:45 AM
Oh, not for other regular 3D apps in my case, but readers/importers in my own projects (3D engines and tools).

jwiede
03-13-2018, 09:51 PM
Going by the doc there is not a single 64-bit data type in LWO3 (not even double floating point vals) so there shouldn't be any 64-bit requirement dictated by the file format.

That doesn't sound right, are you sure you're not looking at the prior version?

Myagi
03-14-2018, 01:43 PM
This document describes the LWO3 file format for 3D objects used by LightWaveŽ. The LWO3 format is new for LightWaveŽ 2018.

Considering that memory addresses aren't saved into files in general, I'd be hard-pressed to think of a reason for a file format to require a 64-bit host process. Of course a file format can be of such nature that it can support holding so much data, that a 32-bit process wouldn't be able to load it. But as long as we're talking about lwo files that aren't so large that it runs into the mem barrier of 32-bit processes, there should be no technical hindrance (of course aside from surfacing not being identical to 2018).

The doc also summarizes the changes as follows


The main difference is that LWO3 is fully 32bit with proper nested forms, instead of the 16bit subchunks in LWO2. The new shading system in LightWaveŽ 2018 has also significantly changed the data in surface blocks

so basically they just removed 16-bit limitations of certain chunks, and updated the surface info to reflect the changes in 2018 surfacing.