[JTB]

A. MXST, MXCL, MXED
- I would like to be able to have the complete image with physical sky and sun and the alpha image too with one rendering....
- I would like to be able to preview HDRIs when selecting them for image based environment
- MXST should be able to handle instances without delays and freezing when selecting objects or panning or... well, it happens almost everytime... (Still to test with more files)
- I would like to have Xrefs with Studio.
- I would like to have MXST as a normal windows application with the same shortcuts, ease of selecting, rotating, moving etc objects as there are hundreds of 3d apps. I feel there is too much effort for something so common... Maybe I'm wrong, as a customer, I just want what's easier for me
- MXED should be very much improved. Windows should be resizable and a material archiving has to be added ASAP.
- A material should have only one name, the name of the file... The name of the material has no meaning... because there is no point having two materials with identical names. Change the smallest thing (roughness for example) and you will have a new material, so you add a new param to the name. Why do we need the material name?
- MXST should confirm all overwrites and exports and deletions before doing any (MXS,images, MXI)
- MXST should be more stable.
- MXCL should be able to show MXS when opened.
- Realistic sky and sun model. The night sky is completely wrong now. (Yellow).
- Whatever core improvements can be made for dielectrics, caustics and SSS.
- Complete handling of cameras and camera targets as objects.

B. PLUGIN (Max)
- Fix instances problems when using Revit->DWG->MAX files.
- Update preview only once,only when change a param of the material, not when I double click and zoom or change the number of mat slots.
- When changing a material by importing one from the library, the name seen at the material editor must not change but we should be able to see the name of the imported file too...


I will probably add something later...

[Bubbaloo]

I would like to be able to have the complete image with physical sky and sun and the alpha image too with one rendering....

What will you do with the alpha?
Have you tried using the alpha on a gradient sky?
It's not pretty.

I would like to be able to preview HDRIs when selecting them for image based environment

I second this one. It would be nice. I always have to open it in hdrshop to preview it first.

[JTB]

@Bubbaloo : About the alpha image...It is not important, but it would save time. Some of my clients are happy with a simple sky as background, some want to add a photo, I usually don't know what they want until last minute.... I would prefer to have a complete image and an alpha channel with one rendering... I know that I can render alpha channel alone as a second pass but I 'd prefer not to if possible... That's all.

[pipcleo]

- MXST should confirm all overwrites and exports and deletions before doing any (MXS,images, MXI)

this should be a given with any software

[JTB]

Now that most of the plugins are updated, I guess NL will go back working on MXST,MXED,MXCL so let's add some things we need...

I want to repeat my wish for a better MXED.

Also, although the plugin is much better with the last update, I think that the actual MXM name should be added (even a path would be nice) so that we always know which we loaded.