[j_man]

Known issues and bugs for V1

Please post if you think any of these are incorrect or if I've missed something.

Known issues: - and possible work arounds!

1/ MXM Materials
- do not retain their names when re-loaded from a file. - the name of the MXM is still visible in MXM slot but you cannot read in the get from scene dialog. Material previews work in the material browser if they're loaded in the material editor.
- do not copy from one slot to another (MXM reference lost)
- cannot be put into a library (all MXM reference and name lost)
- previews do not re-load with max file

2/ Plastic - use an MXM instead!
- textures do not export to studio - rebuild material in studio

3/ Maps
- don't display in the viewport - preview with a standard material, use scenestates to switch between standard and maxwell materials - thanks Robert Cervellione
- don't render correctly (ie rotated) - use unwrap UVW

4/ Memory leakage / Memory release issue.
- Constandly re-sending from max increases memory usage http://www.maxwellrender.com/forum/view ... hp?t=14528

5/ Double click on material preview
- Double clicking on the material preview causes a crash on some configurations, or installations. - Don't do it! < :

6/ Glare doesn't work with multi-light
- it's a maxwell thing. - Choose one or the other.

7/ Memory Leak http://www.maxwellrender.com/forum/view ... hp?t=14528

[michaelplogue]

Please add: Memory leakage / Memory release issue.

http://www.maxwellrender.com/forum/view ... hp?t=14528

[val2]

don't double click the map slot image. it will crash MAX.

[carlos@cmarquitectura.com]

load mxm marerial. or aply mxm marerial from editor it will crash MAX (not ever). Sorry for my bad englis

[j_man]

don't double click the map slot image. it will crash MAX.

hmmm, this doesn't seem to be a problem for me. I even get to see the preview of the material.
Maybe it's your system spec?




J¬

[casey]

Possible new bug: I get all black images if I use a Maxwell free camera instead of a target camera. Toggling to target camera makes everything work perfectly. Toggling back goes back to black.

Anyone else encounter this?

- Casey

[vansan]

The scene scale is transferring incorect to mxcl, when I hit render, if it's not "meters". I made this conclusion because the intensity of lights were very little while working with mm, so i had to "rescale world units" with the 0,001 value. It's very sad...

[casey]

The scene scale is transferring incorect to mxcl, when I hit render, if it's not "meters". I made this conclusion because the intensity of lights were very little while working with mm, so i had to "rescale world units" with the 0,001 value. It's very sad...

In the interim, I have been using this MAXScript function to set the scene scale properly. Unfortunately, the Maxwell renderer does not support MAXScript access to any of its variables as far as I can tell, so the script can't set the scale automatically, you have to see what it prints out and paste it into the box manually.

Also, it seems like the edit box for the scene scale is way underprecise. For example, you can't enter something like .0023252 or whatever, it just truncates to .003. It would be nice if this was more precise.

Code: Select all

fn GetUnitsPerMeter =
(
    return (UnitsPerMeter = 1.0 / (units.decodeValue "1m"));
)

- Casey

[j_man]

Hi Casey,

That's a useful script. I've adapted it for use as a macroscript. i hope you don't mind. If you PM me your correct details I'll add them to the script title if you like. Oh, and I haven't experiemented but changing the spinner precision in max's options might improve the maxwell units spinner accuracy.

-------------------------------------------------------------------------------

This script is a calculator, it doesn't change any settings for you. You need to place the returned value into the render settings ¦ scene scale spinner.

http://scripts.joshuanewman.net/downloa ... nitsV1.zip

Script installation:

First of all, either copy the script to your UI/macroscripts directory, and re-start max OR drag and drop the script into the max viewport.

customize ¦ customize user interface

Choose the 'toolbars' tab,
From the 'category' pull down menu, choose 'maxwell'

Now drag the 'convert system...' to a toolbar of your choice.

J.

[jamsurf]

And it seems that there is no posible to overwrite a mxs file .
if launch render on max with the same mxs name of previous render ,
dont overwrite and give fault . No render .