[3dtrialpractice]

Hi, I wanted to start a list to let the mayall Developers have a Single clear Post of what we need fixed in mayall (based on that mayall's released date) -would love for this to be a sticky..

So please respond to this post with ONLY bugs or suggestions for additions to mayall v1... Ill Edit this First post as a growing list.. adding/removing suggestions.. untill the next mayall is released...
LIST:

-BUG: the way zchannel renders is based on world Z --Not camera Z.(so z can look sideways if camera points down x-axis)

-BUG: upon loading a mayall previously saved scene the command line values are blank in there respective fields.. yet upon render command line values may still apply

-BUG: draging and droping MXMxm shaders from MXED sets the path backslashes"\" as Slashes"/".. Causing maya not to find the correct path to the shaders/textures/images.. (Only way to specify the correct shader is manually click "mx" button in set path field and navigate to the correct file-or flip all slashes to backslashes-.. copying and pasting from one field to another also seems not to recognise file in maya?)

-Missing: mayall info still reads 0.9.1(beta)

-Missing: maxwell menu "help" missing mayall.doc

-Missing: addition of offset and rotation to HDRI controls in Maxwell Environments attributes

-Missing: intensity setting for physical sky (so you can control sky intens w/o loading -ml )

-Missing: there is no setting in objects or shaders attributes that allows us to "hide from camera" like one can in studio -so that object is hidded yet its shadows and reflections still remain in scene
also would be wonderfull to have hiden to camera objects as shadow catchers.


--------------------------------------------------------------------------------
-may5th: UPDATE: mayall for maya 6.5 released(maya6.0 may not be supported?)

[renbry]

BUG: mayall batch render writes out sequences of .mxs files respecting the frame increment value (nth frames) but auto batch file creation doesn't respect nth frame rendering. (eg 1-200 on 10's produces a batch file with 1-200 including EVERY frame in between)

BUG: mayall batch render file doesn't write out .mxi files with frame increment

Missing: to be able to command line request frames 1-200 and for mxcl.exe automatically find frames/mxs files in the case of rendering on nth frames.

BUG:major problems with exporting in batch, a sequence which contains a complex rigged character. Mayall error resulting in only one frame exported. Seems like it doesn't travel to the next frame the same way as a regular frame advance and therefore doesn't update expressions etc.

[ludenhud]

-Missing: Able to "roll" the camera as you're able to do in studio

-Missing: Texture support for the viewport

[Takumi Takahashi]

V1.0, mayall 0.9.1 Clipmap error:

When rendering from within Maya, or exporting to mxs format resulting in :Can't attach bitmap error.

I need to delete the material and recreate mx material and reassign in order to alleviate this problem.


... or am I missing something ?
(a file path is specified with backslash convention, and using tga or tiff format so they shouldn't be a problem)

[Takumi Takahashi]

Animation only accepted by Maxwell at 24fps currently (alpha - V1.0).

I am sure we have non-film based users who prefer to work in 25fps/30fps etc. and this gets critical later on. (It also gets really annoying if the frame extensions coming out with a decimal point)

[Takumi Takahashi]

It would seem to me, to be a good idea to complete plug-ins for the already existing supported platforms and get them to a point where they are usable before making the plugin for other apps.

Just my thoughs...... as I do not use Maxwell at all right now for the very reason of poor texture support, no Nurbs and no only 24 frame/sec control.

Anyone else out there feel my pain!?

diego, I hear you and very sad that the NL's maya plug-in support seemed to be dead right now.

Especially I feel very much neglected for clip map problem since I am writing MEL to automate some cumbersome workflow of Maya to M‾R, and can't cope with it alone - I always end up using M‾R studio to readjust my material, adding up my production time uneccesarilly.

Why can't we have V1.0 Maya plugin with the minor fix !? (not beta 0.9)


... eagerly waiting on V1.x with updated Maya plug.