ColladaMax.dle failed to intialize - oFusion Pro problem?

Hello,

I posted this problem as an oFusion Pro support ticket, but 1) I'm not sure how fast that will take to get addressed (I've not had the Pro version long), and 2) I could really use an answer fast - I've got to meet with team members tomorrow.

Here's the problem, from the ticket:

"I recently purchased oFusion Pro. Soon after installing it, I opened Max 9, opened the material editor, and clicked the "get material" button (the icon with the arrow and blue sphere). At this point Max gave me a message saying:

DLL <C:\Program Files\Autodesk\3ds Max 9\Plugins\ColladaMax.dle> failed to intialize. Error code: 127 - The specified procedure could not be found.

This happens every time, even in an empty scene.

This has not happened before I installed oFusion Pro, and I've had the ColladaMax plugin installed and working for some time now."

I have the gnawing suspicion that the oFusion pro installation might have corrupted the Collada plugin installation.

BTW, I had the oFusion CE installed before, and it was working fine with Collada. Also, Max crashes when it gives the error.

Any thoughts? I was going to try re-installing Collada, and if that doesn't work I could uninstall it altogether. However, I'd rather avoid that, and find a way to make oFusion Pro and Collada play nice together.

Thanks much for any help.

It has nothing to do with your new installation, there is no way that installing a product will corrupt a different plugin file

That error means that either, you have installed a different version of the collada plugin (for a previous version) or your hard drive might have some incorrect blocks or other similar problem

Verify your disk and copy the collada plugin file from the original installation media

One thing I can think of. Does ColladaMax use 3dsmax to compile shaders at all? Ofusion overwrites the CG.dll that comes with 3dsmax with a much older Ogre CG.dll for better videocard compatibility. Unfortunately the Ofusion CG.dll in the max root breaks any 3rd party plugins that use 3dsmax for compiling shaders and can spit out various errors.

I always overwrite the Ofusion CG.dll with the original 3dsmax one. It's not just Ofusion that does it, had problems with other plugins that access 3dsmax shaders.

I know collada supports its own shader format so its possible a 3dsmax collada exporter may use max's shader compiler for something.

It was, as Evak suggested, the CG.DLL, and it sounds as if that was overwritten by the oFusion Pro installation.

I was using the Collada exporter right up the time I installed oFusion Pro, which was right around when Collada stopped working. So it wasn't a stretch to guess the two were related.

Thanks for the suggestion, Evak, it was very helpful. Do you happen to know if CG.DLL would affect ShaderFX? I was also using ShaderFX after the Pro install, and while both seemed to work OK, I'm wondering if I'd get different results with the restored DLL.

Actually it was shaderFX that lead me to inquiring and finding out about the cg.dll problem. ShaderFX and max would just draw red wireframes because the shaders wouldn't compile with the older ofusion cg,dll

Maybe lioric changed how it works in the latest release. I just backed up both cg,dlls. Lioric said that theres a small chance that something might not render the same in ogre using the max dll. I have found that my shaderFX shaders have worked fine when converted to ogre so far.

I'd make a backup incase you have to swap them around but the original max cg.dll is expected by quite a few 3rd party max plugins.

ShaderFX and RTSquare GPU renderer didn't like ofusions cg.dll