Maxwell Render | Official public forum

Hey All,

Anyone else experience this??

App = Max
BitmapSize = 2200x2200
BumpMapSize = 2200X2200
SceneSetUp = 16"X16" sheet of Cloth shot with 35MM daylight&Sky Only

Here's the material setup-->

What could be causing this??

If you're using Studio you could try selecting the object and pressing recalc normals in the object params palette, also check if smoothing is set correctly.

Otherwise could you post more info (plugin used, smoothing settings etc...), perhaps also the scene? Does it do the same with just a default material applied?

Hey Mihai,

I am using the 3D Studio Max Plugin.

I am using turbosmooth over a low poly mesh, perhaps this causes problems? I will try your suggestion of going with a basic no-map material I will convert the cloth to editable mesh as well in case turbosmooth is acting up. It almost seems like it's the shadow edge you would see if turbosmooth wasn't on. Though this would be impossible. I'll post the results and scene shots. Thanks!

EDIT:
Ok another test render is finishing up and it isn't having this problem.

Same mesh same everything except the bitmap is much smaller in this case. 250x250 in this case for the bump and color maps. Hmmm... I must investigate more. It would seem we can rule out mesh as the issue. Could the large bumpmap cause issues I wonder?? I may scale it down and see what happens

i get same problem.. even on object such as simple sphere.. my reg bump map was 1024 so i reduced it to 256 and took out the image map and i still get jaggies just like you had.. Im using maya not max.. still trying to figure it out but its very annoying

I haven't had problems with very big bumps, is there anything different besides bump between the two bumpmaps? Could you post a preview of them? Is one of the greyscale and the other RGB format? I mean it could still be black and white, but saved in rgb mode.

One question, Why are you using nd = 1?

jespi wrote:One question, Why are you using nd = 1?

Nd has no affect on Lambertian materials.

Thanks Tom!.

yep Mihai.. always save my bump maps as rgb not grey...
But here is a quick example of the problem..

Torus with 1024 rez bump:



Torus with 256 rez bump.. the jaggies are still there but not as strong jaggies.. and the bump effect is WAY bumpier in sunshine.. same mxm ..same settings..just smaller rez bump map:




Torus with normal map instead of bump.. WAY jagged! (looks diferent cuz has a reflectance color texture image file too):



zip file of my mxm shader and all my image maps.. large and small bump jpg.. also preview.mxs created from maya..

http://lukeroman3d.cbeckleydesign.net/m ... xtures.zip

and in maya i tried to change the geometry nomral smoothing angle from 45 to 60 to 90 to 180.. didnt fix jaggies.. torus has 1800 faces..

any chance you could tell me what i'm doing wrong? with my mxm shader .etc? also tried this on two spheres still got face jaggies..

I didn't think that bump maps will work with a 100% roughness/Lambertian material. There are no specular highlights to show a bump. Perhaps though I'm mistaken.


I've not had this problem. Using Blender, Max & studio. Have had no issues with using 4000x4000 bump maps.

I've downloaded your file and will test on my machine today.

Tim.

Well, I guess this is a more general problem with maps: AFAIK and have experienced, bump map sampling is not using a MIP or SAT sampling, but just the raw map. Kabe

I've been having this shadow termination problem for a while.

I posted a clear illustration of this on the 11th May 2006 - V1 - simple white material - no textures.

http://www.maxwellrender.com/forum/view ... =artifacts

No one from NL ever bothered to reply.

Sad really. Get the feeling they've all got their heads in the clouds and avoiding basic intrinsic problems with the renderer.

Also posted about this problem previously here and here:

http://www.maxwellrender.com/forum/view ... highlight=

http://www.maxwellrender.com/forum/view ... highlight=

wow samsam i missed that may 11th post.. huh.. I guess it still has those jagies no matter how much you subdivided the geo.. so there is no solution.. no reason why som geo does it and others dont..

so there is no solution..

well there is a solution - first you listen. Then you acknowledge there is a problem. Then you take steps to resolve the problem through bug fixing.

NL - Ignoring the issue is not a solution.

samsam, could you post that mxs scene?

Sometimes posts just disappear too fast, it doesn't mean you're ignored and this issue has also been reported several times in the past. If you post the scene I can try and see what is going on. You can generate an mxs with the newest plugin so it opens in Studio.