Maxwell Render | Official public forum

The first image was created with version 3.0 of Maxwell in my render farm:
CPU type: 10*X5650 + 1*E5-1650
Sampling level reached: 20
Computing time: 6h3m
Image Resolution: 2520x1800px
(the image was post produced)

The second image was calculated with version 3.1 of Maxwell in MacBook Pro:
CPU type: i7 2.5GHz
Sampling level reached: 12
Computing time: 5h18m
Image Resolution: 2520x1800px
(the picture was not produced post)

I wish I could end up rendering with version 3.1 coming to SL 20, to have a better comparison on caustics, because at the present version 3.1 of the caustics seem much cleaner compared to version 3.0.
The only problem is the external references, do not come loaded altogether when instantiated, most likely because they are .mxs written in version 3.0.

http://adobe.ly/1CMiiZk

http://adobe.ly/1vmeyx4

where are the images ?

seghier wrote:where are the images ?

the two imamgine are the following links:
image 1:http://adobe.ly/1CMiiZk
image 2: http://adobe.ly/1vmeyx4

links now work but can you put them directly here

seghier wrote:links now work but can you put them directly here

fact

But what is this comparison about?

i had the same problem with mxs reference with 3.1 beta . i don't tried with the new version

Mihai wrote:But what is this comparison about?

the comparison relates how it behaves version 3.1 of Maxwell with references and references istaziate saved 3.0

Did you modeled it in Max?
I have such problem even in maxwell 2.7.4 (if create instance and move it). If i reset xform object is in right place. Check in your mxs file where is your model:)

I hope it helps

arch3d wrote:Did you modeled it in Max?
I have such problem even in maxwell 2.7.4 (if create instance and move it). If i reset xform object is in right place. Check in your mxs file where is your model:)

I hope it helps

I use Maya on Mac OSX

I see, I thought you ment to look at performance/caustics. I think this bug with instanced MXS references has already been fixed and will be out in a new beta very shortly. In the mean time I guess don't instance the MXS refs, simply copy them instead. In your case it won't make much difference in terms of memory use anyway. Using instances of MXS References makes sense if those referenced scenes have huge poly counts. If not, then copying will achieve basically the same thing as "instancing" since if you change that referenced scene - all your references will change also.

Mihai wrote:I see, I thought you ment to look at performance/caustics. I think this bug with instanced MXS references has already been fixed and will be out in a new beta very shortly. In the mean time I guess don't instance the MXS refs, simply copy them instead. In your case it won't make much difference in terms of memory use anyway. Using instances of MXS References makes sense if those referenced scenes have huge poly counts. If not, then copying will achieve basically the same thing as "instancing" since if you change that referenced scene - all your references will change also.

The performance of caustics is one thing that I noticed at a later time, and caustics of version 3.1 really seem best, but I have to be able to bring this file /".mxi "SL20 in order to have a more accurate comparison.

arch3d wrote:Did you modeled it in Max?
I have such problem even in maxwell 2.7.4 (if create instance and move it). If i reset xform object is in right place. Check in your mxs file where is your model:)

I hope it helps

you can modify position ( and scale ) when you open mxs reference in studio to x,y,z : 0,0,z