mrMaterialAttribs.gup terrorizing my workflow on every step

[alex.motion]

Hi ! 

using max 2019 , that issue appears every time I'm importing xref or adding custom path for textures 

any workaround to get rid of that plugin window appear every time ? 

[Anonymous]

Open scene converter, (Corona users), pick up the Coronarenderer from the list and add a new rule in the left window below, under materials /mrmaterials/remove mrmaterials from the scene and convert. I am afraid you will need to do this every time when opening another old scene. But if you plan to work on one scene for longer than you will not be forced to see this annoying message every time.

[gronchik]

Hello! Those errors, that we love very much, happen due to the fact that old versions of files are not supported in the new version of the program. Yes, and the converter solves this problem, but no one here considered the material libraries that are loaded with the material editor - this is the main mistake, since they are considered a separate file. The solution is as follows:
1. Create as many objects in the scene as there are materials in the library and drag materials from the library onto these objects.
2. Save this scene and restart 3ds max and reopen this scene so that the converter clears it of unnecessary plugins.
3. Select all objects in the scene, go to the material editor and press Alt + G (all materials in the scene will move to the current view), and then create a new library of materials and drop the materials that we need into it.
4. Save the library of materials and rejoice!
Best reguards!

P.S. I apologize for my English, I hope everyone understood what to do.

[Anonymous]

---

@gronchik wrote:
 Save this scene and restart 3ds max and reopen this scene so that the converter clears it of unnecessary plugins.

---

as some have mentioned this happens with new scenes too, scenes that did not use any MR materials etc.
in my case it is a new windows installation, a fresh 3d max 2021.3 installation.

whenever i try to send a sigershader material to the material editor i get an error message:

https://i.imgur.com/Di0Zbu3.png

basically the same installation on a different PC just with 3dmax 2020 instead of 2021 works fine.
i doubt that sigershaders are to blame here.

is autodesk having fun with us?
this error is now a year old and is still not fixed. 😞

the advice to uninstalls 3d max is a sad joke. my installation is 3 hours old.
i think the coders at autodesk have no clue how to fix this. otherwise it should have been fixed after... what.. 18 month now?

[RichardWoolsgrove]

Is there a way to supress the missing dll dialog?

this would solve the problem for me. Some files have multiple Xrefs meaning you need to click Open on the dialog 20+ times on open a single file.

the render seem fine with missing dlls, its just the warning that is the problem.

Richard

[dennis]

Ok add me to the list. I've never used MR, always vray, and I don't want to go through converting files, which frankly makes me nervous. This seems to be something that Autodesk should be fixing, not us.

[RichardWoolsgrove]

I found if you run this line of script it will suppress warnings during the current session of Max.

SetQuietMode On

This can be added on start up but do that with caution as it suppresses all warnings and some you might need to know about.

[dennis]

Thanx, as you say that is an option, but not really the best. I'm no coder, but it seems to me that some smart Autodesk guy could solve this in an hour. They could do something like other software where you're given the option "not to show this warning in the future."

[RichardWoolsgrove]

I agree.

It's very annoying. We didn't even use mental ray but it is totally embedded in all our files. The scene converter tool is simply not fit for purpose for updating thousands of files across a newtork.

It has nor been thought through and not tested in the the real world.

Hoping for a fix from Autodesk!

[jon.bell]

Hi @RichardWoolsgrove and @dennis ,

This article explains how to turn off these warnings and/or automatically remove legacy mental ray elements.

In addition, you can set the Scene Converter to batch-convert all Xrefs or other 3ds Max files in a folder. (Please see the screenshots in the article above.)

If you have any other questions, please let us know. Thanks!

[yann.terrer]

Hi i've the same issue here.

the solution works but the woindow comes back every time i re-run 3ds max and worst it loses all the custom material library i created.

i don't Use mental ray neighter, i' m on Corona.

is there anyone in Dev team to solve that problematic issue?

thanks

[gandhics]

Use 3dsMax 2022.1+, you will never see this popup.

[yann.terrer]

Hi,

If i have to re-install  a recent version of 3Ds max  + all the pluggins for my workflow for something (a bug)  that didn't exist in previous versions, it is very annoying.

I'm sorry to say that. i'll see if it deserves a complete re-install.

Thank you for this answer.

Best Regards

[RobH2]

Yea, the issue has been eliminated with the recent versions of Max. I know that does not ease frustration with the version you have but it's the reality of software these days. Sometimes it's just not possible to solve all bugs for older versions of software.

[gandhics]

This is not a bug. Max is doing what it is suppose to do, letting you know MR doesn't exist anymore and you have MR data in your scene. You can choose to clean up the scene file with Scene Converter, too.

[RobH2]

Not that it really matters much at this point what it is called, I do think there is some small bug in a script or piece of code somewhere. Even with doing every mitigation task (including Scene Converter over and over), multiple times, it kept coming back and terrorizing me. If there wasn't a bug or fault or something, and after stripping all references to MR, the component that was detecting MR and reporting it should give up. For me at least, it never gave up and only new versions of Max solved it for me. 

[gandhics]

Well.. you need to clean up all sources such as xref and material library. If you want to merge something, you need to clean up the merge source. That's why it is simply skip to display now, you can actually choose to ignore anything with script. But, since it is a new feature, you need to upgrade to use it.

[dennis]

As irritating as this problem was, there have been far worse ones. It's nice that they've sort of fixed it - it may just be me, but it does seem that Autodesk has gotten somewhat better with fixing these small issues. I'll take what I can get 😉

[barigazy]

This will be example ie. easy fix if you have some old materials libraries which shows this annoying message every time you load them in Material/Map Browser.

fn fixMtlLib mlib_Path: suffix: =
(
	if not doesFileExist mlib_Path then messagebox "This Material Library not exists!" title:"Warrning" beep:off else
	(
		with redraw off
		(
			local mlpath = getFilenamePath mlib_Path, mlname = getFilenameFile mlib_Path, new_ml = mlpath + mlname + suffix + ".mat"
			local missingLegacyAssetsNames = #("mental ray: material custom attribute"), newLib = materialLibrary()
			local tempLib = loadTempMaterialLibrary mlib_Path
			local arr = (for i = 1 to tempLib.count collect (s = sphere() ; s.material = tempLib[i] ; s)) --; select arr
			SceneConverter.RemoveMissingLegacyAssetsFromScene missingLegacyAssetsNames
			for i = 1 to arr.count do append newLib arr[i].material ; delete arr
			saveTempMaterialLibrary newLib new_ml
		)
	)
)
-- example - this is my old VRay CarPaint library. 
-- use diferent file path and add suffix just to avoid any override
fixMtlLib mlib_Path:@"d:\grayroom\GR_Materials\CarPaints.mat" suffix:"_FIX"