feature requests

[patro]

are you working on your own 100% exporter version?

[hedphelym]

yes ( But will ofcourse be share freely in the repo).
but I can reuse all the current lights \ materials that I've made for luxmax up until this point. (this is because this part of it is maxscript too).

I think this will help greatly in the development, because it's much easier to work directly in maxscript then what it is in c++.

[patro]

c++ isn't much important.....
important is finally to have a working exporter... that gives no problem

[hedphelym]

yes,
and this makes it much easier to implement things that's been missing...
object \ camera transformation for motion blur.
batch export of each frame so that you can render animations.
rendering directly in 3dsmax
export of geometry and textures to separate file (enables you to export "no geometry" but only settings and shaders) for quicker updates.

+ many more things.

I will write it to the current "Luxmax standard" and then do a release of the new maxscript version.
Then you all bugtest everything, then I continue to implement missing features.

It takes some time to write it, but I've already got a long way today.

I honestly think this is the correct way to do this now, since the c++ brings so many pitfalls.

[Lord Crc]

If it's possible to determine in maxscript if an object was changed since last export, then you could f.ex. export one file per mesh, and when re-exporting only replace the files for the meshes that have changed. This could potentially speed up exporting big time. Unfortunately blender does not have this capability, and I have no idea if max has. Would be neat though

[patro]

that's a kick ass idea

don't know if it's possible but Stig know probably the answer!
I think that a work around could be to add a "merge" function to the exporter ui combined with "export only selected" function
but I don't know if it's possible... but nice idea

[hedphelym]

If it's possible to determine in maxscript if an object was changed since last export, then you could f.ex. export one file per mesh, and when re-exporting only replace the files for the meshes that have changed. This could potentially speed up exporting big time. Unfortunately blender does not have this capability, and I have no idea if max has. Would be neat though

this is possible, I can add a "callback" that notifies each time a node is changed.
Then these objects get's added to a array, which then get's exported.

Right now it exports all objects in scene by adding them to an array if they are not hidden.
Just add a checkbox with "export changed only" then replace array with the one containing changed objects.

I'll keep this one in mind, I'm coding some more later today.

[hedphelym]

Hi again everyone.

I've been working on the script today.

The best part about this is that I can keep all the current materials that we use, all the lights,
and all the settings is still "per camera".

The only thing so set in the UI is the output size and file to render to. (for now).
The rest is just like normal.

I've also added a working progressbar

luxmax_maxscript_exporter_gui.jpg (35.79 KiB) Viewed 146 times

The geometry (mesh) is already exporting.
the next is to add all the script for parsing all the camera options.
As soon as this is done I'll finish the material parsing.

[hedphelym]

the camera transformation now works. ( took a while).
Next up is to finish support for all the materials.

When the first release is out I'll start a new "Feature request" (might be named something else), so
that I can keep track on what's relevant for the new exporter..
Pictures will be posted as soon as I've got something cool to show.

[patro]

you need a funny name for your exporter!

what do you think about

LuxAtleMax

so to have:
LuxAtleMax release topic

LuxAtleMax feature request topic