Sure, optimise… how? If you only have an infinity curve, one object and three emitter planes with HDR image assigned, there is nothing to optimise.
Here is a good example of the many dysfunctionalities that have not been ironed out, apart from the slow CPU rendering speed:
1. Open a simple "photo studio" MXS (infinity curve, three emitter planes)
First bug - opening such a file takes around half a minute from the local disk (why?)
2. Import the object to be rendered as an OBJ from NX, rotate it move into location, look at the automatically created UV set
Second bug - no fixed X, Y grid one can snap to, like in any CAD software
Third bug - position of the projector not zero (why?)
3. Open existing MXM in embedded mode, assign a normal map texture where needed, change rotation and set to metres and 0,1 x 0,1 meter which is the real size the texture represents
Fourth bug - changes in offset, rotation or repeat are not visually reflected in the texture preview image
4. Assign MXM to the OBJ
Fifth bug - co-ordinate of OBJ changes, but not in viewport, often all three co-ordinates change (why?)
5. Check texture parameters with textured decal preview
Sixth bug - changing offset, rotation or repeat is not visually reflected in the textured decal preview (why?)
6. Look at the projector change agreed to before
Seventh bug - projector is placed somewhere in space and with scaling (why? what does that scale signify?)
Eigth bug - 2D grids constantly change in 2D views when zooming in and out instead of a fixed setting to for example 1 mm (why?
7. Start fire to see a first preview to make adjustments
Ninth bug - FIRE takes half a minute to start
Tenth bug - texture is rendered in the wrong direction, not as shown as in the textured decal preview (why?)
8. Change projector from cubic to planar
Eleventh bug - huge planar projector, what does it mean? Texture is 0,1 x 0,1 m real scale as before, no other changes were made
9. Changing rotation of texture or projector and bringing in a second OBJ file
Twelfth bug - FIRE crashes = Maxwell Crashes entirely, without warning
How can one ever work productively with such mayhem?