[SDK] Define Multiple ReferenceTarget Classes published for MXS in single DLX plugin

#1

Is this actually possible?

I can do this for DLM and DLC plugins and it works, but almost the same for DLX makes my classes invisible to the system.

Do I miss something? any ideas?

Are there any examples in the SDK?

#2

not sure what you are talking about :face_with_raised_eyebrow:

#3

To explain in a simple way, I want to distribute all my extra modifiers, controllers, and reference targets classes with one DLX.

Now I have one dll (dlm) for extra modifiers, another dll (dlc) for controllers, etc. All my visible extra Values and Rollout controls are going with main dlx.
I want to add some controllers and reference targets to main dlx

#4

dlx’s are handled differently so you can’t use them the same as a dlm or dlc

also

MAXScript plug-ins do not generally use ClassDesc so their .cpp and .def files are simpler, because they do not export the functions GetClassDesc() and GetNumClasses(). A MAXScript plug-in DLL should have the file-extension .dlx.

#5

Many thanks! This is what I need to know (actually, what I should have known before wasting time).

#6

you could do it the other way around and add a function publishing mxs nterface to either the dlm or dlc

#7

Klvnk, thanks again.
Yes… I went this way. I picked a DLC plugin. After I published all the MXS functions and FPMixinInterfaces, it worked. But I spent a week struggling with this… It’s an extension for node and reference target notifications, which helps to monitor any reference target events and overwrite, override or suspend some of them if necessary.