Maxwell Render | Official public forum

I can't understand this! How is it possible!
I just updated Revit to the last build and I have problems with Maxwell, some objects don't show, some other objects change position!
I had this problem in the past but as I remember it was fixed with a re-installation of Maxwell... Today I have re-installed all three apps but the problem is here!
I tried this to my other PC that still has the older Revit build and nothing changes...

Objects having strange positions or don't show at all is because of instances. Check this: http://www.maxwellrender.com/forum/view ... hp?t=26318
When in the past did you have this problem? The instances issue with imported scenes exists with the introduction of instances, and that's Maxwell 1.6.

Bogdan Coroi wrote:Objects having strange positions or don't show at all is because of instances. Check this: http://www.maxwellrender.com/forum/view ... hp?t=26318
When in the past did you have this problem? The instances issue with imported scenes exists with the introduction of instances, and that's Maxwell 1.6.

Nothing to do with that, I have problems with both my PCs and I think it has something to do with Automatic updates of XP, graphics driver, etc...
I will send you some screenshots, I am talking about walls, floors etc, no instances, you won't even recognize the building!
sCANLINE

Maxwell

Maxwell 2 days ago

And if you uncheck "Use instancing" like I mentioned in the above link, and hit render, it doesn't render correctly?

PS. I'm asking you again about the "Use instancing" check, because I'm willing to bet the problem has nothing to do with XP updates or any sort of drivers.

You're right! It works when I uncheck "use instancing" !!!

My god, I lost so many hours, trying things... But, why is this happening?
I mean, why did this happen now? I rendered the last image on 3 of Dec so I think I rendered with 1.6 and everything was ok!

PS. I forgot to say how much surprised I am geting an answer from you on Sunday....

When importing scenes from Revit or VIZ, 3dsmax is creating the geometry to be rendered by using instancing and different modifiers. The funny rendering happens mainly because we haven't found a way yet to deal with some modifiers used on instanced geometry. So until we find a way, we provided the "Use instancing" check. This was not a problem with 1.5 since there was no instancing.

PS. I've given Sunday replies in the past too.

Bogdan Coroi wrote:When importing scenes from Revit or VIZ, 3dsmax is creating the geometry to be rendered by using instancing and different modifiers. The funny rendering happens mainly because we haven't found a way yet to deal with some modifiers used on instanced geometry. So until we find a way, we provided the "Use instancing" check. This was not a problem with 1.5 since there was no instancing.

PS. I've given Sunday replies in the past too.

But my problem is that it is not the first thing I did with 1.6, so I don't understand why I didn't see this with my previous tests... Anyway, thanks, and please find a way to deal with this stupid MAX behaviour. If the problem is in Max there is nothing I can do... What if I use AutoCAD? I mean, import the dwg, export as dxf, import again, save again... can this eliminate the strange geometry issues? I mean, no matter how DWG has created, MAX uses instancing when I import a dwg? So, I will make some tests and see what happens

I have had the same problem, because after reinstalling, you loose the settings and the default is to "use instances".
I have suggested offline to change this and make the box unchecked as a default and/or deliver a "Revit-Preset" like there are mental-ray presets etc.
Anyway, I have done this myself: set everything the way it will work for Revit and safe the settings as a preset: this saves many hours of guessing, because you will have a safe starting point.
(It just hit me again yesterday, when I moved a scene onto another machine, where I have the installation only visible to the Administrator (another thread, unanswered), and all settings had to be re-established)

JTB: You didn't see it in your previous tests because "Use instancing" check is enabled only on new scenes, created with 1.6 plug-in. Scenes made with 1.5 version of the plug-in have it set to unchecked by default.

What if I use AutoCAD? I mean, import the dwg, export as dxf, import again, save again... can this eliminate the strange geometry issues?

I haven't tried it, but I assume not. To fully eliminate it, you have to tweak the modifiers and geometry, but this isn't a solution, don't waste your time. We'll try to find a workaround.

Bogdan Coroi wrote:JTB: You didn't see it in your previous tests because "Use instancing" check is enabled only on new scenes, created with 1.6 plug-in. Scenes made with 1.5 version of the plug-in have it set to unchecked by default.

What if I use AutoCAD? I mean, import the dwg, export as dxf, import again, save again... can this eliminate the strange geometry issues?

I haven't tried it, but I assume not. To fully eliminate it, you have to tweak the modifiers and geometry, but this isn't a solution, don't waste your time. We'll try to find a workaround.

Thanks, I 'll go back to work then...

40% SOLVED!!!

1. EXPORT FROM REVIT
2. FILE LINK IN MAX
3. EXPORT TO DWG
4. FILE LINK IN MAX

Check this image, it's working.

Geometry:
- Num Meshes: 13
- Num Triangles: 89303
- Num Vertexes: 102578
- Num Normals: 102053
Render settings:



Downside... The "export to dwg" step, creates objects as layer names so you will have to be careful with the layers you use for exporting from Revit... Of course you can always use modifiers like edit mesh to assign materials to subobjects

Turning off "use instances" does solve the problem of Revit created geometry jumping when you render it in Maxwell. It renders fine with Mental Ray and Scanline. Render great when you turn off "use instances". Bug.

andrebaros wrote:Turning off "use instances" does solve the problem of Revit created geometry jumping when you render it in Maxwell. It renders fine with Mental Ray and Scanline. Render great when you turn off "use instances". Bug.

Yes, Max bug. We've explained in a couple of other places that this is a Max bug. It works with Scanline because Scanline doesn't know about instancing. It works with mental ray because somehow they manage to figure out when "bad" objects are encountered and turn off instancing on them. We don't know how they detect that, it's not documented (the mental ray plug-in is written by Autodesk, they know but won't share) so you have to turn off instancing manually.

Not worry!

This is a ADesk problem, same as DWG.